Patent Family Trees Do Not Tell You What a Claim Covers

Interactive trees.

Colour-coded jurisdiction maps.

Little country flags joined by lines that travel through a PCT publication and arrive at a continuation with the emotional geometry of an airport baggage system.

Somebody has given the branches rounded corners.

Somebody else has made the earliest priority date glow when your mouse moves over it.

The tree would like to be a conclusion.

It has spent a great deal of time becoming a tree.

Then the claim arrives, with a separate document number, a separate jurisdiction, and a sentence that doesn’t care what the branches are doing.

It wants its limitations read.

It has the calm, withholding manner of a parking authority that has received a colour deck about why the sign should not apply.

A family relationship is a documented way to group related filing records. Claim text is the selected combination of limitations in one member.

Those jobs touch.

They don’t merge.

Your family tree is very good at getting you to the door.

It is very bad at opening it.

Excellent manners, no opinions

A keyword search can return 30 documents that are national equivalents, translations, application publications and grants, all related to a much smaller set of disclosures.

A family grouping reduces that pile to a reviewable unit.

It doesn’t turn the group into one patent right with a shared brain.

Your basic counting decision has a name, and you have to write it down.

A simple DOCDB family, in EPO terms, groups applications it treats as the same technical content.

An INPADOC extended family groups similar technical content through direct or indirect relationships.

The wider unit can join one or more simple families.

Neither is a more sincere version of the other.

Each answers a different question.

For a parallel-equivalents view, use the simple family.

Its first-pass table wants four columns.

Simple-family key.

Representative publication.

Priority set.

Jurisdictions represented.

The arrangement is almost aggressively dull.

That’s what makes it useful.

It tells you where parallel records may be found.

It doesn’t declare their claims, outcomes or remaining legal effect identical.

For a filing-history view, use the extended family.

The route is three steps.

Inspect the seed record.

Expand to extended-family members.

Mark the priority or continuation path that explains each branch.

Divisions, continuations and continuations-in-part can all turn up in that wider neighbourhood.

The result says: these are records to read next.

It doesn’t say these branches all claim the same thing. Which would be an ambitious conclusion for a line segment.

So your count starts by freezing five choices.

Database edition.

Search query.

Date range.

Family definition.

Treatment of missing priority data.

The first two say where the records came from and why.

The third says when you observed the result.

The fourth says what “family” means.

The fifth stops missing fields quietly becoming a philosophy.

The dramatic tree can wait in the lobby.

Not a claim in a trench coat

Suppose the Noreen P. Galloway Municipal Spoon-Alignment System turns up in your search.

It has an earliest priority display, a PCT publication, a US continuation, an EP application, and one branch the database placed in an extended family after a procedural adventure involving divisions.

The visual is handsome.

It has done everything short of issuing tiny property deeds to the lines.

It cannot tell you what the US continuation claims.

A family can contain an application that grants in one jurisdiction, one refused in another, one still pending elsewhere, and one that never moves beyond publication.

“The Galloway family is granted” is not a status statement.

It’s a family tree trying to buy a trench coat.

Status needs a member and a jurisdiction.

Claim scope needs the full claim text of that member.

A useful family review keeps at least three measures apart.

Applications or documents.

Jurisdictions.

Simple or extended families.

A fourth measure, live grants, is calculated member by member and dated.

Fold those into “portfolio strength” and you get a confident noun, minus the records that made the noun possible.

Dates get the same small indignity.

A family display can show you the earliest priority date.

A particular later claim may receive an earlier effective filing date only for subject matter adequately supported by the earlier application.

In US domestic practice, the later application needs a chain of copending applications to get that benefit.

Two date layers, at least.

Earliest recorded priority, and a claim-specific effective filing date.

The US term example is useful precisely because it refuses to be a generic family clock.

For many US utility patents filed on or after 8 June 1995, a continuation, divisional or CIP claiming domestic benefit has the general 20-year term baseline, measured from the earliest US application for which benefit is claimed.

Subject to the stated framework and adjustments.

Foreign priority isn’t used in that US calculation.

The date in your tree did not become an expiration opinion because it learned a new font.

Pick one. Keep the rest.

The first-pass answer isn’t to print every family member and pretend to read them simultaneously.

It’s to select one representative for a stated job, and keep the complete member list behind it.

An early publication may best explain the original disclosure.

A later national grant may best expose a current claim set.

Different reasons.

Different representatives.

Write your choice into the research note.

For a simple family, WIPO landscape work uses a representative member unless it says otherwise.

Your record should say whether the selected document is a disclosure representative, a current-claim representative, or merely the first document you used to orient yourself.

“Representative” is a job title.

Not a promotion to sovereign of the family.

Use a five-field triage card before you open the claims.

Selected family type.

Earliest recorded priority.

Representative disclosure.

Member jurisdictions.

Unresolved branches.

The card is allowed to be boring.

Its purpose is to carry a lead from a search result to documents in your hand.

Not to prepare a keynote about global intellectual-property dominion.

Keep a two-direction index beside it.

Document number to family key, and family key to all known document numbers.

A US publication can lead you to a PCT document, an EP application, or a foreign equivalent.

Even when titles have changed, translations have wandered, and application and publication numbers use different formats.

PCT publication numbers begin with WO.

PCT application numbers begin with PCT.

The index is a finding device.

Not a scope device.

And the database label stays attached throughout.

PATSTAT extended-family IDs are edition-dependent.

An identifier copied without its data release may later retrieve a different membership.

Your reproducible citation is a family type, a supplier, a data edition, an extraction date, and a membership list.

Not a lone number sitting in a slide deck like a laminated sandwich.

You can record the handoff without a research platform named after an endangered bird.

source       = supplier + data edition + extraction date
family rule  = simple DOCDB / INPADOC extended, as selected
search       = query + date range + missing-priority treatment
members      = complete returned membership and relationship path
representative = one identified member + stated first-pass purpose
next record  = that member's jurisdiction-specific status and full claims

That’s a procedure.

Not a declaration that your representative is the best patent among its relatives.

A different task can select a different representative from the same complete list.

The retained list makes the choice reviewable instead of mystical.

Which is a considerable improvement on letting a radial diagram decide in silence.

The map steps aside

Now select the member that matters for your question.

If the question is about a US continuation, get that member’s claim text and status.

If it’s about an EP application, do the same for the EP member.

Your family tree has completed its shift.

It may keep glowing quietly in another tab.

The claim check starts with the claim.

Not the family title, and not the technical abstract.

A useful comparison has three working columns.

The full limitation.

The alleged counterpart in the activity.

Record support for the match.

A modest arrangement of furniture.

It prevents a statement about related filings drifting into a statement about scope.

Consider a member claim requiring a sensor, a controller receiving sensor output, and a transmitter that sends a derived alert.

A three-limitation combination.

A cousin application can describe the same municipal spoon depot, use the same phrases, and have a more expensive-looking flag on your family map.

None of that supplies the receiving relationship or the derived-alert relationship in the selected claim.

A dependent claim is even less impressed by genealogy.

It carries every parent limitation and adds its own.

At three claim levels, the bottom claim carries both preceding packages plus its addition.

So a continuation or a foreign counterpart can require a different chart, even where the family relationship is entirely documented and the disclosure resembles an old filing in a familiar blazer.

MPEP 211 makes the continuation-in-part problem particularly uncooperative.

A CIP may add new matter, and only claims supported by the earlier disclosure receive its earlier date.

In a US dispute, a disputed term can require construction before your comparison.

Markman assigns construction to the court in federal litigation.

Under Phillips, your three intrinsic sources are the claim text, the specification and the prosecution history.

The USPTO uses broadest reasonable interpretation consistent with the specification for pending claims.

A PTAB AIA trial uses the court-style Phillips approach for petitions filed on or after 13 November 2018.

A family relationship has no authority to impersonate any of them.

Literal comparison and equivalence are two routes, not one broad resemblance test. Warner-Jenkinson requires equivalence one element at a time.

The US statutory baseline in 35 U.S.C. 271 concerns unauthorized making, using, offering to sell, selling or importing a patented invention during its term.

None of those rules turns a family relationship into a finding.

They attach to the individual claim, the record, the forum and the accused activity.

Read the claims yourself

Your family screen ends on a deliberately narrow sentence.

Family expansion complete.

Claim and status verification pending.

That isn’t a failure to finish.

It’s the point at which the analysis stops lying about what it has done.

Call it the representative-member rule.

State the database’s family definition.

Preserve the full membership.

Choose one member for an explicit first-pass purpose.

Identify its jurisdiction for any status statement.

Then read its claims, independently, before you say what they cover.