The three requirements of § 112
35 U.S.C. § 112 imposes three key requirements on the patent specification and claims. First, the specification must contain a written description of the invention sufficient to show the inventor was in possession of the claimed subject matter at filing. Second, the specification must enable a person of ordinary skill in the art (POSITA) to make and use the invention without undue experimentation. Third, the claims must be definite — they must inform with reasonable certainty those skilled in the art about the scope of the invention. Each requirement can independently invalidate patent claims if not satisfied. These requirements serve different functions: written description confirms the applicant owned the invention at filing; enablement ensures the public gets the benefit of the disclosure; and definiteness ensures competitors can know where the patent's boundaries are.
Written description
The written description requirement tests whether the specification shows that the inventor possessed the full scope of the claimed invention when the application was filed. A POSITA reading the specification at filing should understand that the inventor invented what is being claimed, not just the examples described. Written description failures arise most often when: (1) claims are amended during prosecution to cover subject matter not described in the original specification (the amendment may be rejected as 'new matter' under § 132); (2) continuation applications claim subject matter that was not described in the parent application; and (3) broad functional genus claims cover species the specification does not adequately describe. Ariad Pharmaceuticals v. Eli Lilly (Fed. Cir. en banc 2010) confirmed that written description is a separate requirement from enablement — a specification must both describe and enable, and failing one is independently fatal to the claims even if the other is satisfied.
Enablement and the undue experimentation standard
The enablement requirement asks: can a POSITA make and use the claimed invention based on the specification's disclosure without undue experimentation? 'Undue experimentation' is the threshold — some experimentation is expected; too much is undue. The Wands factors guide the analysis: quantity of experimentation required; amount of guidance in the disclosure; presence of working examples; nature of the invention; state of the prior art; level of ordinary skill; and whether the technology is predictable. Enablement becomes challenging for broad functional genus claims in unpredictable arts. In predictable arts (mechanical inventions), a single working embodiment typically enables a broad claim. In unpredictable arts (biotechnology, pharmaceuticals), POSITA cannot predict whether untested species in a genus will work — so the claim scope must be enabled by adequate working examples proportionate to the breadth claimed.
Amgen v. Sanofi (2023) — the modern enablement limit
Amgen Inc. v. Sanofi (S.Ct. 2023) is the Supreme Court's most important recent statement on enablement. The patents covered a broad genus of antibodies defined by function — any antibody that binds to PCSK9 at a specific amino acid sequence and blocks PCSK9 from binding the LDL receptor. The claimed genus potentially encompassed millions of antibodies. Amgen's specification described 26 specific antibodies in detail. The Court held unanimously that the claims were not enabled: to identify additional antibodies in the claimed genus, scientists would have to conduct extensive trial-and-error screening — 'the court calls that 'undue experimentation.'' The principle established: the specification must enable the full scope of the claimed invention; it is not enough to enable only a 'starting point' from which POSITA must explore. Amgen has immediate implications for broad antibody claims, AI-generated compositions, and other functional genus claims in biotechnology.
Definiteness: the Nautilus standard
Nautilus, Inc. v. Biosig Instruments, Inc. (S.Ct. 2014) replaced the Federal Circuit's 'not insolubly ambiguous' standard with a higher definiteness requirement: a claim must 'inform, with reasonable certainty, those skilled in the art about the scope of the invention.' The Court rejected claims that merely exist in a state of 'definiteness' while leaving skilled artisans uncertain about what they cover. Common definiteness failures: (1) relative terms without objective anchors — 'substantially' or 'about' are not indefinite per se, but if the specification provides no way to determine the relevant boundary, the claims may be indefinite; (2) functional claiming without structural guidance — claiming a 'fast' processor without defining what qualifies as 'fast'; (3) terms whose antecedent basis is unclear — using 'the device' when no antecedent 'a device' was previously recited; (4) inconsistent use of the same term in different claims to mean different things.
Best mode requirement
35 U.S.C. § 112(a) also contains a 'best mode' requirement: the specification must set forth the best mode contemplated by the inventor for carrying out the claimed invention at the time of filing. However, the America Invents Act significantly changed the consequences of best mode violations: a failure to disclose the best mode can no longer render claims invalid in litigation (AIA § 15 removed invalidity as a remedy). Best mode violations are still grounds for rejecting applications during prosecution, but issued patents cannot be invalidated for best mode violations for applications filed after September 16, 2012. This change was controversial — critics argued it removed an important disclosure incentive; supporters noted it was difficult to prove and led to expensive discovery about inventors' subjective knowledge.
Frequently Asked Questions
What does the written description requirement require?
The written description requirement under 35 U.S.C. § 112(a) requires that the patent specification describe the claimed invention in sufficient detail to show that the inventor was in possession of the full scope of the claimed invention at the time of filing. The test is: would a person of ordinary skill in the art reading the specification at the time of filing understand that the inventors had possession of the claimed subject matter? Written description most often arises in two contexts: (1) when an applicant amends claims during prosecution to add or broaden subject matter not adequately described in the original specification (new matter); and (2) when an issued patent's claims are challenged as covering subject matter the specification does not adequately describe — which can invalidate those claims. The written description requirement is separate from enablement — a specification can describe something without enabling it, and can enable something without adequately describing it (though the distinction is often subtle in practice).
What is the enablement requirement under § 112?
The enablement requirement under 35 U.S.C. § 112(a) requires that the specification describe the invention in enough detail to enable a person of ordinary skill in the art (POSITA) to make and use the claimed invention without undue experimentation. The key standard is 'undue experimentation' — the specification need not describe every detail (POSITA's knowledge fills in routine gaps), but it cannot require undue experimentation to practice the full claimed scope. The Wands factors guide the undue experimentation analysis: the quantity of experimentation required; the amount of guidance presented in the disclosure; the presence of working examples; the nature of the invention; the state of the prior art; the level of skill in the art; and the predictability of the technology. In Amgen Inc. v. Sanofi (S.Ct. 2023), the Supreme Court held that a broad functional genus claim covering all antibodies that bind a specific protein and inhibit its function was not enabled because the specification only enabled a narrow subset — requiring POSITA to screen vast numbers of antibodies to find ones that work was undue experimentation.
What is the definiteness requirement, and what is the Nautilus standard?
The definiteness requirement under 35 U.S.C. § 112(b) requires that patent claims 'particularly point out and distinctly claim' the subject matter the applicant regards as the invention. The standard for definiteness was clarified in Nautilus, Inc. v. Biosig Instruments, Inc. (S.Ct. 2014). Pre-Nautilus, the Federal Circuit applied a 'not insolubly ambiguous' standard — a claim was definite unless its meaning was completely unclear. Post-Nautilus, the standard is higher: a claim is indefinite if it fails to 'inform, with reasonable certainty, those skilled in the art about the scope of the invention.' This is a POSITA-based standard: would a skilled artisan reading the claim in light of the specification and prosecution history know with reasonable certainty what falls within the claim's scope? Common indefiniteness issues: relative terms with no objective anchor ('about,' 'approximately,' 'substantially,' 'high' without defining the reference point); functional claim language that doesn't tell a skilled artisan what structure is required; and claims using inconsistent terminology.
What are means-plus-function claims and why are they risky?
Means-plus-function (MPF) claiming under 35 U.S.C. § 112(f) allows a claim element to be written as a 'means for [performing a function]' rather than specifying the physical structure. The scope of MPF claims is limited to the structure disclosed in the specification that performs the function, plus structural equivalents. The risk: if the specification does not disclose adequate corresponding structure for the 'means for' element, the claim is indefinite. Williamson v. Citrix Online LLC (Fed. Cir. en banc 2015) changed the test for when § 112(f) applies — it no longer requires use of the word 'means.' If a claim element uses 'nonce words' that do not connote structure (e.g., 'mechanism for,' 'module for,' 'system for,' 'unit for') with only functional language, § 112(f) may apply. The practical impact: software patent claims using 'module,' 'engine,' 'component,' or 'system' with purely functional language may be construed as MPF claims, limited to the structures described in the specification, and potentially indefinite if the specification discloses only software without algorithmic detail.
How does Amgen v. Sanofi affect broad patent claims?
Amgen Inc. v. Sanofi (U.S. Supreme Court 2023) significantly tightened the enablement requirement for broad functional genus claims. At issue were patents claiming all antibodies that bind to a specific amino acid sequence of a protein (PCSK9) and block it from binding its receptor — a broad functional genus covering potentially millions of antibodies. The specification described only a small number of specific antibodies. The Court unanimously held the claims were not enabled: to find additional antibodies that meet the functional definition, POSITA would have to make and test vast numbers of candidates — 'a significant portion of the full scope of the claims' — which is undue experimentation. The Amgen decision affirms that the scope of enablement must be commensurate with the scope of the claims. Broad functional genus claims in biotechnology, pharmaceuticals, and other unpredictable arts now face heightened scrutiny. Patent applicants must provide sufficient working examples to enable the full claimed scope, not just a narrow subset.