How to use this checklist

A Section 112 review compares two documents that were usually written by the same person in a hurry: what the claims cover and what the specification teaches. This checklist is built so that a second person can make that comparison cold.

Use Phases 0 through 6 before filing or before amending, and again before any assertion. Phase 7 is for prosecution. Phase 8 is for a patent owner preparing to send a letter or file suit. Phase 9 is for an accused infringer or challenger. Phase 10 applies to both sides in litigation. Print one copy per independent claim.

Each item names the governing authority. Notes explain why it matters. For the reasoning and case readings, read Enablement, Written Description, and Indefiniteness After Amgen v. Sanofi: What Section 112 Demands. For step-by-step drafting and litigation advice, read Drafting Patent Claims and Specifications That Survive Section 112: A Practical Guide. The worksheets that go with these tasks are in the Section 112 Toolkit: Claim Support Charts, Invalidity Contentions, and Expert Declarations.

Phase 0: Classify the patent and the claims

Red flag: The claim's outer boundary sentence ends in a result rather than a thing. That is the shape of the claims in Holland Furniture, Amgen, and Baxalta.

Phase 1: Capture what the inventors actually did

Red flag: Inventors cannot say why the invention works, and all examples came from one lineage, one data set, or one configuration.

Phase 2: Test the scope ladder

  • Confirm at least one claim reads plainly on the product you need to protect.
  • Confirm a rung exists at each commercially useful level: broad structural genus, narrower genus, named embodiments, method, and downstream product.
  • For each rung, cite the paragraph, figure, and example supporting it. 37 C.F.R. § 1.75(d)(1).
  • Rewrite any result-only rung to name a feature that identifies its members.
  • Check that each dependent claim adds a limitation that independently supports validity, not merely a label.
  • Identify the most likely design-around, and ask whether the specification actually teaches it. Note: A claim that reaches a design-around the specification does not teach invites Liebel-Flarsheim Co. v. Medrad, Inc., 481 F.3d 1371 (Fed. Cir. 2007).

Red flag: The broadest claim is the only claim that would cover the expected competitor. If it falls, there is nothing left to assert.

Phase 3: Enablement review

Red flag: The sentence "the skilled artisan is aware of" or "may be determined by routine experimentation" stands where the novel step should be. Wyeth quoted that kind of sentence against the patent owner.

Phase 4: Written description and priority

Red flag: A continuation was filed after a competitor launched, and its new limitation reads on the competitor but appears nowhere in those words in the parent. Prepare for the inventors to be asked, "When did you first see this?"

Phase 5: Definiteness audit

Red flag: A word of approximation sits next to a numeric limit that was amended to avoid close prior art. In Enviro Tech the court observed that the art was almost "about" the claimed value.

Phase 6: Functional language, software, and AI

Red flag: The only description of the claimed element repeats the claim, or a block diagram shows a labeled box. Fintiv called that a black box. An expert saying a programmer could write it will not fill the gap.

Phase 7: During prosecution

Red flag: A statement that "the art is highly unpredictable" appears in a response to a § 103 rejection, and the specification has few examples.

Phase 8: Before asserting a patent (patent owner)

Red flag: The infringement theory needs the claim to reach a technology the inventors have said they did not make and that the specification discourages.

Phase 9: After notice or suit (accused infringer or challenger)

Red flag: Your contention says only that the claims are "broad" or "functional." McRO reversed a summary judgment built on abstraction.

Phase 10: Through trial and appeal (both sides)

  • Identify the burden and standard for each ground. Clear and convincing in court, Microsoft Corp. v. i4i Ltd. Partnership, 564 U.S. 91 (2011); preponderance at the Board.
  • Tee up indefiniteness at claim construction, and request findings on extrinsic evidence. Teva Pharmaceuticals USA, Inc. v. Sandoz, Inc., 574 U.S. 318 (2015).
  • Consider summary judgment if the facts of screening or disclosure are undisputed. Fed. R. Civ. P. 56; Baxalta.
  • Move under Rule 50(a) on each § 112 ground, and renew under Rule 50(b). Fed. R. Civ. P. 50. Note: Wyeth, Seagen, and Teva each turned on JMOL. On enablement, facts go to the jury and the conclusion is law. Written description is a fact question.
  • Draft special verdict questions that separate written description from enablement, and each claim from the others.
  • Preserve each argument on the record. Satius reached enablement on appeal in unusual circumstances. Do not count on that.
  • Monitor later history. Teva's certiorari window and any new Federal Circuit decisions may change the method-of-use analysis.

Red flag: Your expert testifies that a skilled person could make a "leap" from the specification to the claim. Stop and reconsider before that report is served, whichever side you are on.

This checklist is general information and not legal advice for a specific situation.

Related Documents

Related Articles

Related Guides

Related Checklists

Related Toolkits