FTO decision tree: when to conduct an analysis

WIPO describes FTO work as searching and analyzing patent documents to assess whether inventions may be protected by enforceable patents or may be in the public domain; its training guide expressly distinguishes an informal technical report from a legal opinion.¹ For search preparation, Eureka FTO Search builds and refines strategies from a product description, screens potentially relevant claims with legal-status context and organizes claim-level comparisons for review.²

Question 1: how crowded and enforcement-sensitive is the field?

Assessing product and market risk

Question 2: what is the business impact?

• High impact: core product, major launch, financing or transaction dependency, difficult redesign, or significant interruption exposure → broader review and senior decision ownership.
• Moderate impact: meaningful revenue or strategic value with feasible alternatives → staged search, claim review and documented mitigation.
• Lower impact: limited deployment or reversible pilot → focused screening may be proportionate, with clear limits and stop conditions.

Use company-specific exposure, not universal revenue thresholds. A low sales forecast does not eliminate injunction, redesign, customer or diligence risk.

Question 3: where will potentially infringing acts occur?

• Single jurisdiction: examine relevant rights, status and acts in that jurisdiction.
• Several jurisdictions: prioritize markets and supply-chain locations, then document what was and was not covered.
• Multi-region launch: coordinate jurisdiction-specific searches and legal review; do not label one database search a “global clearance.”

Patent protection is territorial, so the market, manufacturing, import, use and sale footprint matters.³

Question 4: how complex is the product architecture?

• Focused technology: map the principal claim-relevant features and interfaces.
• Multi-component product: divide the product into modules, suppliers, standards and use cases.
• Cross-domain or emerging system: add specialists and search each technical layer without assuming that “AI,” “software” or another broad label defines the scope.

Question 5: what does the competitive landscape indicate?

• Known assertion or licensing activity: prioritize the relevant owners, families and claims while keeping the broader search open.
• Known portfolios but limited enforcement evidence: use a standard claim-focused review and monitor changes.
• Little visible activity: verify coverage and legal status before reducing scope; absence of a known dispute is not evidence of freedom to operate.

Question 6: do regulatory, contractual or diligence processes affect the deliverable?

• Yes: identify the exact requirement, decision maker and required form of opinion or evidence.
• No express requirement: continue based on patent exposure and business risk.

Question 7: what risk tolerance has the decision owner approved?

• Low tolerance: broader scope, independent legal review and defined monitoring.
• Moderate tolerance: staged work with escalation when relevant claims or status questions appear.
• Higher tolerance: focused work may be accepted only after limits, assumptions and possible consequences are documented.

Determining analysis type, resources and timing

Question 8: what decision must the analysis support?

Design-around analysis begins with the material claim limitations and considers whether a technically and commercially feasible change can avoid the identified issue. It should not assume that a narrow claim or prior-art reference automatically removes risk.

Question 9: internal, external or hybrid resources?

• Internal screening: appropriate for product decomposition, search preparation, landscape triage and evidence organization when the team has the required expertise.
• External counsel: appropriate when a legal opinion, claim interpretation, infringement assessment, validity strategy, international coordination or response to an assertion is required.
• Hybrid approach: internal technical and search teams prepare the evidence; counsel defines legal scope, reviews material claims and advises on decisions.

Question 10: what does the decision timeline allow?

• Urgent decision: define a narrow interim screen, identify what remains open and set a mandatory follow-up before irreversible launch steps.
• Planned decision: sequence product decomposition, search, family/status review, claim charting and counsel review.
• Longer program: add design iterations, supplier coordination and continuing monitoring.

Do not promise a universal number of weeks. Timing depends on product complexity, jurisdictions, evidence quality, claim volume, language and the type of legal opinion required.

FTO decision tree: quick-reference matrix

This matrix is a triage aid, not a scoring model. A single material patent or legal event can justify escalation even when other factors appear limited.

FTO decision tree: post-analysis decisions

What did the FTO work reveal?

• No material risk identified within the searched scope: continue only with the report’s limits visible; verify critical dates and status, establish monitoring and refresh before material changes.
• Lower-priority references: document why they were deprioritized, monitor relevant families and preserve contingency options.
• Claims requiring further review: obtain claim interpretation, assess product evidence, check status and prosecution history, and compare design-around, licence and validity routes.
• Material blocking risk: escalate to counsel and decision owners before launch, manufacturing or another irreversible commitment.

Because patent applications, grants, legal status and ownership can change, Eureka IP Search can organize source-linked patent evidence and legal-status context for review and later monitoring.⁴ Monitoring supports reassessment; it does not replace legal analysis.

What mitigation strategy should be evaluated?

• Design-around: evaluate claim limitations, technical feasibility, performance, cost, schedule and new risks.
• Licence or acquisition: identify the owner, confirm authority and negotiate scope, territory, field, term and economics. Government guidance likewise treats licensing or purchase as routes for using another party’s patent.⁵
• Validity challenge: assess available grounds, evidence, forum, cost, timing and the consequence of an unsuccessful challenge with counsel.
• Risk acceptance: require an authorized, documented business decision based on legal advice; do not reduce it to enforcement probability alone.
• Delay, narrow or exit: consider changing launch timing, jurisdictions, features or commercial route when mitigation is not acceptable.

What ongoing monitoring is needed?

• Closer monitoring: material products, fast-changing portfolios, pending claims, standards activity or known assertion behavior.
• Scheduled monitoring: stable products with relevant families or periodic market changes.
• Trigger-based monitoring: lower-impact products, with reassessment tied to redesign, new markets, supplier changes, notices, acquisitions or licensing events.

FTO decision tree: real-world examples

Example 1: software startup with an AI product

• Multiple technical layers, a multi-region launch and important financing or partnership decisions increase the consequence of an incomplete screen.
• Decision: decompose the product, prioritize jurisdictions and higher-risk functions, use specialist search support and obtain counsel-led claim analysis before launch commitments.

Example 2: hardware company with a consumer product

• Several components, suppliers and major sales markets call for a staged review rather than a single undifferentiated search.
• Decision: use a hybrid approach: internal teams map features and supplier evidence; external counsel reviews material claims and jurisdiction-specific questions.

Example 3: small company with a niche product

• A narrow product and one initial market may justify a focused first stage, but limited resources and few known competitors do not establish freedom to operate.
• Decision: document the product definition and search scope, escalate any relevant claims, and schedule reassessment before expansion or redesign.

Conclusion

This FTO decision tree helps teams choose a proportionate starting point based on product scope, jurisdictions, technical complexity, business impact, known rights, resources and timing. The key is to preserve the assumptions and escalation triggers behind the decision.

Sources and verification

1. WIPO, Identifying Inventions in the Public Domain: A Guide for Inventors and Entrepreneurs. Accessed July 31, 2026.
2. Patsnap Eureka, IP Search and FTO Search. Accessed July 31, 2026.
3. WIPO, Launching a New Product: Freedom to Operate. Accessed July 31, 2026.
4. Patsnap Eureka, source-linked patent search and legal-status context. Accessed July 31, 2026.
5. UK Intellectual Property Office, Using Somebody Else’s Intellectual Property: Patents. Accessed July 31, 2026.

This article provides general information and a scoping framework, not legal advice or an FTO opinion. Patent scope, infringement, validity, remedies and procedural options vary by jurisdiction and should be reviewed by qualified counsel.