Research question, audience and evidence boundary
What does an incomplete patent or legal dataset permit a researcher to conclude? The central analytical task is coverage, uncertainty and the boundary between evidence and opinion. The page is intended for researchers, inventors, analysts, university teams and decision-makers who need to examine underlying records rather than accept search-result summaries as conclusive findings. Its examples illustrate a possible workflow; they are not reports of a completed engagement, a claim of proprietary data access or proof of results for a specific client.
Research-specific verification matrix
| Verification phase | Evidence operation | Reviewer challenge |
|---|---|---|
| 1. Coverage | Define the target decision, country, technology, filing interval and whether the unit is application, publication, grant or family. | No record found is not evidence of no relevant right or disclosure. |
| 2. Coverage | Create a coverage matrix by office, language, publication date, document type and database refresh date. | Automated confidence scores cannot repair unknown database coverage. |
| 3. Coverage | Reconcile duplicate identifiers and family relationships before interpreting any trend or ranking. | Legal status depends on the competent authority and checking date. |
The uncertainty statement should expose three distinct denominators: the records actually retrieved, the collection the database purports to cover, and the legally relevant universe that may be larger than either. Comparing two counts without fixing the denominator is not an observed discrepancy in inventiveness; it may be only a discrepancy in collection practice. The final publication should name which classes of missing data could change its conclusion.
Worked example and the unit of analysis
Primary reference for checking this procedure: WIPO statistics methodological limitations. This source supports background verification; exact proposition-to-passage review remains necessary.
A team compares five competitors using patent publications from three databases and finds conflicting counts. One supplier collapses families while another counts every publication. The uncertainty is not merely statistical; the objects being counted differ.
For a comparative patent study, independently inspect a sample of publication numbers in each source. Mark missing bibliographic fields separately from contradictory fields. A family-merged chart can be retained beside the underlying publication-level count, but the two must never be described as equivalent. A useful uncertainty register records an evidence boundary, possible impact on the decision and a proposed validation owner.
For the illustrative scenario above, the evidence table should have explicit columns for the source identifier, the particular proposition tested, observed record content, competing explanation and the decision that remains open. The proposed workflow is not a completed case study.
Five-stage evidence workflow
1. Define and delimit
Define the target decision, country, technology, filing interval and whether the unit is application, publication, grant or family. Before searching, record the questions that are intentionally outside scope. An excluded jurisdiction or period might be perfectly reasonable for an exploratory study yet unacceptable for a legal clearance decision. The brief should make that difference legible to someone who has not attended the initial discussion.
2. Collect and preserve
Create a coverage matrix by office, language, publication date, document type and database refresh date. Retain raw record identifiers and original language next to normalized fields. Translations, vendor exports and interface-specific labels simplify review but can erase distinctions. Preserving the unmodified provenance means an analyst can return to the material even after an export format or search interface changes.
3. Reconcile and test
Reconcile duplicate identifiers and family relationships before interpreting any trend or ranking. Test a small counterexample set: a record that should be included, one that should be excluded, and an ambiguous borderline record. This gives reviewers something concrete against which to challenge the grouping rule, rather than assuming the procedure worked because a chart appeared plausible.
4. Interpret with competing explanations
Classify uncertainty as missing observations, delayed events, transliteration, classification change or model inference. Write down at least two explanations for the important pattern and specify which additional observation would discriminate between them. Different publication practice, database refresh and real changes in technical activity can generate superficially similar curves; the report should not flatten them into one story.
5. Report and escalate
Document conclusions at levels supported by the records and assign a separate verification path for high-consequence decisions. Separate verified facts, analytical judgments and unresolved questions in the finished output. Include the conditions under which a result ought to be refreshed, and state whether the next step is deeper technical research, office-register validation or professional legal review.
Official sources and what they establish
WIPO statistics methodological limitations. Consult this source for the relevant published method or official record and check the document version and date. The example here is illustrative, not a claim that this page reports a completed search.
EPO legal event caveats. Consult this source for the relevant published method or official record and check the document version and date. The example here is illustrative, not a claim that this page reports a completed search.
For this question, preserve the distinction between documentation about a data system and the underlying record returned by that system. Include the exact version, issue date or identifier needed to validate consequential findings.
Limitations, contrary evidence and professional review
No record found is not evidence of no relevant right or disclosure. The finding should be qualified against the relevant source and decision rather than generalized across territories or dates.
Automated confidence scores cannot repair unknown database coverage. The finding should be qualified against the relevant source and decision rather than generalized across territories or dates.
Legal status depends on the competent authority and checking date. The finding should be qualified against the relevant source and decision rather than generalized across territories or dates.
This public guide addresses the research process rather than a particular client matter. Refer any disputed statutory interpretation, enforceability or professional clearance issue to the responsible authority or qualified adviser.
Useful output and related research
An illustrative research output is an uncertainty register linking each reported conclusion to its missing-data exposure, source refresh date and next verification action. The file should define its scope, explain material exclusions and give readers identifiers sufficient to reproduce the analysis. It should not imply an engagement has already occurred.
Independent review should revisit the source material most likely to change the result. For this topic, challenge a positive example, a near-boundary example and an omitted record. Document which conclusions survive the challenge and which require correction.
For a scoped research inquiry, describe the technical question, source universe, applicable jurisdiction, deadline assumptions and expected analytical output. The discussion is informational and does not promise a regulated opinion, patent grant, legal clearance or market outcome.
For more context: Parent research collection · Methodology library · Source library · Research inquiry





