Key takeaways
• A low-result search does not establish novelty. Test search coverage before drawing a conclusion.
• Expand each core technical concept across terminology, functional wording, classifications, and document-based routes.
• Use a known relevant document to test retrieval, then record the search scope and remaining limitations.
Treat zero results as a coverage question first
You search for a technical feature and find almost nothing relevant. The tempting conclusion is that the field is empty and the invention must be new.
That skips a question:
Did the search cover the ways patent documents are likely to describe this technology?
A search retrieves documents through the language, classifications, citations, sources, jurisdictions, and filters built into the strategy. Narrow routes produce narrow result sets whether or not relevant documents exist. Low volume is an observation about the search, not about the field.
There is a direct way to test the difference, and it takes one document.
Test the strategy with a document you already know
Pick a document you already know is relevant to the technical subject. Ask whether the current strategy retrieves it.
This is a known-document coverage test, sometimes called reverse validation.
If the document does not appear:
- inspect the terminology in its title, abstract, claims, and description;
- review its classifications and family members;
- identify which concept or route was missing; and
- revise the strategy before relying on its coverage.
Retrieving one known document does not prove the field has been covered. Failing to retrieve it is direct evidence that the strategy has a gap. That asymmetry is what makes the test worth running first rather than last.
Eureka connects technical inputs with source-linked evidence for novelty and FTO review. Turn an invention or product description into structured, source-linked patent evidence for review.
Why familiar technical language misses patent literature
The gap a known-document test exposes is usually linguistic. Patent documents describe the same subject in ways a practitioner would not.
- Vocabulary and abstraction. A product-specific term may appear in a patent as a broader or narrower technical concept.
- Functional and structural wording. A document may describe what a component does, how it is arranged, or what result it produces, instead of naming the component.
- Time, language, and translation. Terminology shifts as a field develops, and equivalent concepts do not map to one literal translation.
Illustrative example
An inventor describes a feature as:
heat dissipation structure for phones
A patent document describes the same territory as:
thermal management assembly for portable electronic devices
The two phrases do not show that the disclosures are the same. They show how differently closely related technology can be worded. A one-phrase search may never reach the second document.
Build a search that can learn from the literature
1. Define the core technical concepts.
Start with the small number of concepts that make the invention work. Separate them from benefits, marketing language, and implementation detail that would narrow the search too early. For a cooling phone case, the starting concepts might be a case or housing for a portable device; heat transfer, cooling, or thermal management; and the particular mechanism that creates the technical distinction, if it is defined well enough to search.
2. Expand each concept along several language routes.
For every concept: direct synonyms, broader and narrower terms, functional expressions, component and material and process terms, historical terminology, and relevant language or translation variants.
Keep the relationships visible. A flat list of keywords is hard to debug. A concept-to-term map shows which technical idea each term is supposed to retrieve, which is what lets you find the missing branch when a known document fails to surface.
3. Add classification and document routes.
Keywords should not be the only path in. Classifications surface documents that use unexpected wording. Citations, families, applicants, and known competitors give further routes where relevant.
Classifications do not guarantee completeness. They can be broad, updated, or applied differently across offices. Their value is that they test the field through a structure other than literal wording.
4. Iterate and record the limits.
Each useful result can teach the next query. Record the terms, classifications, sources, jurisdictions, date limits, and exclusion decisions. Also record what was not searched. That documentation is what lets another reviewer see how the result set was produced and where more work may be needed.
What a low result count can and cannot support
| A low result count may indicate | A low result count does not prove |
|---|---|
| The query is narrow | The invention is novel |
| The terminology is uncommon | No relevant prior art exists |
| The classification route needs refinement | An examiner will not find another document |
| The technology is emerging or specialised | The invention involves an inventive step |
| The selected sources or jurisdictions are limited | The search is complete |
Novelty remains a legal assessment of the claimed invention against the applicable prior art. Under the European Patent Convention, an invention is new if it does not form part of the state of the art, and EPO guidance explains that a novelty objection requires a prior disclosure that directly and unambiguously makes the claimed subject matter available. A result set supplies evidence for that assessment. It does not replace it.
From a search strategy to reviewable evidence
The Eureka Novelty Search workflow begins with a natural-language invention description. It extracts technical features, builds multiple search strategies, and compares relevant prior art against those features. The supporting documents stay available for review.
The workflow can reduce the effort of building and inspecting multiple routes. Reviewers should still:
- check the extracted features and the search strategies;
- test whether known documents can be recovered;
- open the cited source documents; and
- treat the output as evidence for professional judgment, not as proof that no other prior art exists.
Eureka connects technical inputs with source-linked evidence for novelty and FTO review. Turn an invention or product description into structured, source-linked patent evidence for review.
