Part 3: How a Freedom-to-Operate Analysis Actually Works

The Freedom to Operate (FTO) Deep Dive: Questions Your Company Should Be Asking

This is Part 3 of a six-part series on freedom-to-operate analysis.  The series walks through what an FTO is, why it matters, how it works, what to do with the results, how it changes for software, AI, and international products, and the most common ways it goes wrong.  See the full table of contents here. 

Part 3: How a Freedom-to-Operate Analysis Actually Works.

An FTO is only as good as the work behind it.  A one-page conclusory letter and a rigorous limitation-by-limitation analysis can both technically be called “FTO opinions,” but they’re not the same thing, and they don’t provide the same protection.  This post gets into what the analysis actually looks like, how the search works, what claim construction does, and why it’s important, and the two doctrines (doctrine of equivalents and prosecution history estoppel) that determine whether a design-around will hold up.

What Does an FTO Analysis Look Like?

A robust FTO follows a defined process from start to finish.  Each step builds on the one before it, and skipping or shortcutting any of them weakens the final opinion.  The general shape looks like this:

1. Scope Definition. It is important to nail down exactly what product, what version, what features, and what jurisdictions will be analyzed. Although it can be helpful to do an initial search with a rough idea of what the product will eventually look like, a robust FTO needs a clearly defined scope to provide the most value.
2. Search Strategy. Finding the “best” existing patents is foundational to a robust FTO. Missing the key patents will give you an FTO that doesn’t address the patents that you’re most likely to be sued on.  It’s worth layering multiple search strategies, such as classification searches, keyword searches (with synonyms), AI-based searches, citation chains forward and backward from key patents, assignee searches for known competitors and patent assertion entities, and inventor searches.
3. Triage/Sorting. Most hits from the search will be clearly not relevant and can be set aside quickly. The middle tier, where the patents might be relevant, is where the real analytical work begins.  Triage criteria need to be defensible, meaning it is based on whether the claim language plausibly maps to the product’s key functions or structural elements, not just on a subjective sense of how close the patent looks.
4. Claim-by-Claim Analysis. For each potentially relevant patent that is left after triage, walk through every limitation of every independent claim and ask: Does our product do this?
5. Claim Construction. Read the specification and the prosecution history to figure out what the claim language actually means. This is almost never the same as what the words look like they mean on first read.
6. Written Opinion. Document everything: what was searched, what was found, what was analyzed, the conclusions, and the reasoning for each conclusion.

The output is generally organized by patent, by claim, and by limitation, with the factual basis for each non-infringement conclusion stated explicitly.

Why Does Claim Construction Matter?

As with many things legal, patent claims do not always mean what they appear to say.  Patent claims are read in light of the patent specification (the long technical description that comes before the claims) and the prosecution history (the back-and-forth between the applicant and the Patent Office during the time it took to get the patent issued).  Both of those things often narrow the claims compared to what the words of the claim (without context) seem to cover.

A claim that on its face seems to cover your product might, after you read the specification, turn out to require something specific that your product doesn’t have.  Or the prosecution history might show that the applicant told the examiner, “this claim doesn’t cover X,” to get the patent allowed, and your product happens to be X.

This is the part that requires patent expertise to do well.  Someone who just reads the claim and pattern-matches against your product will often get this wrong.

What Is the Doctrine of Equivalents?

The Doctrine of Equivalents (DoE) is a patent-law doctrine that can be used to essentially broaden the scope of the claim.  If your product literally meets every limitation of a claim, that’s “literal” infringement, and the analysis is relatively straightforward.  But it is also possible to infringe a patent claim under the doctrine of equivalents.  Even if your product does not literally meet every limitation, you can still be liable for infringement if it does something “equivalent” to each missing limitation.

The test is whether the substituted element performs substantially the same function, in substantially the same way, to achieve substantially the same result.  This is important because a naive “design-around” that just swaps one functionally identical part for another rarely works.  If your product uses a screw and the claim requires a nail, and the screw and the nail do the same job in the same way to hold the same thing together, you probably haven’t escaped the claim.

What Is Prosecution History Estoppel?

Prosecution history estoppel (PHE) is a patent-law doctrine that limits the doctrine of equivalents.  It applies only when a patentee tries to extend a claim’s reach beyond its literal terms using DoE, and it only restricts that extension.  It does not affect the analysis of literal infringement at all.

Imagine a claim originally said “a fastener” but was amended during prosecution to say “a screw” in order to get over prior art that disclosed a nail.

• If your product uses a screw, you literally infringe.  PHE doesn’t help you here because it only limits DoE, and the patentee doesn’t need DoE to reach you.
• If your product uses a bolt, you don’t literally infringe (because a bolt isn’t a screw).  The patent owner tries to argue that a bolt is an equivalent of a screw under DoE.  PHE blocks that argument because the applicant gave up everything between “screw” and the broader “fastener” when they made the amendment.
• If your product uses adhesive, you don’t literally infringe, and glue is so different from a screw that DoE wouldn’t reach it anyway.  PHE isn’t needed.

The Supreme Court’s Festo decision created a presumption that any amendment narrowing a claim for reasons related to patentability surrenders all equivalents between the original and amended claim language.

This means that the safest design-arounds find limitations that were added or narrowed during prosecution and focuses on those specific limitations.  Avoiding literal infringement of those limitations leaves the patent owner with no DoE fallback, because PHE has already eliminated the equivalents argument.  Mining the prosecution history for these opportunities is one of the highest-leverage things a good FTO opinion does.  The prosecution history often provides the basis for a conclusion that the product does not infringe.

What About Indirect Infringement?

If you make a complete product that infringes a patent, you’re a direct infringer and intent doesn’t matter.  But there are two other kinds of infringement that can come into play, especially for platform and component companies:

Induced Infringement.  This is covered by 35 U.S.C. § 271(b), and it addresses the situation where you encourage or instruct someone else to infringe, for example, shipping a product with documentation that tells customers to use it in an infringing way.

Contributory Infringement.  This is covered by 35 U.S.C. § 271(c), and it addresses the situation where you sell a component that has no substantial non-infringing use, knowing it will be used to infringe.

Both induced and contributory infringement require some level of knowledge or intent.  If your product is a platform that customers can use in lots of ways, some infringing and some not, a robust FTO analysis will cover both “Does our product infringe?” and “Does what we tell customers, or what we know they’ll do, expose us to indirect infringement?”  For SaaS platforms, dev tools, and component suppliers, this is often the more important question.

The mechanics of an FTO are what separate a real opinion from a conclusory one.  The process matters (scope, search, triage, claim-by-claim analysis), but the doctrines matter more: claim construction is where the real legal work happens, doctrine of equivalents is what makes naive design-arounds fail, and prosecution history estoppel is what makes thoughtful ones succeed.  Indirect infringement adds another layer for platforms and components.

Part 4 picks up where this leaves off: the FTO turned up a problem patent.  Now what?