Freedom-to-Operate Analyses: Scope, Timing, and Practical Limits

Freedom-to-operate analyses tend to fail in two ways: too late, when the product is already in market and a competitor’s patent has surfaced; or too broad, when a comprehensive scan across an entire technology space produces a deliverable no one can act on. Both are products of unclear thinking about what an FTO is for.

This post covers what an FTO opinion is and is not, when to commission one, the decisions that set its scope, what the deliverable contains and where its limits lie, and how to build FTO checkpoints into product development.

What an FTO Is and Is Not

A freedom-to-operate opinion is an analysis of whether a defined product, process, or service infringes identified third-party patent claims in identified jurisdictions. For issued patents, the opinion addresses current infringement risk. For pending applications, the analysis is necessarily forward-looking: a pending application cannot itself be infringed, but its claims may change during prosecution and may later issue in a form that creates blocking risk.

The opinion expresses a legal conclusion supported by an element-by-element comparison of the relevant patent claims against the defined product, process, or service. That comparison may require claim construction, technical input from product or engineering teams, and assumptions about how the product is made, used, offered for sale, sold, or imported — the acts that give rise to direct infringement under 35 U.S.C. § 271(a).

FTO is not a patentability analysis (whether the company’s own innovations can be patented), an enforcement analysis (whether the company can sue someone else for infringement), or a complete invalidity analysis (whether identified patents are vulnerable to challenge). Invalidity, enforceability, and design-around options may be considered for patents presenting material risk, but they are distinct questions requiring separate assumptions and, often, separate workstreams.

When to Commission an FTO

• Pre-launch — Before committing engineering and marketing resources to a product, an FTO identifies blocking patents that would force redesign, licensing, challenge, or an informed proceed-with-risk decision.

• Pivot — Material changes to a product’s technology, architecture, manufacturing method, or commercial markets create new infringement exposure that the original FTO did not address.

• Financing — Lead investors commonly request FTO opinions or summaries as part of diligence, particularly for hardware, biotech, medical device, and other patent-sensitive companies.

• Acquisition target evaluation — Buyers commission FTO on target products to price infringement risk into the deal and identify post-closing license, redesign, or indemnity issues.

• Litigation exposure, in the right posture — The willfulness value of an opinion accrues before suit, when the company can actually rely on it. Once a complaint is filed, a new opinion speaks at most to ongoing post-suit conduct, injunction and enhanced-damages exposure, and design-around planning; it does not reach the state of mind at the time of the challenged conduct. That distinction is developed below.

Scope Decisions

FTO scope is defined by several decisions, each affecting cost and confidence.

• Product definition — What exactly is being analyzed. Version, architecture, components, firmware, manufacturing process, deployment model, customer use case, and supply chain can all affect infringement risk. A vague product description produces a vague opinion.

• Jurisdiction — Which countries’ patents are reviewed. The U.S. is standard for many companies; expansion to Europe, China, Japan, Korea, and other commercial or manufacturing markets adds significant cost and may change the infringement analysis. U.S. exposure is not limited to U.S.-made products: 35 U.S.C. § 271(f) and § 271(g) reach the supply of components abroad and the importation of products made by a patented process, and Section 337 proceedings before the International Trade Commission provide a separate exclusion remedy against imports.

• Claim scope — How broadly the analysis scans for relevant patents. Narrow scope examines patents directed to the product’s core technology. Broader scope may examine enabling components, manufacturing methods, software workflows, user interactions, protocols, or downstream uses.

• Time horizon — Whether the analysis covers only issued patents or also reviews pending applications and active patent families. Pending applications add uncertainty because claims can change before issuance, continuation practice can keep patent families alive, and applications published today may mature into enforceable patents after launch.

• Status screening — Whether the analysis confirms that identified patents remain in force. Expiration, lapsed maintenance fees, terminal disclaimers, and prior post-grant outcomes can remove a patent from the risk set at comparatively little cost.

A well-scoped FTO answers a specific question for a specific use case. A poorly scoped FTO produces a deliverable too broad to act on or too narrow to rely on.

The Opinion Itself

A standard FTO opinion includes the defined product or process, the patents and applications reviewed, the methodology by which they were identified, claim charts comparing the relevant claim elements to the analysis subject, conclusions expressed as risk levels for each material patent, and caveats including the as-of date, jurisdictions, product assumptions, search limitations, and technical inputs relied upon.

The comparison should address more than literal infringement. A product that avoids the literal language of a claim may still infringe under the doctrine of equivalents, and an opinion that does not reach that question — or that expressly scopes it out — should say so. Where the prosecution history narrows a claim element, prosecution history estoppel may limit the range of equivalents available, which is itself a reason to review file histories for the patents that matter.

Opinion Strength, Willfulness, and Waiver

Opinion strength matters. An informal memo from in-house counsel is different from a formal written opinion from independent outside counsel. A formal opinion may help rebut willfulness allegations by showing that the company acted with a reasonable basis for believing it did not infringe, or that the asserted patent was invalid or unenforceable.

Since Halo Electronics, Inc. v. Pulse Electronics, Inc., 579 U.S. 93 (2016), enhanced damages under 35 U.S.C. § 284 rest on the district court’s discretion and are reserved for egregious cases of misconduct. The Court framed the inquiry around subjective culpability, which it said is “generally measured against the knowledge of the actor at the time of the challenged conduct.” That framing is what makes timing decisive: an opinion obtained before launch and actually relied on speaks to the state of mind at issue, while an opinion obtained after a complaint is filed does not.

But the opinion is not a litigation immunity device. A company that relies on advice of counsel to defend against willfulness waives privilege over that advice and over related communications on the same subject matter. Federal Circuit law frames the outer bounds of that waiver — see In re EchoStar Communications Corp., 448 F.3d 1294 (Fed. Cir. 2006), and In re Seagate Technology, LLC, 497 F.3d 1360 (Fed. Cir. 2007) (en banc), the latter holding that asserting the defense and disclosing opinion counsel’s work does not, as a general proposition, waive privilege as to trial counsel — though courts retain discretion to extend waiver in unique circumstances, such as chicanery. (Halo abrogated Seagate’s two-part willfulness test; it did not address waiver.) The scope of waiver should be managed deliberately at the outset, not discovered for the first time after a complaint is filed.

Two practical corollaries follow.

• There is no duty to obtain an opinion. Under 35 U.S.C. § 298, a company’s failure to obtain the advice of counsel, or its decision not to present that advice to the court or jury, may not be used to prove that it willfully infringed or that it intended to induce infringement. Section 298 applies to civil actions commenced on or after January 14, 2013 (Pub. L. No. 112-274). It means there is no affirmative duty to obtain an opinion; it does not diminish the value of one the company obtained and relied on.

• Protect the opinion once you have it. The opinion should be marked privileged and attorney work product, its distribution should be controlled, and it should not circulate freely to engineering or sales teams. Broad internal distribution is a routine and avoidable waiver risk, and the operative conclusions can be communicated without releasing the full document.

Practical Limits

• The opinion is current as of its date. New patent issuances, application publications, claim amendments, continuation filings, and product changes affect the conclusion.

• The opinion covers identified patents. Unknown patents — including the patent the search did not find, or an unpublished application that later publishes or issues — are not covered, and search completeness has practical limits.

• The opinion primarily analyzes infringement. A patent the FTO flags may still be invalid, unenforceable, licensed, or exhausted, but those conclusions require separate analysis unless expressly in scope.

• The opinion assumes the product as described. Engineering changes after the opinion may move the product into or out of infringement scope.

• The analysis creates a record of knowledge. Reviewing a patent establishes awareness of it, and knowledge of the patent is a predicate for willfulness under § 284 and for induced and contributory infringement under § 271(b) and (c). Section 298 removes any adverse inference from not obtaining an opinion, but it does not erase knowledge the company actually acquired. The answer is not to avoid the analysis. It is to complete it, document the non-infringement or design-around conclusion, and act on it.

• FTO does not address contract or license obligations. A product that does not infringe a competitor’s patents may still violate license terms, open-source obligations, collaboration agreements, NDA restrictions, or field-of-use limitations.

• FTO does not always resolve multi-actor or indirect infringement questions. For software, platforms, protocols, and distributed systems, the analysis may need to address who performs each claim step, whether any party directs or controls another’s performance, and whether inducement or contributory infringement theories are plausible.

Integration Into Product Development

FTO is most valuable when integrated into product development cadence rather than commissioned reactively. A working integration looks like this:

• Concept stage — lightweight FTO scoped to identify obvious blockers.

• Major architecture decisions — updated FTO, deeper scope, focused on the chosen technology path.

• Pre-launch — expanded scope and, where warranted, a formal opinion: the document the business team uses for launch, redesign, licensing, challenge, or proceed-with-risk decisions.

• Post-launch — monitoring through watch services for new issuances, claim amendments, continuations, and competitor portfolio activity.

• Pre-financing or pre-M&A — refresh the analysis before diligence opens.

The output of an FTO should be operational, not merely archival. For each material patent, the business should understand the recommended path: no material risk, monitor, obtain a non-infringement or invalidity opinion, design around, seek a license, challenge the patent, or proceed with defined risk. A useful FTO translates claim analysis into decisions engineering, product, finance, and leadership can act on.

Integrating FTO into the development cycle can also reduce total cost, because it identifies design-around paths while they are still feasible, narrows the scope of later searching, and avoids emergency licensing discussions after launch.

Practice Note

FTO done at the right time and the right scope is a high-leverage IP investment for a product company. FTO done too late, too broadly, or too informally is wasted spend. The point is not simply to “get an opinion.” The point is to place FTO gates where they can still influence architecture, launch timing, licensing strategy, and risk allocation. Companies that map their roadmap’s commitment points — concept freeze, architecture decision, launch approval — and put a gate in front of each one are the ones that still have options when a blocking patent appears.