The title resembles the product being studied
Compare the relevant features with passages and the selected version of the claims. Describe documented matches and differences; do not turn a similar title into a protection or infringement conclusion.
In-depth practical guides
Distinguish publication, application, family, claims and legal events: document technical research without treating a title or aggregated record as permission to operate.
Updated :

AI-generated illustration
The same technical subject may appear in several publications and countries. A title helps discovery but does not establish the document consulted, the person holding a right or its current status. Useful reading separates documentary research, technical comparison and legal questions requiring specialist examination.
Retain the full number including kind code, office and URL, plus the application number when provided. Distinguish priority, filing, publication and grant dates. Search by identifier rather than title alone and inspect the original document associated with the record.
Record inventor, applicant and proprietor separately when sources provide them. Check the date to which each detail relates. A named inventor must not automatically be described as the current owner; a supposed transfer needs relevant evidence.
Inspect description, drawings and claims in the selected version. For European patents, EPC Article 69 links scope to claims, using description and drawings for interpretation. Do not infer protection from the title or an illustration alone.
Use the family to locate related publications, then compare references, territories and versions. A family is not one interchangeable document to cite. Record the family definition used; documentary grouping does not establish identical legal status for every member.
Date the event lookup and inspect the corresponding file. Aggregated events can guide research; the EPO recommends checking national information in the relevant registers. Do not turn the latest visible event into a universal claim covering all territories.
Cite documents and passages actually read, separating technical observations, consulted status and interpretation. Check translation or OCR against the original when a term affects meaning. Describe search scope and missing records without concluding freedom to operate from a partial search.
Reading workshop
This fictional file separates application, publication and granted text without claiming current protection.
Fictional data and records for learning: none of these results comes from a live service query.
A and B designate demonstration offices. Family F1 links two applications; the file contains three publications of different versions.
If the table exceeds the screen, scroll horizontally; arrow keys work when the region is focused.
| Step | Evidence or value | Reading | Decision |
|---|---|---|---|
| Application APP-A | Filed 2021; stated priority 2020 | The number identifies an application, not all its publications. | Retain dates and references separately. |
| Publication PUB-A1 | Published 2022; three claims | Published version preceding the supplied granted text. | Cite it for historical comparison. |
| Granted text PUB-A2 | Published 2024; two claims | Text changed in territory A. | Compare claims, not only titles. |
| F1 member PUB-B1 | Territory B; application published; grant undocumented | Family membership does not transfer A’s status to B. | Check the competent register and date conclusions. |
Open each proposition to compare its diagnosis. More checks may still be needed.
No: priority and family do not establish current worldwide protection.
No: claim versions differ here.
Appropriate. Name the document read; current status and exploitation require separate examination.
File: DEMO-P14; family F1 APP-A: priority 2020; filing 2021 PUB-A1: 2022; three claims PUB-A2: grant published 2024; two claims APP-B / PUB-B1: territory B; application published Current A/B status: unchecked Citation: exact publication and version
Attach office, publication and version to each extract. Retain the family definition and do not propagate events between members.
Compare the relevant features with passages and the selected version of the claims. Describe documented matches and differences; do not turn a similar title into a protection or infringement conclusion.
Build a list of documents and territories, then choose the counting unit. Separate publications, applications and families. Avoid describing every member as an independent invention.
Identify document, territory, date and event source, then consult the appropriate register. Look for later events and records. Retain uncertainty when current status cannot be established for the territory being studied.
Worked exercise
Fictional example: the values and documents teach the method and do not describe a real organisation.
The simple-family definition is supplied by the fictional extract. Territories and statuses are not recorded.
If the table exceeds the screen, scroll horizontally; arrow keys work when the region is focused.
| Publication | Family under this rule |
|---|---|
| P1 | F1 |
| P2 | F1 |
| P3 | F1 |
| P4 | F2 |
There are four publications and two simple families under this definition. Counts establish neither four distinct inventions nor current protection in four countries. The EPO distinguishes family concepts, so results depend on the chosen one.
Another database using extended families may group differently: compare definitions and members before alleging error.
Keep publications, known priorities, family, definition and territories/statuses to check.
Documentation reference : EPO — Patent families · Consulted on
Do not confuse them. Check document type and the file in the relevant register, then retain the qualification corresponding to the consulted record.
These roles differ. Record details specific to the file and date instead of inferring ownership from an inventor’s name.
It can aid reading, but identify the translation and check decisive terms against the original. Cite the publication and passage, not only the translated display.
No. A search without results does not prove there are no relevant rights. An operating decision requires an appropriate scope and legal analysis.
It helps to understand the relationships between the parts and the territories described. However, each document keeps its identity, date and scope; the family does not replace their reading.
DOCUMENTED REFERENCE
Before counting, state what constitutes a row and which rule groups documents. A comparison loses meaning when it silently mixes publications and families.
| Reference | Value or form | What it identifies |
|---|---|---|
| DOCDB | = | Simple family: same priorities. |
| INPADOC | ↔ | Extended family: priorities linking members. |
| publication ≠ family | ≠ | Declare the counting unit. |
Databases can use different family definitions. Retain database, date, identifiers and family type to make a result reproducible. Documentary grouping alone does not establish a right in force.
Documentation consulted on .
DEEPER READING / PRACTICE
A patent publication is quoted to describe an invention or its holder. The reading must distinguish the content of the document, family, events and status information available.
Updated on .
Release numbers, dates, applicants, inventors and related documents. Examine the events and territories instead of drawing a conclusion from the title alone.
A publication does not automatically demonstrate the current validity of a right or the commercial exploitation of the invention. Family information should be interpreted in their context.
The file contains identifiers, documents, events and reserves. The summary distinguishes what is technically described from what is established on the situation of the file.