Patent claims can contain subtle issues that dramatically impact validity, scope, or enforceability. Our analyzer detects these red flags automatically, but every practitioner should understand what they mean and why they matter.
Structural Red Flags
⚠️ Jepson Claim Format
A Jepson claim recites prior art in the preamble followed by "the improvement comprising..." The danger: the preamble is ALWAYS limiting, unlike normal claims where preamble limiting effect depends on context.
Anything in the Jepson preamble is admitted prior art. You're on record saying "this existed before my invention." This admission can be used against you in validity and infringement analysis.
MPEP 2129; Rowe v. Dror
⚠️ Single Means Claim
A claim reciting the entire invention as a single means-plus-function element is invalid. You cannot claim "means for [entire inventive function]" without any additional structural limitations.
This violates 35 U.S.C. § 112 because it attempts to claim in terms of function without reciting structure. It's essentially trying to claim every possible way of achieving the result.
MPEP 2164.08(a); In re Hyatt
⚠️ Closed Transition
"Consisting of" excludes additional elements. Any component not explicitly recited defeats infringement. This makes claims extremely easy to design around—competitors just add any extra feature.
Use closed transitions only when necessary (e.g., chemical purity is the invention) or when prior art forces it.
MPEP 2111.03
Language Red Flags
⚠️ Means-Plus-Function Limitations
Claims using "means for [function]" invoke 35 U.S.C. § 112(f). Scope is limited to structures disclosed in the specification plus equivalents—NOT all possible structures that perform the function.
Each MPF limitation narrows your claim to whatever you actually described. If your spec shows a processor running an algorithm, "means for processing" is limited to that algorithm and equivalents, not all processing approaches.
MPEP 2181
⚠️ Indefinite Terms
Terms of degree like "substantially," "approximately," "generally," or "about" can render claims indefinite under § 112(b) if not bounded by the specification.
The question is: Would a person of ordinary skill understand the scope? "Substantially planar" might be fine if the spec explains tolerance. "Substantially improved" probably isn't definite enough.
MPEP 2173.05(b); Nautilus v. Biosig
⚠️ Whereby Clauses
"Whereby" clauses expressing an intended result or natural consequence are often NOT given limiting weight. A "whereby" clause that merely states the result of the preceding steps adds nothing to claim scope.
If your "whereby" clause is essential to distinguish over prior art, it may be treated as non-limiting—which means no distinction at all.
MPEP 2111.04
⚠️ Wherein Clauses (Excessive)
Multiple "wherein" clauses may or may not limit scope depending on whether they give "meaning and purpose" to manipulative steps. Courts analyze whether the wherein limitation actually changes what's claimed or just describes an inherent property.
Claims with 3+ wherein clauses warrant review: are these actually limiting, or padding that could be removed without changing scope?
MPEP 2111.04
⚠️ "Capable of" / "Operable to" Language
Language indicating mere capability—"capable of," "operable to," "adapted to"—is typically NOT given significant limiting weight. These phrases describe potential function, not required function.
If your distinguishing feature is "capable of" something, it may not distinguish at all if prior art structures are inherently capable of the same thing.
MPEP 2111.04
Validity Red Flags
🚫 Anticipation Warning
When prior art analysis shows a single reference disclosing ≥90% of claim elements, anticipation under § 102 is a serious concern. Every element must be in one reference, arranged as claimed.
If you're in anticipation territory, consider: Can you add a limitation? Is there an element the reference truly doesn't disclose? Is there a priority date argument?
MPEP 2131
⚠️ Obviousness Warning
When multiple references together cover ≥90% of claim elements but no single reference anticipates, obviousness under § 103 is the concern. The question becomes: Was there motivation to combine?
Post-KSR, "common sense" can supply motivation. Defending against obviousness requires showing why combination would not have been obvious or why the combination produces unexpected results.
MPEP 2141; KSR Int'l Co. v. Teleflex Inc.
⚠️ Alice/Mayo Risk
Claims with high abstract-to-technical language ratio face § 101 challenges. Method claims reciting "receiving," "analyzing," "determining," and "outputting" without technical implementation are prime Alice targets.
The two-step test: (1) Is the claim directed to an abstract idea? (2) Does it recite something "significantly more"? Generic computer implementation doesn't count.
MPEP 2106.04
Enforcement Red Flags
⚠️ Divided Infringement Risk
Method claims requiring multiple actors face Akamai problems. "A user uploads... a server processes... an administrator approves..." requires three actors. Unless one controls or directs the others, there may be no direct infringer.
Watch for: different parties in claim steps, client-server interactions, multi-party workflows, "receiving from" / "sending to" different entities.
Akamai Technologies v. Limelight Networks
⚠️ CRM/Beauregard Claims
Computer-readable medium claims ("A non-transitory CRM storing instructions...") face both Alice challenges and detection difficulties. The instructions execute internally—how do you prove what code is running?
These claims also face the question: Are you infringing by selling software, or only when someone executes it?
MPEP 2106.03
How Our Analyzer Uses Red Flags
Each detected red flag impacts scoring:
- Validity score: Reduced by MPF limitations, indefinite terms, Alice risk, prior art proximity
- Detectability score: Reduced by CRM claims, divided infringement, internal method steps
- Design-around score: Reduced by closed transitions, MPF scope limitations, high element count
- Construction score: Reduced by indefinite terms, MPF requiring spec analysis, ambiguous transitions
Red flags also generate explicit warnings in the analysis output, with MPEP and case law citations for each issue.
Find Your Red Flags
Run your claims through our analyzer to identify issues before they become problems.
Analyze Claims →Spotted a red flag? IP Services can help you address claim issues through strategic prosecution or portfolio optimization.