1. Freeze the Product Version, Jurisdictions, and Project Scope
Before searching begins, the team needs to define exactly what is being analyzed: which product, which version, which functions, and in which countries it will be manufactured, imported, sold, offered for sale, or used.
This is not administrative housekeeping. FTO is territorial and claim-specific. WIPO’s FTO guidance emphasizes identifying patents or applications that may cover the contemplated product or method, confirming whether rights are in force in the relevant jurisdiction and time period, and analyzing the claims that define those rights.
If the product is not yet frozen, an early directional screen can still be useful. But the report should identify the version reviewed, the information available at the time, and the assumptions used. Early-stage results should not silently migrate to a later production version.
At the same stage, the project should identify who approves the budget, who supplies technical information, who answers engineering questions, who receives and reviews the report, and who ultimately makes the business decision.
2. Appoint a Stable Technical Contact and Verify Product Facts
FTO analysis depends on facts that often sit with engineering rather than legal. Drawings, software flows, component relationships, supplier documentation, BOM information, testing materials, and version changes need a stable owner who can coordinate answers.
Engineering should not appear only when the report is nearly complete. Whether data is processed locally or in the cloud, whether two parts merely sit near one another or are functionally connected, and how a supplier module actually operates can all change a claim mapping.
If the existing materials do not show whether the product includes a claim limitation, the correct record is often “not confirmed from current materials,” not “feature absent.” That factual gap is itself part of the FTO conclusion.
3. Break the Product into Searchable Technical Modules
A market-facing product name is useful as an entry point, but it rarely defines a complete search scope. The product should be decomposed into structures, control relationships, process steps, software functions, and key components that can actually be searched and compared against patent claims.
Not every BOM item deserves the same search depth. Proprietary, difficult-to-substitute features that drive product differentiation and sales generally deserve more resources.
For standard parts or mature purchased components, the first questions may instead concern the supplier, model number, source of rights, license scope, indemnity terms, and practical alternatives.
A supplier’s willingness to sell a component does not automatically establish that the brand owner, importer, or seller has all necessary rights to implement it. A supplier license may be limited by act, territory, customer, or other conditions, and contractual indemnity can also be limited.
4. Search Iteratively—and Keep a Search Record
Once the technical scope is defined, formal searching begins. For each module, the search strategy should include keywords, synonyms, broader concepts, relationship terms, and relevant patent classifications.
The first search is rarely the last. Relevant documents supply better terminology, CPC classifications, assignees, family members, and backward or forward citations that should feed into the next round.
The USPTO’s 7-Step U.S. Patent Search Strategy Guide was designed for prior-art searching rather than FTO, so the purposes are different. But its search discipline is useful: identify core concepts and alternative terms, search keywords, study relevant documents, expand through classifications, and record the databases, search dates, classifications, and results.
If the first-round result set is unexpectedly small, the problem may be narrow concepts, unsuitable terms, classification choices, or a genuinely sparse field. If results are large but concentrated in one path, the team should ask whether that reflects the technology or a blind spot in the search design.
5. Screen Results and Verify Legal Status and Patent Families
Clearly irrelevant documents can be removed. Documents shown by a database as expired, abandoned, or lacking rights in the target jurisdiction can receive lower priority—but only after official status, family members, continuations, and the planned implementation date are checked.
Patent status is not a permanent label. Applications can continue, be abandoned, revive, or produce later family members. Patents can change status through fees, term, disclaimer, or invalidity proceedings. WIPO’s FTO materials caution that legal status is dynamic and that the timeliness and accuracy of status information directly affect the conclusion.
For U.S. matters, Patent Center can be used to check application status and the public file record.
For the patents that survive screening, start with the claims—not the title or abstract. A patent can have a product-facing title but claims that do not reach the target product; another can look remote by title while a claim captures a core structure or control relationship.
6. Build a Claim Chart and Close Product-Fact Gaps
For the priority claims, each necessary limitation should be separated and mapped against the corresponding structure, step, location, function, or relationship in the product.
Where current materials support the mapping, identify the evidence source. Where a feature may correspond, state the conditions and assumptions. Where the product appears different, explain the technical difference. Where information is insufficient, record the gap rather than guessing.
If the product, under a reasonable interpretation, lacks one required limitation, that can support exclusion of literal infringement for that claim. But an internal claim chart should not automatically convert that observation into an absolute non-infringement conclusion. Product facts may be incomplete; claim construction may remain disputed; and further legal analysis may still be required.
7. Convert the Mapping into Risk Analysis and Action Options
Only after the priority claims have been mapped can a more complete risk assessment be made.
High, medium, and low can be useful communication labels, but each rating should be tied to concrete reasons. Risk may arise because claim coverage appears close, a term has a plausible competing interpretation, product facts are incomplete, legal status is uncertain, or there is not yet a strong invalidity position.
The report should also consider what can actually be done: design around, license, investigate validity, change a product version, change a supplier, or reconsider a target market.
A small product change is not automatically an effective design-around. The question is whether the changed product avoids one or more required limitations of the relevant claim—and whether other claims or legal issues remain.
8. Review, Deliver in Layers, and Define Update Triggers
Before formal delivery, the draft should undergo an internal review that checks not only the legal and technical analysis, but also the product version, claim version, legal status, evidence sources, citations, search cutoff date, assumptions, and consistency of the written conclusions.
A mature deliverable is usually layered. Management needs the major risks, business impact, and available options. Legal teams need the full basis, assumptions, scope limits, and analysis. R&D needs to know which structures, process steps, or product facts require attention.
An executive summary, substantive analysis, and detailed claim charts serve different audiences. Compressing everything into a one-page conclusion is rarely enough; forcing management to extract decision points from dozens of pages of technical analysis is not useful either.
An FTO Report Has a Cutoff Date—not an Expiration-Free Life
An FTO project can be completed as of an agreed search cutoff date, but that does not make its conclusions permanent.
Product redesigns, supplier or key-module changes, new software functions, added target countries, issuance of a high-interest pending application, or significant changes in the claims or status of a target patent may all justify an update.
For highly relevant pending applications and priority patents, a company may choose post-report monitoring based on the product lifecycle and risk level. But continuing monitoring should be separately defined in the engagement scope. If monitoring is not included, the report should clearly state its cutoff date, applicable product version, and the conditions that should trigger a refresh.
The Eight-Step FTO Workflow
- Define the product version, target jurisdictions, and project scope.
- Appoint a technical contact and collect and verify product information.
- Break the product into technical modules and design the search strategy.
- Search iteratively and retain the search record.
- Screen results and verify legal status and patent-family relationships.
- Build claim charts and close product-fact gaps.
- Form the risk assessment, response options, and analytical boundaries.
- Complete internal review and layered delivery, and define update triggers.
The purpose is to align product facts, enforceable patent rights, and business decisions step by step. Search volume alone does not make the result usable.
The Takeaway
A useful FTO is not simply a list of patents and it is not a report that can be detached from the product version indefinitely.
Clear scope, complete product facts, traceable evidence, reviewable analysis, and explicit update conditions are what make an FTO capable of supporting a real business decision.