Freedom-to-operate (FTO) analysis answers one concrete question: can we make, use, sell, offer to sell, or import this product in this market without infringing someone else's valid, in-force patent? That is different from patentability, which asks whether your invention is novel and non-obvious enough to earn its own patent. The distinction sinks companies that confuse the two: you can hold a fistful of your own patents and still infringe third-party patents on other features. Owning a patent is a sword (the right to exclude); FTO is the shield, and it must be earned on its own terms.

This checklist runs the workflow from scoping to communication. For the doctrine in depth, pair it with conducting freedom-to-operate analysis for new products and what constitutes patent infringement. Run the searching steps with patent counsel, and handle the whole package with privilege in mind.

Phase 1 — Define exactly what you are clearing

  • Get a concrete technical specification, not a marketing description ("a mobile payment app" is useless input).
  • Meet with the engineering team and maintain open communication; the spec need not be final but must be concrete enough to lay alongside a patent claim element-by-element.
  • Catalog every implicated feature: how it authenticates, what protocols and encryption it uses, how data is stored and processed, what UI gestures it relies on, and how it touches hardware.
  • Define geography—run the analysis separately for every country where the product will be made, used, sold, offered, or imported (patent rights are territorial).
  • Define time—a patent expiring before launch poses no forward risk (but can support past-damages claims); pending applications go on a watch-list, since their claims can change before grant.

Phase 2 — Search the landscape

  • Search free databases: USPTO Patent Public Search and Patent Center (uspto.gov), the EPO's Espacenet (worldwide.espacenet.com, 100+ jurisdictions), and WIPO PATENTSCOPE (patentscope.wipo.int, PCT applications).
  • Use commercial platforms where warranted (Google Patents, Derwent Innovation, PatSnap, Questel Orbit) for analytics and machine translation.
  • Classification searching: use CPC and IPC schemes to find patents an examiner filed in a technical area regardless of wording.
  • Text searching: brainstorm synonyms and alternative phrasings, then refine with Boolean operators, proximity connectors, and truncation.
  • Assignee searching: sweep the portfolios of known competitors, major players, and patent-assertion entities active in the field—they catch patents classification and keyword searches miss.
  • Iterate: a broad first pass maps the terrain; reviewing hits surfaces new terminology and classifications; refined searches target the danger zones.
  • Document everything: databases queried, classifications and keywords, exact strings, dates run, and results.

Why document. The search record is the evidentiary backbone of a later good-faith story, and it lets a junior associate efficiently update the search a year later. 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—overlapping places, opposite reasons.

Phase 3 — Triage to the patents that actually matter

  • Technological relevance: discard hits plainly outside the product's technology despite a keyword match.
  • Claim scope: read the representative independent claims—not the title or abstract—to see whether they could read on the product.
  • Legal status: eliminate expired, lapsed, disclaimed, or already-invalidated patents; flag any tied to a terminal disclaimer for special handling.
  • Build a prioritized list: in-force patents whose claims plausibly cover the product, owned by entities with an enforcement track record or business model.
  • Put pending applications in their own monitored bucket.

The normal funnel is hundreds → a couple dozen worth a careful read → a handful that earn deep, opinion-grade analysis.

Phase 4 — Read and construe claims

  • Focus on independent claims (no infringement of an independent claim means no infringement of its dependents).
  • Remember a patent is infringed if even one claim is infringed.
  • Apply the all-elements rule: a product infringes only if it contains every element the claim recites; one missing element defeats literal infringement.
  • Watch transitional phrases: "comprising" is open-ended; "consisting of" is closed.
  • Flag "means for [function]" language and "nonce" words (module, mechanism) that may invoke 35 U.S.C. § 112(f), limiting the claim to disclosed structure and equivalents (Williamson v. Citrix Online, LLC, 792 F.3d 1339 (Fed. Cir. 2015) (en banc)).
  • Construe terms under Phillips v. AWH Corp., 415 F.3d 1303 (Fed. Cir. 2005) (en banc): ordinary meaning to a skilled person, read in light of intrinsic evidence (claims, specification, prosecution history) before extrinsic evidence.
  • Pull the file history—hunt for narrowing amendments and clear disclaimers that shrink claim scope.
  • Check whether the claims were already construed in a prior Markman order, ITC investigation, or PTAB proceeding.

Phase 5 — Assess infringement (literal and by equivalents)

  • Build a claim chart—a two-column table lining up each claim element against what the product actually does. This is the workhorse document of FTO.
  • Assess literal infringement: is every element present exactly as construed? One absent or materially different element clears that claim.
  • Assess the doctrine of equivalents: even outside the literal words, does the product perform substantially the same function in substantially the same way to reach substantially the same result (insubstantial differences)?
  • Apply the limits on equivalents: element-by-element analysis, the dedication rule, and—above all—prosecution-history estoppel (Festo Corp. v. Shoketsu Kinzoku Kogyo Kabushiki Co., 535 U.S. 722 (2002)), which bars recapturing territory surrendered by a narrowing amendment.
  • Keep indirect/cross-border theories in view: inducement (§ 271(b)), contributory infringement (§ 271(c)), and § 271(f)/(g) for exported components or imported products of a patented process.
  • Characterize each relevant claim's risk: high / moderate / low / none, with reasoning—not a false binary.

Phase 6 — Evaluate validity (for high/moderate-risk patents)

  • Hunt prior art for anticipation (§ 102, single reference discloses every element) and obviousness (§ 103, KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007)); reach beyond patents into technical literature, manuals, and standards.
  • Consider § 112 attacks: indefiniteness (Nautilus, Inc. v. Biosig Instruments, Inc., 572 U.S. 898 (2014)) and written-description/enablement gaps.
  • Consider § 101 eligibility for software/business-method patents after Alice Corp. v. CLS Bank International, 573 U.S. 208 (2014).
  • Remember the asymmetry: a patent is presumptively valid (§ 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.

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

  • Confirm the patent is in force and pin the expiration date—do not just add 20 years to the issue date.
  • Check for patent term adjustment (§ 154(b)) and patent term extension (§ 156), which can extend the term.
  • Check maintenance-fee payment status; a lapsed patent can sometimes be revived under 37 C.F.R. § 1.378, so a recent lapse is not a guarantee of freedom.
  • Check for a terminal disclaimer (§ 253; 37 C.F.R. § 1.321), which can shorten the term and render the patent unenforceable if no longer commonly owned.

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

  • Recall the stakes: a court may treble damages (§ 284) and award fees in an exceptional case (§ 285) for egregious infringement; Halo Electronics, Inc. v. Pulse Electronics, Inc., 579 U.S. 93 (2016), made the infringer's subjective knowledge and good faith the focus.
  • Remember there is no duty to obtain an opinion: § 298 forbids using the absence of one to prove willfulness or inducement.
  • Prefer a non-infringement opinion over an invalidity one 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)).
  • Use a competent, reasonable opinion (not aggressive constructions a court would reject), authored by a qualified U.S. patent attorney, 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/issue; do not share opinions with third parties without a common-interest agreement.

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

  • Design-around: identify the risky claim element; under the all-elements rule, eliminating or substantially changing any single element avoids literal infringement of that claim—but the change must be substantial enough to exit the equivalents range. Feed results to engineering before the design freeze.
  • License: identify who owns the risky patents (competitor, university, PAE, existing partner) and review your own license portfolio for existing coverage; consider buying the patent outright.
  • Challenge: weigh an early IPR against a weak patent before any demand arrives.
  • Flag patent-assertion entities separately: a PAE makes no product (so you cannot counter-sue) and often prices demands below the cost of defense—assess the economics of being targeted, not just technical merit.

Phase 10 — Document and communicate risk honestly

  • Write an FTO report covering scope analyzed, search methodology, patents identified and triaged, claim charts, claim-construction analysis, infringement risk with reasoning, validity issues, and an overall characterization—plus a plain-English executive summary.
  • Calibrate communication to the audience: a green/yellow/red characterization for executives, detail for product/engineering, full analysis for legal.
  • Avoid false precision—qualitative categories with context beat a spurious "30% likelihood."
  • 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), since new patents (including continuations drafted to read on your product) issue every week.

Common mistakes

  • Treating "we have patents" as a clearance opinion—patentability looks inward; FTO looks outward.
  • Reading titles and abstracts instead of claims—only the claims define what infringes.
  • Skipping the file history—prosecution-history estoppel often supplies the defense, gift-wrapped.
  • Relying on invalidity alone—a presumptively valid patent stays enforceable until canceled, and invalidity is no defense to inducement.
  • Forgetting term/status—building an elaborate opinion on a patent that expired eighteen months ago, or clearing one that lives longer than the calendar suggested.

Primary authority

  • 35 U.S.C. §§ 101, 102, 103, 112, 154, 156, 253, 271, 282, 283, 284, 285, 298. 37 C.F.R. §§ 1.321, 1.378.
  • Markman v. Westview Instruments, Inc., 517 U.S. 370 (1996); Phillips v. AWH Corp., 415 F.3d 1303 (Fed. Cir. 2005) (en banc); Warner-Jenkinson Co. v. Hilton Davis Chemical Co., 520 U.S. 17 (1997); Festo Corp. v. Shoketsu Kinzoku Kogyo Kabushiki Co., 535 U.S. 722 (2002); KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007); Alice Corp. v. CLS Bank Int'l, 573 U.S. 208 (2014); Halo Electronics, Inc. v. Pulse Electronics, Inc., 579 U.S. 93 (2016); Commil USA, LLC v. Cisco Systems, Inc., 575 U.S. 632 (2015); In re EchoStar Communications Corp., 448 F.3d 1294 (Fed. Cir. 2006).
  • Search resources: USPTO Patent Public Search (https://ppubs.uspto.gov), Espacenet (https://worldwide.espacenet.com), PATENTSCOPE (https://patentscope.wipo.int), Google Patents (https://patents.google.com).

This checklist is general information, not legal advice. FTO is fact-specific—consult qualified patent counsel about your particular product and markets before launch.

Related resources