Patent Search Log Template: Record Queries, Evidence and Research Gaps

A useful patent search log lets another reader understand what you searched, which documents you examined and what remains uncertain. Saving a list of links alone loses the query, filters and reasons behind each selection.

Download the blank patent search log (Markdown). The file is available without an account. Copy it into a text editor or your team's research notes and fill it in locally; this page does not upload your completed research.

What to record before searching

Write down the research question, purpose, date, databases, jurisdictions and languages. Separate a search for earlier technical disclosures from a review of rights affecting a particular product or market. The same result list does not answer both questions.

If you apply a date boundary, record what the date means and why it matters. A filing date, a publication date and a priority date are different fields. Include any coverage or update information the database actually shows; leave it unknown if it is not available.

Keep one entry for each query

Copy the exact query you entered, the searched fields, active filters and sort order. If the service reports partial results or an error, keep that note next to the result count. Do not silently replace an unavailable count with zero.

The template gives each run a place for the candidates selected, why you selected them, and the next change to try. This prevents a later list of bookmarks from looking like a complete search when it was only one attempt.

A synthetic example of a query change

Suppose the research question concerns a clamp that holds a cylindrical workpiece. Your first concept might combine “workpiece” and “clamp”; a later run could use “tube” and “grip” after checking the vocabulary in relevant documents. Record each actual expression separately, with its fields and filters.

This is an illustration of record-keeping, not a performed search or a patentability finding. It does not prescribe syntax that works in every database. See the patent search fundamentals guide for concept groups and classification.

Link every comparison to the original document

For each candidate, retain the full publication identifier and kind code, title, applicant, date, URL and document version. Record the claim, paragraph or figure that matters to your question, then distinguish what the source says from your interpretation.

If you used a translation, identify it and note which passages you checked against the original. Treat family members as related documents to inspect, not as interchangeable claims. Where legal status matters, record its source and update date separately from the technical comparison.

Make missing coverage visible

Before handing over the log, list languages, databases and date ranges you did not check, full texts you could not obtain, and uncertain identifiers. A search with no results should include the actual conditions used and any alternatives tried.

Use the final section to separate verified facts, working assumptions and questions for a patent professional. A completed template is a record of work, not proof that a search is exhaustive or that a product is clear to launch.

Continue the investigation

Search patent documents on CNIPA.AI and keep the log alongside your results. For Chinese documents, the CNIPA tools and search methods guide explains official entry points, identifiers and status checks. CNIPA.AI is an independent third-party service and is not affiliated with the patent office.

Can I use this with another database?

Yes. The fields describe research records rather than a particular query language. Record the service and its actual search syntax for each run.

Is this a legal opinion or an official filing form?

No. It is a blank research aid. Questions about patentability, claim scope and rights in a particular market require their own evidence and appropriate professional review.