The invention disclosure is the single document from which your patent application is forged. An attorney cannot claim what you never disclosed, enable what you never explained, or distinguish prior art you never mentioned. A thin disclosure produces a thin patent—one a competitor designs around over a long lunch—while a thorough one lets counsel fence off a market for the life of the grant. This checklist turns that principle into concrete tasks. Work through it before your intake meeting; complete it in consultation with counsel where you can; and mark the finished document confidential (it is an attorney-client privileged communication when prepared for your lawyer).

For the underlying doctrine, pair this checklist with our deep guides on how to prepare an invention disclosure for your patent attorney and general information concerning patents.

Phase 1 — Frame the administrative basics

  • Give the invention a working title and a disclosure date.
  • List every contributor by name, with department/affiliation, contact information, residence, and citizenship (citizenship and residence matter for some foreign filings).
  • Identify the related project or program and any funding source (government funding can trigger Bayh-Dole obligations and march-in rights).
  • Mark the document "CONFIDENTIAL — ATTORNEY-CLIENT PRIVILEGED COMMUNICATION" and limit who sees it.
  • Note any deadline pressure (an imminent paper, demo, sale, or product launch) at the top, in bold, so counsel can triage timing first.

Why this matters. People leave companies; memories fade; the notebook gets boxed up. Your disclosure is a time capsule a litigator you have never met may open in 2034. Capturing who-did-what and how-to-reach-them now preserves access to contributors and their records when it counts.

Phase 2 — State the technical problem (concretely)

  • Write the problem the invention solves before describing the solution.
  • Quantify it. "Charging is too slow" is useless; "DC fast charging needs 30–60 minutes for an 80% charge because current above ~2C generates heat that degrades cell chemistry" is claimable.
  • Name the root cause, not just the symptom.
  • Note whether the problem was long recognized and stubbornly unsolved, and whether others tried and failed.

Why this matters. A crisp problem statement does real legal work on non-obviousness under 35 U.S.C. § 103. Evidence that a problem was a long-felt but unmet need, or that others failed, is a recognized secondary consideration of non-obviousness under the Graham v. John Deere Co., 383 U.S. 1 (1966), framework—and KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007), made that objective evidence more valuable, not less.

Phase 3 — Describe the mechanism, not just the result

  • For each significant aspect, answer both how it works and why it works better than the alternatives.
  • Carry enough technical detail that a skilled person could build it: if it's an algorithm, give the steps; if a structure, the parts and arrangement; if a process, the ordered steps.
  • Connect each technical choice to the benefit it produces in an explicit cause-and-effect chain.
  • List the core components or steps, what each one does, and how each relates to the others.
  • Separate essential features (the floor of claim scope) from optional ones.

Trap to avoid. Discuss limits, drawbacks, and failed avenues orally with counsel rather than memorializing colorful failure language ("this completely fails above 60°C") in writing—such lines can be quoted back at you in litigation, stripped of context. Tell your lawyer everything; let your lawyer decide what enters the written record.

Phase 4 — Document the alternatives you did NOT build

  • For each aspect, name the broadest category (the "genus") that captures your approach.
  • List specific examples within it (the "species"), flag your preferred one, and explain the tradeoffs across the range.
  • Capture component alternatives, process alternatives, configuration alternatives, and parameter ranges (with preferred values).
  • For each genus, give the bridges between species—design rules, selection criteria, worked examples—so the broad claim is supported, not merely aspirational.

Why this matters. You do not need to have built the alternatives. A sufficiently detailed, enabling description is a "constructive" reduction to practice; an invention can be "ready for patenting" by drawings and descriptions alone (Pfaff v. Wells Electronics, Inc., 525 U.S. 55 (1998)). But beware the written-description and enablement limits of § 112: a single disclosed species supports a broad genus claim only with enough guidance to reach the others without undue experimentation (Amgen Inc. v. Sanofi, 598 U.S. 594 (2023)). This same scope map feeds a later freedom-to-operate analysis.

Phase 5 — Identify and disclose prior art

  • List every reference you know of—patents, published applications, journal articles, conference papers, theses, products on sale, technical standards, public demos, and posted videos—with enough detail (numbers, authors, titles, links) for counsel to find it.
  • For each, explain how the invention differs.
  • Flag areas where prior art probably exists but you have not searched.
  • Include your own earlier work—your publications, talks, product launches, and your employer's prior sales.
  • Ask yourself: "What did I read, see, or buy that pointed me toward this idea?" Then write all of it down.
  • Do NOT draw conclusions about patentability—list what you know and let counsel decide what to cite in an Information Disclosure Statement.

Why this matters. The duty of candor under 37 C.F.R. § 1.56 obliges everyone substantively involved to disclose information material to patentability. A deceptive omission of material prior art can render the entire patent unenforceable for inequitable conduct under Therasense, Inc. v. Becton, Dickinson & Co., 649 F.3d 1276 (Fed. Cir. 2011) (en banc). See our companion checklist on maintaining the duty of candor to avoid inequitable conduct.

Phase 6 — Pin down conception, reduction to practice, and records

  • Record the conception date (the "aha" of a definite and permanent idea of the complete invention) with the notebook page or file that anchors it.
  • Record development milestones: first working example, first successful test, first disclosure to another (and to whom).
  • Confirm lab-notebook hygiene: entries signed and dated, witnessed near the time of the work by a qualified non-inventor, failures recorded alongside successes.
  • Cross-reference related notebooks and explain gaps in the dates.
  • Keep legal characterizations OUT of the notebook—no editorializing about patentability, no disparaging competitors, no transcribing conversations with counsel.

Why this matters. Uncorroborated inventor testimony about conception is treated as unreliable, and an unsigned, unwitnessed notebook gets no more weight than that testimony. A notebook signed and witnessed by a non-inventor who watched the work can be powerful corroboration. Good notebook discipline flows naturally from a trade secret protection program.

Phase 7 — Capture contributor roles for inventorship

  • Document, in detail, what each contributor did, cross-referenced to dates and records.
  • Identify everyone who created, discovered, developed, tested, or analyzed any aspect—inside or outside the organization.
  • Do NOT pronounce on inventorship; give counsel the raw facts to make the legal call.
  • Designate one inventor to coordinate and serve as counsel's primary contact.
  • Have all potential inventors review the disclosure for accuracy before submission.
  • Flag any meaningful role an AI tool played in conceiving a feature—do not paper over it.

Why this matters. Ownership flows from inventorship. The test comes from Pannu v. Iolab Corp., 155 F.3d 1344 (Fed. Cir. 1998): a joint inventor must contribute significantly to conception, not insignificantly in quality, and do more than explain well-known concepts. Funders, supervisors, and technicians who merely carry out instructions are usually not inventors. An innocent error can be corrected under 35 U.S.C. § 256, but a deceptive one can invalidate the patent. Inventorship sets who invented; the employee invention assignment agreement sets who owns.

Phase 8 — Catalog timing events and public disclosures

  • List every public disclosure: publication, conference talk, posted video, demonstration, and beta deployment, with dates and audiences.
  • List every commercial event: offers for sale, sales, quotes sent to customers, and beta agreements—with dates and whether under NDA.
  • If a potentially barring event already happened, calendar the one-year U.S. grace-period deadline immediately and make sure any filing beats it.
  • If you may seek protection abroad, plan to file before any public disclosure—most of the world demands absolute novelty and offers no grace period.

Why this matters. Under 35 U.S.C. § 102, prior art includes anything "patented, described in a printed publication, or in public use, on sale, or otherwise available to the public" before the effective filing date, anywhere in the world. The U.S. one-year grace period (§ 102(b)(1)) is largely an American indulgence. And the on-sale bar is broad: even a secret, confidential commercial sale can trigger it (Helsinn Healthcare S.A. v. Teva Pharmaceuticals USA, Inc., 586 U.S. 123 (2019)). What looks like a routine business deal to you may look like a statutory bar to a litigator.

Phase 9 — Address best mode and § 112 support

  • Identify the embodiment you currently consider best, and explain why—do not withhold your "secret sauce."
  • Confirm that any range or genus you describe is itself described and enabled across its whole scope, not just at the one value you tested.
  • Attach labeled drawings, flowcharts, schematics, or photographs.

Why this matters. Section 112(a) requires disclosure of the best mode contemplated. The AIA eliminated best-mode failure as an invalidity defense (35 U.S.C. § 282(b)(3)(A)), but concealment can still surface in an inequitable-conduct narrative and can sink the related enablement and written-description tests. Enablement is measured against the full scope of the claims (Amgen v. Sanofi); written description asks whether you possessed the full claimed invention (Ariad Pharmaceuticals, Inc. v. Eli Lilly & Co., 598 F.3d 1336 (Fed. Cir. 2010) (en banc)).

Phase 10 — Tailor to the type of invention

  • Software/algorithm: describe the system from the computer's perspective—architecture, modules, data structures, the algorithm as ordered steps, flowcharts or pseudocode—and frame it as a technical solution to a technical problem; flag any open-source components. (See patent subject matter eligibility (Alice) checklist.)
  • Mechanical/hardware: provide multiple drawing views, preferred materials, critical dimensions, tolerances, and any novel manufacturing method.
  • Chemical/pharmaceutical: give precise structures, synthesis routes, experimental data, and which structural modifications preserve activity.
  • Business method: identify the specific technical systems that implement the method and why it is more than an abstract idea on generic hardware.

Phase 11 — Final review and submission

  • Confirm the disclosure describes the problem, the mechanism, the alternatives, the advantages, the prior art, the key dates, and the contributors.
  • Verify every potential inventor has reviewed and signed off.
  • Re-confirm the confidentiality marking and that the invention has not been publicly disclosed without counsel's approval.
  • Submit as soon as the invention is developed enough to describe—do not wait for an imminent launch.

Common mistakes

  • Describing only what you built (no alternatives) → narrow, sidesteppable patent.
  • Omitting the problem → starves the non-obviousness argument and claim drafting.
  • Marketing language instead of technical language ("revolutionary breakthrough") → nothing a lawyer can claim.
  • Assuming the attorney already knows your field → define your terms.
  • Hiding prior art → risks unenforceability under Therasense.
  • Waiting too long → a publication, sale, or use ripens into a § 102 bar.
  • Getting inventorship wrong → clouds ownership or, if deceptive, invalidates under Pannu.

Primary authority

  • 35 U.S.C. § 101 (eligibility; inventorship); § 102 (novelty; on-sale/public-use bars; grace period); § 103 (non-obviousness); § 112 (written description, enablement, best mode); §§ 116, 256 (joint inventors; correction); § 282(b)(3)(A) (best mode not an invalidity defense).
  • 37 C.F.R. § 1.56 (duty of candor); § 1.63(c) (inventor's oath).
  • Pfaff v. Wells Electronics, Inc., 525 U.S. 55 (1998); Helsinn v. Teva, 586 U.S. 123 (2019); Pannu v. Iolab Corp., 155 F.3d 1344 (Fed. Cir. 1998); Therasense v. Becton, Dickinson, 649 F.3d 1276 (Fed. Cir. 2011) (en banc); Amgen v. Sanofi, 598 U.S. 594 (2023); Graham v. John Deere Co., 383 U.S. 1 (1966); KSR v. Teleflex, 550 U.S. 398 (2007).
  • USPTO MPEP §§ 2138.04 (conception), 2133.03 (on-sale/public-use), 2000.01 et seq. (duty of disclosure), 2163–2164 (written description and enablement). USPTO inventor resources: https://www.uspto.gov/patents/basics

This checklist is general information, not legal advice. Patent law evolves; confirm current law and consult a qualified patent attorney.

Related resources