Claim Chart for SEPs
A claim chart for a standard essential patent maps each element of a patent claim against the text of a standard specification. It shows whether a claimed feature is essential to the standard, optional, or dependent on the implementer.
| Clause | Standard evidence | Status |
|---|---|---|
| 1.1 | §4.3.2 — procedure for X, as specified | Essential |
| 1.2 | §4.3.5 — optional field, note 3 | Optional |
| 1.3 | §5.1.1 — configuration-dependent behaviour | Impl.-dependent |
Why the mapping matters
Monetising patents by joining a patent pool, cross-licensing, licensing out, or litigating all rest on the same thing: a claim chart good enough to show whether a patent is essential to the standard, optional, or implementer-dependent.
Three ways a feature can map
Essential
The standard requires it — there's no way to be compliant without practising the claim.
Optional
The standard allows it, but a compliant implementation could go without it.
Implementer-dependent
Whether it's practised depends on choices the implementer makes, not the standard itself.
Against the standard, or against a product?
Both charts break the claim into clauses and map each one to evidence — they just point the mapping at different things.
Chart against a standard
Maps the claim to the words of the standard specification. Supports essentiality arguments and patent pool submissions.
Evidence of use chart
Maps the same claim to a product that's been bought, tested, or documented. Supports infringement and licensing talks with one named implementer.
Licensing programmes often need both, in that order — essentiality first, then evidence against a specific product.
The part that matters most
The inventive step of the independent claim.
That's what distinguishes the claim from what came before, so an essentiality argument stands or falls on whether the standard actually requires it. Dependent claims follow once the independent claim is settled, and cited specification documents are published after the patent's priority date.
A patent is only as valuable as the chart that proves it reads on the standard.
What we need to start
- The patent to be charted, and the standard it's said to read on.
- Family members you want covered, the relevant release of the standard, and the prosecution history.
- If the chart is going to a patent pool — the format that pool expects.
- Where claim language is implementer-dependent — which configurations matter to you.
Who it's for
SEP holders
Preparing a patent pool submission and needing the essentiality case made clearly.
Licensing teams
Opening cross-licensing or outbound licensing talks that turn on the same mapping.
Litigation counsel
Need claim-level evidence read against a published standard before proceedings start.
What you receive
- A claim chart mapping each claim clause to evidence from the standard specification documents
- A clause-by-clause breakdown of the independent claim and its inventive step
- Citations to specification documents published after the priority date of the patent
- A marking of each mapped feature as essential or optional to the standard
Frequently asked questions
What is a claim chart for SEPs?
A table that places each element of a patent claim beside the passage of a standard document that discloses it. The claim is broken into individual clauses, and every clause is mapped to evidence from the specification documents. The chart then states whether the mapped feature is essential to the standard or optional. Patent owners rely on the result when joining a patent pool, negotiating cross-licences, licensing out, or preparing litigation.
How does this differ from an evidence of use chart?
A claim chart against a standard maps the claim to the words of the standard specification. An evidence of use chart maps the same claim to a product that's been bought, tested, or documented. Both use the same clause-by-clause structure. The standard-based chart supports essentiality arguments and pool submissions; the product-based chart supports infringement and licensing discussions with one named implementer. Licensing programmes often need both, in that order.
Which part of the claim matters most in the mapping?
The inventive step of the independent claim — the most crucial aspect of the chart. That feature distinguishes the claim from what came before, so an essentiality argument stands or falls on whether the standard actually requires it. Cited specification documents are published after the priority date of the patent, and dependent claims follow once the independent claim is settled.
What do you need from us to start a claim chart?
The patent to be charted and the standard it's said to read on. Family members you want covered, the release of the standard in question, and the prosecution history all help, since the file history shows how the claim language was allowed. If the chart is going to a patent pool, the format that pool expects is useful up front. Where claim language is implementer-dependent, tell us which configurations matter to you.
Get your claim chart mapped
Tell us the patent, the standard it reads on, and where the chart is headed, and we'll scope the mapping.
