Prior-Art Search Before You Fall in Love with the Idea

Do not begin with is my idea patented. Split the concept into a problem, user, function, mechanism, components, interfaces, and use environment. Decide whether you are looking for vocabulary, technical approaches, crowded features, possible differentiators, or documents for a professional review. Each purpose produces different queries and notes.

Write the current concept revision and date at the top of the search log. Patent searching is iterative, and the design will change. A search for one mechanism does not automatically cover a later mechanism or claim. Keep discovery separate from legal conclusions: patentability, validity, ownership, enforceability, and freedom to operate involve claims, status, jurisdictions, dates, and legal analysis.

List everyday, technical, industry, historical, and outcome language for each important element. A device described as a feeder might appear under dispenser, metering, dosing, hopper, auger, gate, portion, or delivery terms. Combine one function with one mechanism or context, then broaden and narrow. Record the exact query and result count so another reviewer can reproduce the path.

Search the problem even when the proposed solution is novel. Earlier documents may use a different mechanism but reveal hazards, controls, user expectations, or classification codes. Search adjacent fields where the same functional problem appears. Avoid adding every detail to the first query; over-specific searches can return nothing and create false reassurance.

Start with broad keyword combinations in USPTO Patent Public Search. Open promising documents and capture publication number, title, applicant or assignee, inventors, priority and publication dates, abstract, drawings, relevant claims, classifications, and citations. Titles and abstracts help triage, but the claims define the legal boundaries being sought or granted and deserve professional interpretation.

Run a second pass with the terminology found in strong results. Run a third pass with classification codes. Run a fourth pass on cited and citing documents. Search by known applicants or inventors only after functional searching, because ownership can change and important work may sit under unexpected names. Save direct document links or identifiers rather than screenshots alone.

The Cooperative Patent Classification groups technical subject matter even when documents use different words. Find codes on relevant documents, read the classification definition, move up for broader concepts and down for narrower ones, and search nearby groups. A classification is a navigation aid, not proof that every result is relevant or every relevant document is present.

Document why each code matters to the current concept. Searching only one code can miss interdisciplinary work or classification changes. Pair classification searching with keywords and citations. The USPTO publishes CPC information, while PATENTSCOPE and Espacenet support broader international discovery paths that can expose terminology and families outside a U.S.-only pass.

Use drawings to understand architecture, then read the detailed description and claims relevant to your feature. Note whether you are viewing an application publication or granted patent. Look for related applications and patent families, because similar material may appear across jurisdictions with different claim sets and status. A publication's existence does not mean every claim was granted, remains active, applies in your market, or covers your design.

Do not infer freedom to operate from an expired or abandoned document without reviewing related rights. Do not infer patentability because no quick result looks identical. Dates and public disclosures can matter. When commercial or investment decisions depend on the answer, give counsel the concept revision, search log, closest documents, jurisdictions, intended launch timing, and specific questions.

For each close document, write similarity, difference, evidence, and design consequence. A finding might change terminology, add a safety requirement, expose a maintenance problem, suggest an alternative mechanism, or show that the intended differentiator is common. Rank findings by impact on the concept rather than collecting a large bibliography no one reviews.

Update the brief and preserve the old revision. If the concept changes materially, search the new mechanism. Do not design around a claim based on casual interpretation. The responsible output of a founder discovery pass is a better question set and source trail. ConjureAnything can help generate alternatives, but those alternatives require their own search and review.

Fields: concept revision; searcher and date; purpose; problem statement; functional elements; synonyms; keyword queries; classifications; databases; result counts; closest publication numbers; relevant drawings and claims; citation trails; family notes; status to verify; similarity; difference; design impact; open question; next query; and professional-review trigger.

Finish with a limitations statement: databases and queries used, date searched, scope, jurisdictions not assessed, and conclusions not made. Attach the log to the evidence pack. A transparent incomplete search is useful because another reviewer can extend it; an undocumented confident search must be repeated from the beginning.