What does indefiniteness mean in patent law?
Indefiniteness is a statutory requirement grounded in 35 U.S.C. § 112(b), which demands that a patent specification conclude with one or more claims particularly pointing out and distinctly claiming the subject matter the inventor regards as the invention. A claim that fails to meet this requirement can be rejected during examination and invalidated in litigation.
The governing standard
In Nautilus, Inc. v. Biosig Instruments, Inc., 572 U.S. 898 (2014), the Supreme Court established the governing test: a claim is indefinite unless it informs those skilled in the art about the scope of the invention with reasonable certainty, read in light of the specification and prosecution history. The standard acknowledges that absolute precision in claim language is unattainable, but it holds that the definiteness requirement mandates clarity sufficient to give the public notice of what the patent covers. Nautilus replaced the Federal Circuit's prior "insolubly ambiguous" standard, which the Court found set too low a bar for claim clarity.
Who is "one skilled in the art"?
Definiteness is not evaluated in a vacuum or from the perspective of a lay reader. It is assessed from the viewpoint of one of ordinary skill in the relevant art at the time of filing, considering the specific disclosure of the application, prior art teachings, and the ordinary level of skill in the field. A term that reads as vague to a non-practitioner may be perfectly clear to an experienced engineer in the technology area.
Breadth does not equal indefiniteness. A broad claim is not indefinite merely because it encompasses a wide scope of subject matter, provided the scope is clearly defined.
Common sources of indefiniteness
Terms of degree
Words like "substantially," "about," and "approximately" are routine in patent claims and are not automatically indefinite; they are definite when the specification provides measurement standards or context that allow a skilled artisan to determine the scope of the claimed subject matter. The failure point comes when no such standard or context exists and the claim leaves readers with no objective basis for drawing the line.
Antecedent basis
A claim may be indefinite for lack of antecedent basis when it uses a definite reference such as "said lever" to an element that was never introduced earlier in the claim, unless the scope of the claim would still be reasonably ascertainable to those skilled in the art. This is one of the easier issues to catch at the drafting stage: read through each claim element and confirm that every "said" or "the" reference has a clear prior introduction in the same claim.
Functional language and means-plus-function
Functional language does not in itself render a claim indefinite, but when a claim element is expressed as a means or step for performing a specified function under 35 U.S.C. § 112(f), the specification must disclose the corresponding structure, material, or acts that perform that function. When that disclosure is missing, the element is indefinite under § 112(b): a means-plus-function limitation is indefinite when the specification does not disclose corresponding structure sufficient for a skilled artisan to identify what performs the recited function.
This is a significant trap in software-related claiming. A claim element like "means for processing user input" invokes 112(f), and if the specification describes no corresponding algorithm or structure, the element is indefinite regardless of how clear the function itself sounds.
Subjective terms
Claim language that can only be evaluated by reference to an individual's personal opinion is indefinite unless the specification provides an objective standard for applying the term. "Aesthetically pleasing" is a classic example. "Comfortable for average use" presents the same risk unless the specification provides objective measurement criteria.
Prosecution vs. litigation
Indefiniteness arises in two procedural settings, and the applicable standards differ.
During USPTO examination: Claims receive the broadest reasonable interpretation consistent with the specification, a threshold lower than the post-grant litigation standard, to give applicants the opportunity to clarify scope while amendments are still straightforward. The examiner bears the initial burden to establish a prima facie case of indefiniteness by identifying the specific language that renders the claim indefinite and explaining the reasoning; the burden then shifts to the applicant to amend the claim or argue that a skilled artisan would understand the scope.
After issuance, in litigation: Indefiniteness is a defense to a charge of patent infringement under 35 U.S.C. § 282(b), and a successful showing renders the affected claim invalid. An issued patent is presumed valid, and the party asserting invalidity bears the burden of establishing it. The court applies the Nautilus reasonable-certainty standard, reading the claims in light of the complete specification and prosecution history.
At a glance
| Scenario | What applies |
|---|---|
| Claim under examination at USPTO | Broadest reasonable interpretation; examiner makes initial showing |
| Issued patent challenged in court | Nautilus reasonable-certainty standard; challenger bears the burden |
| Means-plus-function with no structure in spec | Indefinite under § 112(b) regardless of context |
| Broad claim with clearly defined scope | Definite, even if coverage is wide |
| Term of degree with objective spec anchor | Likely definite |
| Term of degree with no specification anchor | Likely indefinite |
Responding to a § 112(b) rejection
When an examiner issues a § 112(b) rejection, you have three main paths:
- Amend the claim. Rewrite the indefinite term with language the specification clearly supports. This is often the fastest path to allowance.
- Point to the specification. Argue that a skilled artisan reading the claim in light of the specification would understand the scope with reasonable certainty. Identify specific passages, examples, or definitions that anchor the disputed term.
- Submit a declaration. In appropriate cases, a declaration from a technical expert can establish what the disputed term means to practitioners in the field.
Avoid arguments that address the disputed term in isolation. The Nautilus standard evaluates claim language in light of the specification and prosecution history together, so arguments framed only around the claim text rarely succeed on their own.
A note on scope traps in drafting
Indefiniteness problems that surface in litigation are more expensive to fix than those caught during prosecution, because you cannot amend issued claims in a district court proceeding (though inter partes review and ex parte reexamination allow some amendment). Writing specifications that provide objective anchors for every term of degree, that clearly link every means-plus-function element to a disclosed structure, and that introduce every claim element with an indefinite article before referencing it with "said" protects you on both fronts.