How to do a patent search for relevant publications
Run a patent search using technical terms and classifications, then check publication numbers, family links, and relevant passages for a review list.
Free app. Runs on your Mac with the Claude or Codex plan you already have.
What a patent search is
A patent search finds published patent documents that may describe technology relevant to a research question. Start with the technical features you care about, then search patent publications using alternate terms, technology classifications, and applicant names when useful. Read the documents behind the matches and list the passages that justify keeping each candidate. The result is a source-linked research draft that a technical reviewer or qualified patent professional can inspect and extend.
A publication list can help you study technical approaches, focus a review of an invention, or prepare for a broader prior art search. Prior art is material that may bear on whether an invention was already known or disclosed. A broader search may need technical papers, manuals, or other records beyond patent databases. Name the databases, criteria, and search date so the reviewer can see what you covered, which documents are closely related, and where more work is needed.
What it does for the business
- Focus engineering review on concrete documentsA list with relevant passages lets engineers compare how publications describe a feature or solve a problem. The team can choose which approaches merit deeper technical reading before allocating design time.
- Make professional review easier to scopePublication identifiers, dates, queries, and missing sources give a patent professional a clear place to start. They can see whether to widen the technical search, check a related document, or conduct a separate review for a specific jurisdiction.
- Reduce repeated reading across related documentsFamily context helps reviewers choose where to start when several publications cover closely related material. Keeping the individual records makes it possible to return to a particular publication when the wording or date matters.
- Preserve the research behind a decisionSave the scope and the source-linked list with the project notes. When the technical design or research question changes, the team can reuse relevant records and identify which parts of the search need to be repeated.
Patent search, step by step
Define the question and build a search vocabulary
Search for the features that solve the problem, using the different words a technical author might choose.
What to do
- Write down what the search should inform and which technical features matter. Describe how each feature works and which combinations make a document worth reviewing.
- List alternate names for components, their functions, and the problems they solve. Use an applicant name to test a specific lead or focus a pass, and preserve a broader pass that can find unfamiliar applicants.
- Identify likely classes using patent classification, the system databases use to group documents by technical subject. Look up the meanings of relevant IPC or CPC codes before relying on them to narrow a query.
- Choose databases, jurisdictions, and date bounds that fit the question. If a cutoff matters to a legal decision, have the qualified reviewer confirm which dates to collect and how to use them.
Why
A search based on one product name or one favored expression can skip documents that describe the same function in different words. Searching by function and by class gives you different ways to find useful candidates. A written scope lets the reviewer judge whether the selected databases and time window support the next decision.
Open the publications and record traceable evidence
Keep the full publication number and the passage that made the document worth reading.
What to do
- Open the source document for each promising result. Capture its stable link, observation time, title, applicant, publication date, and full publication number including the kind code, the suffix that identifies the type of published document.
- Record the abstract and the specific passages that describe the features you are looking for. Cite the claim number, paragraph, or other location so a reviewer can find the wording in context.
- Keep the publication date separate from any filing or priority dates you record. Use a clear label for each and return to the original record if different sources disagree.
- Note the family identifier when available and record which database supplied it. Leave missing fields open and log unreadable documents or unavailable sources for follow-up.
Why
A publication can seem relevant from a title while describing a different mechanism in its text. The full identifier keeps a reviewer on the same document you read, and the passage shows what justified including it. Separating the different dates also keeps a reviewer from using the wrong date for a question that depends on timing.
Remove exact duplicates and review related publications
Use family information to organize related reading while preserving each distinct publication.
What to do
- Combine repeated copies of the same full publication identifier, keeping the source needed to verify it. Preserve documents with different publication numbers or kind codes as distinct records.
- Use the patent family, a group of related patent documents, to organize the shortlist. Keep the individual jurisdictions, dates, and document versions visible inside the group.
- Read representative abstracts and claims for each family. Compare any differing passages that matter to your research question and explain which feature each relevant document describes.
- Check the strongest matches against the brief. Keep a short reason for inclusion, move incidental word matches out of the shortlist, and mark passages that need a closer technical reading.
Why
Several databases can return the same publication, and related publications can crowd the top of the list. Removing exact duplicates and showing family relationships makes that list easier to read. Retaining distinct documents matters when a qualified reviewer needs the exact text, date, or jurisdiction behind an observation.
Verify the shortlist and hand it over for review
Lead with the strongest technical evidence and show the reviewer where the search stopped.
What to do
- Reopen the originals for the leading rows. Verify publication numbers and codes, check the cited passages against the brief, and make sure family grouping did not conceal a distinct document you need.
- Summarize the most relevant findings using specific features and sources. Record the observation date, databases and query scope, and the gaps that affect how the list can be used.
- Write the next step as an assignment someone can complete. Identify a document for a technical specialist to read, a missing publication to obtain, or a question a patent professional should investigate.
- Send the table as a research draft for a qualified patent professional when a legal decision is at stake. Ask for separate review of current status, claim scope, or freedom to operate, the assessment of whether a planned activity raises patent infringement concerns.
Why
A technical match can help you decide where to look next. Legal questions depend on the specific activity, relevant jurisdictions, and the applicable documents and their status. A source-linked draft gives the reviewer a useful starting point and shows which observations can be checked directly and which questions need separate analysis.
Common mistakes
- Searching for one phraseUse technical synonyms and relevant classifications to find documents that describe the same feature in different terms.
- Dropping the kind codeKeep the full publication identifier so the next reader opens the same version of the document.
- Using title matches as technical evidenceRead the abstract and relevant passages to see whether the document actually describes the feature you care about.
- Collapsing all family members to one recordGroup related documents and retain their individual identifiers, jurisdictions, dates, and source links.
- Drawing a legal conclusion from the shortlistGive a qualified patent professional the draft and identify the specific decision or status question that needs review.
What a good result looks like
- The research purpose, features, dates, databases, and search limits are stated.
- Every shortlisted document has a full publication number, a source link, and an observation date.
- A reviewer can locate the passages and understand why they relate to the brief.
- Exact duplicates are removed and distinct family publications remain identifiable.
- The draft records missing evidence and assigns a clear next check.
And then what? Using the result
- Ask a technical reviewer to compare the passages that describe the mechanism or feature driving the search.
- Extend the search to technical papers, manuals, or other records if the research requires broader prior art coverage.
- Send the scope, shortlist, and open questions to a qualified patent professional when status or claim analysis matters.
- Save the queries and source-linked records so a later reviewer can repeat the search or adjust it to a design change.
When to run it
- Before choosing a technical approachUse a publication shortlist to compare how earlier documents describe ways to solve the same problem.
- When preparing an invention reviewGather the closest documented disclosures and their dates so a qualified reviewer can decide what to examine next.
- When a technical design changesRepeat the relevant portions of the search for the changed features and record which earlier findings still apply.
- When tracking publications in a defined areaPreserve a dated baseline and repeat the search using comparable sources and criteria, with any coverage gaps visible.
Questions people ask
How do you start a patent search?
Describe the feature or technical problem, list synonyms, and identify relevant patent classes before searching official publication databases. Record the queries and open candidate documents to verify their relevance.
What is a patent kind code?
A kind code is the suffix that identifies a type of patent document issued by the publishing office. Keep it with the number and consult the source record when the exact publication type matters.
Why can several publications belong to one patent family?
A family groups related patent documents, often through shared priority information. Keep distinct publication numbers and dates so a reviewer can open the individual records that matter to the question.
How do you know whether a patent publication is relevant?
Read the abstract and the pertinent claims or description to see whether the publication addresses the feature in your brief. Record the specific passage and state the link to the feature in your own words.
Can a patent search establish freedom to operate?
Freedom to operate requires a separate legal assessment from a qualified patent professional. Provide your intended activity, relevant jurisdictions, and the publication shortlist to help scope that review.
Which date should you record for each publication?
Record the publication date for the specific document you reviewed. If filing or priority dates also matter, record them under separate labels and have a qualified reviewer confirm their significance.
More jobs in Research
Find relevant patent publications, on your own Mac.Free app. Runs on your Mac with the Claude or Codex plan you already have. Your files stay on your computer.
Download for Mac