Checklist · Intellectual Property

Running a Freedom-to-Operate Patent Search: A Practical Checklist

Type
Checklist
Jurisdiction
National
Date
2025-07-29
Topic
Intellectual Property

A product that reads on a valid, in-force patent can be enjoined off the market, saddled with a reasonable royalty, and hit with treble damages if the infringement was willful. A freedom-to-operate (FTO) search is how a company earns informed confidence before it spends the money to launch. This checklist runs the full workflow: fixing the exact product, geography, and time you are clearing; searching USPTO Patent Public Search, Espacenet, and PATENTSCOPE by classification, keyword, and assignee; triaging hundreds of hits down to the dangerous few; construing claims under Phillips and reading the file history for disclaimers; building the claim chart that anchors every infringement call; testing literal infringement, the doctrine of equivalents, and the estoppel and dedication rules that cabin it; weighing validity against the presumption in Section 282; confirming term and status; and deciding among a design-around, a license, and an early challenge. It explains why a non-infringement opinion beats an invalidity opinion after Halo and Section 298, and why the search record is the evidentiary spine of any good-faith story. Use it to reach the market with clear eyes rather than crossed fingers.

Running a Freedom-to-Operate Patent Search: A Practical Checklist

Intellectual Property > Patent | Published 29 July 2025 - Updated 12 October 2025 | UpLaw - uplaw.us

A freedom-to-operate search asks one blunt, commercial question: can we make, use, sell, offer to sell, or import this product in these markets without infringing somebody else's valid, unexpired patent? This checklist walks the entire workflow, from scoping the product through the search, the claim charts, the infringement and validity calls, and the go/no-go decision, and grounds each step in the controlling statutes and cases.

Keywords: freedom to operate, FTO, patent clearance, claim chart, claim construction, doctrine of equivalents, prosecution history estoppel, willful infringement, opinion of counsel, design-around, patent validity, 35 U.S.C. 271, 35 U.S.C. 298, Halo

Why this search is different from every other patent search

A freedom-to-operate (FTO) search points a company's attention outward. It hunts for other people's patents that might block a planned product. That is the opposite direction from the search most founders think of first, the patentability search, which points inward and asks whether your invention is novel and non-obvious enough to earn its own patent. The two overlap in mechanics, because both comb the same databases, and they diverge completely in purpose. A patentability search wants prior art that reads on your idea so you can gauge what claims you might get. An FTO search wants live patents whose claims read on your product so you can gauge what you might get sued over. Confuse them and you will make the single most expensive mistake in this field: treating a wallet full of your own patents as permission to ship.

Owning a patent grants a right to exclude, not a right to practice. The two are genuinely different rights, and nothing in the Patent Act promises that your patented gadget escapes someone else's patented sub-component. A company can hold a strong patent on its wearable's heart-rate algorithm and still infringe a third party's patent on the strap's quick-release buckle, the app's push-notification protocol, or the charging coil. The sword and the shield are forged separately. This checklist forges the shield.

The stakes justify the effort. A patent owner who proves infringement can win an injunction removing the product from the market, a reasonable royalty or lost profits under 35 U.S.C. § 284, and, where the infringement was egregious, damages trebled for willfulness plus attorney's fees in an exceptional case under § 285. FTO does not deliver certainty, because litigation outcomes never come with guarantees, but a disciplined search converts a blind gamble into a priced, documented, defensible business decision. For the doctrine underneath this workflow, read it alongside the freedom-to-operate analysis explained end to end for a product launch and the anatomy of the Section 271 infringement analysis. Run the search steps with patent counsel, and manage the whole file with privilege in mind from the first email.

A note on how to use what follows. The checkboxes are meant to be worked, not admired. Each phase opens with the tasks and then explains the law that makes each task matter, because a checklist you do not understand is a checklist you will skip at exactly the wrong moment. A running hypothetical threads through the phases: Meridian Robotics, an invented startup preparing to launch Trundle, a four-wheeled autonomous sidewalk delivery robot that carries takeout across a college town. Trundle is fictional, and any resemblance to a real robot is coincidental; it exists here only to give the doctrine something concrete to bite.

Phase 1 — Define exactly what you are clearing

  • [ ] Obtain a concrete technical specification, not a marketing sentence. "An autonomous delivery robot" clears nothing; a claim chart cannot be built against a slogan.
  • [ ] Sit with the engineers and keep the channel open. The design need not be frozen, but it must be concrete enough to lay beside a patent claim element by element.
  • [ ] Inventory every implicated feature: how the device senses obstacles, what localization and mapping it runs, how it authenticates a recipient, what wireless protocols and encryption it uses, how it stores and processes data, what the user gestures are, and how software touches hardware.
  • [ ] Fix the geography. Patent rights are territorial, so run the analysis separately for every country where the product will be made, used, sold, offered for sale, or imported.
  • [ ] Fix the time. A patent that expires before launch poses no forward blocking risk, though it can still support a claim for past damages; pending applications go on a watch-list because their claims can change before grant.

Scoping is where most FTO searches quietly fail, because the temptation is to start typing keywords into a database before anyone has written down what the product actually is. Resist it. Patent counsel and the search that follows can only be as good as the specification handed to them. The practice notes put it plainly: the analysis begins with "a thorough understanding of certain product designs," which in turn requires counsel to "meet and maintain open communications with key members of the product development team." Practical Law, Freedom-to-Operate Analysis and Opinions (Practice Note w-001-3655). For Trundle, that means the search team needs to know that the robot uses a spinning LIDAR unit for obstacle detection, a particular simultaneous-localization-and-mapping approach, a geofence that halts the robot at the campus boundary, and a one-time code texted to the recipient that unlocks the cargo bin. Each of those is a separate patentable feature and therefore a separate infringement surface. A robot is not one product for FTO purposes; it is a dozen inventions bolted together, and any one of them can be the thing that gets you sued.

Geography deserves special discipline because a patent is a national grant. A U.S. patent reaches acts within the United States and, through § 271(f) and (g), certain cross-border conduct; it says nothing about what happens on a sidewalk in Munich. If Meridian plans to pilot Trundle in the United States this year and in Germany next year, those are two clearance projects, sequenced to the market entries, not one global sweep that pretends the world shares a patent office. The strategic dimensions of multi-jurisdictional patent exposure reward planning the geography before the search, not after.

Time is the cheapest defense in the field and the most often overlooked. A patent has a life, and half of clearance is simply confirming that the patent you are worried about is still breathing. Scope that determination now so the later status check (Phase 7) has something to check against: identify the target markets' launch dates, and treat any patent expiring before them as a past-damages question rather than an injunction question.

Phase 2 — Search the field

  • [ ] Search the free databases first: USPTO Patent Public Search and Patent Center at uspto.gov, the European Patent Office's Espacenet (worldwide.espacenet.com, covering more than 100 jurisdictions with machine translation), and WIPO's PATENTSCOPE (patentscope.wipo.int, for PCT applications).
  • [ ] Add commercial platforms where the budget and stakes warrant them (Google Patents, Derwent Innovation, PatSnap, Questel Orbit) for analytics, family mapping, and better translation.
  • [ ] Run classification searches using the Cooperative Patent Classification (CPC) and International Patent Classification (IPC) schemes to catch patents an examiner filed in a technical area regardless of the words the drafter chose.
  • [ ] Run text searches: brainstorm synonyms and alternative phrasings, then tighten with Boolean operators, proximity connectors, and truncation.
  • [ ] Run assignee searches: sweep the portfolios of named competitors, the large incumbents in the field, and any patent-assertion entities known to be active in the technology. Assignee searches catch what classification and keyword searches miss.
  • [ ] Iterate deliberately. A broad first pass maps the terrain; reviewing the hits teaches you the field's vocabulary and its favorite classifications; a refined second and third pass drills into the danger zones.
  • [ ] Document everything: databases queried, classifications and keywords used, the exact search strings, the dates run, and the results retrieved.

The search rests on a three-legged stool, and a search standing on one leg falls over. Classification searching exploits the fact that every patent is sorted by a human examiner into a technical bucket, so a CPC subclass for "autonomous ground vehicles" or "obstacle detection using laser radar" will surface patents whether the drafter called the sensor a LIDAR, a laser scanner, a light-detection unit, or an optical ranging module. Text searching catches the newest filings before they are fully classified and lets you chase the field's idiosyncratic vocabulary. Assignee searching is the leg practitioners forget, and it is often the decisive one. If a well-known robotics company or a delivery-logistics incumbent has spent a decade patenting curb-navigation and last-meter handoff, the fastest route to their dangerous patents is to read their portfolio directly rather than hope your keywords intersect it.

Why the obsession with documentation? Two reasons, one forward-looking and one backward. Forward: the search record is the evidentiary backbone of a later good-faith story. If Meridian is ever accused of willful infringement, a dated, methodical record showing that it searched competently and formed a reasonable non-infringement view is worth far more than a lawyer's recollection that "we looked into it." Backward, or rather ongoing: an FTO search is perishable, and a well-kept record lets a junior associate update the search a year later without reconstructing it from scratch, re-running the same strings against everything published since. The distinction from a validity search matters here too. An FTO search hunts for patents whose claims might cover your product; a validity search (Phase 6) hunts for prior art that might invalidate their patent. Same databases, opposite objectives, and a good record keeps the two from blurring. For the searching mechanics that also feed the front end of prosecution, compare the workflow described in the invention-disclosure checklist, where the same databases are worked for the mirror-image purpose.

Worked example — the search that changes shape. Meridian's first pass on Trundle keywords ("delivery robot," "autonomous cargo") returns roughly 900 hits, most of them noise about warehouse forklifts and drones. Reading the twenty most relevant, the team learns the field calls curb-crossing "traversable terrain classification" and files it under a specific CPC group, and that a logistics giant holds a cluster of patents on "recipient authentication for unattended delivery." Two refined searches, one classification-anchored and one assignee-anchored, cut the field to about 40 patents worth a real read and surface a handful the keyword search never would have found. That is the loop working as designed: broad, learn, narrow.

Phase 3 — Triage to the patents that actually matter

  • [ ] Cut for technological relevance: discard hits that a keyword happened to match but that plainly concern a different technology.
  • [ ] Cut for claim scope: read the representative independent claims, not the title and not the abstract, to judge whether they could conceivably read on the product.
  • [ ] Cut for legal status: eliminate patents that are expired, lapsed, disclaimed, or already invalidated, and flag any tied to a terminal disclaimer for special handling.
  • [ ] Build a prioritized shortlist: in-force patents whose claims plausibly cover the product, held by entities with the appetite or business model to enforce them.
  • [ ] Put pending applications in their own monitored bucket, because you cannot infringe a claim that has not issued, but you can be blindsided by one that issues next quarter.

Triage is the art of throwing away almost everything you found without throwing away the patent that matters. The funnel is steep: a few hundred raw hits narrow to a couple dozen worth a careful read, which narrow to a handful that earn deep, opinion-grade analysis. The discipline that makes the funnel safe is reading the right part of the document. Titles and abstracts are marketing; the claims are the law. A patent titled "Autonomous Delivery System" may claim nothing more than a specific drone battery-swap station, in which case Trundle is nowhere near it. A blandly named patent may carry an independent claim broad enough to cover any wheeled robot that hands a package to a person using a code. You cannot tell which is which from the cover page, and the single most common FTO error is triaging on the abstract.

Legal status does real work at this stage too, and it is cheap work. A patent that lapsed for non-payment of maintenance fees three years ago drops off the shortlist immediately, subject to the revival caveat in Phase 7. A patent already invalidated in an inter partes review or a district-court judgment is a different animal, and PTAB and court records are searchable. Triaging status early keeps counsel from spending opinion-grade hours on a patent that died before the analysis began.

Pending applications get their own list because they are a moving target. Their claims can be amended, narrowed, or broadened right up to allowance, and a competitor watching your public launch can draft continuation claims aimed squarely at your product. Meridian should treat the logistics giant's pending continuations as a standing risk, not a resolved one, and revisit them as they progress toward grant.

Phase 4 — Read and construe the claims

  • [ ] Concentrate on the independent claims. If a product does not infringe an independent claim, it cannot infringe any claim that depends from it.
  • [ ] Remember the arithmetic of infringement: a patent is infringed if even one claim is infringed. Grober v. Mako Prods., Inc., 686 F.3d 1335, 1344 (Fed. Cir. 2012).
  • [ ] Apply the all-elements rule. A product infringes only if it contains every limitation the claim recites; a single missing element defeats literal infringement. V-Formation, Inc. v. Benetton Group SpA, 401 F.3d 1307, 1312 (Fed. Cir. 2005).
  • [ ] Watch the transitional phrase. "Comprising" is open-ended and admits additional elements; "consisting of" is closed and excludes them.
  • [ ] Flag "means for [function]" language and "nonce" words like module, mechanism, or unit that may invoke 35 U.S.C. § 112(f), limiting the claim to the structure disclosed in the specification and its equivalents. Williamson v. Citrix Online, LLC, 792 F.3d 1339, 1349 (Fed. Cir. 2015) (en banc).
  • [ ] Construe the terms under Phillips v. AWH Corp., 415 F.3d 1303 (Fed. Cir. 2005) (en banc): the ordinary meaning to a person of ordinary skill in the art, read in light of the intrinsic evidence (claims, specification, prosecution history) before any resort to extrinsic evidence.
  • [ ] Pull the file history. Hunt for narrowing amendments and clear disclaimers that shrink the claim's reach.
  • [ ] Check whether the claims were already construed in a prior Markman order, an ITC Section 337 investigation, or a PTAB proceeding.

Claim construction is where FTO earns its keep, because the words of a patent claim rarely mean exactly what a layperson thinks they mean. The Federal Circuit's en banc decision in Phillips fixed the method: a claim term carries the meaning it would have to a person of ordinary skill in the art at the time of the invention, and that meaning is anchored first in the intrinsic evidence, the claims themselves, the specification, and the prosecution history, with dictionaries and expert testimony admitted only as a secondary check and never to contradict what the intrinsic record shows. Phillips, 415 F.3d at 1313, 1318-19. The order of operations matters. A defensible FTO position is one built on the intrinsic evidence, not one that leans on an aggressive dictionary definition a court would reject.

Two features of claim reading generate more non-infringement positions than any others, and both live in the intrinsic record. The first is the specification's tendency to over-commit. If the written description repeatedly identifies a single embodiment as "the invention" and offers nothing broader, a court may read the claims narrowly to match. X2Y Attenuators, LLC v. International Trade Commission, 757 F.3d 1358, 1362 (Fed. Cir. 2014); Honeywell International, Inc. v. ITT Industries, Inc., 452 F.3d 1312, 1318 (Fed. Cir. 2006). The second is prosecution disclaimer. If, to get the patent allowed, the applicant told the examiner that its invention does not cover a particular approach, the patentee is later held to that surrender. Computer Docking Station Corp. v. Dell, Inc., 519 F.3d 1366, 1374-79 (Fed. Cir. 2008). The file history is, in the practice-note phrase, a defense often "gift-wrapped," and the failure to pull it is a recurring FTO malpractice.

The means-plus-function trap deserves its own beat. Under § 112(f), a claim element written as a means for performing a function, or in the modern cases a nonce word that recites function without reciting definite structure, is construed to cover only the structure the specification actually discloses for that function, plus equivalents of that structure. Williamson, 792 F.3d at 1349, 1351-52. That construction can be a gift to the accused product, because it shrinks a claim that reads broadly on its face down to whatever the drawings and description actually show. For Trundle, a claim reciting a "control module configured to authenticate a recipient" may, under Williamson, be limited to the specific authentication circuitry the specification discloses, and if Meridian authenticates differently, the narrowed claim may miss it entirely. To test infringement of such a claim you first identify the recited function, then the corresponding structure, then ask whether the product's structure is the same or an equivalent. Kemco Sales, Inc. v. Control Papers Co., 208 F.3d 1352, 1364 (Fed. Cir. 2000).

Finally, do not construe in a vacuum if someone has construed before you. A prior district-court Markman order can bind the patentee, and an ITC or PTAB construction, while not binding on an Article III court, is persuasive and predictive. Texas Instruments Inc. v. Cypress Semiconductor Corp., 90 F.3d 1558, 1569 (Fed. Cir. 1996). If the logistics giant already litigated its authentication patent and a court construed "recipient credential" narrowly, Meridian inherits that gift. Construction also runs into validity, because courts construe claims where possible to preserve their validity, Phillips, 415 F.3d at 1327, which is one reason the broadest reading a patentee wants is often the reading that walks its claim into the prior art.

Phase 5 — Assess infringement, literally and by equivalents

  • [ ] Build a claim chart: a two-column table that lines up each claim limitation against exactly what the product does. This is the workhorse document of the entire analysis.
  • [ ] Assess literal infringement: is every limitation present in the product exactly as construed? A single absent or materially different limitation clears that claim. Monsanto Co. v. Syngenta Seeds, Inc., 503 F.3d 1352, 1359 (Fed. Cir. 2007).
  • [ ] Assess the doctrine of equivalents: even where a limitation is not literally met, does the product's counterpart perform substantially the same function in substantially the same way to reach substantially the same result, or differ only insubstantially? Warner-Jenkinson Co. v. Hilton Davis Chemical Co., 520 U.S. 17 (1997).
  • [ ] Apply the limits on equivalents: element-by-element analysis, the dedication rule, the prior-art bar on a broadened range, and above all prosecution history estoppel. Festo Corp. v. Shoketsu Kinzoku Kogyo Kabushiki Co., 535 U.S. 722 (2002).
  • [ ] Keep the indirect and cross-border theories in view: inducement under § 271(b), contributory infringement under § 271(c), and § 271(f) and (g) for exported components and imported products of a patented process.
  • [ ] Characterize each relevant claim's risk on a graded scale, high / moderate / low / none, with reasons. A false binary hides the very uncertainty the client is paying to understand.

The claim chart is where abstraction ends. Down the left column go the claim's limitations, broken out one at a time as the patent drafter numbered them; down the right column goes a truthful description of what the product does for each. The chart is unforgiving by design, and that is its value. Because the all-elements rule requires every limitation to be present, the chart's job is to find the one limitation the product lacks, since that single gap defeats literal infringement of the claim, and if it defeats the independent claim it defeats every dependent claim beneath it. Monsanto, 503 F.3d at 1359. A good chart does not argue; it aligns, and lets the gaps or overlaps speak.

Worked example — reading the chart honestly. The logistics giant's independent claim recites (a) an autonomous ground vehicle, (b) a plurality of sensors including at least one rotating laser rangefinder, (c) a cargo compartment with an electronically actuated lock, and (d) a controller that unlocks the compartment upon receiving a single-use numeric credential transmitted to the recipient's mobile device. Trundle plainly meets (a), (c), and (d). Element (b) is the fight. Trundle's production design replaced the spinning LIDAR with a fixed array of solid-state LIDAR units that scan electronically, with no rotating part. Literally, the product may lack a "rotating laser rangefinder." That gap, if it holds up under the construction of "rotating," clears the claim literally. The chart's honesty then forces the next question, the one that separates real FTO from wishful thinking: is a solid-state array an equivalent of a rotating rangefinder?

That next question is the doctrine of equivalents, and it exists precisely to stop an infringer from escaping liability through an insubstantial change. The Supreme Court's function-way-result test, inherited from Graver Tank & Manufacturing Co. v. Linde Air Products Co., 339 U.S. 605 (1950), and reaffirmed in Warner-Jenkinson, asks whether the substitute performs substantially the same function in substantially the same way to reach substantially the same result, and equivalence is judged element by element, not for the invention as a whole. Warner-Jenkinson, 520 U.S. at 29, 40; DePuy Spine, Inc. v. Medtronic Sofamor Danek, Inc., 469 F.3d 1005, 1016-17 (Fed. Cir. 2006). For Trundle, a patentee will argue that a solid-state array and a spinning unit both sweep the surroundings with laser pulses to build a distance map, differing only in whether a motor or an electronic circuit does the sweeping. That is a serious argument, and an honest FTO memo says so rather than declaring victory on the literal gap alone.

The reason FTO does not stop at the equivalents argument is that the doctrine has powerful limits, and the most powerful is prosecution history estoppel. When a patentee narrowed a claim during prosecution for a reason related to patentability, it surrenders the territory between the original and amended claim and cannot recapture that territory through equivalents. Festo, 535 U.S. at 733-34. So Meridian's counsel pulls the authentication patent's file history and looks for exactly this: did the applicant, to get around a prior-art rejection, amend "sensor" to "rotating laser rangefinder"? If so, the patentee presumptively surrendered non-rotating sensors, and the solid-state array is likely safe from the equivalents argument, unless the patentee can rebut the Festo presumption by showing the equivalent was unforeseeable, that the amendment's rationale was merely tangential to the equivalent, or some other reason it could not have claimed the equivalent. Festo Corp. v. Shoketsu Kinzoku Kogyo Kabushiki Co., 344 F.3d 1359, 1366-69 (Fed. Cir. 2003) (on remand); Eli Lilly & Co. v. Hospira, Inc., 933 F.3d 1320, 1330-31 (Fed. Cir. 2019). This is why Phase 4's instruction to pull the file history is not bureaucratic diligence; it frequently supplies the decisive answer.

Estoppel is not the only cabin on equivalents, and a thorough memo checks the others. The dedication rule holds that subject matter disclosed in the specification but not claimed is dedicated to the public and cannot be recaptured through the doctrine of equivalents, Johnson & Johnston Associates Inc. v. R.E. Service Co., 285 F.3d 1046, 1054-55 (Fed. Cir. 2002) (en banc), so if the patent's specification mentioned solid-state sensors but claimed only rotating ones, the patentee gave the alternative away. The prior-art limit prevents a range of equivalents so broad it would ensnare the prior art, because a patentee cannot capture through equivalents what it could not have claimed literally over the art. Jang v. Boston Scientific Corp., 872 F.3d 1275, 1285 (Fed. Cir. 2017). And where the specification discloses an alternative and disclaims it, or the claim language specifically excludes subject matter, equivalents cannot reach back in. Retractable Technologies, Inc. v. Becton, Dickinson & Co., 653 F.3d 1296, 1307 (Fed. Cir. 2011).

Two more surfaces round out the infringement analysis. First, indirect and cross-border theories. A company that ships components can face inducement under § 271(b), which requires knowledge that the induced acts constitute infringement, Global-Tech Appliances, Inc. v. SEB S.A., 563 U.S. 754, 765-66 (2011); contributory infringement under § 271(c) for supplying a non-staple component; and liability under § 271(f) for exporting components for combination abroad, cabined by Life Technologies Corp. v. Promega Corp., 580 U.S. 140 (2017) (a single commodity component is not "a substantial portion"), and under § 271(g) for importing products made by a patented process. If Meridian sells Trundle kits to overseas assemblers, those theories matter. Second, the risk grade. Resist the binary. "Infringes / does not infringe" oversells the certainty; "high / moderate / low / none, and here is why" tells the executive what she is actually buying. The full mechanics of these theories are laid out in the practical guide to patent infringement claims and defenses, which pairs naturally with this checklist.

Phase 6 — Evaluate validity, but only where infringement risk is real

  • [ ] Hunt prior art for anticipation under § 102 (a single reference disclosing every element, arranged as claimed and enabling) and for obviousness under § 103. KSR International Co. v. Teleflex Inc., 550 U.S. 398 (2007). Reach beyond patents into technical literature, product manuals, standards documents, and even newsgroup posts.
  • [ ] Consider § 112 attacks: indefiniteness under Nautilus, Inc. v. Biosig Instruments, Inc., 572 U.S. 898 (2014), and gaps in written description or enablement.
  • [ ] Consider § 101 eligibility for software and business-method claims after Alice Corp. v. CLS Bank International, 573 U.S. 208 (2014), and for life-sciences claims after Mayo and Myriad.
  • [ ] Weigh the asymmetry. A patent is presumptively valid under § 282(a), and a challenger must prove invalidity by clear and convincing evidence, so a clean non-infringement position is usually worth more than a strong invalidity argument.

Validity analysis is expensive, so spend it where infringement risk is genuine. The practice notes flag the sequence: if the infringement risk is significant, or if it is in the client's interest even at slight risk, counsel turns to invalidity. The strongest ground is almost always prior art, and the reason is procedural. A patent enjoys a statutory presumption of validity, and to overcome it a challenger must prove invalidity by clear and convincing evidence. Apotex USA, Inc. v. Merck & Co., 254 F.3d 1031, 1037 (Fed. Cir. 2001); 35 U.S.C. § 282(a). That burden is easiest to carry with prior art the USPTO never considered during prosecution, because a reference the examiner already weighed carries little persuasive punch the second time around. Meridian's most valuable invalidity find would be an obscure robotics-conference paper predating the authentication patent that discloses exactly the single-use-code unlock, never cited in the file.

Anticipation under § 102 is a strict, single-reference test: one prior-art reference must disclose every claim element, expressly or inherently, arranged as in the claim, and enable a skilled artisan to practice the invention. Elan Pharmaceuticals, Inc. v. Mayo Foundation for Medical Education & Research, 346 F.3d 1051, 1054-55 (Fed. Cir. 2003). Obviousness under § 103 is the broader and more commonly successful ground, asking whether the differences between the claim and the prior art would have been obvious to a person of ordinary skill, an inquiry the Supreme Court loosened in KSR by rejecting rigid tests in favor of an expansive, common-sense analysis of whether the combination was predictable. KSR, 550 U.S. at 416. A thorough obviousness view also anticipates the patentee's secondary-consideration rebuttals, such as commercial success, long-felt need, and copying, and the nexus each requires. The deeper mechanics live in the comprehensive guide to Section 103 obviousness and in the checklist for defeating a Section 103 rejection, which translate the standard into working arguments.

For software, fintech, and AI features, § 101 eligibility is often the fastest kill and the most volatile. The Alice/Mayo two-step asks whether the claim is directed to an abstract idea, law of nature, or natural phenomenon and, if so, whether it adds an inventive concept amounting to significantly more. Alice, 573 U.S. at 217. A claim to "authenticating a recipient using a one-time code" may read as an abstract idea dressed in generic computing, but eligibility law shifts often enough that no FTO memo should treat a § 101 attack as a sure thing. For the current contours, see the Section 101 strategy guide for software and business-method inventions after Alice and the companion Alice eligibility checklist.

A closing caution the practice notes stress: an invalidity opinion built solely on § 112 is a weaker foundation than one built on unconsidered prior art, because the presumption of validity is harder to dislodge on written-description or enablement grounds. And there is a subtle tension counsel must not walk into, arguing simultaneously that a claim is obvious (a skilled artisan would have known how to make it) and that it is non-enabled or indefinite (a skilled artisan would not have known how to make it). A patentee will happily point out that both cannot be true, so pick the stronger and lead with it.

Phase 7 — Confirm the patent is alive: status, term, and calendar

  • [ ] Confirm the patent is in force and pin the actual expiration date. Do not simply add twenty years to the issue date; utility term runs twenty years from the earliest non-provisional filing, subject to adjustment.
  • [ ] Check for patent term adjustment under § 154(b) and patent term extension under § 156, either of which can push the expiration date later than the naive calculation.
  • [ ] Check maintenance-fee status. A patent can lapse for non-payment, but a recently lapsed patent can sometimes be revived under 37 C.F.R. § 1.378, so a lapse is not an automatic all-clear.
  • [ ] Check for a terminal disclaimer under § 253 and 37 C.F.R. § 1.321, which can shorten the term and, if the patent is no longer commonly owned with its companion, render it unenforceable.

This phase is short, cheap, and routinely botched, which is a bad combination. Building an elaborate non-infringement opinion on a patent that expired eighteen months ago wastes money; clearing a product against a patent you assumed expired when term adjustment kept it alive another three years courts disaster. The expiration date is a calculation, not a guess. Utility patents run twenty years from the earliest U.S. non-provisional filing date, but § 154(b) patent term adjustment credits the patentee for USPTO delays during prosecution, sometimes adding months or years, and § 156 patent term extension can restore time lost to regulatory review, which is why pharmaceutical patents so often outlast the calendar. Both are recorded in the patent's file and must be checked rather than assumed.

Maintenance fees introduce the one wrinkle that keeps a lapsed patent from being a safe harbor. A U.S. patent requires fees at 3.5, 7.5, and 11.5 years, and a missed payment lapses the patent, but the USPTO can revive a patent under 37 C.F.R. § 1.378 in defined circumstances. A patent that lapsed last month is not the same as a patent that expired for term; the former may come back. Terminal disclaimers, filed to overcome obviousness-type double patenting, both shorten a patent to match its companion's expiration and tie its enforceability to common ownership, so a disclaimed patent that has since been sold apart from its family may be unenforceable, a fact that can convert a scary patent into a non-issue. The interplay of double patenting and terminal disclaimers is developed further in the UpLaw materials on how the U.S. patent system grants, maintains, and expires rights.

Phase 8 — Decide on an opinion of counsel and manage willfulness

  • [ ] Understand the stakes. A court may treble damages under § 284 for egregious infringement and award fees under § 285 in an exceptional case. After Halo Electronics, Inc. v. Pulse Electronics, Inc., 579 U.S. 93 (2016), the focus is the infringer's subjective knowledge and good faith at the time of the conduct.
  • [ ] Remember there is no duty to obtain an opinion, and § 298 forbids using the absence of one to prove willfulness or inducement.
  • [ ] Prefer a non-infringement opinion over an invalidity opinion where the analysis supports it. It rests on a lower burden and, unlike invalidity, defends against inducement. Commil USA, LLC v. Cisco Systems, Inc., 575 U.S. 632 (2015).
  • [ ] Insist on a competent opinion: thorough, non-conclusory, authored by a qualified U.S. patent attorney, grounded in defensible constructions, and dated before the potentially infringing activity where possible.
  • [ ] Protect privilege. Relying on an opinion as a willfulness defense waives privilege over that subject matter. In re EchoStar Communications Corp., 448 F.3d 1294 (Fed. Cir. 2006). Consider separate opinions per patent or issue, and never share an opinion with a third party without a common-interest agreement.

Willfulness is the reason FTO is worth doing carefully rather than cheaply. Although patent law awards no punitive damages as such, § 284 lets a court multiply the damages award up to three times for egregious misconduct, and § 285 adds fees in exceptional cases. The governing standard changed in 2016. The Federal Circuit's rigid two-part Seagate test, which required objective recklessness, was swept aside in Halo, where the Supreme Court held that enhanced damages turn on the infringer's culpability judged at the time of the challenged conduct, not on litigation-time rationalizations counsel might invent later. Halo, 579 U.S. at 105-07. The practical consequence is that what the company knew and believed before it launched now carries decisive weight, and a timely, competent FTO opinion is direct evidence of a good-faith state of mind at exactly the moment that matters. Omega Patents, LLC v. CalAmp Corp., 920 F.3d 1337, 1352-53 (Fed. Cir. 2019).

The freedom that § 298 grants is the freedom not to obtain an opinion at all. Congress provided that neither the failure to obtain advice of counsel nor the failure to present it to the jury may be used to prove willful infringement or inducement. So there is no affirmative duty, and a company that chooses to rely on its documented search and internal analysis instead of a formal written opinion commits no adverse inference. But choosing to obtain an opinion, and choosing what kind, is a genuine strategic decision. A non-infringement opinion is usually the better instrument for three reasons. It rests on the patentee's burden (infringement is proven by a preponderance) rather than the challenger's higher burden (invalidity requires clear and convincing evidence). Technology Licensing Corp. v. Videotek, Inc., 545 F.3d 1316, 1327 (Fed. Cir. 2008). It does not require also delivering an invalidity opinion to defeat willfulness. Finisar Corp. v. DirecTV Group, Inc., 523 F.3d 1323, 1339 (Fed. Cir. 2008). And, decisively, it defends against inducement, whereas a good-faith belief in invalidity does not, because the Supreme Court held in Commil that believing a patent invalid is no defense to inducing its infringement. Commil, 575 U.S. at 642.

What makes an opinion "competent" is not length but rigor. A competent non-infringement opinion describes the product and its features in concrete detail (diagrams help), lays the product beside the construed claims to show the absence of at least one limitation both literally and under the doctrine of equivalents, addresses any prosecution history estoppel that would block the equivalents argument, and reaches a clear conclusion, commonly qualified with probabilities because patent litigation is uncertain. It relies on reasonable constructions a fact-finder would accept, not aggressive ones a court would reject. The author should be a U.S. patent attorney with a background in the relevant technology; in-house counsel can suffice if the opinion is genuinely competent, Cohesive Technologies, Inc. v. Waters Corp., 526 F. Supp. 2d 84, 106 (D. Mass. 2007), aff'd in part, 543 F.3d 1351 (Fed. Cir. 2008), though for high-risk situations outside counsel is often preferred as more objective, and the author is generally kept separate from trial counsel to limit the scope of any later waiver.

Which brings us to privilege, the trap that turns a shield into a discovery weapon. Relying on an opinion of counsel as a willfulness defense waives attorney-client privilege and work-product protection over the opinion's subject matter, and the waiver reaches communications between opinion counsel and the client on that subject. EchoStar, 448 F.3d at 1298-99, 1302. That waiver is a feature, not a bug, when the opinion helps, but it means the company must decide with open eyes what it is exposing. Three defensive habits follow. Prepare separate opinions for unrelated patents and issues, so relying on one does not necessarily open the others (courts split on how far the waiver runs; compare the survey in Autobytel, Inc. v. Dealix Corp., 455 F. Supp. 2d 569, 574 (E.D. Tex. 2006)). Do not share an opinion with an investor, acquirer, or partner without a common-interest agreement, because voluntary disclosure to a third party can waive the privilege for everyone. And treat the timing rule seriously: an opinion dated after the launch it was supposed to justify is worth a fraction of one dated before. Critikon, Inc. v. Becton Dickinson Vascular Access, Inc., 120 F.3d 1253, 1259-60 (Fed. Cir. 1997). The larger willfulness-and-clearance strategy, including how documented diligence rebuts enhanced damages, is developed in the IP clearance toolkit for securing freedom to operate before launch.

Phase 9 — Choose a path: design around, license, or challenge

  • [ ] Design around. Identify the single riskiest claim limitation and change or eliminate it. Under the all-elements rule, removing or substantially altering any one limitation avoids literal infringement of that claim, but the change must be substantial enough to escape the doctrine of equivalents. Feed the result to engineering before the design freeze.
  • [ ] License. Identify who owns the risky patents, whether a competitor, a university, a patent-assertion entity, or an existing partner, and review your own portfolio for coverage you may already hold. Consider buying the patent outright.
  • [ ] Challenge. Weigh an early inter partes review against a weak patent before any demand letter arrives, when timing and estoppel considerations are still yours to control.
  • [ ] Flag patent-assertion entities separately. A PAE makes no product, so there is nothing to counter-sue over, and it often prices a demand just below the cost of defense. Assess the economics of being targeted, not merely the technical merits.

A finished FTO analysis is not a verdict; it is a menu. Each identified risk should arrive paired with the options for retiring it, and the first option is usually the cheapest: design around the patent. The all-elements rule that makes infringement so demanding also makes design-arounds so effective, because eliminating or substantially changing one limitation drops the product out of the claim. The critical timing point is that a design-around discovered before the design freeze costs a schematic revision, while the same insight discovered after launch costs a recall. Meridian's solid-state-LIDAR choice is a design-around in the classic sense, but only if the change is substantial enough to escape equivalents, which loops the decision back to Phase 5. A design-around that clears the literal claim but sits squarely inside the equivalents range is no design-around at all.

Licensing is the path when the patent is strong, the owner is rational, and a design-around is costly or impossible. The threshold task is to know who holds the patent, because the negotiating posture differs enormously across a competitor who values exclusivity, a university that wants royalties, and a PAE that wants a quick settlement. Sometimes the cheapest license is the one you already own, buried in a cross-license or a supplier agreement, which is why reviewing your own portfolio precedes any outreach. Structuring the deal, from royalty base to grant scope to the traps in Brulotte and Kimble, is its own discipline; see the patent-license term-sheet checklist and the guide to monetizing a patent from valuation to term sheet. Where the blocking patent is standard-essential, the calculus shifts again into FRAND territory, addressed in the analysis of standard-essential patents and FRAND licensing in 5G and IoT.

Challenging the patent is the aggressive path, and timing is everything. An inter partes review filed proactively against a weak patent, before a demand arrives, keeps the initiative and the estoppel clock on your side; the same IPR filed reactively after suit is a defensive scramble. Finally, treat the patent-assertion entity as a distinct problem, not a variant of the competitor problem. A PAE has no product to enjoin and no market share to defend, so the usual leverage of a counter-suit evaporates, and its business model is to price demands below litigation cost so that paying feels rational even when the patent is weak. The right response is an economic one: model the cost of defense, the settlement range, and the reputational effect of paying, and decide with numbers rather than indignation. The full sweep of these choices, from pre-suit posture through appeal, is mapped in the roadmap and research guide to litigating patent infringement and, for smaller companies, in the patent-focused federal-litigation field guide.

Phase 10 — Document the analysis and communicate risk honestly

  • [ ] Write an FTO report covering the scope analyzed, the search methodology, the patents identified and triaged, the claim charts, the claim-construction analysis, the graded infringement risk with reasoning, the validity issues, and an overall characterization, all fronted by a plain-English executive summary.
  • [ ] Calibrate the message to the audience: a green / yellow / red signal for executives, feature-level detail for product and engineering, and the full analysis for legal.
  • [ ] Avoid false precision. Qualitative categories with context beat a spurious "30% likelihood" that no honest analyst can defend.
  • [ ] Pair every identified risk with mitigation options (design-around, license, IPR, accept-and-reserve, acquire, await expiration), each tagged with cost, timeline, and residual risk.
  • [ ] Treat FTO as a living process. Set standing search alerts and schedule reviews, annually or tied to major releases, because new patents, including continuations drafted to read on your shipping product, issue every week.

The report is where a good analysis either lands or evaporates. Its structure should mirror the workflow, but its opening should not: executives read the first page and delegate the rest, so the executive summary carries the load. The hard discipline is honesty about uncertainty. Patent litigation resists precise probability, and a memo that assigns "27% infringement risk" invites a cross-examiner to ask how the analyst got to 27 rather than 24. Graded qualitative categories, high / moderate / low / none, each backed by the reasoning from the claim chart and the file history, communicate more and expose less. Every risk should travel with its remedies and their price tags, so the decision-maker sees not just the danger but the cost of avoiding it.

Two audiences deserve special mention. Product and engineering need the risk at the feature level and early enough to act on it, because the whole point of front-loading FTO is to move the design before the freeze. And the recipient inside the company matters for the willfulness story: the practice notes stress delivering the opinion to an executive with both knowledge of the product and the authority to act on it, since prompt action on counsel's advice is itself evidence of good faith. An FTO report that sits unread in a folder protects no one.

Finally, FTO does not end at launch. The prior-art field keeps moving, competitors keep filing, and a continuation application published today may issue next year with claims written after studying your public product. Standing alerts on the relevant classifications and assignees, plus a scheduled re-run of the search, keep the clearance current. Meridian's Trundle file should be a subscription, not a snapshot.

The mistakes that sink FTO analyses

Some errors recur often enough to name. Treating "we have patents" as clearance confuses the inward-looking patentability question with the outward-looking FTO question and is the field's original sin. Reading titles and abstracts instead of claims triages on marketing copy when only the claims define infringement. Skipping the file history forfeits the prosecution-history-estoppel defense that so often decides the equivalents fight. Leaning on invalidity alone ignores both the clear-and-convincing burden that keeps a presumptively valid patent enforceable until a tribunal cancels it and the Commil rule that invalidity is no defense to inducement. Forgetting term and status produces the twin embarrassments of an elaborate opinion on a patent that expired last year and a clean bill of health for a patent that term adjustment kept alive longer than the calendar suggested. And false precision dresses a judgment call in a decimal to make it look like arithmetic. Each mistake is cheap to avoid and expensive to make.

Where FTO sits in the wider IP picture

Freedom to operate is one clearance among several, and a product launch usually needs more than the patent sweep this checklist describes. Trademarks must be cleared so the brand name does not infringe, a workflow that parallels this one in spirit and diverges in doctrine; copyrights and open-source licenses in the software stack carry their own obligations; and trade secrets impose duties on hires who arrive from competitors. The patent piece is the most technically demanding and often the most expensive, which is why it earns a dedicated checklist, but a company that clears patents and forgets the rest has only bought part of its peace. The broader clearance program, and the way patent FTO fits inside it, is mapped in the IP clearance toolkit for securing freedom to operate before you launch, and the damages exposure that makes all of it worth doing is quantified in the guide to what an IP case is worth. For the marking and notice rules that shape how much of a patentee's past damages are even recoverable, and therefore how urgent a given risk is, see the practical guide to patent marking requirements.

A last word on humility. FTO delivers informed confidence, never absolute safety. Claims get construed by judges you cannot predict, juries weigh equivalents in ways no memo forecasts perfectly, and a continuation you flagged as pending can issue with claims aimed at your product. The value of this workflow is not that it eliminates risk but that it finds the risk while the design is still soft, prices it, and hands the business a real decision instead of a hopeful shrug. That is the whole job: to bring a product to market with clear eyes rather than crossed fingers.

Primary authority

This checklist is general legal information from the UpLaw digital law library, not legal advice. Freedom to operate is intensely fact-specific and jurisdiction-specific. Consult qualified patent counsel about your particular product, features, and target markets before you launch.

Related UpLaw Resources

Related Guides

Related Checklists

Related Toolkits

Related Articles