Patent Task§ JOURNAL · Tutorial
Free Invention Disclosure Template with a US Patent Example
An invention disclosure gives a patent professional the technical facts needed to begin drafting: the problem, the mechanism or process, the relationships that make it work, and the evidence behind any stated result. A useful template also preserves what the inventor has not yet answered.
Download the free invention disclosure template (Markdown). No account is needed. Complete the blank worksheet locally in your editor; downloading it does not upload your invention to Patent Task. The same question set is provided below for copying into a document.
This is an internal preparation worksheet for an inventor-to-practitioner handoff, not an official USPTO form. For a US draft, 35 U.S.C. § 112(a) provides the written-description and enablement context. Completing a form does not establish that those requirements have been met. The US drafting guide shows how the collected facts feed the description, claims, abstract and drawings.
Copy this invention disclosure form
Use “unknown” where an answer is not available. Give file names, page numbers or experiment identifiers so the person drafting can find the source.
| Field | Questions to complete | Your entry |
|---|---|---|
| Working title | What technical object or process does this concern? | |
| Context | Who uses it, with what equipment, inputs and operating conditions? | |
| Existing approach | What is done now, and what observed problem remains? | |
| Proposed solution | What parts, materials or steps are involved? How do they interact? | |
| Operating sequence | What happens first, what causes each change, and what is the end state? | |
| Implementation | What connections, parameters and conditions have actually been determined? | |
| Differences and effects | What changes from the described baseline? Which results are measured and which are expected? | |
| Alternatives | Which variants can the inventor explain, and what remains the same? | |
| Figures | Which sketches exist? What should each additional view explain? | |
| Source record | Which version, notes, files and reviewers support these statements? | |
| Open questions | What is unknown, inconsistent or awaiting a technical answer? |
For a plain-text version to paste into Word or another editor:
WORKING TITLE / DISCLOSURE VERSION / DATE:
TECHNICAL CONTACT:
1. Context and technical field:
2. Existing approach and observed problem:
3. Proposed components or process steps:
4. Connections, interactions and complete operating sequence:
5. Confirmed implementation details and source locations:
6. Intended effects / measured results (label each):
7. Explained alternatives and their limits:
8. Existing figures / planned views / consistent component names:
9. Unknown facts, conflicts and person to answer:
10. Technical review: confirmed version, reviewer and date:
The downloadable version adds tables for effects, alternatives, figure references, support mapping and questions. You can expand those tables without changing the basic handoff structure.
What to write for different technical subjects
Mechanical devices: describe the physical connection, relative position, motion and load path. “A controller adjusts a clamp” leaves open what actually moves and how force reaches the workpiece.
Software and control methods: describe inputs, intermediate operations, decision conditions, outputs and exceptions. Distinguish an implemented procedure from a desired result such as “detect faults accurately.” Identify the relevant system components and data flow.
Materials and chemical processes: record the actual composition, preparation conditions and supporting observations. Keep untested ranges and proposed substitutions separate from performed experiments.
These prompts collect technical information. They are not a statement that every field is mandatory for every invention or that filling every box establishes patentability.
Worked example: a positioning clamp
This fictional example is written for teaching. It is not client material, a patentability assessment or a record of an AI generation run. We use the same mechanism in the annotated claims example.
A small assembly bench holds a cylindrical workpiece for marking. In the example's setup, flat jaws may allow the workpiece to rotate. A fixed jaw is mounted on a base, and a movable jaw is guided along a slot in the base. A screw advances the movable jaw toward the fixed jaw. Each jaw has a V-shaped locating groove; the grooves oppose each other to receive the workpiece. Replaceable contact pads are provided at those locating surfaces.
The stated purpose of the grooves is to help locate the workpiece. No test results are supplied, so the disclosure does not claim a measured stability improvement or clamping force. It also does not specify the screw engagement, groove angle, pad attachment or pad material.
Completed entries and remaining questions
| Template field | Example entry | Question to retain |
|---|---|---|
| Technical object | Positioning clamp for a cylindrical workpiece during marking | What workpiece range and mounting arrangement are intended? |
| Existing problem | Flat jaws may allow rotation in the described setup | What observation or test supports that statement? |
| Proposed solution | Fixed jaw mounted on a base; screw-driven movable jaw guided along a slot in the base | How does the screw engage and retain the moving jaw? |
| Locating surfaces | Each jaw has a V-shaped groove facing the groove on the other jaw; the locating surfaces have replaceable contact pads | What geometry and pad attachment have actually been determined? |
| Operating sequence | Place workpiece; turn screw; movable jaw advances toward fixed jaw | What defines the usable clamping condition and release sequence? |
| Effect | Locate the workpiece; allow worn pads to be replaced | Which effects have been measured? None are supplied here. |
| Figures | Proposed overall view, groove detail and guide relationship view | Which views exist, and which still need to be prepared? |
This table is useful because it does not turn unknowns into plausible specifications. Adding “90-degree grooves” or an alloy name would change the facts, even if that detail is common in other products.
Give source facts stable labels
For this example, the following labels support later review:
- D1: a positioning clamp has a base, a fixed jaw mounted on the base, and a movable jaw.
- D2: a guide slot along which the movable jaw is guided.
- D3: a screw advances the movable jaw toward the fixed jaw.
- D4: the fixed jaw and the movable jaw each have a V-shaped locating groove; the grooves oppose each other to receive a cylindrical workpiece.
- D5: replaceable contact pads are provided at those locating surfaces.
For your own invention, record real source locations as well: a drawing revision, notebook page, email answer or technical paragraph. D1–D5 are teaching labels, not evidence that any real application has adequate support. The claims example demonstrates how to map these facts to proposed limitations.
Keep effects separate from evidence
A helpful effect entry has four parts: the baseline, the changed feature, the intended technical effect and the supporting information.
| Baseline | Changed feature | Intended effect | Evidence status |
|---|---|---|---|
| Flat locating surfaces in the example | Opposing V-shaped grooves | Locate a cylindrical workpiece | Expected purpose; no comparative test supplied |
| Contact surfaces that can wear | Replaceable contact pads | Permit replacement of the pads | Stated design feature; attachment and service process unresolved |
Avoid converting an expected effect into an experimental result during polishing. If results exist, retain the test conditions and source record so the draft can describe what was actually observed.
Use the worksheet in an inventor interview
Ask the inventor to walk through the mechanism while you follow the sketch or process diagram. Note each missing connection, condition or exception. Read the sequence back using consistent component names; this often exposes a gap that a long narrative hides.
A focused first-pass request for a drafting assistant is:
Organize the supplied technical disclosure. Separate confirmed facts,
proposed details and unanswered questions. For each open question,
identify the relevant source location and what technical relationship
is unclear. Do not invent dimensions, results, references or connections.
Keep this pass to source organization and questions, before drafting claims.
When answers arrive, update the same disclosure version and record the technical confirmation. Keep a drawing reference-number register beside it so names and figure signs remain consistent.
The USPTO's written-description guidance explains why describing the claimed subject matter matters. The worksheet is a way to organize evidence for professional review; it does not replace that analysis.
Move from disclosure to a US draft
Review the US drafting workflow and example, provide the disclosure or upload the material, and inspect the proposed drafting plan. Confirm the plan and the US jurisdiction before continuing. After generation, compare the claims and description with the source version, and keep unresolved facts visible.
Use the US patent drafting guide for the document handoff. If you are comparing software first, run the tool evaluation exercise with synthetic input before deciding whether a service fits your workflow.
Is an invention disclosure the same as a patent specification?
No. The disclosure is an input and handoff record. A patent specification develops that material into an application document with a deliberate technical account and claims. Copying the worksheet headings into a file does not complete that work.
Can I complete this template in Word?
Yes. Copy the question set and tables into Word, or open the Markdown download in a text editor. The download is a plain Markdown worksheet, not a promised DOCX form.
Must every invention have test data?
The needed support depends on the subject matter. Record available evidence accurately and distinguish it from predictions. Do not create measurements simply to fill a template field.
Can I use confidential client material in a tool trial?
Check the client's authorization, your organization's policy and the provider's processing, retention and deletion terms. The privacy policy and support contact are available for product questions. Use a synthetic disclosure when you only need to evaluate the workflow.