The FTO-Landscape Sequence: Why the Order You Run These Two Searches In Changes the Answer You Get

Introduction

Most companies treat patent landscape analysis and freedom to operate search as separate, independent tools. The landscape is a strategic exercise run by the IP or R&D function when entering a new technology area or reviewing a competitive position. The FTO is a legal exercise run closer to launch — often by in-house counsel or an external IP firm, scoped to the product features that need clearing. The two exercises rarely talk to each other. The landscape team does not brief the FTO team. The FTO scope is set without the benefit of what the landscape revealed. 

This separation is understandable. It is also a source of systematically avoidable FTO errors. The most significant ones — the errors that result in post-launch injunctions, forced redesigns, or expensive licensing negotiations entered from a position of weakness — are not errors of execution. They are errors of scope. The FTO searched in the right places with professional rigour and missed the blocking patent because the blocking patent was in a place the scope did not cover. 

Running a landscape analysis before the FTO — and using the landscape output to scope the FTO — is the structural fix for scope errors. This article explains why, and what the integrated workflow looks like for the corporate IP teams and IP law firms that commission both searches for complex product launches. 

What Running FTO Cold Actually Means 

A cold FTO begins without a prior landscape analysis. The searcher scopes the search based on the product feature description, a set of patent classification codes derived from the product technology, and professional judgment about where the relevant patents are likely to sit. This is the standard approach for most FTO searches commissioned by in-house IP teams and by external firms serving London-based corporate clients. For well-defined, single-technology products in spaces where the major patent holders are known and the classification structure is clear, it works well. Our guide on FTO search best practices covers the methodology that makes a cold FTO accurate within its scope — comprehensive prior art search, rigorous claim mapping, legal status assessment, and validity pre-screening of high-risk blocking candidates. A well-executed cold FTO within the right scope is a high-quality analysis. The limitation is not the execution. It is the scope. 

Where cold FTO fails: The cold FTO approach produces scope errors most consistently in four situations. Products that operate across multiple technology classification spaces — where the relevant patents span primary and adjacent classifications that the product description alone does not make obvious. Products entering markets where the dominant patent holders are not the obvious incumbents — where a company from an adjacent industry has built a significant position in the target technology space through a filing strategy that does not show up in the standard classification codes. Products that combine technology elements from multiple sub-domains — where the blocking patents are held at the intersection of those sub-domains rather than in either one individually. And products entering geographies or market segments with different patent filing patterns than the team’s primary market experience.

The knowledge gap: The cold FTO scope depends on what the searcher already knows about the landscape before the search begins. In familiar technology spaces with well-known patent holders, that prior knowledge is usually sufficient. In unfamiliar spaces, adjacent markets, or technology combinations that cross classification boundaries, it may be precisely the things the searcher does not know — the non-obvious patent holders, the adjacent classification risks, the cross-domain blocking positions — that represent the highest FTO risk. A landscape analysis fills that knowledge gap before the FTO scope is set. 

How Landscape Analysis Changes the FTO Scope 

A landscape analysis run before the FTO provides four specific inputs that improve scope accuracy. Each addresses a different category of cold FTO scope error. 

  1. Complete patent holder identification. A landscape analysis identifies the full set of relevant patent holders in the technology space — including entities that hold significant positions but would not appear on a standard list of known competitors. A technology company from an adjacent industry that has built a patent portfolio through acquisition. A university whose research programme generated patents that were licensed to a holding entity. A non-practising entity that accumulated patents in the space during a period of filing activity the product team is not aware of. The landscape surfaces all of them. The cold FTO, scoped from the product team’s knowledge of the competitive landscape, may miss the non-obvious ones entirely. 
  2. Technology classification mapping. A landscape analysis maps which patent classification codes contain the most relevant prior art — and critically, which adjacent classifications contain cross-domain patents that a primary-classification FTO search would miss. For a product that integrates technology elements from multiple sub-domains, the landscape reveals where the blocking patents actually sit across the full classification structure, not just in the primary codes the product description suggests. 
  3. Filing trend data. The landscape shows which parts of the technology space are actively growing — relevant pending applications that represent forward-looking FTO risk — and which are stable or declining. For the FTO, this means the search can be weighted toward the most active filing zones and the most commercially significant patent holders, rather than treating the entire classification space as equally likely to contain blocking patents. 
  4. High-citation patent identification. The landscape’s citation network analysis identifies the most-cited and most-forward-cited patents in the space — the ones that prior art searches and litigation consistently return to as foundational. These are the highest-priority blocking candidates for the FTO claim mapping. The landscape provides a verified starting point rather than requiring the FTO team to identify them through the search itself. 

A practical example of landscape output directly informing FTO scope: our analysis of how the UPC is reshaping patent landscape analysis for European R&D teams specifically notes that a well-structured European landscape feeds directly into FTO scoping decisions — identifying which UPC-active asserters require full pan-European FTO coverage and which holders represent manageable country-specific risk only. The landscape output is not a report to file and set aside. It is a scoping brief for the FTO that follows. 

The Cross-Domain Risk That Cold FTO Consistently Misses

The cleanest way to hold the distinction between these two tools is a single pair of words. 

The most consequential FTO errors — the ones that emerge as blocking positions after launch rather than before it — involve patents that sit outside the primary technology classification for the product. This is the cross-domain risk, and it is the category of FTO gap that landscape analysis most reliably surfaces. 

  • Medical devices with wireless connectivity. A medical device that incorporates Bluetooth or Wi-Fi connectivity may have its primary FTO risk not in the medical device classification but in the wireless communication classification — where the device’s radio frequency management, data transmission protocol, or antenna design may infringe patents held by telecommunications companies that have no product presence in the medical device market. A medical device FTO scoped only to device classifications misses this risk entirely. 
  • Clean energy products with integrated storage. A product that integrates renewable energy generation with battery or hydrogen storage faces blocking patents in both the generation classification and the storage classification — and potentially in the grid-balancing or power electronics classifications that govern the interface between them. A single-classification FTO scoped to the generation technology will not cover the storage or integration patents that may be equally blocking. 
  • Software-implemented features in hardware products. A hardware product with software-defined functionality may face blocking patents in both the physical implementation classification and the software or algorithm classification. In UK and European prosecution, the post-Aerotel EPO-comparable approach means that software-implemented features in otherwise hardware products can now support granted patent claims. A hardware-focused FTO that does not cover the software classification space may miss recently granted or pending patents that cover the product’s software-defined capabilities. 

“The cross-domain blocking patent is not the one the FTO team was looking for. It is the one they did not know to look for. Landscape analysis shows the searcher where to look before the search begins — including the adjacent classifications and non-obvious patent holders that the product description alone would not flag as relevant.” 

What the Integrated Landscape-First FTO Workflow Looks Like 

The landscape-first FTO workflow has four stages. Each stage feeds directly into the next, with the landscape output serving as the scope brief for the FTO rather than as a separate deliverable consumed independently. 

Stage 1: Landscape Analysis Scoped to the product technology space, covering primary and adjacent patent classifications identified from both the product feature description and the broader technology context. Filing trend analysis for the last 5 years. Top holder identification including non-obvious entrants from adjacent industries. Citation network analysis to identify foundational blocking candidates. Geographic distribution of filing activity across the jurisdictions relevant to the product launch. 

Stage 2: Landscape-to-FTO Handoff Briefing The landscape output is translated into a specific FTO scope brief: the patent holders to cover in the FTO search, the primary and adjacent classification codes to include, the cross-domain areas that require explicit search coverage, the pending applications to flag for monitoring, and the foundational blocking candidates identified through citation analysis that should be the first claim mapping priority. 

Stage 3: FTO Search Conducted using the landscape-informed scope brief. The search covers the patent holders, classification areas, and cross-domain spaces identified in the briefing — not just the default scope derived from the product feature description. High-citation blocking candidates are prioritised for detailed claim mapping. Pending applications in active filing zones are flagged for ongoing monitoring. 

Stage 4: FTO Opinion with Documented Scope The opinion explicitly references the landscape coverage: which patent holders were included and why, which classification areas were searched and why adjacent classifications were included, which cross-domain areas were covered. The scope documentation means the opinion can be updated efficiently as the landscape evolves — without requiring a full new search when a specific follow-up trigger fires. 

When the Integrated Approach Matters Most 

The landscape-first approach adds the most value in specific scenarios. For straightforward products in well-understood technology spaces with known patent holders, a well-scoped cold FTO may be fully sufficient. The integrated approach is not always necessary. It is most valuable precisely when the product or market complexity is highest — which is also when the consequences of an incomplete FTO are most severe. 

  • Complex technology spaces. Products that combine technology elements from multiple sub-domains, that operate across classification boundaries, or that integrate emerging technology with established hardware. The more complex the technology combination, the higher the likelihood that the most significant blocking patents sit in adjacent classifications that a cold FTO scope would not cover.
  • Non-obvious patent holder environments. Technology spaces where the dominant patent holders are not the obvious incumbents — where patent positions have been built through acquisition, cross-licensing, or filing strategies by companies from adjacent industries. For London-based corporate IP teams managing multi-product portfolios across technology sectors, non-obvious patent holders in adjacent industries are one of the most frequently missed FTO risk categories.
  • Geographic expansion into unfamiliar markets. A product expanding from a primary market into new geographies where the patent filing patterns, dominant holders, and enforcement environment differ from what the team has direct experience with. A landscape analysis of the new market’s patent environment is the most efficient way to scope a jurisdiction-specific FTO accurately.
  • High-stakes launches. Products where the commercial value of the launch is high enough that the cost of a post-launch injunction — including product withdrawal, litigation, forced redesign, or licensing negotiation from a position of market exposure — materially exceeds the cost of the combined landscape and FTO engagement. For these products, the integrated workflow is the lower-cost risk management approach even if it appears more expensive at the point of commission.

How Our Service Covers the Full Landscape-FTO Workflow 

Our freedom to operate service and patent landscape analysis service are structured to work as an integrated sequence where the landscape output directly informs the FTO scope. For clients commissioning both, we provide a landscape-to-FTO handoff briefing that translates the landscape findings into specific FTO scope inputs — patent holders to cover, classification areas to prioritise, cross-domain risk areas to include, and pending applications to flag for monitoring. The FTO opinion documents its landscape-informed scope explicitly, so that follow-up reviews can be targeted efficiently rather than requiring a full new search. For corporate IP teams at London-based companies managing complex product pipelines across multiple technology areas and jurisdictions, the integrated landscape-FTO workflow is the foundation of an IP clearance process that catches the cross-domain risks, non-obvious patent holders, and adjacent classification blocking positions that cold FTO consistently misses. 

Running FTO without a prior landscape analysis means scoping the search from assumptions. Our integrated landscape-FTO workflow uses the landscape output to define the FTO scope — covering the cross-domain risks and non-obvious patent holders that cold FTO consistently misses.  →  Contact Us 

Conclusion: The Takeaway 

The order you run landscape analysis and FTO in is not a procedural preference. It determines the scope of the FTO search — which patent holders it covers, which classification areas it includes, which cross-domain risks it catches, and which adjacent blocking positions it surfaces before rather than after launch. FTO run cold produces a scope defined by what the searcher already knows about the landscape. FTO run after a landscape produces a scope defined by what the landscape actually contains. 

In familiar technology spaces with well-known patent holders, those two scopes may be close. In complex, multi-technology, or non-obvious-holder environments — which describes a growing proportion of the product launches that matter most commercially — the two scopes diverge. The gap between them is where the avoidable FTO errors live. The integrated workflow closes that gap before the product enters a market where a blocking patent can exploit it. 

Insights

More Related Articles

Biosimilars Market Report: Trends, Opportunities & Insights

Whitespace Analysis vs. Patent Landscape Analysis: What Is the Difference and Which One Does Your R&D Team Actually Need?

When a Clean FTO Opinion Is Not Enough: The Four Situations That Require a Follow-Up Search

FTO in Switzerland After the 2027 Patent Act Reform: What Pharma and MedTech Companies Need to Clear Before Launch