Claim Scope Ladder
Capture the invention at narrow, intermediate, and broad levels, each rung a different claim, each checked for §112 support. Free worksheet for patent practitioners.
Written for patent practitioners as a work-aid. Not a substitute for professional judgment.
Attorney work-aid sequence
A structured place to capture the invention at several levels of specificity, narrow, intermediate, and broad, so each rung can inform a different candidate claim concept, using the graduated-specificity drafting technique. It also prompts a check of disclosure support for each rung, the commercial anchor, and a design-around self-test.
This is a capture scaffold for an attorney's own analysis. The template stays neutral, it mirrors the rungs the practitioner articulates and does not draft claim language. The notes below explain the §112 doctrine behind the rungs for context; none of it is legal advice, and scope decisions stay with the practitioner.
The Template
Scope Ladder
Linked Disclosure
Optional, the invention disclosure this ladder builds on. The disclosure usually gives the narrow rung for free.
Invention Summary
A one- or two-sentence summary to anchor the rungs.
Narrow Rung
The most specific version, closest to what was built, with the most limitations.
Intermediate Rung
A middle level, some limitations relaxed while the core remains.
Broad Rung
The candidate broad rung, the fewest proposed technical limitations. Treat it as a candidate to be tested by the checks below, not as supportable or advisable until they are done.
Support in Disclosure §112
Where each rung finds written-description and enablement support, and whether the specification supports the full breadth of the broader rungs, not just the narrow one. Flag any rung that outruns the disclosure.
Validity Risk by Rung
The three-way tradeoff, per rung. The broad rung sits closest to both §101 abstraction (result-oriented, mechanism-free) and the §102/§103 prior art; the narrow rung is safest but easiest to design around. Note each rung's eligibility exposure and prior-art exposure.
Functional-Language Check §112(f)
Does any rung lean on heavily functional language ("means for," "module configured to") without corresponding structure? That risks means-plus-function construction under §112(f). Flag functional terms that lack structural support.
Additional Rungs
Any further useful levels, label and description.
Commercial Anchor
The rung that best maps to the commercial embodiment you most want to cover.
Design-Around Self-Test
For each rung, how might a competitor design around it? And can infringement of each rung be detected and proven from outside the product? Server-side steps, multi-actor methods (divided infringement), and internal thresholds are hard to assert even when infringed. Where the broad rung is easy to avoid, note what a narrower rung captures that it misses.
The doctrine behind the rungs
The ladder exists because a broad claim is only as good as its support under 35 U.S.C. § 112. The specification has to enable a skilled person to make and use the invention across the full breadth of the claim (LizardTech, Fed. Cir. 2005), and the Supreme Court applied the strict version in Amgen v. Sanofi (2023): the more a party claims, the broader the monopoly it demands, the more it must enable. Amgen disclosed 26 antibody examples but claimed the entire functional class, and the Court unanimously held the claims failed. That is the risk the Support in Disclosure check surfaces for the top rung.
The rung is a three-way tradeoff. The broad rung is simultaneously closest to §101 abstraction (result-oriented, mechanism-free claims are the ones held ineligible) and closest to the §102/§103 prior art; the narrow rung is the safest to validity but the easiest to design around. Making that breadth-versus-validity-versus-eligibility tradeoff explicit per rung is the whole point of the exercise, and it cross-links to the §101 and §103 worksheets.
Watch functional language at the top. Heavily functional claim terms can trigger means-plus-function construction under §112(f) (the Williamson v. Citrix line), narrowing a rung to the disclosed structure and its equivalents, often the opposite of the breadth intended.
This ladder is the practitioner counterpart to Three Levels of Your Idea, the inventor-side articulation worksheet: send that to the client first, then build the ladder from what comes back.
Educational context on the governing framework, not legal advice, and not a prediction for any specific claim.
Use it in the platform (coming soon)
Our platform will let you fill this in interactively from a linked disclosure and export a finished document. Until it launches, use the template above.
See the Concept Scanner.
Frequently Asked Questions
What is the enablement requirement under §112?
Section 112 requires the specification to teach a person skilled in the art how to make and use the claimed invention without undue experimentation, across the full scope of the claim. A claim broader than what the disclosure actually enables is vulnerable, which is why each rung of the ladder is checked against the specification.
How did Amgen v. Sanofi change functional claiming?
In Amgen v. Sanofi (2023) the Supreme Court reaffirmed the strict enablement standard for broad functional claims: the more you claim, the more you must enable. Amgen disclosed 26 example antibodies but claimed an entire functional genus, and the Court unanimously invalidated the claims. Broad, function-defined rungs need commensurate disclosure.
How many claim scope levels should an application support?
There is no fixed number. The practical answer is: as many rungs as the disclosure genuinely supports, from the narrow built embodiment up to the broadest version §112 will carry. The ladder's job is to make each rung's support and risk explicit so the drafter can choose; the count follows from the disclosure, not a target.
When does functional claim language trigger §112(f)?
Under Williamson v. Citrix (Fed. Cir. 2015), claim terms that recite function without sufficient structure can be construed as means-plus-function under §112(f), limiting them to the structure disclosed in the specification and its equivalents, even without the words "means for." Heavily functional language at the broad rung is where this most often bites.
Scope. Completing the ladder does not establish written-description support, enablement, validity, infringement coverage, or advisable claim scope. Primarily US law and USPTO practice; other jurisdictions differ.
Disclaimer. This worksheet is a practitioner work-aid for capturing an attorney's own analysis. Obviously Not is not a law firm and does not provide legal advice; this worksheet and any output are for informational and documentation purposes only, are not legal, patent, patentability, eligibility, non-obviousness, claim-scope, validity, or freedom-to-operate advice, and do not create an attorney-client relationship. All legal judgment, including whether and how to file or argue, remains with a licensed patent practitioner exercising independent professional judgment. Nothing here predicts an outcome at the USPTO or any court.