How to do a patent landscape search

A patent landscape search begins with a scope statement. Describe the technology in plain terms, list the features that matter, and say what is out of bounds. A scope such as "wearable sensors" will return thousands of documents. A scope such as "wrist-worn devices that detect falls using motion sensing" is narrower and more useful.

Decide at the start what the landscape is for. A team choosing a development direction needs a broad view of who is active. A team preparing for investor questions may want a close look at the few patents that seem nearest to its design. The purpose shapes how wide to search and how many documents to read closely.

Set a time window and the jurisdictions you care about. Patents are filed country by country, so a family of related filings can appear in several places.

Searching works best with two methods used together.

Keyword searching uses the words inventors and applicants write. Because different companies describe the same idea differently, include synonyms and related terms, for example "fall," "drop," and "impact," and use proximity operators if the database supports them. Keep a log of each query and how many results it returned.

Classification searching uses the Cooperative Patent Classification, or CPC, a hierarchical system that assigns patents to technical categories. Once you find a few relevant patents, look at the CPC codes on them and search by those codes. This finds documents that describe the technology in unusual words. Combining a CPC code with a few keywords is a common way to narrow results.

It also helps to follow citations. A relevant patent lists earlier documents it cites and later ones that cite it, and both directions often surface close neighbors.

A comparison matrix puts the selected patents in rows and the features that matter to your product in columns. Typical columns include the owner, filing and priority dates, legal status, key technical features, and which markets the family covers. Reading across a row shows what a patent emphasizes. Reading down a column shows which features are common and which few documents mention them.

Claims define what a patent protects, so they deserve the most attention. At a business level, read the independent claims first and note the main elements. Compare those elements with your own design to see where there appear to be overlaps and where there appear to be distinctions. This tells you which documents deserve a closer look from an attorney. It does not say anything about whether a product infringes.

The matrix can also show patterns, such as which companies file most, in which years, and in which technical areas. These patterns give business context to the technical reading.