Beyond Yes or No: How a Reviewable FTO Analysis Works

An engineering team asks, "can we launch?" The answer comes back as yes, no, or a colour-coded risk label.

The label is concise and hard to use, because the team cannot see:

• which product configuration, activities, and markets were assessed;
• which patents and claims drove the concern;
• how product evidence was mapped to each claim element;
• what was excluded or remains uncertain; and
• what change would trigger another review.

This is the FTO black box. The problem is not that a conclusion exists. It is that the evidence and assumptions needed to review it are missing.

Everything below answers one of these. They also work as a checklist against any FTO output, including one you did not produce.

1. What exactly was assessed, and as of when?
2. How were candidates found, and what was left out?
3. Why did each candidate stay in or drop out?
4. For the claims that mattered, what product evidence supports each element?
5. Who owns the next step, and what would trigger a reassessment?

1. Define the subject, activities, markets, and assumptions

FTO is territorial and fact-specific. Before searching, define the subject and the decision the work has to support.

A usable scope statement records the product, process, or planned activity and which configurations are included; the relevant commercial activities, such as manufacturing, importing, offering for sale, selling, or using; the target countries or regions; the review date or planned launch window; and the suppliers, components, assumptions, exclusions, and open questions that may affect the analysis.

Translate the product into a technical description that legal, engineering, and product teams can review together. Identify the essential features, relevant variants, component relationships, and evidence sources. State what is outside the analysis. If the product is still changing, identify the work as an early screen rather than a final clearance opinion.

Patent rights are territorial. A right that matters in one market may have no enforceable counterpart in another, and status changes over time. The same product can therefore need different analysis across jurisdictions and dates.

2. Search for potentially relevant rights

Build search routes around the defined product and activities. Relevant routes may include technical and functional terms, classifications, citations, patent families, applicants, inventors, and target jurisdictions.

The objective is not to collect every document that sounds similar. It is to identify rights whose claims may warrant comparison with the product being assessed.

Record the databases, jurisdictions, dates, legal-status sources, terms, classifications, and exclusions used. That record is what lets a later reviewer understand why a candidate entered or left the analysis.

3. Screen candidates without hiding uncertainty

Screening narrows the set before detailed claim work. For each candidate:

• Is the technical subject relevant to the product?
• Is there a family member in a target jurisdiction, and what is its available legal-status information?
• Do the claims warrant element-level comparison?
• Is the available evidence enough to exclude it, or should it stay for deeper review?

Preserve the reason for each decision. Labels such as include for claim review, exclude with reason, monitor, or status uncertain make the screening record inspectable. They are not infringement conclusions.

4. Map claim elements to product evidence

Claim charting breaks a selected claim into its required elements and connects each element to evidence about the product.

Two disciplines keep the chart honest.

Uncertain is a result. A chart containing only yes and no has usually forced its borderline calls. Those are the calls a decision-maker most needs to see.

An empty cell is missing evidence, not a missing element. Product documentation is often incomplete, and reading a blank as absence is a straightforward route to a confident wrong answer.

Claim interpretation and infringement standards depend on the applicable jurisdiction and facts. Concepts such as equivalents are not a universal checklist. They require qualified legal analysis in the relevant market.

5. Frame options and assign accountable review

The output should connect the evidence to the decision at hand. Depending on the facts and professional advice, the team may need to improve the product evidence or refine the defined scope; change a feature or investigate a design-around; monitor a pending application, reassess changing legal status, or explore a licence; or carry out further validity or claim-construction work with qualified counsel and record the resulting decision.

Name who owns each next step, and which changes or assumptions would trigger reassessment. An analysis that ends without those two lines has not finished.

A relevance score says a patent looks similar. A claim chart shows which element is being compared, what product evidence exists, and where the comparison is still uncertain.

That distinction matters in both directions. A product can be technically similar to a patent without every required element being identified. It can also look different at a high level while one particular claim still warrants deeper analysis.

A useful chart therefore supports three separate conversations: with engineering, about whether the product description is accurate and what evidence backs each feature; with patent review, about how the claim language should be read in the relevant jurisdiction; and with the business, about which options remain practical before design freeze, launch, or expansion.

Eureka IP Search starts from a natural-language product description. It structures technical features, builds search routes, and organises potentially relevant claims into claim-level comparisons with legal-status context. The supporting documents remain available to open.

The workflow supports the record described above. It does not produce a clearance. Claim construction, validity, equivalents, and infringement determinations depend on jurisdiction and facts, and belong with qualified professionals.