Checklist · Intellectual Property

Responding to a Patent Office Action: A Practical Checklist

Type
Checklist
Jurisdiction
National
Date
2025-08-30
Topic
Intellectual Property

A patent office action reads like a verdict but functions like an opening bid. This checklist gives patent counsel and inventors a disciplined workflow: read the action structurally, docket the deadlines that protect patent term, verify the examiner's claim construction, and then choose deliberately among argument, amendment, declaration evidence, the examiner interview, and appeal. It works through the four substantive rejections in detail—anticipation under Section 102, obviousness under Section 103, eligibility under Section 101, and the Section 112 family—along with restriction and rejoinder, Rule 1.130 declarations that remove prior art, after-final practice in the post-AFCP-2.0 world, requests for continued examination, and the full Patent Trial and Appeal Board track. Worked hypotheticals illustrate each move, and the 2025 fee changes that reshaped post-final strategy are folded into the analysis. The goal is not merely to get a patent issued but to get one whose claims are still worth owning.

Responding to a Patent Office Action: A Practical Checklist

Intellectual Property > Patent | Published 30 August 2025 - Updated 23 September 2025 | UpLaw - uplaw.us

An office action is the patent system's way of starting a conversation, not ending one. The examiner has told you why, on the present record, the claims cannot issue. The statute then hands you the next word—and usually the word after that. This checklist turns that structural advantage into a repeatable method for converting rejections into granted claims that are still worth the paper they print on.

Keywords: office action response, patent prosecution, USPTO, non-final rejection, final rejection, Section 102 anticipation, Section 103 obviousness, Section 101 eligibility, Section 112, claim amendment, examiner interview, RCE, PTAB appeal, after-final practice, restriction requirement, prosecution history estoppel, broadest reasonable interpretation.

The office action is the process, not an interruption of it

Ask a first-time inventor what a rejection means and you will usually hear some version of "the government said no." Ask an experienced prosecutor the same question and you will hear a shrug. The overwhelming majority of patents that eventually issue do so only after at least one rejection; a first-action allowance is the statistical rarity, not the norm. The USPTO is built around a policy of "compact prosecution," under which the examiner is expected to raise every ground of rejection in one action and the applicant is expected to answer them all in one reply. Rejection is simply the mechanism by which examiner and applicant find the boundary between what the prior art already taught and what the claims may lawfully capture.

That reframing matters because it changes what "winning" looks like. A prosecutor who treats the office action as an insult tends to argue hard, amend little, and preserve nothing. A prosecutor who treats it as the opening move in a structured negotiation reads the action for what it is—a set of positions, each with a legal standard and an evidentiary burden—and answers each on its own terms. This document is a workflow for the second kind of practitioner. It assumes you understand the substantive requirements of patentability; if you need the foundational map first, start with How U.S. Patents Work: A Comprehensive Practical Guide and the prosecution roadmap in the Prosecuting a Patent Application toolkit. For a narrative companion to this checklist—the same doctrine told as strategy rather than steps—pair it with Turning Patent Rejections Into Granted Claims.

Two disciplines run underneath everything that follows. The first is that you argue the claims, not the invention you wish you had drafted and not the marketing prose in the specification. The second is that every word you say to the examiner becomes part of a permanent public record that a future infringer's counsel will read closely, hunting for admissions and disclaimers. Prosecute as though your file history will be cross-examined, because one day it may be. See What Counts as Patent Infringement: An Anatomy of the Section 271 Analysis for how those statements come back around.

Phase 1 — Read the action structurally and sort what you find

Before analyzing a single rejection, understand the anatomy of the document in front of you. An office action is a form assembled from standardized components, and misreading its structure is the most common way competent prosecutors get into trouble.

  • [ ] Decode the header. Confirm the application number, the examiner's name, the art unit, the mailing date, and the shortened statutory response period. The mailing date—not the date you happened to open the mail—starts the clock under 35 U.S.C. § 132 and 37 C.F.R. § 1.111.
  • [ ] Pull the examiner's statistics. Allowance rate, average number of actions to disposition, interview frequency, and PTAB affirmance rate are all discoverable through Patent Center, the Patent Examination Data System, or a commercial analytics platform. An examiner who allows five percent of cases at first action and reverses course after interviews calls for a different playbook than one who allows forty percent on the papers.
  • [ ] Determine whether the action is non-final or final. This single attribute governs what you may do next as of right, and it is discussed in its own right below.
  • [ ] Separate the body into three species. Not everything in an office action is a rejection, and the distinction controls your remedy:
    • Rejections go to patentability (§§ 101, 102, 103, 112) and are appealable to the Patent Trial and Appeal Board (PTAB) under 35 U.S.C. § 134(a).
    • Objections address formal defects—drawing informalities, specification typographical problems, a claim that depends from a cancelled claim—and are not appealable. They are challenged by petition to the Director under 37 C.F.R. § 1.181 (MPEP § 1201).
    • Requirements, chiefly the restriction requirement, demand that you elect among inventions and are handled under their own rules (Phase 7).
  • [ ] Read the entire action. Objections and requirements bind exactly as rejections do. Silence in your response is treated as concession.

Why appealable-versus-petitionable is not a formality

Confusing an objection for a rejection—or vice versa—can forfeit a right. If you brief a formal objection to the PTAB, the Board will decline to reach it because it lacks jurisdiction; if you petition a substantive rejection, the Director's office will bounce it back to the examiner. The line is jurisdictional, and the MPEP draws it at § 1201. When an examiner blends the two—say, a § 112(b) indefiniteness rejection that is really a complaint about antecedent-basis formatting—flag the ambiguity and address it under both frameworks so you are protected whichever way the office later characterizes it.

Worked example: reading the structure

Suppose Nimbus Robotics receives a first action on its warehouse-navigation application. The action contains: (1) a § 103 rejection of independent claim 1 over two references; (2) a § 112(b) rejection of claim 7 for the term "substantially aligned"; (3) an objection to the drawings for missing reference numerals; and (4) a restriction requirement between the navigation-method claims and the separately drawn charging-dock claims. A structural read tells Nimbus's counsel immediately that items (1) and (2) are the merits fight, item (3) is a two-line fix by petition or amendment, and item (4) must be answered with an election before anything else is entered. Four different tools, four different standards, one deadline. Sorting them first is what keeps a response coherent.

Phase 2 — Docket the deadlines before you read another word

Nothing you do in prosecution matters if it arrives late. The single most preventable malpractice event in patent practice is a blown response deadline, and it is preventable precisely because the deadline is knowable the instant the action issues.

  • [ ] Docket the response date the moment the action arrives, not after you have analyzed it. The shortened statutory period is ordinarily three months, extendable to a maximum of six months by paying escalating fees under 37 C.F.R. § 1.136(a).
  • [ ] Treat the six-month limit as a hard wall. The outer limit is statutory under 35 U.S.C. § 133 and cannot be extended for any price; miss it and the application goes abandoned (revival is possible but neither automatic nor free).
  • [ ] Treat three months as the real deadline for patent-term reasons. Under the patent term adjustment regime, 35 U.S.C. § 154(b) and 37 C.F.R. § 1.704(b), an applicant reply filed more than three months after the action is charged as applicant delay, and every day of that delay is subtracted from the patent's term. A patent you win with a six-month reply is a shorter patent than one you win with a three-month reply.
  • [ ] Preserve a last-day option. If a filing goes to the wire, pay the necessary extension fee and use a certificate of transmission or the electronic filing timestamp so the reply is timely even if it lands at 11:59 p.m.

The term-adjustment math, stated plainly

Patent term runs twenty years from the earliest non-provisional filing date, so anything that lengthens prosecution eats into the enforceable life of the patent. The USPTO gives back some of that time as PTA when the office is slow, but it claws PTA back when the applicant is slow, and the three-month reply period is the trigger. Consider a specification-heavy biotech application where the applicant routinely takes the full six months to answer each of three office actions. That is roughly nine months of applicant delay across the prosecution—nine months shaved off a patent that might otherwise protect a blockbuster molecule into its final, most lucrative year. The lesson generalizes: absent a strategic reason to slow-walk, answer within three months and keep the term you paid for. Applicants who deliberately want more time before commitment have cleaner tools than blowing the reply period—continuations and requests for continued examination, discussed in Phase 9.

Phase 3 — Deconstruct each rejection before choosing a weapon

Resist the urge to start drafting arguments. The examiner has made a set of factual and legal assertions; your first job is to test each one against the record, because the winning argument is frequently hiding in a mismatch the examiner did not notice.

  • [ ] Build an element-by-element claim chart for every rejection, mapping each claim limitation to the specific passage the examiner cited. A chart forces you to confront exactly which limitations the examiner claims to have found and where.
  • [ ] Read the cited references in full, not just the passages the examiner quoted. Prior art is a document, not a pull-quote. The paragraph two columns over often teaches away from the combination, discloses a different structure, or omits the very limitation the examiner needed.
  • [ ] Verify the examiner's claim construction first, because it is the lever under every other argument. During examination, claims receive their "broadest reasonable interpretation" (BRI) in light of the specification as a skilled artisan would read them (MPEP §§ 2111, 2111.01; In re Am. Acad. of Sci. Tech Ctr., 367 F.3d 1359 (Fed. Cir. 2004); In re Morris, 127 F.3d 1048 (Fed. Cir. 1997)). BRI is broader than the Phillips standard courts apply in litigation (Phillips v. AWH Corp., 415 F.3d 1303 (Fed. Cir. 2005) (en banc)), which is why an examiner can read a claim onto art that would never support an infringement verdict.

Claim construction is where most fights are actually won

Because BRI is broad, the examiner's reading is where an overreaching rejection usually starts—and where you usually break it. Two moves are available. First, invoke lexicography: an applicant may be his own lexicographer, so if the specification defines a term (expressly or by consistent usage), that definition controls and can pull the claim out from under the art. Second, insist that "broadest reasonable" still means reasonable—a construction untethered from the specification is not entitled to deference. If the examiner reads "mesh network" to cover a single point-to-point radio link because the claim does not expressly exclude it, the answer is not to amend but to show that no skilled reader, having read the specification's description of self-healing multi-node routing, would understand "mesh network" that way.

Worked example: the missing limitation surfaces in the chart

Return to Nimbus Robotics. Its independent claim recites, among other steps, "recomputing the route in response to a detected obstacle before the robot decelerates." The examiner's chart maps every limitation to a cited lidar-navigation patent—except that the cited patent recomputes the route only after a full stop. Nimbus's own chart, laid side by side, exposes the gap: the temporal limitation ("before the robot decelerates") has no counterpart in the art. That single mismatch, invisible in the examiner's prose but glaring in a chart, is the whole case. The remaining phases are about naming that gap in the language the governing statute requires.

Phase 4 — Defeat a Section 102 anticipation rejection

Anticipation is the most technically demanding rejection to sustain and, correspondingly, one of the most vulnerable to a precise response. Section 102 requires that a single prior-art reference disclose every claim limitation, arranged as in the claim.

  • [ ] Confirm the single-reference, all-elements rule. One reference must teach each and every limitation; a rejection that stitches two references together is an obviousness rejection wearing an anticipation label (Verdegaal Bros., Inc. v. Union Oil Co., 814 F.2d 628 (Fed. Cir. 1987)).
  • [ ] Confirm the "arranged as in the claim" requirement. It is not enough that a reference mentions every element somewhere in its four corners; the elements must be arranged or combined in the same way the claim recites (Net MoneyIN, Inc. v. VeriSign, Inc., 545 F.3d 1359 (Fed. Cir. 2008)). A reference that lists your components in a parts catalog does not anticipate a claim to their specific configuration.
  • [ ] Identify any genuinely missing limitation. If even one element is absent from the reference, the rejection fails as a matter of law. Say so, and cite the rule—do not merely assert that the reference is "different."
  • [ ] Police improper inherency. An examiner may argue that an unstated feature is nonetheless "inherent" in the reference. Inherency requires that the feature be necessarily present, not merely probable or possible; a result that flows from the reference only sometimes is not inherent (In re Robertson, 169 F.3d 743 (Fed. Cir. 1999); Continental Can Co. v. Monsanto Co., 948 F.2d 1264 (Fed. Cir. 1991); In re Oelrich, 666 F.2d 578 (C.C.P.A. 1981)). A short declaration under 37 C.F.R. § 1.132 showing that the feature does not always occur can defeat the theory outright—though be alert to the burden-shifting that attaches to functional and product-by-process claims (In re Schreiber, 128 F.3d 1473 (Fed. Cir. 1997)).
  • [ ] Test the genus-species gap. A broad genus disclosure anticipates a narrow species only if a skilled reader would "at once envisage" the claimed species from the genus (In re Petering, 301 F.2d 676 (C.C.P.A. 1962); Kennametal, Inc. v. Ingersoll Cutting Tool Co., 780 F.3d 1376 (Fed. Cir. 2015)). A reference disclosing "a transition metal catalyst" does not automatically anticipate a claim to one particular ruthenium complex.
  • [ ] Confirm the reference is enabling and actually qualifies as prior art. A non-enabling disclosure cannot anticipate, and a reference must satisfy the correct § 102 subsection—verify the effective dates and the inventor/applicant relationship before conceding the art is even citable. This last point sets up the Rule 1.130 declaration in Phase 8.

Worked example: inherency overreach

A medical-device applicant claims a catheter coating "that reduces platelet adhesion by at least 40% relative to an uncoated surface." The examiner cites a prior coating patent that is silent on platelet adhesion and asserts the 40% reduction is inherent because the coatings share a polymer family. Under Robertson and Continental Can, "shares a polymer family" is a probability argument, not a necessity argument. A § 1.132 declaration from the inventor, attaching bench data showing the prior coating achieves only a 15% reduction under the same protocol, converts the examiner's speculation into a factual loser. Anticipation dissolves, and the case moves—if at all—to the harder ground of obviousness.

Phase 5 — Defeat a Section 103 obviousness rejection (the main event)

Obviousness is where most applications live or die. Since KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007), examiners enjoy broad latitude to combine references and to invoke common sense, but that latitude is not unlimited—the rejection still must rest on articulated reasoning, and the applicant retains a full arsenal of rebuttals. Because the topic is deep enough to fill its own treatment, this phase gives the operational moves; for the doctrine in full, see the Defeating a Section 103 Obviousness Rejection checklist and the analytical companion Obviousness Under Section 103: A Comprehensive Guide.

  • [ ] Hold the examiner to the prima facie burden. The examiner must articulate why a skilled artisan would have combined the references and had a reasonable expectation of success—"articulated reasoning with some rational underpinning," in the words KSR borrowed from In re Kahn, 441 F.3d 977 (Fed. Cir. 2006). A bare recitation that both references "relate to" the same field names a category, not a motivation. Conclusory combinations do not survive review (In re NuVasive, Inc., 842 F.3d 1376 (Fed. Cir. 2016); In re Jung, 637 F.3d 1356 (Fed. Cir. 2011)).
  • [ ] Attack the motivation to combine directly. Ask what, in the art itself or in the knowledge of a skilled artisan, would have prompted the specific modification the examiner needs. If the only roadmap to the combination is your own application, that is hindsight, not motivation—and KSR itself warns against the "distortion caused by hindsight bias" (550 U.S. at 421).
  • [ ] Argue teaching away. A reference that criticizes, discredits, or discourages the claimed approach teaches away from it, and a combination that requires ignoring that teaching is suspect (In re Gurley, 27 F.3d 551 (Fed. Cir. 1994)).
  • [ ] Argue change in principle of operation. If adopting the secondary reference would require the primary reference to be redesigned or would defeat its stated purpose, a skilled artisan would not have made the combination (In re Ratti, 270 F.2d 810 (C.C.P.A. 1959)).
  • [ ] Build the affirmative Graham record. The framework is still Graham v. John Deere Co., 383 U.S. 1 (1966): establish the scope and content of the prior art, the precise differences between the art and the claim, and the level of ordinary skill—then place your objective evidence on top.
  • [ ] Marshal secondary considerations with a proven nexus. Commercial success, long-felt but unmet need, failure of others, unexpected results, copying by competitors, and industry praise can each rebut a prima facie case—but only if tied by nexus to the claimed features, not to unclaimed marketing or price advantages (WBIP, LLC v. Kohler Co., 829 F.3d 1317 (Fed. Cir. 2016); Leapfrog Enters., Inc. v. Fisher-Price, Inc., 485 F.3d 1157 (Fed. Cir. 2007)). Objective indicia are usually delivered by declaration and must be weighed before the ultimate conclusion, not after it.

The nexus problem, illustrated

Nexus is where secondary-considerations arguments most often collapse. Imagine a consumer-electronics applicant whose noise-cancelling earbud is a runaway commercial success and who submits sales figures to rebut obviousness. If the claimed advance is a particular feedback-filtering circuit, but the earbud's sales are plausibly driven by its celebrity endorsement and aggressive pricing, the examiner will discount the success for lack of nexus. The declaration must therefore connect the market response to the claimed circuit—for instance, third-party reviews praising the specific noise-floor performance the circuit produces, or evidence that competitors copied that circuit rather than the branding. Success in the abstract proves nothing; success because of the claimed feature proves a great deal.

Worked example: assembling the obviousness response

An agricultural-drone applicant claims a spray nozzle that varies droplet size in real time based on wind speed measured by an onboard sensor. The examiner combines a variable-nozzle irrigation patent (Reference A) with a drone-mounted anemometer patent (Reference B) and declares the combination obvious. The applicant's response works the checklist in order: the claim chart shows Reference A varies droplet size on a fixed schedule, not in response to a sensor, so the "real-time, wind-responsive" limitation is missing from A; Reference B measures wind but says nothing about spraying; and nothing in either reference suggests feeding the anemometer's output into the nozzle controller. The examiner's only bridge between them is the applicant's own disclosure—classic hindsight. Layered on top: a § 1.132 declaration from an agronomist attesting that the industry had chased drift-reduction for a decade without solving it (long-felt need), and evidence that a competitor reverse-engineered and copied the wind-responsive control within months of the product's launch (copying, with nexus to the claimed feature). That is a complete obviousness answer—prima facie attack plus objective rebuttal—rather than a bare denial.

Phase 6 — Defeat a Section 101 subject-matter eligibility rejection

Eligibility rejections are the most doctrinally unsettled in modern prosecution, and they demand a framework-driven answer under the Alice/Mayo two-step (Alice Corp. v. CLS Bank Int'l, 573 U.S. 208 (2014); Mayo Collaborative Servs. v. Prometheus Labs., Inc., 566 U.S. 66 (2012)), as operationalized by the USPTO's 2019 Revised Patent Subject Matter Eligibility Guidance (84 Fed. Reg. 50 (Jan. 7, 2019); MPEP § 2106). This phase is a summary; for a full drafting-and-prosecution treatment, see the Section 101 Eligibility After Alice checklist and the strategy guide, Protecting Software and Business-Method Inventions After Alice.

Worked example: pulling a claim down from the clouds

A fintech applicant claims a method of "detecting fraudulent transactions using a machine-learning model." The examiner characterizes it as the abstract idea of "identifying fraud"—an age-old human activity—and rejects. The applicant's response refuses the framing. The claim, read honestly, recites a specific architecture: a graph-neural-network that ingests transaction-topology features, retrains on a rolling window, and flags anomalies below a dynamically computed threshold. Under Prong One, "identifying fraud" is an impermissible over-abstraction that reads the technical limitations out of the claim. Under Prong Two, the claim improves the functioning of the fraud-detection system itself by catching topological fraud patterns that rule-based systems miss—an Enfish-style improvement in computer capability, not a business practice run on a generic box. And under Step 2B, the examiner's naked assertion that graph-neural-networks are "conventional" is a Berkheimer factual claim requiring evidence the record does not contain. The rejection is answered on all three fronts, and none of the answers required narrowing the claim.

Phase 7 — Defeat the Section 112 family

The § 112 rejections police the disclosure bargain: in exchange for a patent, the applicant must teach the public how to make and use the full scope of what is claimed and must claim it with precision. The three common variants call for three different responses.

  • [ ] Written description under § 112(a). The specification must show the inventor "had possession" of the claimed subject matter as of the filing date (Ariad Pharms., Inc. v. Eli Lilly & Co., 598 F.3d 1336 (Fed. Cir. 2010) (en banc); Vas-Cath Inc. v. Mahurkar, 935 F.2d 1555 (Fed. Cir. 1991)). To answer, point to specific passages as originally filed—never add new matter—or narrow the claim to the scope the disclosure actually supports.
  • [ ] Enablement under § 112(a). Enablement is measured against the full scope of the claim: a skilled artisan must be able to make and use the entire claimed range without undue experimentation, assessed through the Wands factors (Amgen Inc. v. Sanofi, 598 U.S. 594 (2023); In re Wands, 858 F.2d 731 (Fed. Cir. 1988)). Amgen is a warning against functional genus claims that claim an outcome while disclosing only a handful of species—if the claim reaches further than the teaching, either supply more teaching or narrow the claim.
  • [ ] Definiteness under § 112(b). A claim is indefinite if, read in light of the specification and prosecution history, it fails to inform a skilled artisan of the scope of the invention with "reasonable certainty" (Nautilus, Inc. v. Biosig Instruments, Inc., 572 U.S. 898 (2014)). Fix antecedent-basis defects, define relative terms ("substantially," "about") in the specification, or demonstrate a settled meaning in the art.
  • [ ] Means-plus-function under § 112(f). If a claim uses functional language without reciting sufficient structure, it may be construed under § 112(f) and confined to the corresponding structure disclosed in the specification and its equivalents. Confirm the specification actually discloses that structure—especially for computer-implemented "modules," where an algorithm, not a black box, is required (Williamson v. Citrix Online, LLC, 792 F.3d 1339 (Fed. Cir. 2015) (en banc); In re Donaldson Co., 16 F.3d 1189 (Fed. Cir. 1994) (en banc)).

Worked example: the full-scope enablement trap

A biotech applicant claims "an isolated antibody that binds antigen X and neutralizes it," disclosing three working antibodies. Post-Amgen, that functional genus is exposed: the claim covers the entire universe of neutralizing antibodies to antigen X, but the specification teaches how to make only three, leaving a skilled artisan to a "trial and error" hunt for the rest. The response options are stark and instructive. The applicant can narrow to the disclosed antibodies (by sequence or by defined structural features), preserving something enforceable; or the applicant can attempt to show, via the Wands factors, that the art was predictable enough that the disclosed species enable the genus—a much harder sell after Amgen. What the applicant cannot do is wave at the breadth of the field and hope. Written-description and enablement rejections reward disclosure discipline that begins long before the office action; the Drafting an Invention Disclosure checklist and its companion article, Drafting an Invention Disclosure That Maximizes Patent Scope, are where that discipline is built.

Phase 8 — Handle a restriction requirement and preserve rejoinder

A restriction requirement is not a rejection—it is a demand that you elect one of several inventions the examiner says are independent or distinct. Mishandling it can forfeit both claims and rights, so the moves are precise.

  • [ ] Confirm both required showings. To restrict, the examiner must show that the inventions are independent or distinct and that examining them together would impose a "serious burden" (separate classification, separate status in the art, or a divergent field of search). MPEP §§ 802–808 govern the analysis; MPEP §§ 821–821.04 govern the aftermath.
  • [ ] Traverse the serious-burden prong, not distinctness. This is counterintuitive and important. Arguing that the inventions are not distinct can read as an admission that they are obvious variants of one another—an admission a future litigant will happily quote against you. Fight the burden showing instead, which costs you nothing on the merits.
  • [ ] Make a provisional election with traverse. Elect the invention you most want to prosecute, but elect with traverse so you preserve the right to challenge the requirement later; an election without traverse forfeits that challenge.
  • [ ] Request rejoinder if the elected claims are allowed. Non-elected process or product claims that depend from or otherwise correspond to allowed elected claims may be rejoined and issued in the same patent (MPEP § 821.04). Draft claims with rejoinder in mind.
  • [ ] Preserve non-elected subject matter in a divisional. File a divisional under 35 U.S.C. § 121 to pursue the non-elected inventions. The reward is the § 121 safe harbor: a patent issued on a divisional cannot be used as an obviousness-type double-patenting reference against the parent (or vice versa) for the restricted-out claims. That safe harbor is a genuine strategic asset—see Combining Design and Utility Patents for how it interacts with double-patenting doctrine.

Worked example: why you never traverse on distinctness

Nimbus Robotics is restricted between its navigation-method claims and its charging-dock apparatus claims. Tempted to keep everything in one application, its counsel is about to argue that the two inventions are really one integrated system—that is, not distinct. That argument, if it worked, would keep the case together; if it failed, it would sit in the file history as an assertion that the dock and the method are so intertwined that a patent on one renders the other obvious. Later, when a competitor sells a dock, that very statement becomes ammunition for an obviousness-type double-patenting attack. The disciplined move is to elect the navigation claims with traverse, contest only the serious-burden showing, and file a divisional on the dock—preserving both inventions and the § 121 safe harbor without conceding anything about their relationship.

Phase 9 — Choose your instruments deliberately

By now you have diagnosed each rejection. The remaining question is how to answer—and the choice among argument, amendment, declaration, and interview has consequences that outlast prosecution.

  • [ ] Argue before you amend. Where a clean legal or factual argument defeats the rejection, argument keeps your claim scope intact at zero estoppel cost. Amendment is a concession; do not make it reflexively.
  • [ ] Amend purposefully when you must. Every narrowing amendment surrenders claim scope and can trigger prosecution-history estoppel, barring you from recapturing the surrendered territory under the doctrine of equivalents (Festo Corp. v. Shoketsu Kinzoku Kogyo Kabushiki Co., 535 U.S. 722 (2002); on remand, 344 F.3d 1359 (Fed. Cir. 2003) (en banc); Warner-Jenkinson Co. v. Hilton Davis Chem. Co., 520 U.S. 17 (1997)). Trace every added word to support in the original disclosure, use the § 1.121 status identifiers ("Currently Amended," "Previously Presented"), and confirm the amended claim still reads on your actual or planned commercial embodiment—a narrowed claim that no longer covers your product is a self-inflicted wound.
  • [ ] Keep a claim ladder. Maintain dependent claims that step down in scope so that, if the independent claim falls, a narrower fallback remains in play without a further round of amendment.
  • [ ] Use § 1.132 declarations when argument cannot establish a fact. Inventor, expert, and commercial declarations under 37 C.F.R. § 1.132 supply evidence—of unexpected results, of the non-inherency of a feature, of nexus for secondary considerations—that attorney argument alone cannot.
  • [ ] Consider a Rule 1.130 declaration to remove a reference entirely. Under 37 C.F.R. § 1.130, an applicant can disqualify a reference as prior art in two ways: § 1.130(a) attribution, showing the disclosure came from the inventor or was derived from the inventor; and § 1.130(b) prior public disclosure, showing the inventor publicly disclosed the subject matter first, within the one-year grace period of AIA § 102(b). Watch the one-year wall and the special problem that a § 1.130(b) declaration generally cannot swear behind a U.S. patent or published application that names another inventor and claims the same subject matter under § 102(a)(2). Getting a reference removed is often more powerful than arguing around it.
  • [ ] Request an examiner interview—the most underused tool in prosecution. Under 37 C.F.R. § 1.133 and MPEP § 713, an interview lets you explain the invention, test proposed amendments before committing them to the record, and often compress two or three more rounds of paper into one conversation. Interviews correlate with higher allowance rates, and floating an amendment orally lets you gauge the examiner's reaction while minimizing prosecution-history estoppel. An interview does not toll your response deadline, and only a registered practitioner of record or the applicant may conduct one (MPEP § 713.05).

Argument versus amendment, in one sentence

If you can win on the record you have, argue and keep your scope; if you cannot, amend as little as the rejection requires and document exactly why—because the narrower your surrender and the clearer your reasons, the less territory Festo takes from you in litigation. The duty-of-candor dimension of everything you file here is not optional; an incomplete or misleading submission can taint the entire patent, as detailed in Avoiding Inequitable Conduct at the USPTO and the deeper treatment in Inequitable Conduct and the Duty of Candor: Patent Law's Atomic Bomb.

Phase 10 — After a final rejection

A final rejection narrows your options as of right, but it does not end the case. The response clock still runs from the final action's mailing date, and several paths remain open.

  • [ ] Understand what "final" restricts. After a final rejection under 37 C.F.R. § 1.113, amendments are no longer entered as a matter of right; the examiner has discretion whether to enter an after-final amendment under 37 C.F.R. § 1.116 (MPEP §§ 714.12, 714.13). Amendments that merely cancel claims, comply with a requirement of form, or place the case in condition for allowance are the ones most likely to be entered.
  • [ ] Use the two-month advisory-action rule to control fees. If you file a complete after-final response within two months of the final action, the examiner's advisory action (if the response does not persuade) resets the clock for extension-fee purposes to the advisory-action date, reducing the extension fees you owe (MPEP § 706.07(f)). Filing early is not just tidy; it is cheaper.
  • [ ] Account for the end of AFCP 2.0. The After Final Consideration Pilot Program 2.0, which had given examiners paid time to consider after-final amendments and conduct interviews, ended December 14, 2024. With that cushion gone, the premium on earlier interviews and tighter pre-final amendments has risen—resolve issues before the action goes final rather than counting on after-final grace.
  • [ ] Consider a request for continued examination (RCE). An RCE under 37 C.F.R. § 1.114 reopens prosecution by withdrawing finality, letting you enter amendments and new evidence as of right. Note the 2025 fee increases: effective January 19, 2025, a first RCE runs roughly $1,500 and a second-or-subsequent RCE roughly $2,860 for large entities (confirm current figures before filing). An RCE filed while an appeal is pending withdraws the appeal.
  • [ ] Consider a continuation. A continuation under 35 U.S.C. § 120 preserves your priority date while you pursue different or broader claims in a fresh application. Copendency is unforgiving—the continuation must be filed on or before the day you pay the issue fee on the parent. Newer fee schedules also add surcharges for very long total pendency (on the order of $2,700 at six-plus years and $4,000 at nine-plus years from the earliest benefit date), which should factor into continuation strategy.
  • [ ] Appeal when the examiner has committed legal error that further argument will not cure. If you and the examiner have reached genuine impasse on a question of law—claim construction, the sufficiency of a motivation to combine, the presence of a missing limitation—more argument to the same examiner is unlikely to move the needle. That is what the PTAB is for.

Choosing among the after-final paths

Think of the after-final options as a decision tree keyed to why you are stuck. If a small amendment plus a persuasive argument would plainly put the case in condition for allowance, an after-final response under § 1.116 (ideally previewed in an interview) is fastest and cheapest. If you need to introduce new claims, new evidence, or a materially different amendment, an RCE buys you a clean slate at a known price. If you want to keep the parent alive while chasing broader claims on a parallel track, a continuation is the tool. And if the disagreement is legal rather than factual, stop spending money persuading the examiner and take the record to the Board.

Phase 11 — Appeal to the PTAB

An appeal shifts the forum from the examiner to a three-judge administrative panel and changes the nature of the exercise: you are no longer negotiating, you are litigating the record you have built.

  • [ ] Confirm the right to appeal. The claim must have been twice rejected (35 U.S.C. § 134(a); 37 C.F.R. § 41.31(a)(1)). A rejection can be "twice rejected" across two different actions even if the specific rejection changed, so read the history carefully.
  • [ ] File the Notice of Appeal with the fee by the response due date (including any purchased extension), under 37 C.F.R. §§ 41.31 and 41.20(b)(1) (MPEP § 1204).
  • [ ] Consider a Pre-Appeal Brief Request for Review for a rejection that rests on a clear factual error or omits an essential element of a prima facie case. The request (no more than five pages) is filed with the notice of appeal and can end the fight before you invest in a full brief (MPEP § 1204.02).
  • [ ] File the Appeal Brief addressing every ground of rejection. Under 37 C.F.R. § 41.37 (MPEP § 1205), a ground you do not argue is waived, and the Board may summarily sustain it. Organize the brief by ground, lead with your strongest argument, and attach an appendix collecting declarations and evidence of secondary considerations so the panel can evaluate them without hunting through the file.
  • [ ] Track the downstream deadlines. After the Examiner's Answer, you may file a Reply Brief; you must pay the appeal forwarding fee to have the appeal docketed; and you may request an oral hearing. Each step has its own clock, and missing one can dismiss the appeal.
  • [ ] Stop amending once you appeal. You are now defending a fixed record. Continued amendment generally means reopening prosecution, which forfeits the appeal you just perfected. Decide before you file the notice that the claims are the ones you intend to stand on.

What the Board is—and is not—for

The PTAB reviews the examiner's legal conclusions and the factual findings underlying them; it is not a venue for a fresh negotiation or a new invention. The strongest appeals are narrow: a single dispositive error, cleanly framed, that the panel can correct without wading into the whole prosecution. If your real problem is that the claims are too broad and need amendment, the Board is the wrong tool—take an RCE or continuation and fix the claims. If your problem is that the examiner is legally wrong and will not be moved, the Board is exactly right. For a sense of how the same claims and prior art play out once a patent leaves the office and enters litigation, see The Patent Infringement Lawsuit From Filing to Appeal and the Litigating Patent Infringement roadmap.

Phase 12 — Pre-flight review before you file

Every response, whatever its content, should clear the same final checklist before it leaves your hands.

  • [ ] Address every rejection and every objection. Silence concedes. An unargued ground survives, and on appeal it is waived.
  • [ ] Argue the claims, not the specification's marketing language. Patentability lives in the claim limitations; laudatory prose about the invention's advantages persuades no examiner and can create disclaimer problems.
  • [ ] Characterize the prior art accurately—quote it. Mischaracterizing a reference is the fastest way to lose credibility with an examiner, and a demonstrable misstatement can later feed an inequitable-conduct or file-history argument.
  • [ ] Confirm every amendment is supported and new-matter-free, and that no argument you are making now contradicts a position taken earlier in the same file.
  • [ ] File before the deadline with correct fees. If the filing is tight, pay the extension fee and rely on the electronic timestamp or a certificate of transmission so the reply is timely on its face.

Common and costly mistakes

  • Missing the deadline. No brilliance survives an untimely filing; the reply is a nullity and the application goes abandoned.
  • Failing to address every rejection. An unargued ground is conceded before the examiner and waived before the Board.
  • Arguing the specification instead of the claims. Examiners reject claims and allow claims; that is where the argument must live.
  • Amending when you could have argued. Needless narrowing surrenders scope and hands a future infringer a Festo estoppel and a prosecution-history disclaimer for free.
  • Traversing restriction on distinctness. Fighting the wrong prong can become a double-patenting or obviousness admission; contest the serious-burden showing instead.
  • Over-generalizing your own claim in a § 101 response. Adopting the examiner's abstraction to argue around it concedes the very ground you need to hold.
  • Treating the file history as private. Everything you say is public and permanent; write each sentence as though opposing counsel will read it aloud to a jury, because someone eventually might.

Primary authority at a glance

Statutes. 35 U.S.C. §§ 101 (eligibility), 102 (novelty), 103 (non-obviousness), 112 (specification), 120 (continuation copendency), 121 (divisional safe harbor), 132 (notice of rejection), 133 (time for response), 134 (appeal), 154(b) (patent term adjustment).

Regulations. 37 C.F.R. §§ 1.104, 1.111 (reply), 1.113 (final rejection), 1.114 (RCE), 1.116 (after-final amendments), 1.121 (amendment format), 1.130 (declarations to disqualify prior art), 1.132 (evidentiary declarations), 1.133 (interviews), 1.136(a) (extensions), 1.181 (petition to the Director), 1.704 (PTA reductions), 41.20/41.31/41.37 (appeal fees, notice, brief).

Supreme Court. Alice Corp. v. CLS Bank Int'l, 573 U.S. 208 (2014); Mayo Collaborative Servs. v. Prometheus Labs., Inc., 566 U.S. 66 (2012); KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007); Graham v. John Deere Co., 383 U.S. 1 (1966); Amgen Inc. v. Sanofi, 598 U.S. 594 (2023); Nautilus, Inc. v. Biosig Instruments, Inc., 572 U.S. 898 (2014); Festo Corp. v. Shoketsu Kinzoku Kogyo Kabushiki Co., 535 U.S. 722 (2002); Warner-Jenkinson Co. v. Hilton Davis Chem. Co., 520 U.S. 17 (1997); Bilski v. Kappos, 561 U.S. 593 (2010); Diamond v. Diehr, 450 U.S. 175 (1981).

Federal Circuit and predecessors. Verdegaal Bros. v. Union Oil Co., 814 F.2d 628 (Fed. Cir. 1987); Net MoneyIN v. VeriSign, 545 F.3d 1359 (Fed. Cir. 2008); In re Robertson, 169 F.3d 743 (Fed. Cir. 1999); In re NuVasive, 842 F.3d 1376 (Fed. Cir. 2016); In re Kahn, 441 F.3d 977 (Fed. Cir. 2006); In re Gurley, 27 F.3d 551 (Fed. Cir. 1994); In re Ratti, 270 F.2d 810 (C.C.P.A. 1959); Enfish v. Microsoft, 822 F.3d 1327 (Fed. Cir. 2016); McRO v. Bandai Namco, 837 F.3d 1299 (Fed. Cir. 2016); Berkheimer v. HP, 881 F.3d 1360 (Fed. Cir. 2018); Ariad v. Eli Lilly, 598 F.3d 1336 (Fed. Cir. 2010) (en banc); In re Wands, 858 F.2d 731 (Fed. Cir. 1988); Williamson v. Citrix Online, 792 F.3d 1339 (Fed. Cir. 2015) (en banc).

USPTO guidance. MPEP §§ 706, 713 (interviews), 714 (amendments), 802–808 and 821–821.04 (restriction and rejoinder), 1201–1205 (appeals), 2106 (eligibility), 2111 (broadest reasonable interpretation), 2143 (obviousness rationales), 2144.03 (official notice). 2019 Revised Patent Subject Matter Eligibility Guidance, 84 Fed. Reg. 50 (Jan. 7, 2019); July 2024 eligibility guidance update, 89 Fed. Reg. 58128 (July 17, 2024). USPTO Patent Center: https://patentcenter.uspto.gov.

This checklist is general legal information, not legal advice, and does not create an attorney-client relationship. USPTO fees and rules change frequently; confirm current amounts and procedures and consult a registered patent practitioner before acting.

Related UpLaw Resources

Related Checklists

Related Guides and Articles

Related Toolkits