How to Create a Claim Chart or Evidence-of-Use Chart With AI

To create a claim chart, break the selected patent claim into individual limitations, place each limitation in its own row, and map it to specific evidence from a product, process, standard, or prior-art reference. The chart should explain what the evidence shows, identify a pinpoint citation, and show whether the support is complete, partial, unsupported, or disputed.

A patent claim chart is an analytical and evidentiary document. It is not a court ruling, legal opinion, or automatic determination of infringement or validity. CASRAI describes a claim chart as an element-by-element table that compares claim language with corresponding features of a product, process, standard, or prior-art reference. CASRAI

An evidence-of-use chart, or EoU chart, uses the same basic structure but maps a claim to a specific real-world product or process. The evidence may include manuals, datasheets, technical specifications, source code where lawfully available, teardown materials, or product demonstrations. An invalidity chart instead maps the claim to one or more prior-art references.

Choose the chart type before using AI

The evidence and legal question depend on the chart’s purpose.

Chart type	Compare the claim against	Question the chart helps investigate
EoU or infringement	A specific product, service, or process	Is there evidence that the target contains each required limitation?
Prior art or invalidity	A patent, publication, or other prior-art reference	Where is each limitation disclosed?
Obviousness	A reasoned combination of references	What facts and rationale support combining the references?
FTO or non-infringement	Your product against an active claim	Which limitation appears absent, uncertain, or disputed?

For U.S. obviousness analysis, a multi-reference chart is not merely a checklist showing that different references contain different features. The analysis needs factual findings and an articulated rationale that connects those findings to the conclusion. The USPTO’s MPEP § 2143 describes the need for a reasoned link between the factual findings and an obviousness conclusion. MPEP § 2143

Prepare the evidence set first

Before opening an AI tool, assemble:

• The exact claim text, patent number, claim number, and relevant version or status.
• The purpose of the analysis, such as internal screening, licensing support, FTO, or litigation support.
• An authorized evidence set. Use product documents for an EoU chart and complete prior-art references for an invalidity chart.
• The target product or reference version, document dates, and access dates.
• A named patent professional who will review the chart before external use.

For a U.S. examination matter, claim construction requires a specific caution. The USPTO gives pending claims their broadest reasonable interpretation consistent with the specification. Courts do not use that examination standard when interpreting issued patent claims in infringement or validity proceedings. MPEP § 2111

How to create a claim chart in seven steps

1. Select a technically meaningful claim

Start with one independent claim. Once its structure and evidence are stable, add dependent claims and identify which additional limitations they introduce.

Do not begin by asking AI to chart an entire patent without defining the claim, target, evidence set, and analysis type. A narrow scope makes unsupported mappings easier to detect.

2. Read the claim in context

Review the specification, drawings, definitions, and relevant prosecution history before deciding how to divide the claim.

The claim should not be treated as an isolated sentence. The surrounding disclosure may clarify technical terms, relationships between components, or the operation required by a functional limitation.

3. Parse the claim into limitations

Create a separate row for each required structure, relationship, action, function, or result. Preserve the exact claim language in the chart.

For U.S. examination, the USPTO instructs examiners to identify and evaluate each claim limitation, then correlate each limitation with the portions of the disclosure that describe it. The MPEP also notes that the limiting effect of a preamble, “wherein” clause, functional language, or other wording depends on the facts of the claim. MPEP § 2103

A useful limitation ID might be:

• 1a: required component
• 1b: required relationship or connection
• 1c: required function or result

Keep related language together where separating it would destroy the relationship required by the claim. At the same time, avoid placing an entire long claim in one row.

4. Use a reproducible table

A practical chart can include these columns:

Limitation ID	Exact claim language	Evidence quote	Pinpoint citation	Proposed mapping	Status	Reviewer notes

Claim charts commonly place claim limitations in one column and evidence of use or evidence of publication in another. Dilworth IP

The status field should make uncertainty visible. Useful labels include:

• Candidate support
• Complete support
• Partial support
• Unsupported
• Disputed
• Needs construction review

Do not replace the evidence quote with a conclusion such as “present.” The reviewer should be able to read the cited passage and understand the proposed correspondence.

5. Collect primary technical evidence

For an EoU chart, prefer technical materials tied to the product version being analyzed. Examples include product manuals, API documentation, datasheets, technical specifications, source code where lawfully available, teardown material, and technical publications from the target company.

For an invalidity chart, use the actual patent, published application, publication, or other authorized reference. Record:

• Document title
• Publication or version information
• Relevant date
• Page, paragraph, section, figure, column, or line
• URL or file location
• Access date
• Any uncertainty about the date or version

Lumenci also identifies technical data, product images, specifications, and other supporting documentation as components of a strong claim chart. Lumenci

6. Explain every proposed mapping

For each row, explain two separate things:

1. What the evidence actually says.
2. Why that disclosure may correspond to the complete claim limitation.

The explanation should address required relationships and functions, not just individual keywords. A product document that mentions a temperature sensor may support the existence of the sensor, but it may not establish that the sensor performs every function required by the claim.

Keep evidence and reasoning separate. The evidence quote is the source material. The proposed mapping is the analyst’s interpretation of that material.

7. Check completeness and contradictions

Before relying on the chart, confirm that:

• Every limitation has a visible status.
• Each citation opens to the cited passage.
• The evidence relates to the correct product, software, or document version.
• Dates are recorded and relevant.
• The mapping addresses the full limitation.
• Weak, partial, and disputed rows remain visible.
• Conflicting documents have not been silently ignored.
• A patent professional has reviewed claim construction and the proposed conclusion.

Worked hypothetical EoU chart example

Hypothetical, not an infringement conclusion

Claim: “A monitoring system comprising: (a) a sensor configured to detect temperature; (b) a processor coupled to the sensor and configured to compare detected temperature to a threshold; and (c) an interface configured to transmit an alert when the threshold is exceeded.”

ID	Exact limitation	Proposed mapping	Evidence
1a	“a sensor configured to detect temperature”	The manual describes a temperature sensor in the device enclosure.	Product Manual v4.1, p. 12, Fig. 3
1b	“a processor coupled to the sensor and configured to compare detected temperature to a threshold”	The technical guide states that controller 210 receives readings and compares them with an administrator-set threshold.	Technical Guide v4.1, §5.2, p. 28
1c	“an interface configured to transmit an alert when the threshold is exceeded”	The user guide states that an email alert is sent when the configured threshold is exceeded.	User Guide v4.1, p. 36; screenshot capture record

This chart identifies candidate support for each listed limitation. A patent professional must still assess claim construction, product version, admissibility, and contrary evidence before reaching a legal conclusion.

Use AI for a reviewable first pass

AI can assist with the mechanical parts of chart preparation, but it should not make the final legal call.

A claim-chart product describes an AI first-draft workflow that parses claim limitations, searches user-selected documents, proposes pinpoint citations and rationales, and leaves approval, rejection, or editing to the attorney. That is a vendor-described workflow, not independent evidence of performance. &AI

Useful AI tasks include:

• Extracting approved claim and evidence text into a consistent worksheet.
• Proposing a limitation breakdown for reviewer correction.
• Finding candidate passages within an authorized document set.
• Drafting evidence quotes and pinpoint-citation fields.
• Suggesting proposed mappings.
• Flagging missing citations, duplicate evidence, version conflicts, and partial support.
• Applying consistent status labels across rows.

The human reviewer must decide whether the proposed construction is appropriate, whether the citation supports the entire limitation, whether a doctrine-of-equivalents issue requires separate analysis, whether a multi-reference obviousness rationale is supported, and whether the chart can support an external assertion or filing.

For matters before the USPTO, existing rules and professional obligations apply regardless of how a submission was generated. The USPTO’s guidance specifically warns practitioners to address the risks of AI use and not leave AI-generated work unchecked. USPTO AI-use guidance

Prompt template for a first-pass chart

Objective: Create a draft [EoU / prior-art / non-infringement] chart for Claim [number] of [patent number]. Use only the authorized evidence set.

For each limitation:
1. Preserve the exact claim language.
2. Assign a limitation ID.
3. Quote candidate evidence verbatim.
4. Give a pinpoint citation.
5. Explain the proposed correspondence.
6. Do not reach an infringement, invalidity, or essentiality conclusion.
7. Label the row candidate support, partial, unsupported, or disputed.

Output:
Limitation ID | Claim language | Evidence quote | Pinpoint citation | Proposed mapping | Status | Reviewer notes

Common failure cases and final checks

Watch for these recurring failures:

• Keyword matching instead of full-limitations analysis.
• Marketing copy with no technical support.
• AI-generated citations that a reviewer has not opened.
• Mixed product, software, or document versions.
• Treating a similar feature as proof of the claimed relationship or function.
• Combining prior-art references without stating the factual basis and rationale for the combination.
• Hiding unsupported rows in a summary conclusion.

A chart is ready for professional review when every limitation has a status, citations are pinpoint and reproducible, evidence is distinct from reasoning, weak rows are visible, and the proposed conclusion has not outrun the record.

Where Esgenix fits

Esgenix is a decision-gated agentic patent workflow platform, not litigation counsel or an EoU-chart service. Its invalidity workflow states that it maps claim elements to disclosing passages and produces a claim-chart report reviewed before release. Invalidity Analysis

That reflects an important workflow principle: the system that generates an analysis should not be its only reviewer. Esgenix separates production from professional judgment through five decision gates: Intake, Strategy, Claims, Specification & Figures, and Sign-off.

For teams evaluating AI-assisted patent analysis, the practical standard is simple: use AI to organize evidence and propose a first pass, then keep claim construction, evidence assessment, legal reasoning, and external reliance under professional control.

Bring a granted claim set and its closest references to a demo of Esgenix’s decision-gated patent workflow.