How to Read a Patent Claim Chart (And Why Lawyers Use Them)

Patent claim charts are the working document of patent litigation, licensing, and IPR proceedings. Every patent attorney who has ever written a demand letter, prepared for trial, or filed an IPR petition has built dozens of them.

Yet most people who read about patent disputes never encounter a claim chart. Understanding what they are — and how to read one — unlocks a much clearer picture of what patent litigation is actually about.

What a claim chart is

A patent claim chart is a structured mapping of patent claim elements to either (a) features of an accused product (in infringement analysis) or (b) disclosures in a prior art reference (in invalidity analysis).

The format is always a table. One column contains the claim language — often broken down element by element. The other columns contain analysis: what in the accused product or prior art reference corresponds to each element, supported by documentary evidence.

The fundamental principle is the all elements rule: to infringe a claim, every element of that claim must be found in the accused product or method. A claim chart is the systematic exercise of checking every element.

Why lawyers use them

In litigation — Before filing a complaint, plaintiff's counsel builds a claim chart mapping each asserted claim element to features of the defendant's product. This forces early precision: you cannot assert infringement of claims you haven't charted. Defense counsel builds their own charts showing where elements are absent or where prior art anticipates the claims.

In licensing — When a patentee is seeking licensing fees, the opening move is typically a claim chart showing the prospective licensee how their products practice the asserted claims. The response is a counter-chart showing non-infringement or invalidity.

In IPR proceedings — An IPR petition (challenging patent validity before the USPTO) requires claim charts mapping each challenged claim element to disclosures in prior art references. These charts must be complete and specific — the PTAB won't fill in gaps the petitioner leaves.

In freedom-to-operate analysis — A lawyer reviewing whether a client's planned product would infringe existing patents builds claim charts mapping competitor patent claims to the client's product design.

How to build an infringement claim chart

Step 1: Identify the claim elements

Take the patent claim — typically claim 1 — and break it into its constituent elements. This means parsing the claim language at the commas and semicolons, treating each requirement as a separate row.

Using a simplified example: a claim to "a method for processing customer orders comprising: receiving order data from a user interface; validating the order data against inventory records; generating a shipping label containing the validated order details; transmitting the shipping label to a fulfillment system."

Four elements:

1. Receiving order data from a user interface
2. Validating the order data against inventory records
3. Generating a shipping label containing the validated order details
4. Transmitting the shipping label to a fulfillment system

Step 2: Map to accused product features

For each element, identify the feature of the accused product that corresponds to it. This requires actually understanding how the accused product works — through documentation, source code review, product testing, or reverse engineering.

Step 3: Document with evidence

For each mapping, cite the evidence. In litigation, evidence includes product documentation, marketing materials, source code, deposition testimony, and expert analysis. The chart must be supported — an attorney's naked assertion of infringement is worthless.

Step 4: Assess the gaps

Any element you cannot map to an accused feature is a gap in the infringement case. If element 3 (generating a shipping label) is performed by a third-party service, not the defendant, you have an argument to make about whether the defendant directly infringes or only induces infringement. Gaps reveal litigation risk.

Worked example: US7657849

US7657849 is a patent on a system and method for real-time network monitoring and alerting. Claim 1 (simplified for illustration):

A computer-implemented system for monitoring network activity, comprising: (a) a data collection module configured to receive network traffic data from a plurality of network nodes; (b) a rule engine configured to evaluate said traffic data against configurable threshold parameters; (c) an alert generation module configured to produce a notification when a threshold is exceeded; (d) a reporting interface configured to display network activity data to an administrator.

An infringement claim chart against a hypothetical network monitoring product:

#	Claim Element	Claim Language	Accused Product Feature	Evidence
(a)	Data collection module	"receive network traffic data from a plurality of network nodes"	NetMonitor Agent deployed on each endpoint; central collection server aggregates packet data	User Manual §3.2; Architecture Diagram v2.1
(b)	Rule engine	"evaluate...against configurable threshold parameters"	"Policy Engine" applies user-defined rules to traffic metrics; thresholds configurable via admin UI	Product Spec §4.1; Admin Guide p. 14
(c)	Alert generation	"produce a notification when a threshold is exceeded"	"Alert Manager" sends email/SMS when rules trigger; documented in Notifications Guide	Notifications Guide §2; API Documentation
(d)	Reporting interface	"display network activity data to an administrator"	Web dashboard at /admin/dashboard shows live traffic graphs and historical trends	UI Screenshots; Demo Video timestamp 4:23

If all four elements are mapped with evidence, the patentee has made out a prima facie case of infringement. The defendant's response would challenge the mappings — arguing, for instance, that their "Policy Engine" doesn't evaluate the same traffic data that the "data collection module" receives, breaking the functional chain.

Infringement charts vs. invalidity charts

Infringement charts map claim elements → accused product features.

Invalidity charts map claim elements → prior art disclosures. Instead of the accused product column, you have a prior art reference column showing where each claim element appears in a reference that predates the patent's priority date. A complete invalidity chart on a single prior art reference that accounts for every claim element supports a §102 anticipation argument (the prior art alone anticipates the claim). Partial prior art charts — multiple references needed to cover all elements — support §103 obviousness arguments.

The structure is identical. The analysis is the inverse.

Reading a claim chart handed to you

If you receive a claim chart in a demand letter or licensing negotiation, the first thing to check is whether every claim element has a corresponding entry in the accused product column — and whether that correspondence is actually supported by cited evidence or is just an attorney's assertion.

Gaps, weak mappings, and unsupported assertions in claim charts are negotiating leverage. A well-done claim chart is hard to dismiss. A sloppy one reveals an aggressive opening position rather than a strong case.

PatentBrief is not a law firm. Nothing here is legal advice.