Skip to content
PatentBrief

Patent Drafting

Claim Indefiniteness

A claim that fails to inform a POSITA of its scope with reasonable certainty is invalid under § 112(b). Nautilus raised the bar above the old "insolubly ambiguous" test — and many issued claims haven't cleared it.

FAQ

What is the definiteness requirement for patent claims under § 112(b)?

35 U.S.C. § 112(b) requires that a patent specification conclude with 'one or more claims particularly pointing out and distinctly claiming the subject matter which the inventor or a joint inventor regards as the invention': PURPOSE: the definiteness requirement serves two functions: (a) public notice — competitors and the public must be able to determine what is and is not covered by the patent without guessing; (b) claim scope limitation — prevents inventors from claiming beyond what they disclosed; NAUTILUS INC. v. BIOSIG INSTRUMENTS (S.Ct. 2014): rejected the Federal Circuit's prior 'insolubly ambiguous' standard (which was very permissive of vague claims); replaced with: a claim is definite if it 'inform[s] those skilled in the art about the scope of the invention with reasonable certainty'; WHAT 'REASONABLE CERTAINTY' MEANS: read in conjunction with the specification and prosecution history; reasonable certainty allows for some ambiguity (patent claims can't be perfectly precise); but claims that leave reasonable persons skilled in the art to guess as to scope are invalid; INVALIDITY CONSEQUENCE: an indefinite claim is INVALID under § 112(b); unlike an obvious claim (which could be narrowed through amendments in prosecution), an issued indefinite claim cannot be saved by post-issuance amendment without filing a reissue application; BURDEN OF PROOF: in litigation, a challenger must prove indefiniteness by clear and convincing evidence (the same standard as other invalidity challenges); PROSECUTION: the USPTO examiner raises § 112(b) rejections during examination; applicant can overcome by clarifying claim language or pointing to specification disclosure that provides meaning.

What are the most common sources of claim indefiniteness?

Courts have found claims indefinite based on several recurring patterns: 1. ANTECEDENT BASIS FAILURES: using 'the widget' in a claim body without first introducing 'a widget'; creates ambiguity about what element is being referenced; example: 'a method comprising providing a bolt; securing the widget to the surface' — 'the widget' has no antecedent; fix: introduce every element with 'a' before referring to 'the'; 2. PURELY SUBJECTIVE TERMS: terms like 'smooth,' 'relatively small,' 'substantially similar,' or 'aesthetically pleasing' without objective benchmarks in the specification; Datamize v. Plumtree Software (Fed. Cir. 2005): 'aesthetically pleasing' interface = indefinite (purely subjective, no objective anchor); BUT: 'substantially' is often definite if the specification provides context defining the range of deviation; 3. TERMS WITHOUT SPECIFICATION ANCHORS: claim terms that have no definition, embodiment, or example in the specification that provides meaning to a POSITA; 4. FUNCTIONAL CLAIMING WITHOUT STRUCTURAL ANCHOR: 'a means for achieving [result]' without disclosed structure in the specification may be indefinite under § 112(f) if no corresponding structure is disclosed; 5. NUMERICAL RANGES WITH AMBIGUOUS ENDPOINTS: ranges using 'between' without specifying inclusive/exclusive; overlapping ranges in related claims; 6. REFERENCING DIFFERENT CLAIM CATEGORIES: a claim referencing elements of another claim in a different category (method vs. apparatus) can create indefiniteness; 7. COMBINING APPARATUS AND METHOD LIMITATIONS: a single claim that recites both a structural configuration ('a device having X') AND a method step ('the device performs Y') may be indefinite as a hybrid claim; IPXL Holdings v. Amazon (Fed. Cir. 2005): mixing apparatus and method limitations in one claim = indefinite.

How is 'substantially' and similar hedging language treated for definiteness?

'Substantially,' 'approximately,' 'essentially,' and similar hedging terms in claims are frequently challenged as indefinite — but courts often uphold them: GENERAL RULE: hedging terms are not automatically indefinite; they are definite if the specification or prosecution history provides objective criteria for determining the bounds of the range; SUBSTANTIALLY: probably the most common hedging term; examples of DEFINITE 'substantially': 'substantially pure' — the specification provides a test for purity and states that 99.5% purity is 'substantially pure'; 'substantially coplanar' — a POSITA understands the term in context as within normal manufacturing tolerances; SUBSTANTIALLY as INDEFINITE: where the specification provides no guidance and a POSITA cannot determine from the claim language what degree of deviation from exact is covered; CASE EXAMPLES: Interval Licensing v. AOL (Fed. Cir. 2014): 'unobtrusive manner' was indefinite — specification provided no objective anchor for what constitutes 'unobtrusive'; Dow Chemical v. Nova Chemicals (Fed. Cir. 2015): 'substantial' in the context of slope measurements was definite with specification support; POST-NAUTILUS ANALYSIS: after Nautilus, courts apply the 'reasonable certainty' standard to 'substantially' terms; the question is whether a POSITA reading the entire specification would understand the scope with reasonable certainty; PROSECUTION STRATEGY: if using 'substantially' in a claim, add language to the specification establishing objective criteria (e.g., 'substantially' as used herein means within X% of); this provides an anchor for definiteness analysis and narrows the scope to a known range.

How does the USPTO address indefiniteness during patent prosecution?

The USPTO examines claims for definiteness under § 112(b) using a Broadest Reasonable Interpretation standard: USPTO EXAMINATION STANDARD: examiners use BRI (Broadest Reasonable Interpretation) rather than the Nautilus 'reasonable certainty' standard; BRI asks: what is the broadest reasonable interpretation of this claim consistent with the specification?; BRI ≠ NAUTILUS: the BRI standard is less strict than Nautilus; a claim that passes BRI during prosecution may still be found indefinite in district court under Nautilus; this can result in issued claims later found invalid in litigation; HOW EXAMINERS RAISE § 112(b) REJECTIONS: identification of the specific term or element the examiner finds unclear; explanation of why the specification does not provide sufficient guidance; request that the applicant clarify or define the term; RESPONDING TO § 112(b) REJECTIONS: (a) ARGUMENT: explain why the specification provides sufficient guidance; cite relevant portions of the specification and drawings; cite POSITA's understanding of the term in the art; (b) AMENDMENT: add a definition or objective criterion for the ambiguous term; add claim language that anchors the term (e.g., replace 'substantially smooth' with 'having a surface roughness Ra of less than 2.0 μm'); (c) LIMITATION: replace the subjective term with an objective measurement or a structural limitation; PTAB REVIEW: PTAB applies the same BRI standard as examiners in IPR and PGR proceedings; indefiniteness can be raised in PGR (Post-Grant Review, within 9 months of grant on any ground); IPR only allows § 102/103 invalidity, NOT § 112 indefiniteness; PGR (available only for patents with effective filing date after March 16, 2013) allows § 112 challenges.

What are effective strategies for challenging or defending against indefiniteness in litigation?

Indefiniteness is a powerful invalidity defense because it goes to the heart of claim scope and prevents enforcement: CHALLENGING INDEFINITENESS (DEFENDANT): STEP 1 — IDENTIFY THE AMBIGUOUS TERM: scan all asserted claims for subjective terms, antecedent basis failures, means-plus-function elements with no disclosed structure, and reliance on terms undefined in the specification; STEP 2 — CLAIM CONSTRUCTION BRIDGE: file a claim construction brief arguing the term is not amenable to a definite construction; courts often decide indefiniteness as part of Markman; STEP 3 — EXPERT TESTIMONY: submit expert declaration from a POSITA explaining why the claim scope cannot be determined with reasonable certainty; courts give significant weight to expert testimony on what a POSITA understands; STEP 4 — PROSECUTION HISTORY: review prosecution history for examiner-applicant exchanges that reveal inconsistent claim scope; applicant representations that the term means 'X' in one context but now the patentee argues it means 'Y' for infringement; STANDARD: clear and convincing evidence (the challenger must meet a high burden); DEFENDING AGAINST INDEFINITENESS (PATENTEE): identify specification language that gives objective meaning to the challenged term; cite expert testimony that a POSITA would understand the term in the art; cite the prosecution history for consistent usage; rely on the patent's claim construction for the same term in prior infringement arguments; argue the Nautilus standard requires 'reasonable certainty' not 'perfect precision' — some latitude for industry-standard terms; PARALLEL PTAB (PGR): if within 9 months of grant, a petitioner can challenge § 112(b) indefiniteness in a PGR petition; PGR must be filed within 9 months of issuance; unlike IPR, PGR allows all § 112 challenges; PGR institution rate for § 112 challenges has been lower than IPR institution rates for § 102/103.

Related Guides

Claim ScopeClaim LanguageClaim ConstructionMeans-Plus-FunctionWritten DescriptionPost-Grant Review