Key takeaways
- Define the product configuration, commercial activity, target markets, timing, and scope before building the search.
- Use the early screen to identify patents that merit deeper claim analysis, not to declare the product cleared.
- Convert the evidence into specific next actions while design, market, and timing choices remain open.
Start with the decision the screen must support
An FTO search is not a general search for patents related to a technology. It starts from defined product activities, jurisdictions, and timing, and identifies patent claims that warrant review in that context. Whether those activities infringe requires further legal analysis.
That makes the first question operational: what decision does the team need to make now?
For an early screen, the answer might be whether to retain a component architecture, investigate an alternative implementation, prioritize one launch market, or escalate a patent for legal review. The purpose is to surface decision-relevant issues while options are still available. It is not to replace a formal legal opinion.
The WIPO Freedom to Operate Toolkit describes a preliminary FTO screen early in product development and further analysis as the product and commercial plan become more defined. That staged approach matters because the subject of the analysis changes with the product.
Build a usable early FTO brief
A product name or broad feature list is not enough. The brief should define five dimensions.
| Brief dimension | What to record | Why it changes the work |
|---|---|---|
| Product configuration | Components, processes, technical relationships, optional variants, and the version being assessed | Different configurations can map to different claim elements |
| Commercial activity | Making, using, selling, offering for sale, importing, supplying, or another relevant activity | The activity helps define which legal questions and product elements require attention |
| Target markets | Countries or regions where the included activities would take place, including relevant manufacture, use, sale, and import locations | Patent rights are territorial, and family members or claim scope can differ by jurisdiction |
| Timing | Intended launch, manufacture, import, or expansion window; search date and date of each material legal-status check | Planned activity dates and evidence-check dates answer different questions; applications, grants, expiries, and status can change |
| Scope boundaries | Included and excluded modules, suppliers, interfaces, workflows, and assumptions | A visible boundary prevents a narrow screen from being mistaken for a product-wide conclusion |
Ask product and engineering owners to confirm the configuration. Ask the commercial owner to confirm the activity, markets, and timing. Record uncertainties instead of silently choosing an interpretation.
Translate the brief into searchable technical features
Break the included configuration into technical elements and relationships that can be searched and later compared with claim language. Retain the terminology used in the product description, but add functional, structural, broader, narrower, and classification-based search routes where technically justified.
Keep the routes connected to the brief. A route should identify which product element or relationship it is testing. If the design includes alternatives, label them separately rather than combining them into one abstract description.
At this stage, distinguish search breadth from legal relevance. Search terms help retrieve candidates. They do not establish whether a claim reads on the product.
Screen candidates in the right legal and commercial context
The first pass should remove clearly irrelevant material and preserve the reasons for retention, exclusion, monitoring, or an unresolved decision. Inspect at least:
- whether the candidate concerns the included product element or activity;
- the relevant family member and jurisdiction;
- the claims that appear to warrant review;
- available legal-status and date information; and
- why the document was retained, excluded, or left uncertain.
Status labels and expiry estimates are useful triage inputs, but they can be incomplete or change. Confirm material records in the relevant official register or with qualified counsel before relying on them for a decision.
The output of screening is a smaller, documented candidate set. It is not a list of patents the product necessarily infringes. Potentially relevant pending applications may require monitoring rather than automatic exclusion. Unpublished applications and incomplete source coverage remain limits to record and revisit.
Map claim elements to the defined product
For each selected claim, record the patent or publication number, jurisdiction, claim number, and the version being reviewed. Compare the full claim, including inherited limitations in a dependent claim, with the defined product evidence. Preserve functional and structural relationships. Keep four things visible:
- the exact claim language;
- the product feature or activity being compared;
- the source evidence supporting the comparison; and
- the reason for a match, difference, or unresolved point.
Do not replace an element-by-element comparison with a similarity score or a single risk label. A claim may contain one apparently similar feature and several elements that require different evidence or interpretation.
This is where the early brief pays off. If the product configuration was vague, the comparison will also be vague. If a design variant was excluded from the brief, the resulting analysis should say so.
Turn the screen into options before design freeze
Summarize the retained patents, mapped claim elements, uncertainties, and scope limits. Then connect each material issue to an owner and a next action. Depending on the facts, options may include:
- investigating a design alternative;
- asking qualified counsel for a deeper claim or validity review;
- evaluating licensing or acquisition options;
- changing a market, supplier, activity, or launch sequence; or
- documenting the current assessment and monitoring later events.
These are team decisions, not automatic product outputs. Record which product version and markets they apply to, and define the trigger for refreshing the work. A design change, new launch market, newly published application, granted patent, or updated legal status can make the earlier screen incomplete.
How the early-screen workflow appears in Eureka
In Eureka FTO Search, a natural-language product description is summarized and broken into technical features. Those features support expanded terms and search routes. Candidate patents can then be screened before reviewers open a technical feature comparison.
The reviewer still needs to confirm the brief, inspect the search scope, verify material legal-status information, and evaluate the claim mapping. Interface labels such as Retained, Equivalent, or Warranting Further Review organize the analysis; they are not legal conclusions. In particular, Equivalent should not be read as a determination of infringement under a jurisdiction’s doctrine of equivalents.
Structure an early FTO screen in Eureka
Open Eureka IP SearchDisclaimer: This article is provided for general informational purposes only and does not constitute legal advice or an FTO opinion. Patent scope, legal status, jurisdiction, product configuration, commercial activity, and timing affect any analysis. Consult qualified counsel before making a legal or commercial decision about a specific product.
