How do you prepare technical source material before drafting?
What to gather, how to mark open points, and what to leave out before a claim draft or a specification draft starts.
Publisher: patentagents.ai
Short answer
Prepare the notes, specifications, code context, diagrams, and design documents that describe the technical subject, mark what is still undecided, and leave out files that do not belong. That set is what a later claim draft and specification draft can follow, with each part named and each gap still visible.
What source material should you gather?
Start with the current technical description of the subject. Add the notes that explain why a part exists, the specifications or design documents that name the parts, and the code context that shows how those parts behave. If a diagram already exists, include that file. Give each file a plain name, and keep one subject in one folder so the collection can be read as a single set.
Keep versions that disagree. When a design document and a code comment describe the same part differently, keep both and mark the disagreement on the open-point list. Dropping one of them hides the conflict until a sentence in a draft has already picked a side. Include only material you are allowed to share. If a file is restricted, leave the file out rather than rewriting the restricted detail in a note.
Remove credentials and private keys from notes and from code excerpts. Keep a code excerpt to the behavior a later section has to explain.
How do you mark open points?
An open point is a fact the source set leaves unsettled. Write it as a short line next to the material it concerns, in the note itself or at the top of the file list. A mark in the file reaches the draft. Leave the point unknown. A line that says the value is unknown is more useful than a sentence that fills the blank.
A later claim or a specification section can repeat that the point is open. A number, a material, or a mode enters the draft after the source set records it.
If two notes use different words for the same part, pick one working term and write the other beside it as an alias. A short glossary at the top of the set is enough. Use that working term in any note you add after the choice.
Mark a missing file the same way you mark an open point. If a diagram was never saved out of the design tool, write that the diagram is not in the set. A text list of the parts can sit beside that mark if you label the list as a memory aid, not as the diagram.
What do you leave out?
Leave out material that does not describe the technical work. Scheduling notes, duplicate copies of the same document, and files from a different project make the set harder to read. A larger set is not a clearer set. Also leave out notes about who should look at a document and notes about filing plans. Keep the set technical: parts, steps, constraints, and the words you already use for them.
Leave out customer names, private correspondence, and account records. If a screenshot contains both a technical screen and private text, crop it to the technical content or skip the file. Include a drawing when its file is already in the set. A text list of its parts can sit beside the image as a reading aid, and the image stays in the set.
What does a full reading of the set confirm?
Before drafting starts, read the set from start to finish. Confirm that every open point is still marked, that the working terms match across the notes, and that you can point to the file that supports each major part. This reading records the files, the terms, and the gaps the later draft will follow. If a specification or a diagram is missing, add the file or mark it missing on the same list.
When the reading is done, the set has three short lists: the files, the working terms with any aliases, and the open points. The files stay editable after that reading. patentagents.ai can start an editable claim draft and a specification draft from that set and export either draft as a Word .docx file.
What does section 112(a) ask the description to contain?
Section 112(a) of title 35 requires a specification to contain a written description of the invention and of the manner of making and using it, in terms that enable a person skilled in the art to make and use it, and to set forth the best mode contemplated by the inventor of carrying out the invention.
The source set is where those details live before the sections are written. Notes, specifications, code context, diagrams, and design documents hold the making and using steps and the preferred way of carrying out the work.
An open point is a detail the set does not yet contain. Mark it, so a later section presents that detail as unknown rather than as a completed written description or as the best mode. 37 CFR 1.75 also requires the claims to conform to the invention set forth in the rest of the specification, and the terms in the claims to find clear support in the description. Gathering the source set is how those terms and that support stay visible.
Source preparation flow
- 1Gather notes, specifications, code context, diagrams, and design documents
- 2Mark open points and pick one working term per part
- 3Leave out unrelated files and private text
- 4Read the set before drafting
Sources
Tradeoffs and limits
- A short source set is easier to read and can omit a detail a later draft needs. Marking the missing file is the remedy. Adding unlabeled files is not.
- Marking an open point keeps a guess out of the draft and leaves a blank that has to be resolved before that line can be treated as settled.
- Keeping two conflicting notes preserves the disagreement and makes the set longer. Dropping one of them makes the set shorter and hides the disagreement.
Next step
One link. Choosing it does not start a run.