Book a demo

FTO Templates and Forms: Six Practical Worksheets

FTO Documentation

FTO templates and forms help teams document patent searching, screening, claim charting, risk review, and business decisions consistently.

Effective freedom-to-operate work requires more than a final risk label. Teams need a record of what was searched, what was excluded, how claims were mapped, which assumptions were used, and who reviewed the result. The six worksheets below can be copied and adapted to a product, jurisdiction, decision stage, and counsel-approved process.

These FTO templates and forms organize evidence; they do not guarantee completeness, establish privilege, or create a legal opinion. WIPO’s FTO Tool 5 describes its process as a preliminary determination and recommends qualified professionals for more extensive searching and the legal analysis required before committing to a specific design path.[1]

For additional context, see the related five-step FTO analysis process, which follows the work from technology definition through risk review.

Template 1: Patent Search Plan

Purpose: Document the planned scope and search strategy before execution so another qualified reviewer can understand and, where appropriate, reproduce the work.

The related patent search strategy guide provides additional context for combining terminology, classifications, citations, and multiple sources.

For teams organizing an assisted search, Patsnap Eureka FTO Search builds and refines search strategies from a product description, screens potentially relevant claims with legal-status context, and organizes claim-level comparisons for review.[3] The form below remains useful for recording scope, assumptions, review ownership, and decisions outside the tool.

Patent Search Plan

Project name: ____________________

Product or technology: ____________________

Date prepared / prepared by: ____________________

Search objectives

  • Identify potentially relevant patent families and claims
  • Identify relevant rights holders and ownership questions
  • Understand the patent context for the defined product
  • Surface possible design-around questions for technical and legal review
  • Other: ____________________

Subject technology definition

Technology description: ____________________

Feature 1 / Feature 2 / Feature 3: ____________________

Included scope: ____________________

Excluded scope and rationale: ____________________

Product versions and optional features: ____________________

Search terms and classifications

Technical terms and synonyms: ____________________

Functional terms: ____________________

Commercial or industry terms: ____________________

Problem-oriented terms: ____________________

IPC / CPC / relevant local or legacy classifications: ____________________

Sources and geographic scope

Target countries or regions: ____________________

Manufacturing, sale, use, offer-for-sale, and import locations: ____________________

Date scope and rationale: ____________________

Execution, consolidation, and review

Search 1 — source / query / filters / date / result count: ____________________

Search 2 — source / query / filters / date / result count: ____________________

Additional searches: ____________________

  • Forward and backward citations reviewed where useful
  • Patent families consolidated
  • Duplicates removed without losing family or status context
  • Coverage gaps and search limitations recorded

Planned effort, timing, and resources: ____________________

Prepared / reviewed / approved by and date: ____________________

Template 2: Preliminary Screening Form

Purpose: Record an initial relevance and status screen so potentially important rights move to detailed analysis and exclusions remain reviewable.

Preliminary Screening Form

Publication / application / patent number: ____________________

Title and patent family: ____________________

Applicant, owner, and ownership source/date: ____________________

Priority, filing, publication, and grant dates: ____________________

Screener / screening date / technology area: ____________________

Screening criteria

Technical relevance: □ High □ Medium □ Marginal □ Not apparent

Relevant product features and passages: ____________________

Current status by jurisdiction: □ Pending □ In force □ Expired/lapsed □ Abandoned/revoked □ Uncertain

Status source and verification date: ____________________

Target-market coverage: □ All defined markets □ Some defined markets □ None identified □ Uncertain

Claim-review note: □ Potential element overlap □ No overlap apparent at screen stage □ Counsel review needed

Evidence of enforcement or licensing activity, if relevant and verified: ____________________

Avoid profile-based assumptions: company size, “NPE” status, or silence about enforcement does not by itself establish whether a right will be asserted.

Screening decision

□ Detailed review — priority to be assigned with rationale

□ Monitor pending claims or status

□ Exclude from current scope, with documented reason

Rationale, assumptions, and reviewer: ____________________

Template 3: Claim Charting Template

Purpose: Among the FTO templates and forms, this worksheet maps each limitation of a selected claim to product evidence and identifies questions for technical and legal review.

WIPO’s current FTO toolkit recommends checking legal status and using a claim chart to compare claims.[1] A chart is an evidence-organizing tool, not an infringement ruling.

Claim Charting Analysis

Patent / family / jurisdiction / current status: ____________________

Claim number and complete claim text: ____________________

Product name, version, configuration, and analysis date: ____________________

Analyst and reviewers: ____________________

Claim-element mapping — repeat for every limitation

Exact claim limitation: ____________________

Product feature or evidence: ____________________

Source document / drawing / test / version: ____________________

Provisional mapping: □ Present □ Not apparent □ Uncertain □ Not assessed

Reasoning and open questions: ____________________

Claim-construction or equivalents issue for counsel: ____________________

Overall review

Literal-overlap assessment: □ Potential overlap □ No overlap apparent □ Uncertain □ Counsel review pending

Equivalents analysis: □ Not assessed □ Counsel review pending □ Counsel conclusion recorded separately

Key assumptions, missing evidence, and confidence: ____________________

Potential design alternatives for review: ____________________

Technical / legal review and date: ____________________

Template 4: Risk Assessment Matrix

Purpose: Summarize distinct risk dimensions and evidence so decision-makers can prioritize next steps without turning a score into a legal conclusion.

Risk Assessment Record

Project / patent family / assessment date / assessor: ____________________

DimensionEvidence to recordProvisional labelNext reviewer
Potential claim overlapClaim chart, product evidence, assumptions, unresolved constructionHigher / medium / lower / uncertainPatent counsel and technical reviewer
Legal status and territoryCurrent official source, verification date, family member, target marketRelevant / not currently relevant / uncertainQualified status reviewer or local counsel
Validity questionSpecific prior art and legal ground; no presumption from a quick searchIssue identified / none identified / not assessedPatent counsel
Verified enforcement contextPublic proceedings, licensing demand, or other sourced evidenceEvidence present / none located / not assessedLegal and business team
Business exposureProduct dependency, market timing, alternatives, financial assumptionsMaterial / manageable / limited / uncertainBusiness owner

Do not combine the labels mechanically. Validity, infringement, status, enforcement evidence, and business exposure are separate questions. Record who set the decision threshold and why.

Overall decision direction and rationale: ____________________

Mitigation options: □ Design review □ Licensing inquiry □ Additional search □ Validity analysis □ Monitor □ Other

Cost/timing assumptions and source: ____________________

Assessed / reviewed / approved by and date: ____________________

Template 5: Decision Record Form

Purpose: This section of the FTO templates and forms records the decision, evidence considered, assumptions, responsible owners, and review pathway.

FTO Analysis Decision Record

Product / version / target markets / decision date: ____________________

Decision owner and participants: ____________________

Decision summary

  • Proceed to the next development stage, subject to stated conditions
  • Proceed with design modifications and re-review
  • Explore licensing or other permission
  • Delay or narrow the planned activity
  • Change technology or market strategy
  • Other: ____________________

Analysis summary

Search scope, dates, and limitations: ____________________

Families reviewed / monitored / excluded: ____________________

Key claim-chart and status findings: ____________________

Legal conclusions, if any, and issuing counsel: ____________________

Decision rationale

Business factors: product value, timing, alternatives, strategic importance

Legal factors: potential overlap, status, validity questions, verified enforcement context

Financial factors: sourced assumptions for search, redesign, licensing, delay, and dispute response

Approved risk thresholds and escalation triggers: ____________________

Alternatives considered and why not selected: ____________________

Contingency and implementation

If a right is asserted: ____________________

If redesign or licensing becomes necessary: ____________________

Actions / owners / dates / dependencies: ____________________

Monitoring events and review dates: ____________________

Decision / legal / business / technical sign-off: ____________________

Template 6: FTO Analysis Checklist

Purpose: Confirm that required workflow steps were considered and document any intentional omission. Completion does not prove that a search or legal analysis is complete.

Pre-Analysis Phase

Planning and preparation

  • Objectives, decision stage, target activities, countries, products, and versions defined
  • Stakeholders, decision owners, technical reviewers, and qualified legal resources identified
  • Resources, milestones, risk thresholds, escalation criteria, and record procedures approved
  • Confidentiality and privilege protocol defined with counsel; access restricted accordingly

Subject technology definition

  • Technical documents, drawings, configurations, optional features, and variants gathered
  • Included and excluded features recorded with rationale
  • Technical experts validated the description and unresolved assumptions

Patent Search Phase

Strategy and execution

  • Technical, functional, commercial, and problem-oriented terms recorded
  • IPC, CPC, and relevant local or legacy classifications considered
  • Sources, target markets, date scope, filters, queries, search dates, and result counts documented
  • Keyword, classification, citation, family, applicant, and inventor approaches used where justified
  • Search limitations, language gaps, status gaps, and unsearched sources identified

Consolidation

  • Families consolidated and duplicates handled without losing relevant status context
  • Results organized by documented relevance criteria
  • Master list, exclusions, and coverage gaps retained for review

Preliminary Screening Phase

  • Screening criteria, reviewer instructions, and quality-review method documented
  • Technical relevance, family, owner, target-market coverage, and current status verified
  • Claim relevance kept provisional until detailed review
  • Included and excluded records sampled or reviewed under the agreed quality process
  • Decisions, evidence, uncertainty, and escalation rationale recorded consistently

Detailed Analysis Phase

Claim analysis and charting

  • Complete claims and relevant specification, drawings, file history, and dependent claims reviewed as needed
  • Each limitation mapped to version-specific product evidence
  • Structural, functional, relational, and claim-construction questions recorded
  • Equivalents and other jurisdiction-specific issues reserved for qualified legal review
  • Technical and legal reviewers, dates, assumptions, and confidence recorded

Validity analysis, when commissioned

Validity searching is a separate task from FTO claim screening. Where counsel directs a prior-art review, Patsnap Eureka Novelty Search extracts technical features, builds multiple search strategies, and compares prior art feature by feature for human review.[3]

  • Specific claims and legal grounds defined by counsel
  • Prior-art search scope, references, dates, and limitations documented
  • Novelty, obviousness or inventive step, enablement, written description, and definiteness addressed only where applicable. For U.S. patents, written description and enablement are addressed in 35 U.S.C. § 112(a), while definiteness is addressed in § 112(b).[4]
  • No quick-search result treated as a final validity conclusion

Design-around analysis

  • Candidate changes tied to specific claim limitations
  • Technical feasibility, performance, cost, timing, and new dependencies assessed
  • Revised design returned for claim and legal review

Risk Assessment and Mitigation Phase

  • Claim overlap, status, territory, validity questions, enforcement evidence, and business exposure recorded separately
  • Confidence and missing evidence documented for each dimension
  • Design review, licensing, further searching, monitoring, challenge, and acceptance options evaluated under approved criteria
  • Costs and timelines labeled as sourced estimates or internal assumptions
  • Preferred action, owner, conditions, and escalation events approved

Documentation and Record Management Phase

  • Search, screening, claim charts, status evidence, legal advice, business decisions, and mitigation records organized
  • Consistent naming, version control, access controls, retention rules, and authorized backups applied
  • Privilege and confidentiality handled under counsel-approved procedures; labels alone not treated as creating protection
  • Distribution limited to authorized recipients with a documented need

Legal Opinion Phase, If Applicable

  • Need, scope, jurisdiction, counsel, assumptions, products, rights, timing, and budget defined
  • Relevant information and contrary evidence supplied to counsel
  • Opinion reviewed for stated scope, assumptions, limitations, and conclusions
  • Use, distribution, retention, and privilege handled as counsel directs

Post-Analysis Phase

Implementation and monitoring

  • Approved findings communicated to authorized stakeholders
  • Design, licensing, filing, market, or monitoring actions assigned and tracked
  • Review refreshed when product design, claims, ownership, legal status, markets, supply chain, or law materially changes
  • Monitoring scope and cadence set according to risk and counsel guidance rather than a universal annual rule

Continuous improvement and sign-off

  • Process gaps, search misses, inconsistent criteria, and lessons recorded
  • Procedures, training, and quality checks updated where approved
  • Completed / reviewed / approved by and date: ____________________
  • Notes, limitations, and open actions: ____________________

How to Use These FTO Templates and Forms

Customize FTO Templates and Forms

Add or remove fields based on the product, target jurisdictions, decision stage, legal advice, and organizational controls. Preserve definitions and version labels so records remain comparable over time. Do not simplify away assumptions, exclusions, status dates, or reviewer ownership.

Integration

Use the FTO templates and forms at the workflow stages where each record answers a distinct review question:

  • Use the search plan before executing searches.
  • Use the screening form during initial triage.
  • Use the claim chart only after selecting claims for detailed review.
  • Use the risk record to keep legal and business dimensions separate.
  • Use the decision record to document an approved course of action.
  • Use the checklist to record completed, omitted, pending, and escalated steps.

Documentation for FTO Templates and Forms

Maintain controlled records with consistent naming, version history, source dates, permissions, retention rules, and review ownership. Ask counsel how privilege and confidentiality should be handled in the relevant jurisdiction and organization; marking a form “privileged” does not by itself create protection.

Conclusion

These FTO templates and forms provide a practical starting point for consistent documentation. They help teams preserve search logic, evidence, assumptions, review steps, and business decisions without implying that a completed form guarantees exhaustive searching or a particular legal result.

Key takeaway: customize the six worksheets to the defined product, markets, workflow, and counsel-approved review process, and update them whenever the underlying facts materially change.

Legal-information notice: These templates provide general workflow guidance, not legal advice, an infringement opinion, a validity opinion, or a privilege determination. Patent law and professional obligations vary by jurisdiction and facts.

Sources and Verification

  1. WIPO: Using Inventions in the Public Domain—Tool 5, Freedom to Operate
  2. EPO: Espacenet Patent Search
  3. Patsnap Eureka IP Search: FTO and Novelty Search
  4. 35 U.S.C. § 112: Specification

Official guidance and product information verified July 2026. Legal rules, database coverage, status data, and product capabilities may change.

Build a Reviewable FTO Record

Start with a defined product and market scope, then preserve search strategies, status context, claim-level comparisons, assumptions, and review decisions.

Explore Patsnap Eureka FTO Search

Your Agentic AI Partner
for Smarter Innovation

Patsnap fuses the world’s largest proprietary innovation dataset with cutting-edge AI to
supercharge R&D, IP strategy, materials science, and drug discovery.

Book a demo