FTO Best Practices Checklist: A Practical Guide

Pre-analysis checklist

Planning and preparation

• Define the business decision and clear FTO objectives.
• Identify stakeholders, decision owners and escalation authority.
• Allocate proportionate resources: budget, qualified people and time.
• Select qualified internal specialists and external patent counsel where needed.
• Establish a timeline, milestones and review gates.
• Define scope by product or process, planned acts, markets and technologies.
• Document risk tolerance and decision criteria without promising zero risk.
• Establish documentation, version-control and record-management procedures.
• Ask counsel how privilege and confidentiality should be handled; do not assume labels create privilege.
• Communicate the approved plan, scope and limitations to relevant stakeholders.

WIPO’s guide frames FTO as a staged process: define what will be done, where and when; search published patent literature; then analyze claim scope and legal status.¹ For evidence 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 professional review.²

Subject technology definition

• Gather current technical documentation and identify the controlling product version.
• Involve technical experts in defining the subject technology.
• Describe what the analysis includes.
• Describe what the analysis excludes.
• Record technical specifications, operating parameters and intended use.
• Identify claim-relevant technical features, interfaces and innovations.
• Validate the subject-technology definition with technical and decision owners.
• Record the rationale for inclusion and exclusion decisions.
• Create diagrams or feature maps when they make the product easier to search.
• Confirm that stakeholders understand the definition and any unresolved assumptions.

The product definition should capture the what, where and when of the planned activity. WIPO’s FTO tool specifically links this description to keywords, classification symbols, countries, languages and time frames used in the search.³

Patent search in an FTO best practices checklist

Search strategy development

• Develop a search strategy tied to the defined product and jurisdictions.
• Identify technical terms, synonyms, translations and spelling variants.
• Identify functional terms that describe what a feature does.
• Use commercial terms only as supplements to technical searching.
• Identify problem-oriented and result-oriented terms.
• Identify relevant classification symbols, such as IPC and CPC, plus jurisdiction-specific schemes when useful.
• Select databases based on jurisdiction, coverage, legal-status needs and language.
• Define the geographic scope from planned manufacture, import, use, sale and other relevant acts.
• Define any justified date limits without excluding potentially enforceable rights prematurely.
• Record each search string, database, filter, date and rationale.

The EPO provides separate patent-search tools and legal-information resources, including Espacenet and the European Patent Register. Use each source for the question it is designed to answer.⁴ Patsnap’s patent search strategy guide provides a related framework for coordinating keywords, classifications, citations and assignee searches.

Search execution

• Search USPTO Patent Public Search for relevant U.S. patents and published applications.
• Search EPO tools, including Espacenet and the European Patent Register, where relevant.
• Search WIPO PATENTSCOPE for relevant PCT and participating national collections.
• Search the official databases or registers of other target jurisdictions.
• Use Google Patents as a supplemental discovery source, not as proof of complete coverage.
• Combine keyword, classification, assignee, inventor and citation searching as appropriate.
• Review backward and forward citations without assuming they are exhaustive.
• Analyze relevant competitor patent portfolios without limiting the search to known competitors.
• Identify major applicants, owners and patent families within the defined scope.
• Record all searches performed, including unsuccessful searches.
• Record result counts as reproducibility notes, not quality metrics.
• Record the search date and database-update limitations.
• Save review sets and source links in a reproducible format.

USPTO Patent Public Search provides public access to U.S. patents and published applications,⁵ while WIPO PATENTSCOPE supports international and participating national collections.⁶ Google’s own coverage notice says Google Patents cannot guarantee complete coverage and advises prior-art searchers to check non-patent literature.⁷

For source-linked patent retrieval and evidence review across search steps, teams can also use Eureka IP Search. Database convenience does not remove the need to verify critical records and status in official sources.

Search consolidation

• Consolidate results from all search paths.
• Group duplicates and patent-family members while preserving jurisdiction-specific records.
• Organize records by technical relevance and review status.
• Create a master list of patent families and specific rights requiring review.
• Record consolidation, deduplication and family-grouping decisions.
• Identify known coverage gaps, language limits and unresolved status questions.

Preliminary screening checklist

Screening preparation

• Define screening criteria linked to the product, claims, jurisdictions and relevant date.
• Create a consistent screening template.
• Assign records to screeners with appropriate technical and language expertise.
• Train screeners on inclusion, exclusion and escalation rules.
• Establish quality-assurance sampling and second-review procedures.

Screening execution

• Assess technical relevance for each record.
• Verify whether the relevant record is an application, granted patent or other document.
• Check current legal status in the relevant official register; record uncertainty.
• Confirm geographic coverage and relevant family members.
• Review independent and relevant dependent claims; avoid rating claim breadth from the abstract alone.
• Identify the recorded applicant or owner and verify material ownership questions separately.
• Record known enforcement or licensing evidence without inferring future enforcement intent.
• Assign an operational disposition: detailed review, monitor, exclude or escalate.
• State the reason and evidence for each disposition.
• Apply the same criteria across the review set.

Screening quality assurance

• Review a sample of excluded records.
• Review a sample of included records.
• Compare how different screeners applied the criteria.
• Correct errors and document material changes.
• Consolidate the quality-controlled screening results.
• Prepare a screening summary that states scope, methods, limits and unresolved questions.

Detailed analysis checklist

Claim analysis

• Read the claims with the specification, drawings and prosecution or register context needed for interpretation.
• Understand the claimed invention and the purpose of each material limitation.
• Identify each limitation in the relevant independent claims.
• Break complex limitations into reviewable elements without changing their meaning.
• Record relationships and dependencies among elements.
• Identify functional, structural, numerical and process limitations.
• Review relevant dependent claims and claim dependencies.
• Identify claim-construction questions for qualified counsel.
• Record the claim version, jurisdiction, status source and analysis date.
• Document both supporting and contrary evidence.

Claim charting

• Create a claim chart for each material patent and product configuration.
• Map every material claim limitation to product evidence or mark it unresolved.
• Have qualified counsel assess literal infringement where a legal conclusion is required.
• Have qualified counsel assess equivalents or other jurisdiction-specific scope doctrines where relevant.
• Give a reasoned, source-linked explanation for each comparison.
• Identify potential design-around questions without treating them as cleared alternatives.
• Record confidence and the reason for uncertainty.
• Review charts for completeness and consistency.
• Involve technical experts while keeping legal conclusions with qualified counsel.

Claim scope is a legal question. For example, the EPC Protocol on Article 69 rejects both a strictly literal reading and a reading that treats claims only as a guideline; it also requires due account of equivalents.⁸ The governing test varies by jurisdiction.

Validity analysis

• Decide with counsel whether a separate validity or prior-art review is proportionate.
• Define the claims, jurisdiction, grounds and relevant dates for that review.
• Identify prior-art references and verify publication or availability dates.
• Assess novelty under the applicable legal standard.
• Assess inventive step or obviousness under the applicable legal standard.
• Assess enablement, written description or sufficiency only where relevant to the jurisdiction.
• Assess clarity or indefiniteness only under the applicable legal framework.
• Keep validity, unenforceability and noninfringement analyses distinct.
• Record the evidence, assumptions, open issues and counsel review.

In the United States, 35 U.S.C. § 282 presumes each claim valid and lists noninfringement, unenforceability and invalidity as distinct defenses.⁹ Do not merge those concepts into one generic “patent validity” score.

Design-around analysis

• Identify which claim limitations might be changed or omitted.
• Assess technical feasibility with product and engineering owners.
• Estimate implementation cost using current business inputs.
• Assess effects on product function and intended use.
• Assess effects on performance, quality and compliance.
• Assess manufacturing, supplier and schedule effects.
• Document each option and the product version reviewed.
• Prioritize options only after technical, commercial and legal review.

Risk assessment in an FTO best practices checklist

Risk quantification

• Use qualified counsel to assess infringement risk where legal judgment is required.
• Keep patent validity, enforceability and noninfringement as separate questions.
• Record known enforcement, licensing and litigation evidence without predicting intent.
• Apply a documented risk-rating method; do not present a label as a statistical probability.
• State confidence, missing evidence and assumptions for every material rating.
• Document the reasoning and decision owner.

This FTO best practices checklist uses ratings for prioritization and communication, not as numerical predictions of a legal outcome. Define each rating, connect it to evidence and show who approved the resulting decision.

Mitigation strategy development

• Develop options for each material risk.
• Evaluate design-around feasibility, timing and cost.
• Evaluate whether licensing outreach is appropriate with counsel.
• Evaluate whether a validity challenge or defensive position is appropriate with counsel.
• Evaluate risk acceptance only with approved contingency plans and authority.
• Compare options using current technical, legal and commercial inputs.
• Recommend a preferred path and alternatives; do not describe any path as risk-free.
• Record the selected action, owner, deadline and trigger for reassessment.

Documentation checklist

Documentation standards

• Document the approved scope, product version, jurisdictions and relevant date.
• Document search strategies, databases, dates, filters and results.
• Document screening criteria, dispositions and quality checks.
• Document claim analysis and claim charts.
• Document any separate validity review.
• Document design-around analysis and assumptions.
• Document risk ratings and unresolved questions.
• Document mitigation options and business decisions.
• Use consistent terminology and stable identifiers.
• Make limitations and exclusions as visible as conclusions.

Record management

• Maintain an organized matter and evidence structure.
• Maintain version control for product descriptions, searches and reports.
• Follow counsel’s instructions for privilege and confidentiality.
• Limit access according to approved need and organizational policy.
• Apply the organization’s legally reviewed retention schedule.
• Keep records accessible to authorized reviewers.
• Use approved backup, recovery and information-security controls.

Legal opinion checklist

Opinion preparation

• Determine with counsel whether a formal legal opinion is needed.
• Select counsel qualified in the relevant jurisdictions and subject matter.
• Define the opinion’s product, acts, jurisdictions, date and decision purpose.
• Provide complete, current technical and search information to counsel.
• Agree on timeline, review gates and dependencies.
• Agree on budget and scope-change procedures.
• Follow counsel’s privilege and confidentiality instructions.

Opinion review

• Review whether the opinion answers its stated question.
• Check product facts, patent identifiers and cited evidence for accuracy.
• Confirm which patents, claims, jurisdictions and product versions were covered.
• Confirm that scope and limitations are explicit.
• Confirm that assumptions and unresolved facts are explicit.
• Confirm that conclusions are qualified to the stated evidence and date.
• Confirm suitability for the stated business or legal purpose; do not assume uses beyond scope.
• Store and distribute the opinion according to counsel’s instructions.

Post-analysis FTO best practices checklist

Implementation

• Communicate findings, limitations and owners to the approved stakeholders.
• Implement approved product modifications and verify the resulting version.
• Conduct licensing discussions through the appropriate legal and commercial teams.
• Pursue validity or other legal action only on counsel’s advice.
• Accept residual risk only through the approved decision process.
• Record implementation decisions and supporting evidence.
• Update product and FTO records together.

Monitoring and updates

• Define a monitoring process for material patent families and search concepts.
• Monitor newly published applications, grants and relevant family events.
• Monitor known litigation, licensing demands and status changes where relevant.
• Refresh the analysis when product design, supplier, use or market changes.
• Set a risk-based review cadence instead of relying on a universal annual rule.
• Monitor material changes in patent law and enforcement practice.
• Maintain an escalation route to qualified counsel.

Keep the FTO best practices checklist linked to the monitored product version and target markets. An alert matters only when an assigned reviewer can decide whether it changes the prior scope, analysis or action. For teams that need portfolio and legal-event monitoring, Patsnap Analytics provides monitoring tools and legal-status data for review.

Continuous improvement

• Evaluate the FTO process after material decisions or events.
• Identify search, screening, handoff and documentation improvements.
• Assign owners and deadlines for approved improvements.
• Track process metrics that measure timeliness and review quality, not promised legal outcomes.
• Compare decisions and assumptions with later evidence.
• Update procedures based on documented lessons.
• Train relevant teams on approved changes.
• Share reusable practices without disclosing privileged or confidential matter details.

Industry-specific checklists

Software and SaaS

• Route open-source license, copyright and security questions to their separate review workstreams.
• Assess relevant software and computer-implemented-invention patent claims.
• Assess method, platform, interface and data-processing claims tied to actual product functions.
• Assess user-interface and design-right issues separately where relevant.
• Assess algorithm, model, training, inference and data-flow features in scope.
• Assess cloud architecture, deployment location and third-party infrastructure.
• Assess integrations, APIs and customer-configured uses.

Hardware and consumer electronics

• Assess semiconductor and component-level patent risks.
• Assess wireless, connectivity and standards-related patent issues.
• Assess design-patent or registered-design risks in a separate visual-clearance workstream.
• Assess manufacturing processes and supplier responsibilities.
• Assess integration among modules, firmware and accessories.
• Assess user-interface implementations.
• Assess accessories, replacement parts and peripherals.

Medical devices and pharmaceuticals

• Assess composition-of-matter and active-ingredient claims.
• Assess method-of-treatment, use and dosing claims under applicable law.
• Assess formulation, delivery and combination claims.
• Assess manufacturing, purification and quality-control process claims.
• Assess device design and component claims where relevant.
• Check patent-term adjustment, extension or supplementary protection where relevant.
• Coordinate patent review with the regulatory timeline while keeping regulatory approval distinct from patent clearance.

Conclusion

This FTO best practices checklist supports thorough, consistent and reviewable work without treating completeness as a guarantee. It can help teams reduce avoidable search gaps, maintain consistent records, make limitations visible and route legal questions to qualified counsel.

Use the checklist for each FTO project, then tailor it to the product, markets, industry and decision. Update it when the product, relevant claims, legal status, jurisdictions or intended commercial acts change.