Checklist · Intellectual Property

Defeating a Section 103 Obviousness Rejection: A Practical Checklist

Type
Checklist
Jurisdiction
National
Date
2025-03-01
Topic
Intellectual Property

A Section 103 obviousness rejection is the ground on which most patent claims live or die, and it is also the ground examiners are most likely to build on a shaky foundation. This checklist shows how to take that foundation apart. It walks through framing the fight (regime, claim construction, and the level of ordinary skill), testing whether the examiner ever made out a prima facie case, holding each KSR rationale to its hidden factual predicates, and deploying the substantive rebuttals: attacking the motivation to combine, severing motivation from a reasonable expectation of success, teaching away, non-analogous art, change in principle of operation, and the full slate of objective indicia with their all-important nexus. It explains how Rule 1.132 declarations, examiner interviews, and the duty of candor fit into the record, how the burden shifts at the examiner's desk, the PTAB, and in district court, and how to win without narrowing your claims into worthlessness. Worked hypotheticals illustrate each move.

Defeating a Section 103 Obviousness Rejection: A Practical Checklist

Intellectual Property > Patent Prosecution | Published 1 March 2025 - Updated 8 July 2025 | UpLaw - uplaw.us

Obviousness is the rejection you will meet most often and lose most avoidably. This checklist treats a Section 103 rejection as a structure with load-bearing parts—differences, motivation, expectation of success, and the objective evidence—and shows how to test each one before you concede a single claim word.

Keywords: obviousness, 35 U.S.C. § 103, Graham v. John Deere, KSR v. Teleflex, prima facie obviousness, motivation to combine, reasonable expectation of success, teaching away, non-analogous art, obvious to try, secondary considerations, nexus, Rule 1.132 declaration, POSITA, hindsight, MPEP 2143, prosecution history estoppel

An anticipation rejection under § 102 is a factual claim: one reference already shows everything you claimed, so go home. It is falsifiable in an afternoon. Obviousness is different, and worse. Section 103 does not ask what a single reference discloses; it asks a counterfactual about a hypothetical person—would the claimed invention as a whole have been obvious, before the effective filing date, to a person of ordinary skill in the art? That question invites the examiner to stitch references together, to modify a single reference, to fill gaps with "common sense," and to reason from the very disclosure you filed. Because the inquiry is so elastic, it is where most prosecution is won and lost, and where a great many rejections are quietly overbuilt on assumptions the examiner never actually proved.

The instinct that sinks applicants is to treat an obviousness rejection as a verdict and start amending. Resist it. A § 103 rejection is an argument with named parts, each of which the examiner must support, and each of which can fail independently. Knock out the wrong one and you keep the full scope of a claim worth owning. This checklist gives you the sequence: frame the fight, test whether a prima facie case was ever made, hold the cited rationale to its predicates, then work through the substantive rebuttals in order of cost—cheapest (argument that preserves scope) to most expensive (amendment that surrenders it). It pairs naturally with the deeper doctrinal treatment in Obviousness Under Section 103: A Comprehensive Guide to the Analysis and with the procedural mechanics in Responding to a Patent Office Action: A Practical Checklist.

The framework you are actually litigating

Everything downstream flows from two decisions and one statute. The statute is 35 U.S.C. § 103, which bars a patent if the differences between the claimed invention and the prior art "are such that the claimed invention as a whole would have been obvious" to a person of ordinary skill. The two decisions are Graham v. John Deere Co., 383 U.S. 1 (1966), which fixed the factual scaffolding, and KSR International Co. v. Teleflex Inc., 550 U.S. 398 (2007), which loosened how the top of that scaffolding is reasoned.

Graham makes obviousness a question of law resting on four factual predicates: (1) the scope and content of the prior art; (2) the differences between the prior art and the claims at issue; (3) the level of ordinary skill in the art; and (4) any objective indicia of nonobviousness—the so-called secondary considerations. Graham, 383 U.S. at 17-18. Every one of those is a factual finding. That matters, because a legal conclusion of obviousness is only as good as the facts under it, and facts have to be found, not assumed. See KSR, 550 U.S. at 406-07; In re NuVasive, Inc., 842 F.3d 1376, 1381-82 (Fed. Cir. 2016).

KSR did two things people conflate. It rejected any rigid, mandatory application of the older "teaching, suggestion, or motivation" (TSM) test—the Federal Circuit had, in the Supreme Court's view, been demanding an explicit teaching to combine even where none was needed. KSR, 550 U.S. at 415-419. And it authorized a more flexible, "common sense" approach, reminding everyone that "[a] person of ordinary skill is also a person of ordinary creativity, not an automaton." Id. at 421. But KSR did not abolish the need for reasoning. Its most quoted operative sentence is a warning to examiners: a rejection "cannot be sustained by mere conclusory statements; instead, there must be some articulated reasoning with some rational underpinning to support the legal conclusion of obviousness." Id. at 418 (quoting In re Kahn, 441 F.3d 977, 988 (Fed. Cir. 2006)). Post-KSR, TSM survives as one useful "insight," not the only path. The Federal Circuit has enforced KSR's articulation requirement with real teeth—reversing rejections that recite a conclusion without a reason. See In re Van Os, 844 F.3d 1359, 1361-62 (Fed. Cir. 2017); NuVasive, 842 F.3d at 1383-85; Arendi S.A.R.L. v. Apple Inc., 832 F.3d 1355, 1361-66 (Fed. Cir. 2016).

Finally, understand the burden architecture, because your whole strategy keys off it. At the Patent Office the examiner bears the initial burden of establishing a prima facie case of obviousness; only if that burden is carried does it shift to the applicant to rebut it with argument or evidence. In re Oetiker, 977 F.2d 1443, 1445 (Fed. Cir. 1992); MPEP §§ 2142, 2143. This is the single most exploited fact in prosecution. Before you argue about the merits, ask whether the examiner ever earned the right to make you argue at all.

A worked example to anchor the checklist

Because obviousness is abstract, carry one invented fact pattern through the whole analysis. Suppose an applicant, NimbusAg, claims a solar-powered drip-irrigation controller that (a) reads soil-moisture from a capacitive probe, (b) pulls a same-day evapotranspiration forecast over a low-power cellular radio, and (c) throttles each zone valve using a control loop that weights the forecast twice as heavily in the final six hours before a predicted rain event. The examiner rejects the sole independent claim as obvious over Reference A (a mains-powered irrigation timer that reads a soil-moisture probe) in view of Reference B (a smart thermostat that downloads weather forecasts over Wi-Fi to pre-cool a house). The examiner says a POSITA would have combined A and B "to conserve resources by using forecast data, yielding predictable results."

Hold that hypothetical. It has the classic vulnerabilities: a missing limitation (the rain-window weighting), a conclusory motivation, a secondary reference from a different field and a different power/connectivity regime, and no stated expectation that a Wi-Fi thermostat's approach ports to a battery-and-cellular field device. We will return to it at each phase.

Phase 1 — Set the frame before you argue a word

You cannot rebut a rejection you have not pinned down. Four framing moves come first.

  • [ ] Confirm the governing regime. Post-AIA § 103 applies to any application that has ever contained a claim with an effective filing date on or after March 16, 2013; pre-AIA § 103 governs the rest. 35 U.S.C. § 100 (note); MPEP § 2159. The regime changes what even qualifies as prior art, and pre-AIA law still offers a common-ownership escape hatch that post-AIA law reshaped. Establish the effective filing date across the whole priority chain before you rely on any date-based argument. 35 U.S.C. §§ 100(i), 120.
  • [ ] Verify the examiner's claim construction. During prosecution, claims get their "broadest reasonable interpretation" in light of the specification, and examiners routinely read limitations more broadly than an inventor intended. Anchor every disputed term in your own written description; a claim is construed as a POSITA would read it in context, not in a vacuum. Phillips v. AWH Corp., 415 F.3d 1303, 1312-19 (Fed. Cir. 2005) (en banc). Half of all "obvious" limitations evaporate once the term is construed correctly—if the claim requires forecast weighting keyed to a predicted rain event, a generic "uses weather data" reading is simply wrong.
  • [ ] Pin down the level of ordinary skill (the POSITA). A higher skill level makes combinations look inevitable; a modest one makes them look like invention. The level is a factual finding drawn from the field's education, the problems encountered, prior solutions, the pace of innovation, and the sophistication of the technology. Daiichi Sankyo Co. v. Apotex, Inc., 501 F.3d 1254, 1256 (Fed. Cir. 2007). Examiners often leave the level implicit; an examiner "need not make an express" finding, but where the level is doing hidden work you should force it into the open and argue the defensible, field-supported level. MPEP § 2141.03.
  • [ ] Map the rejection element by element. Build a chart: every claim limitation in one column, the exact reference and passage the examiner cites for it in the next. The obviousness inquiry is directed to the claim "as a whole," so a faithful, limitation-by-limitation mapping is both required of the examiner and clarifying for you. MPEP §§ 2141.02, 2143.03. The gaps in that chart are your case.

Run NimbusAg through this. The map shows Reference A supplies the soil probe and valve control; Reference B supplies "download a forecast." Nothing supplies the six-hour rain-window double-weighting. That empty cell is where Phase 2 begins.

Phase 2 — Test the prima facie case (the cheapest possible win)

Before conceding anything, confirm the examiner actually built a prima facie case. It has three structural requirements, and a defect in any one is fatal to the rejection as written.

  • [ ] All differences identified. The examiner must account for every limitation. A rejection that silently omits a limitation—or hand-waves it as "well known" without a citation—has not mapped the claim as a whole. In NimbusAg, the rain-window weighting appears in no cited passage; the rejection is incomplete on its face.
  • [ ] An articulated reason to combine or modify. This is the heart of the case and the most common point of failure. The examiner must do more than observe that the references collectively contain the elements or that a POSITA could combine them. "[T]he mere fact that references can be combined or modified does not render the resultant combination obvious unless the results would have been predictable to one of ordinary skill in the art," and the examiner must supply "articulated reasoning with some rational underpinning." In re Van Os, 844 F.3d at 1361 (quoting KSR); In re Kahn, 441 F.3d at 988. "To conserve resources by using forecast data, yielding predictable results" is a conclusion wearing the costume of a reason.
  • [ ] A reasonable expectation of success. Beyond a reason to try the combination, the record must show a POSITA would reasonably have expected it to work. In re Kubin, 561 F.3d 1351, 1360 (Fed. Cir. 2009); MPEP § 2143.02. This is a distinct requirement, and in less predictable arts it does independent work (Phase 5).
  • [ ] Say so, plainly, first. If any element is missing, lead with it. The most efficient victory in all of patent prosecution is "the examiner never made a prima facie case," because it costs you nothing in claim scope and shifts nothing to you.

Two Federal Circuit decisions are the workhorses here. In In re NuVasive, the Board's finding of a motivation to combine was reversed because it "did not articulate a reason why a [POSITA] would have combined the prior art references"—the agency had pointed to the elements but not to the why. 842 F.3d at 1382-85. In Arendi, the court rejected the use of "common sense" to supply a wholly missing claim limitation without evidence or reasoned explanation, cautioning that common sense "cannot be used as a wholesale substitute for reasoned analysis and evidentiary support." 832 F.3d at 1361-62. Quote them. They convert your response from a plea into a demand that the agency meet its own burden. For the broader procedural setting, see Turning Patent Rejections Into Granted Claims: A Prosecution Response Guide.

Phase 3 — Hold the cited KSR rationale to its predicates

After KSR, the MPEP catalogs a set of "exemplary rationales" an examiner may invoke, lettered (A) through (G) in MPEP § 2143(I): combining prior art elements according to known methods to yield predictable results; simple substitution of one known element for another; use of a known technique to improve similar devices in the same way; applying a known technique to a known device ready for improvement; "obvious to try" from a finite number of identified, predictable solutions; design incentives or market forces prompting predictable variations; and some teaching, suggestion, or motivation in the art (surviving TSM). Each rationale is a label with factual predicates baked in. The label is not self-proving; the predicates are the fight.

  • [ ] Identify which rationale the examiner actually invoked, and quote the MPEP's own statement of that rationale's required findings back into the record. Reframe the dispute from the unanswerable "is this obvious?" to the answerable "has the examiner satisfied the agency's own stated predicates?"
  • [ ] "Obvious to try" is the most abused, so police its predicates hardest. It applies only when there was "a finite number of identified, predictable solutions" and a POSITA had good reason to pursue the known options within their technical grasp. KSR, 550 U.S. at 421. The doctrine's boundary is the classic In re O'Farrell dichotomy: obviousness where the art points to a small, defined set of predictable options, but not where the art gives "only general guidance as to the particular form of the claimed invention or how to achieve it," which is the impermissible "throwing metaphorical darts at a board." In re O'Farrell, 853 F.2d 894, 903 (Fed. Cir. 1988); see In re Kubin, 561 F.3d at 1359. If the examiner's "finite set" is really an open-ended research program, the rationale collapses. And "obvious to try" still requires the predictability that a reasonable expectation of success supplies. Teva Pharms. USA, Inc. v. Corcept Therapeutics, Inc., 18 F.4th 1377, 1380-82 (Fed. Cir. 2021).
  • [ ] "Simple substitution" requires a known equivalent doing the same job. The substituted element must have been known, must have performed the same function, and the result must have been predictable. If the "equivalent" behaves differently in the claimed environment—say, a Wi-Fi radio versus a duty-cycled low-power cellular radio on a solar budget—it is not a simple substitution at all.
  • [ ] "Design incentives / market forces" needs a predictable variation. KSR's design-incentive rationale applies when market demand prompts variations a POSITA could predict and implement. KSR, 550 U.S. at 417. It does not license the leap from "the market wanted water savings" to "therefore this specific control law was obvious."
  • [ ] "Common knowledge" and official notice have evidentiary limits. An examiner may rely on facts that are "capable of instant and unquestionable demonstration as being well-known," but not to paper over a genuine gap. In re Zurko, 258 F.3d 1379, 1385-86 (Fed. Cir. 2001); MPEP § 2144.03. Traverse official notice properly and you can force the examiner to produce a reference or withdraw the point.

Applied to NimbusAg: if the examiner invoked "combine known elements for predictable results," the predicate is predictability of the combined result. The record must explain why a POSITA would predict that a home-thermostat forecast-download scheme yields a working rain-window irrigation control law on a solar-and-cellular device. Absent that, the rationale is a naked label.

Phase 4 — Attack the motivation to combine

If a prima facie case exists on its face, go after its keystone: the reason to combine. The examiner must "point to evidence establishing that a POSITA would be motivated to combine or modify the references," not merely note that the references disclose the elements or that a POSITA had the skill to do so. In re Van Os, 844 F.3d at 1361-62; In re Kahn, 441 F.3d at 988.

  • [ ] The references are too different to combine. Disparate fields, scales, or purposes weigh against motivation. Where two references solve different problems in different environments, the bridge between them has to be built, not assumed. Cf. Adidas AG v. Nike, Inc., 963 F.3d 1355, 1359 (Fed. Cir. 2020) (motivation-to-combine findings must be supported and explained). A mains-powered home comfort system and a solar-powered field irrigator differ in power budget, connectivity, latency tolerance, and failure consequences; those differences are motivation-defeating facts, not footnotes.
  • [ ] The combination is conclusory. Flag any rejection whose entire "reason" is that the combination "yields predictable results" or is "well known," with no explanation of why predictable or what in the art prompts it. In re NuVasive, 842 F.3d at 1383-85; Arendi, 832 F.3d at 1361-62. Make the examiner fill the blank on the record.
  • [ ] The combination defeats a reference's purpose or breaks it. If bolting B onto A would render A "unsatisfactory for its intended purpose" or inoperable, a POSITA would not make it. In re Gordon, 733 F.2d 900, 902 (Fed. Cir. 1984) (turning a reference device upside down would render it inoperable for its stated purpose); MPEP § 2143.01(V). A control law that starves zones of water in the final hours before a predicted rain that then fails to arrive could defeat a general-purpose timer's core promise of reliable irrigation—use that.
  • [ ] The examiner read the prior art selectively. A proper analysis considers the prior art "as a whole," including passages that cut against the rejection. Point to the parts of the cited references (and other art of record) that a POSITA would have weighed against the combination. Sanofi-Aventis U.S., LLC v. Dr. Reddy's Labs., Inc., 933 F.3d 1367, 1377 (Fed. Cir. 2019); MPEP § 2141.02(VI).
  • [ ] Name the hindsight. Where the only discernible "reason" to combine is the applicant's own disclosure, say it directly: the examiner used the specification as a roadmap. Obviousness must be assessed without "the benefit of hindsight," which is easy to slip into and hard to see from the inside. W.L. Gore & Assocs., Inc. v. Garlock, Inc., 721 F.2d 1540, 1553 (Fed. Cir. 1983); MPEP § 2142. The tell is a rejection that reads the claim's own inventive combination back into a pile of unrelated references.

A word of caution on one motivation argument that examiners love to defeat: do not rest your case on "the references cannot be physically combined." The obviousness test asks what the combined teachings of the references would have suggested to a POSITA, not whether one device could be bodily stuffed into another. In re Keller, 642 F.2d 413, 425 (C.C.P.A. 1981); In re Mouttet, 686 F.3d 1322, 1332 (Fed. Cir. 2012) ("the test for obviousness is not whether the features of a secondary reference may be bodily incorporated into the structure of the primary reference"). An examiner can nearly always answer a bodily-incorporation objection, so frame the point correctly: not that the parts will not fit, but that their teachings would not have led a skilled artisan to the claimed arrangement, or would have led away from it. In NimbusAg, the winning framing is that a Wi-Fi thermostat's forecast-download teaching, read for what it actually conveys, says nothing about weighting a forecast against an imminent rain event on a power-constrained field device—not that a thermostat cannot be screwed onto a sprinkler.

Phase 5 — Sever motivation from a reasonable expectation of success

Motivation and expectation of success are different requirements, and one of the most productive moves in all of § 103 practice is to grant the first while denying the second. A POSITA might have every reason to want a result and no rational basis to expect a given approach to deliver it.

For NimbusAg, even granting that a POSITA wanted to fold forecasts into irrigation, nothing in a Wi-Fi thermostat teaches that a rain-event-weighted control law will behave stably on a duty-cycled cellular link with intermittent forecast refreshes. The expectation of success is asserted, not shown.

Phase 6 — Teaching away, non-analogous art, and change in principle of operation

Three further primary-factor rebuttals can defeat obviousness outright. They are not "secondary considerations"; they go to the prima facie case itself.

  • [ ] Teaching away. A reference teaches away when it "criticize[s], discredit[s], or otherwise discourage[s]" the path the examiner took—not merely when it prefers an alternative. In re Gurley, 27 F.3d 551, 553 (Fed. Cir. 1994). It is "a significant factor" in rebutting obviousness. In re Peterson, 315 F.3d 1325, 1331 (Fed. Cir. 2003); MPEP § 2145(X). Be precise: a reference that merely fails to prefer your approach, or that lists your approach among several, is not teaching away. In re Fulton, 391 F.3d 1195, 1201 (Fed. Cir. 2004). But a thermostat reference that warns against acting on forecasts because of their unreliability would genuinely discourage the examiner's combination.
  • [ ] Non-analogous art. An obviousness rejection may rely only on analogous art—art either (1) from the same field of endeavor as the claimed invention or (2) reasonably pertinent to the particular problem the inventor faced. In re Klein, 647 F.3d 1343, 1348 (Fed. Cir. 2011); In re Bigio, 381 F.3d 1320, 1325-27 (Fed. Cir. 2004); MPEP § 2141.01(a). The "reasonably pertinent" prong turns on whether the reference "logically would have commended itself to an inventor's attention." Donner Technology, LLC v. Pro Stage Gear, LLC, 979 F.3d 1353, 1359 (Fed. Cir. 2020); Airbus S.A.S. v. Firepass Corp., 941 F.3d 1374, 1379-82 (Fed. Cir. 2019). A home-comfort thermostat may be neither in the field of agricultural irrigation nor reasonably pertinent to the problem of scheduling water on a solar power budget—argue it. But handle this argument with care: articulating the inventor's problem too broadly can hand the examiner a ready-made motivation drawn from an "admittedly known" problem. See Dome Patent L.P. v. Lee, 799 F.3d 1372, 1380 (Fed. Cir. 2015).
  • [ ] Change in principle of operation / unsatisfactory for intended purpose. If the proposed modification would change the primary reference's basic mode of operation, a POSITA would not make it. In re Ratti, 270 F.2d 810, 813 (C.C.P.A. 1959) (modification requiring a "substantial reconstruction and redesign" that changes the reference's principle of operation is not suggested); In re Gordon, 733 F.2d at 902; MPEP § 2143.01(VI). This overlaps with the "defeats the purpose" argument in Phase 4 but is analytically distinct—it targets how the reference works, not why someone would combine.
  • [ ] Build the affirmative Graham record while you rebut. Do not just deny; construct. Put on record the true scope and content of the art, the precise element or arrangement that is missing, what a POSITA actually knew and did not know, and any objective evidence. A clean Graham record is what an examiner (and later the PTAB, and a reviewing court) needs to sustain a withdrawal.

Phase 7 — Marshal objective indicia, and win the nexus fight

Secondary considerations—the fourth Graham factor—are real evidence, not a tiebreaker to be reached only when the other three factors are in equipoise. When they exist, they must be considered as part of the obviousness determination itself. In re Cyclobenzaprine Hydrochloride Extended-Release Capsule Patent Litig., 676 F.3d 1063, 1075-79 (Fed. Cir. 2012); Apple Inc. v. Samsung Elecs. Co., 839 F.3d 1034, 1048 (Fed. Cir. 2016) (en banc). The examiner "must consider" rebuttal evidence of these indicia. In re Sullivan, 498 F.3d 1345, 1351-53 (Fed. Cir. 2007); MPEP § 2145.

  • [ ] Gather evidence in the recognized categories. Commercial success; long-felt but unmet need; failure of others; unexpected results; skepticism of experts; copying by competitors; industry praise; and licensing acquiescence. See In re DBC, 545 F.3d 1373, 1383-84 (Fed. Cir. 2008); Graham, 383 U.S. at 17-18. Not every case has all of them; two well-documented indicia beat eight asserted ones.
  • [ ] Win the nexus. This is where most secondary-considerations evidence dies. The proponent must show a nexus between the evidence and the claimed features—not a brand, a price point, a marketing budget, or an unclaimed feature. Demaco Corp. v. F. Von Langsdorff Licensing Ltd., 851 F.2d 1387, 1392 (Fed. Cir. 1988). A presumption of nexus arises when the product that embodies the evidence is coextensive with the claim, but that presumption is unavailable—and can be rebutted—where the product includes unclaimed features or the claim is broader than the commercial embodiment. WBIP, LLC v. Kohler Co., 829 F.3d 1317, 1329-30 (Fed. Cir. 2016); Fox Factory, Inc. v. SRAM, LLC, 944 F.3d 1366, 1373-75 (Fed. Cir. 2019). If NimbusAg's sales come from a rugged housing and a low price, not the claimed rain-window control law, the commercial success proves nothing about this claim.
  • [ ] Match each indicium to the right declarant. Sales, market share, and copying: a business executive or sales officer. Unexpected results and skepticism: a technologist or independent expert. Long-felt need and failure of others: someone who lived the problem. Tie the declaration's facts to the claim limitations, not to the product as a marketed whole.
  • [ ] Insist the indicia be weighed within the analysis, not after it. A rejection that "finds" obviousness on factors 1-3 and then dismisses your evidence as insufficient to overturn a conclusion already reached has inverted the Graham method. Cyclobenzaprine, 676 F.3d at 1075-79.

Phase 8 — Build the evidentiary record: Rule 1.132 declarations

Attorney argument is free but weightless on contested facts; a declaration under 37 C.F.R. § 1.132 puts evidence into the record. Used well, it supplies the factual predicate an argument cannot. Used carelessly, it hands a future infringer a weapon.

  • [ ] Make it specific, supported, and commensurate in scope. A declaration must state facts, show its reasoning, and cover subject matter commensurate with the claims; conclusory declarations are discounted. In re Sullivan, 498 F.3d at 1352; MPEP §§ 716, 2145. "In my opinion the invention is not obvious" is worthless; "in testing, configuration X reduced water use by 34% versus the closest prior art, a result the art did not predict because…" is evidence.
  • [ ] Choose the right vehicle for the fact. Use declarations to establish: that a combination's results were unpredictable and a POSITA would not have made it; that there was no reasonable expectation of success; that a reference is non-enabling; or that objective indicia exist with a stated nexus. In re Kumar, 418 F.3d 1361, 1368 (Fed. Cir. 2005) (rebutting with non-enablement evidence); MPEP § 716.
  • [ ] Weigh the cost before you file. A declaration is a public admission that adverse parties can mine to narrow claims or attack the patent later. File one because it is necessary to allowance, state only the facts required, include only what the declarant genuinely understands and will stand behind, and keep it commensurate with the claims. When in doubt, treat a declaration as a considered last resort, not a reflex.
  • [ ] Observe declaration formalities. If styled as a declaration under 37 C.F.R. § 1.68, include the acknowledgment that willful false statements are punishable under 18 U.S.C. § 1001. The credibility of the declarant is part of the record.

Phase 9 — Amendment versus argument, and the estoppel you create

Sequence matters. Argue before you amend, because argument that preserves claim scope is nearly always worth more than an amendment that surrenders it—and because everything you say and everything you cut becomes a permanent part of the file that follows the patent into litigation.

  • [ ] Argue first where you can. A clean, winning argument keeps full scope at zero estoppel cost. Reserve amendment for limitations you genuinely need.
  • [ ] If you amend, amend surgically. Add a limitation the combined art truly does not teach, that is fully supported by your original specification, and that still reads on your commercial and licensable embodiments. A narrowing amendment that excludes the accused-infringer-of-tomorrow's product is a self-inflicted wound.
  • [ ] Price in prosecution-history estoppel. Every narrowing amendment made for reasons of patentability presumptively surrenders the territory between the original and amended claim for purposes of the doctrine of equivalents. Festo Corp. v. Shoketsu Kinzoku Kogyo Kabushiki Co., 535 U.S. 722, 733-42 (2002). Keep a ladder of dependent-claim fallbacks so you can retreat in ordered steps rather than gutting the independent claim.
  • [ ] Mind what your arguments do to claim scope. Statements characterizing the prior art or your claims can be used later to construe the claims narrowly or to create argument-based estoppel. Kaken Pharm. Co. v. Iancu, 952 F.3d 1346, 1352-53 (Fed. Cir. 2020); Typhoon Touch Techs., Inc. v. Dell, Inc., 659 F.3d 1376, 1381 (Fed. Cir. 2011). Say what you must to win; not a sentence more.

The interplay between claim breadth, amendment, and downstream enforcement is developed further in Patent Infringement, Claims, and Defenses: A Practical Guide for Businesses and Counsel and in the disclosure-drafting discipline covered by Drafting an Invention Disclosure That Maximizes Patent Scope.

Phase 10 — Use the examiner interview, and honor the duty of candor

  • [ ] Request an interview to test a theory before you commit it to the record. An interview lets you dispel a misreading of the reference, float a proposed amendment, and learn what the examiner would allow—without freezing a losing position into the file. Follow the interview with an accurate summary; the examiner's own interview record is part of the file history.
  • [ ] Bring the element map and one clean argument, not ten. Examiners respond to a focused demonstration that a specific limitation is missing far better than to a scattershot traverse. Lead with the strongest gap (in NimbusAg, the unmapped rain-window weighting).
  • [ ] Comply with the duty of candor. You must disclose material prior art known to you and must not misrepresent what a reference teaches or lacks. 37 C.F.R. § 1.56. Overstating a reference's gaps to win an obviousness fight is exactly the kind of misstep that can mature into an inequitable-conduct defense years later. Calibrate your candor practice against Avoiding Inequitable Conduct at the USPTO: A Duty-of-Candor Checklist; the stakes are laid out in Inequitable Conduct and the Duty of Candor: Patent Law's Atomic Bomb.

Phase 11 — Know the forum and its burden

The same rejection meets three very different burdens depending on where the fight happens. Calibrate your record to the forum you are in—and to the forums you may end up in.

Common mistakes that lose winnable rejections

  • Conceding the prima facie case. The reflex to start amending skips the cheapest win. Always test whether the examiner carried the initial burden before you shoulder yours. In re Oetiker, 977 F.2d at 1445.
  • Treating a KSR rationale as self-proving. "Simple substitution" and "obvious to try" are labels, not conclusions. Every rationale in MPEP § 2143 has factual predicates; make the examiner satisfy them. In re Kubin, 561 F.3d at 1359.
  • Conflating motivation with reasonable expectation of success. They are separate requirements, and the second is frequently the weaker link in the examiner's chain. Intelligent Bio-Systems, 821 F.3d at 1367-68.
  • Offering secondary-considerations evidence without nexus. Commercial success tied to price, brand, or an unclaimed feature proves nothing about the claim. Fox Factory, 944 F.3d at 1373-75.
  • Reflexive amendment. Narrowing a claim into commercially worthless scope is a defeat dressed as an allowance, and it triggers Festo estoppel to boot. Festo, 535 U.S. at 733-42.
  • Overstating the reference to win the day. A candor problem created in an office-action response can detonate as an inequitable-conduct defense in litigation. 37 C.F.R. § 1.56.

The master checklist, condensed

Use this as the one-page version you actually work from at the desk.

Frame it

  • [ ] Confirm AIA vs. pre-AIA regime and the true effective filing date. 35 U.S.C. § 100 (note).
  • [ ] Verify the examiner's claim construction against your specification. Phillips, 415 F.3d 1303.
  • [ ] Pin the POSITA level and argue the defensible one. Daiichi Sankyo, 501 F.3d 1254.
  • [ ] Chart every limitation against the exact cited passage.

Test the prima facie case

  • [ ] Are all differences accounted for?
  • [ ] Is there articulated reasoning to combine, not a conclusion? NuVasive, 842 F.3d 1376; Van Os, 844 F.3d 1359.
  • [ ] Is there a stated reasonable expectation of success? Kubin, 561 F.3d 1351.

Break the rationale and the motivation

  • [ ] Hold the MPEP § 2143 rationale to its predicates; police "obvious to try." O'Farrell, 853 F.2d 894.
  • [ ] References too different / different problems. Adidas, 963 F.3d 1355.
  • [ ] Combination defeats purpose or breaks the reference. Gordon, 733 F.2d 900.
  • [ ] Art read selectively; point to contrary teachings. Sanofi-Aventis, 933 F.3d 1367.
  • [ ] Name hindsight. W.L. Gore, 721 F.2d 1540.

Negate expectation of success

Deploy the other primary rebuttals

Marshal objective indicia

Record, sequence, forum

  • [ ] Draft specific, commensurate Rule 1.132 declarations only when necessary. 37 C.F.R. § 1.132; Sullivan, 498 F.3d 1345.
  • [ ] Argue before amending; keep dependent fallbacks; price in estoppel. Festo, 535 U.S. 722.
  • [ ] Interview to test amendments; honor the duty of candor. 37 C.F.R. § 1.56.
  • [ ] Match your record to the forum's burden. i4i, 564 U.S. 91.

A note on the point of all this

The goal is not merely to escape a rejection; it is to escape it while keeping claims broad enough to be worth owning. A patent that survives examination only because it was whittled down to your exact shipping product is a patent a competitor designs around in a weekend. Every phase above is oriented toward the same end: make the examiner meet the agency's own burden, rebut on the merits before you concede scope, and reserve amendment for the narrowest cut that clears the art. Do that, and a § 103 rejection becomes what it usually is—a first draft of an argument the examiner has not yet proven, rather than a verdict on your invention. For the full doctrinal architecture behind these moves, continue with Obviousness Under Section 103: A Comprehensive Guide to the Analysis; for the surrounding examination process, see How U.S. Patents Work: A Comprehensive Practical Guide and USPTO Patent Procedure Explained: Answers to Common Filing Questions.

Primary authority

Statutes and rules. 35 U.S.C. §§ 103, 100 (note), 120, 282; 37 C.F.R. §§ 1.56, 1.68, 1.111, 1.132; 18 U.S.C. § 1001. MPEP §§ 2141, 2141.01(a), 2141.02, 2141.03, 2142, 2143, 2143.01, 2143.02, 2143.03, 2144.03, 2144.05, 2145, 716, 2159.

Supreme Court. Graham v. John Deere Co., 383 U.S. 1 (1966); KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007); Festo Corp. v. Shoketsu Kinzoku Kogyo Kabushiki Co., 535 U.S. 722 (2002); Microsoft Corp. v. i4i Ltd. P'ship, 564 U.S. 91 (2011).

Federal Circuit and predecessors. In re NuVasive, Inc., 842 F.3d 1376 (Fed. Cir. 2016); Arendi S.A.R.L. v. Apple Inc., 832 F.3d 1355 (Fed. Cir. 2016); In re Van Os, 844 F.3d 1359 (Fed. Cir. 2017); In re Kahn, 441 F.3d 977 (Fed. Cir. 2006); In re Kubin, 561 F.3d 1351 (Fed. Cir. 2009); In re O'Farrell, 853 F.2d 894 (Fed. Cir. 1988); Intelligent Bio-Systems, Inc. v. Illumina Cambridge Ltd., 821 F.3d 1359 (Fed. Cir. 2016); Eisai Co. v. Dr. Reddy's Labs., Ltd., 533 F.3d 1353 (Fed. Cir. 2008); Procter & Gamble Co. v. Teva Pharms. USA, Inc., 566 F.3d 989 (Fed. Cir. 2009); Novartis Pharms. Corp. v. West-Ward Pharms. Int'l Ltd., 923 F.3d 1051 (Fed. Cir. 2019); Teva Pharms. USA, Inc. v. Corcept Therapeutics, Inc., 18 F.4th 1377 (Fed. Cir. 2021); In re Stepan Co., 868 F.3d 1342 (Fed. Cir. 2017); In re Gurley, 27 F.3d 551 (Fed. Cir. 1994); In re Peterson, 315 F.3d 1325 (Fed. Cir. 2003); In re Fulton, 391 F.3d 1195 (Fed. Cir. 2004); In re Gordon, 733 F.2d 900 (Fed. Cir. 1984); In re Ratti, 270 F.2d 810 (C.C.P.A. 1959); In re Klein, 647 F.3d 1343 (Fed. Cir. 2011); In re Bigio, 381 F.3d 1320 (Fed. Cir. 2004); Donner Technology, LLC v. Pro Stage Gear, LLC, 979 F.3d 1353 (Fed. Cir. 2020); Airbus S.A.S. v. Firepass Corp., 941 F.3d 1374 (Fed. Cir. 2019); In re Oetiker, 977 F.2d 1443 (Fed. Cir. 1992); Adidas AG v. Nike, Inc., 963 F.3d 1355 (Fed. Cir. 2020); Sanofi-Aventis U.S., LLC v. Dr. Reddy's Labs., Inc., 933 F.3d 1367 (Fed. Cir. 2019); W.L. Gore & Assocs., Inc. v. Garlock, Inc., 721 F.2d 1540 (Fed. Cir. 1983); Demaco Corp. v. F. Von Langsdorff Licensing Ltd., 851 F.2d 1387 (Fed. Cir. 1988); WBIP, LLC v. Kohler Co., 829 F.3d 1317 (Fed. Cir. 2016); Fox Factory, Inc. v. SRAM, LLC, 944 F.3d 1366 (Fed. Cir. 2019); In re Cyclobenzaprine Hydrochloride Extended-Release Capsule Patent Litig., 676 F.3d 1063 (Fed. Cir. 2012); Apple Inc. v. Samsung Elecs. Co., 839 F.3d 1034 (Fed. Cir. 2016) (en banc); In re Sullivan, 498 F.3d 1345 (Fed. Cir. 2007); In re DBC, 545 F.3d 1373 (Fed. Cir. 2008); In re Kumar, 418 F.3d 1361 (Fed. Cir. 2005); In re Zurko, 258 F.3d 1379 (Fed. Cir. 2001); Daiichi Sankyo Co. v. Apotex, Inc., 501 F.3d 1254 (Fed. Cir. 2007); Phillips v. AWH Corp., 415 F.3d 1303 (Fed. Cir. 2005) (en banc); Kaken Pharm. Co. v. Iancu, 952 F.3d 1346 (Fed. Cir. 2020); Typhoon Touch Techs., Inc. v. Dell, Inc., 659 F.3d 1376 (Fed. Cir. 2011); Dome Patent L.P. v. Lee, 799 F.3d 1372 (Fed. Cir. 2015).

This checklist is general legal information, not legal advice, and does not create an attorney-client relationship. Obviousness turns on the specific claims, references, and record before you; consult a registered patent practitioner for a particular matter.

Related UpLaw Resources

Related Guides

Related Checklists

Related Toolkits

Related Articles