Written Description Requirement: 7 Essential Rules for Patents

You can teach the world how to build your invention and still lose the claim. That is the trap of the written description requirement under 35 U.S.C. § 112(a): the specification must show that, on your filing date, you actually possessed what you now claim — not just that a skilled reader could make it. Broad claims fail here more than almost anywhere else in prosecution and litigation. This guide breaks down the possession test, why it is separate from enablement, where it most often goes wrong, and seven practical rules for drafting claims that hold up.

What the Written Description Requirement Actually Means

The first paragraph of 35 U.S.C. § 112 demands that a patent specification contain “a written description of the invention.” The written description requirement asks a simple-sounding question: does the disclosure show that the inventor was in possession of the claimed subject matter as of the filing date? If the specification describes one narrow thing but the claims sweep in a much broader class, the claims can be invalid even though the patent otherwise works.

The Federal Circuit settled the doctrine en banc in Ariad Pharmaceuticals, Inc. v. Eli Lilly & Co., 598 F.3d 1336 (Fed. Cir. 2010), confirming that § 112 contains a written description requirement that is separate and distinct from enablement. The court described the test as whether the disclosure reasonably conveys to a person of ordinary skill that the inventor had possession of the claimed invention. The full statutory text is on Cornell’s Legal Information Institute.

Written Description vs. Enablement: They Are Not the Same

Applicants routinely conflate the two prongs of § 112(a), and it is a costly mistake. Enablement asks whether the disclosure teaches a skilled person how to make and use the invention without undue experimentation. Written description asks something prior: did you show you actually had the invention in hand?

The Supreme Court’s 2023 decision in Amgen v. Sanofi tightened enablement for broad functional genus claims, but that case was about enablement, not written description. The two often fail together — a claim that reaches far beyond what was disclosed usually flunks both — yet they are independent grounds. You can enable a broad class (teach how to make many variants) and still fail written description if the specification never showed you possessed that whole class. Because the requirements diverge, treat them as separate checkboxes when you draft.

• Enablement: can a skilled person make and use it from your disclosure?
• Written description: does the disclosure show you possessed the full claimed scope?
• A claim can satisfy one and fail the other; both are required.

The Possession Test: Showing You Had the Invention

Possession is judged from the four corners of the specification through the eyes of a person of ordinary skill. You do not need to have actually built or reduced the invention to practice, but the description must do more than state a goal or a wish. Claiming a result — “a compound that lowers cholesterol” — without describing the structures that achieve it is the classic written description failure the courts police.

For a genus, possession usually means disclosing either a representative number of species that fall within the class or structural features common to the members of the class so a skilled reader can visualize what is and is not covered. For biotech and chemistry, that often means actual sequences, structures, or characterized examples — not a functional label alone. The MPEP § 2163 collects the USPTO’s examination guidance on exactly this point.

Where the Written Description Requirement Fails Most Often

• Broad genus claims backed by one or two species and no shared structural features.
• Purely functional or result-oriented claims that recite what the invention does, not what it is.
• New matter added by amendment: importing a limitation the original filing never described.
• Antibody and biotech claims defined only by the antigen they bind, without disclosing the antibodies themselves.
• Continuation and continuation-in-part claims that reach back for an early priority date the parent never supported.
• Numerical ranges or subranges claimed later but absent from the original disclosure.

Most of these share a root cause: the claims grew during prosecution while the specification stood still. If you broaden or pivot the claims, re-read the disclosure and ask whether it still shows possession of the new scope.

How the Test Plays Out in Prosecution and Litigation

During prosecution, an examiner raises the written description requirement as a § 112(a) rejection, most often after you amend or add claims. The examiner’s burden is to explain why a skilled reader would not see possession of the claimed scope in the original disclosure; your response is to point to specific passages, examples, or drawings that provide support — not to argue that the invention would have been obvious to build. If the support is not there, no attorney argument can manufacture it, and adding it later is new matter.

In litigation the stakes rise. Written description is a question of fact, and an accused infringer will use it to invalidate the broadest, most valuable claims — the ones drafted to capture competitors. Because invalidity must be proven by clear and convincing evidence, the fight usually turns on expert testimony about what the specification conveyed on the filing date. This is also why a challenger’s prior-art and file-history analysis so often opens with § 112: a claim that overreaches its disclosure is frequently the softest target in the patent.

The takeaway for portfolio owners is to audit your broadest claims the way an opponent would. If the disclosure only ever showed a handful of embodiments, a claim that reaches an entire class is living on borrowed time.

Seven Rules to Satisfy the Requirement When Drafting

1. Describe the invention by structure, not just function or desired result.
2. For any genus, disclose a representative set of species and the features they share.
3. Provide working or prophetic examples across the breadth you intend to claim.
4. Support every range, ratio and subrange you might later want to claim.
5. For computer-implemented inventions, disclose the algorithm or steps, not just “a processor configured to.”
6. Never add matter by amendment that the original filing did not describe.
7. Before broadening a claim, confirm the specification already shows possession of the wider scope.

These habits also strengthen your enablement and definiteness positions. For the drafting mechanics behind them, see our guides to patent specification writing and patent claims drafting, and how the written description requirement pairs with the enablement requirement.

Written Description and Priority Claims

The requirement does more than kill claims outright — it controls your priority date. To claim the benefit of an earlier application (a provisional, a parent, or a foreign priority filing), that earlier document must itself provide written description support for the claim. If it does not, the claim only gets the later filing date, and any intervening prior art suddenly counts against it.

This is why continuation-in-part strategy is delicate: the new matter you add gets only the CIP’s date, and older claims keep the parent’s date only to the extent the parent described them. Map each claim to the disclosure that supports it before you rely on a priority chain. Our best mode requirement guide rounds out the § 112 picture.

How PerspireIP Can Help

PerspireIP’s patent team drafts specifications built to survive written description and enablement challenges, and we pressure-test issued claims and priority chains before they reach a courtroom. Whether you are preparing a filing or defending claim scope, contact us to make sure your disclosure actually shows what your claims say you own.

Frequently Asked Questions