I asked this question:
Patent Enablement - how do you balance retention of secrets and teaching make and use
In the comments the question came up:
What is the best (or at least very very good) way for a technical expert to document their work and set up for the patent attorney to have the best success?
(Why to not close it before reading)
While opinions can be had, there are some realities that make objective answers both reasonable and important.
- Any patent attorney can tell you about "the ugly", the staging that makes it hard, has critical gaps, or such. A clean and organized of those is the evil-twin of a good way to set up for success.
- USPTO tries to provide resources to make things work better for their reviewing personnel, so something that improved the quality of content a reviewer needs to make an evaluation, all else being equal, would also be good.
- The successful "patent your idea" companies have to have some forms and basic processes that set up their work for ease of productivity. This means that at least for the application process, they have an idea of what makes things work better or worse.
Can you provide a rubric, a checklist, or guidelines that either help clarify what a superb "tee-up" of a patent applicationfor a patent attorney should have?
If not that, what few things if they are done that way make things very difficult and unpleasant for the attorney? I'm not looking at invalidating the patent by disclosing it improperly or such, but in terms of documentation and staging what things make the job less easy, efficient, or effective.
This should include things that make the patents substantially stronger and more defensible as "good" things and, and things that without malicious intent can substantially weaken the quality or viability of an otherwise plausibly novel, useful, and non-obvious patent idea as "bad things".