eduKateSG · Why Science?
Group related patent documents, then check each jurisdiction and legal event
Read Espacenet through DOCDB simple families, INPADOC extended families, priority, bibliographic data, legal events and official-register verification.
The same technical idea can produce patent publications in several countries, languages and procedural stages. EPO Espacenet gives free access to worldwide patent information and groups related documents so users can explore the disclosure without counting every publication as an unrelated invention.
The European Patent Office explains two important family types. A DOCDB simple family groups applications considered to cover the same technical content and having the same priorities. An INPADOC extended family connects applications with at least one priority in common, directly or indirectly, so its technical scope can be broader.
Did you know? Espacenet can display legal events reported by patent offices, but an event list is not a universal yes-or-no answer about enforceability. Jurisdiction, event code, effective date, reporting coverage and the official register all matter.
This guide treats family and legal-status information as evidence with defined limits. The goal is a reproducible technical search, followed by precise verification where a legal conclusion is needed.
Chapter index
Chapters 1–9: document identity, priority and family grouping
- 1. Espacenet is a worldwide patent search service
- 2. One invention can produce many publications
- 3. Priority claims are the family foundation
- 4. DOCDB simple families target the same content
- 5. INPADOC families connect similar content
- 6. Family definitions vary across databases
- 7. A representative member is a display choice
- 8. Bibliographic data identifies the document
- 9. Descriptions and claims answer different questions
Chapters 10–17: legal events, status limits and reproducible search
- 10. Citations provide discovery routes
- 11. Legal events are dated reports
- 12. A legal event is not the whole status story
- 13. Coverage varies by office and period
- 14. National status needs national verification
- 15. Family legal status is jurisdiction-specific
- 16. Search syntax and filters should be saved
- 17. Patent-information skills support innovation careers
CHAPTER 1 OF 17 · Find the publication
1. Espacenet is a worldwide patent search service
A patent family groups related publications so one invention is not mistaken for many unrelated ideas. The EPO describes Espacenet as a free service covering patent documents from around the world, with data updated regularly and supporting information about grants and status. This helps students explore technical change while respecting the limits of database status summaries.
Try this
Evidence question: Which collection and update context apply to this record? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Save the publication number, source office and access date. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for espacenet is a worldwide patent search service, its identifier or version context, and one limit that must remain visible.
CHAPTER 2 OF 17 · Find the publication
2. One invention can produce many publications
Espacenet combines worldwide patent searching with bibliographic, family and legal-event information. Applications may be published at different procedural stages and in different jurisdictions. A result list therefore contains documents rather than a direct count of inventions. It also explains why family counts and document counts are not interchangeable.
Try this
Evidence question: Which publications belong to the same technical filing route? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Group the documents before reporting a technology count. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for one invention can produce many publications, its identifier or version context, and one limit that must remain visible.
Simple and extended family definitions answer different grouping questions. Patent families are built from relationships among applications through priority claims. Priority numbers and dates are the evidence for those relationships. Priority links provide the evidence for family relationships.
Try this
Evidence question: Which priority is shared by the family members? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Create a member-by-priority matrix. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for priority claims are the family foundation, its identifier or version context, and one limit that must remain visible.
CHAPTER 4 OF 17 · Find the publication
4. DOCDB simple families target the same content
Legal events are dated reports from patent offices and need jurisdiction-specific interpretation. The EPO defines a DOCDB simple family as documents considered to cover a single invention with identical priority sets, subject to its family-building rules. A careful conclusion names the member, country, event date and source register.
Try this
Evidence question: Do all members show the same relevant priorities? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Use “Also published as” and verify the priority table. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for docdb simple families target the same content, its identifier or version context, and one limit that must remain visible.
CHAPTER 5 OF 17 · Understand family types
5. INPADOC families connect similar content
A patent family groups related publications so one invention is not mistaken for many unrelated ideas. An INPADOC extended family links documents when each member shares at least one priority with another member, directly or indirectly. Members can therefore cover similar rather than identical technical content. This helps students explore technical change while respecting the limits of database status summaries.
Try this
Evidence question: Which chain of shared priorities connects distant members? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Draw the links rather than assuming every pair is identical. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for inpadoc families connect similar content, its identifier or version context, and one limit that must remain visible.
CHAPTER 6 OF 17 · Understand family types
6. Family definitions vary across databases
Espacenet combines worldwide patent searching with bibliographic, family and legal-event information. The EPO warns that databases can use different family definitions, so the members and counts for the same invention may differ. It also explains why family counts and document counts are not interchangeable.
Try this
Evidence question: Which system and family type produced this total? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Put the database name and definition in the chart caption. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for family definitions vary across databases, its identifier or version context, and one limit that must remain visible.
CHAPTER 7 OF 17 · Understand family types
7. A representative member is a display choice
Simple and extended family definitions answer different grouping questions. Espacenet groups results by family and selects a representative document for display according to its rules. Other members remain relevant for languages and jurisdictions. Priority links provide the evidence for family relationships.
Try this
Evidence question: Which family member are you actually reading? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the representative publication and the member used for the evidence. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for a representative member is a display choice, its identifier or version context, and one limit that must remain visible.
CHAPTER 8 OF 17 · Understand family types
8. Bibliographic data identifies the document
Legal events are dated reports from patent offices and need jurisdiction-specific interpretation. Publication and application numbers, dates, applicants, inventors, classifications and priorities create the bibliographic fingerprint. Similar titles alone are insufficient. A careful conclusion names the member, country, event date and source register.
Try this
Evidence question: Which fields distinguish this record from a neighbour? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Verify at least four bibliographic fields before merging records. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for bibliographic data identifies the document, its identifier or version context, and one limit that must remain visible.
CHAPTER 9 OF 17 · Read legal events
9. Descriptions and claims answer different questions
A patent family groups related publications so one invention is not mistaken for many unrelated ideas. The description explains embodiments and technical context; claims define requested or granted legal scope in a particular document stage. This helps students explore technical change while respecting the limits of database status summaries.
Try this
Evidence question: Which section supports the technical statement? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Link each note to an abstract, description paragraph, figure or claim. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for descriptions and claims answer different questions, its identifier or version context, and one limit that must remain visible.
Espacenet combines worldwide patent searching with bibliographic, family and legal-event information. Patent citations can point to earlier or later documents and examiner or applicant references. Citation relationships do not automatically show agreement, validity or commercial use. It also explains why family counts and document counts are not interchangeable.
Try this
Evidence question: Who cited what, and in which procedural context? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Follow the cited document and label the citation source. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for citations provide discovery routes, its identifier or version context, and one limit that must remain visible.
Simple and extended family definitions answer different grouping questions. INPADOC legal-event data records events reported by national and regional offices, using jurisdiction-specific codes and descriptions. Priority links provide the evidence for family relationships.
Try this
Evidence question: Which office, event code and effective date are shown? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Copy the code and description together. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for legal events are dated reports, its identifier or version context, and one limit that must remain visible.
Legal events are dated reports from patent offices and need jurisdiction-specific interpretation. Fee payments, grants, lapses, reinstatements, oppositions and transfers can occur over time. A single event must be read in sequence and jurisdiction. A careful conclusion names the member, country, event date and source register.
Try this
Evidence question: What later event could change the conclusion? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Build a chronological event timeline before summarising status. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for a legal event is not the whole status story, its identifier or version context, and one limit that must remain visible.
A patent family groups related publications so one invention is not mistaken for many unrelated ideas. Legal-event coverage depends on the data supplied by patent authorities and the dates and event types included. Missing events should not be interpreted as proof that nothing happened. This helps students explore technical change while respecting the limits of database status summaries.
Try this
Evidence question: What does the coverage documentation include? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: State the coverage boundary beside any absence claim. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for coverage varies by office and period, its identifier or version context, and one limit that must remain visible.
CHAPTER 14 OF 17 · Verify the conclusion
14. National status needs national verification
Espacenet combines worldwide patent searching with bibliographic, family and legal-event information. For decisions about whether rights are in force, the EPO directs users toward authoritative registers and office information. Espacenet supports discovery, not final legal advice. It also explains why family counts and document counts are not interchangeable.
Try this
Evidence question: Which register is authoritative for this member? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Follow the member to the responsible office and note the register check date. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for national status needs national verification, its identifier or version context, and one limit that must remain visible.
CHAPTER 15 OF 17 · Verify the conclusion
15. Family legal status is jurisdiction-specific
Simple and extended family definitions answer different grouping questions. Members of one family can have different outcomes: one may grant, another lapse, and another remain pending. There is no single family-wide status. Priority links provide the evidence for family relationships.
Try this
Evidence question: Which member and territory support the statement? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Use one row per jurisdiction instead of one status cell for the family. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for family legal status is jurisdiction-specific, its identifier or version context, and one limit that must remain visible.
CHAPTER 16 OF 17 · Verify the conclusion
16. Search syntax and filters should be saved
Legal events are dated reports from patent offices and need jurisdiction-specific interpretation. Smart search, advanced search, classification and filters can change the retrieved set. Espacenet is intended for interactive research rather than bulk automated retrieval. A careful conclusion names the member, country, event date and source register.
Try this
Evidence question: Which exact query and filters created the result? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Save the query text, sort, filters and date. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for search syntax and filters should be saved, its identifier or version context, and one limit that must remain visible.
CHAPTER 17 OF 17 · Verify the conclusion
17. Patent-information skills support innovation careers
A patent family groups related publications so one invention is not mistaken for many unrelated ideas. Engineers, scientists, information professionals, analysts and patent practitioners use family and event data to understand technical landscapes. This helps students explore technical change while respecting the limits of database status summaries.
Try this
Evidence question: Which part of the task is technical and which requires legal expertise? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Create a handover with separate disclosure and status sections. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for patent-information skills support innovation careers, its identifier or version context, and one limit that must remain visible.
Contents · Previous chapter · Continue at the Science Learning Hub
A family map explains relationships; a register check supports a status conclusion
Espacenet makes technical literature easier to navigate by grouping related publications and exposing bibliographic and legal-event trails. The family definition tells you why documents are together.
Save the query, representative member, exact publication, family type, priorities, member list, event codes, event dates, jurisdiction, coverage note and access date. Use the official register for any decision that depends on current legal force.
| Reading object | What it can support | Question to keep visible |
|---|---|---|
| DOCDB simple family | Documents treated as the same technical content | Do priority sets match? |
| INPADOC extended family | Documents connected through shared priority chains | How broad is the technical relationship? |
| Legal event | Dated office-reported occurrence | Which code, territory and effective date apply? |
| Official register | Authoritative jurisdictional record | What is the current verified position? |
Sources and next reading
Substantive resource claims in this article were checked against the primary pages below. A structured record is a route into evidence; it does not by itself prove a scientific conclusion. Recheck the live record, evidence labels and release context before using it in assessed work or research.
For a classroom enquiry, save a short research receipt containing the question, search terms, selected object, exact identifier, version, access date and the evidence boundary you observed. Add the file or page that supports each statement. This small routine turns browsing into accountable science learning and gives a teacher, classmate or future analyst a route they can independently follow.
Before sharing the conclusion, ask another reader to retrace the route without verbal hints. If they reach a different version, file or interpretation, improve the receipt and narrow the claim. Reproducibility begins with this practical check. It teaches careful reading, supports fair collaboration and keeps uncertainty visible while evidence moves from an online service into notes, analysis and a final explanation.
A useful final review separates five questions. What object was found? Which organisation or repository maintains it? What exact evidence was inspected? Which statement does that evidence support? What remains uncertain? Answer each question in one sentence, then connect every answer to a visible field, file or source page. This review catches common mistakes: citing a collection when a file supplied the value, treating the newest release as the analysed release, confusing permission with scientific suitability, or turning a discovery count into a conclusion. It also gives students a calm way to improve work. A missing detail becomes a next research step instead of an invitation to guess. When the route is complete, the final explanation can stay simple because the identifiers, dates, versions, limitations and supporting evidence are already organised underneath it.
Primary sources
- EPO Espacenet overview — accessed 25 October 2026.
- EPO patent families overview — accessed 25 October 2026.
- DOCDB simple patent family — accessed 25 October 2026.
- INPADOC extended patent family — accessed 25 October 2026.
- EPO patent searching and legal information — accessed 25 October 2026.