Evidence of Use Chart: What It Is, How to Build One, and How AI Automates It
An evidence-of-use (EoU) chart is a patent claim chart that maps each element of a patent claim to specific, documented evidence that a product or process performs that element. EoU charts are used in two contexts: licensing negotiations (to demonstrate to a potential licensee that their product infringes your patent) and litigation (as formal exhibits proving infringement element-by-element). A well-constructed EoU chart is the single most effective tool for converting a patent into licensing revenue — it transforms a licensing request from a speculative ask into a documented business proposition.
What Is an Evidence of Use Chart?
An evidence of use chart — also called an EoU chart, patent claim chart, or patent infringement claim chart — is a structured document that presents the legal and technical basis for a patent infringement assertion. It is organized as a table with one row per claim element (limitation), and at minimum two columns: the claim element quoted verbatim, and the corresponding evidence that a specific product performs that element.
The patent claim chart format is the standard document used by patent attorneys, IP licensing firms, and courts in every patent infringement matter. It operationalizes the legal standard for infringement: a patent is infringed if every element of at least one independent claim is present in the accused product. The chart makes this element-by-element analysis explicit, traceable, and arguable.
EoU charts serve as the foundational exhibit in licensing negotiations, demand letters, and litigation. A well-built chart signals preparation and seriousness — distinguishing a credible licensing approach from a speculative one. Companies that receive documented EoU charts are significantly more likely to engage in substantive negotiations than those that receive generic letters asserting infringement without evidence.
Evidence of Use Chart vs. Patent Claim Chart
The terms evidence of use chart and patent claim chart are often used interchangeably, but there is a meaningful technical distinction:
Patent Claim Chart
Any structured comparison of a patent's claims against a product, process, or prior art. Used in infringement analysis, validity challenges, licensing, and claim construction. Does not require real-world product evidence — an assertion or citation to prior art may suffice depending on purpose.
Evidence of Use Chart
A specific type of claim chart that requires documented, citable evidence for each claim element — showing that a real product actually performs that element. All EoU charts are claim charts; not all claim charts are EoU charts. The evidence requirement is what gives an EoU chart its persuasive power in licensing contexts.
For licensing negotiations and demand letters, always use an EoU chart (evidence required). For internal FTO analysis or claim construction exercises, a general claim chart without product evidence may suffice.
When Do You Need an Evidence of Use Chart?
Licensing Negotiations
When approaching a company to license your patent, an EoU chart documenting that their product uses your patented claims is far more persuasive than a generic licensing letter. It eliminates the licensee's ability to claim the patent is not relevant, establishes the legal basis for the license request, and demonstrates that you have done professional-grade preparation. Licensing approaches backed by EoU charts have significantly higher engagement rates than those without.
Demand Letters
A patent demand letter (a formal letter asserting patent rights and requesting a license) should always be accompanied by an EoU chart for the strongest result. The chart transforms the letter from a speculative assertion into a documented infringement analysis. Some jurisdictions have enhanced pleading standards for patent demands — an EoU chart ensures your demand meets or exceeds those standards and reduces the risk of a declaratory judgment action by the accused infringer.
Patent Litigation
In patent litigation, EoU charts are required exhibits filed with infringement contentions. Courts require patentees to provide element-by-element claim charts early in the case — typically within 14–28 days after service of the complaint under local patent rules. The litigation EoU chart must meet higher evidentiary standards than a licensing chart: each evidence citation must be to a specific product version, document, and date. A Markman hearing (claim construction proceeding) may revise claim element interpretations, requiring chart updates.
How to Build an Evidence of Use Chart: 4 Steps
The standard process for building a patent claim chart with documented evidence. Ipiry's AI automates Steps 1–3.
Parse Patent Claims into Elements
The first step is decomposing each independent claim into its individual claim elements (also called limitations). Each element becomes one row in the EoU chart. Independent claims are those that stand alone without referencing another claim — they define the broadest scope of protection and are the primary target of infringement analysis. Dependent claims (those referencing an independent claim) add additional limitations and are generally narrower.
Key rule: Quote claim language verbatim in the chart. Paraphrasing introduces interpretive ambiguity. If a claim says “receiving input data from a user interface,” that exact phrase goes in the claim element column — not “accepts user input.”
Research the Target Product
Gather all publicly available technical documentation about the target product. The strongest evidence sources, in order of persuasive value: (1) the target company's own patents — their patent claims often describe their technology in the same terms as the asserted patent; (2) technical documentation and API specifications; (3) engineering blog posts and white papers; (4) product manuals and user guides; (5) marketing materials describing product features; (6) screenshots and product demos.
Pro tip: Search the target company's name on Google Patents — their patent filings often provide the most precise technical descriptions of how their products work, and use terminology closest to the asserted patent's claim language.
Map Each Claim Element to Product Evidence
For each claim element, find the specific evidence showing the target product performs that element. This is claim element mapping — the core analytical task. The evidence must be specific: cite the document name, page number or URL, and quote the relevant passage. Evidence language that mirrors the claim element language is the strongest indicator of infringement.
Literal infringement: The product feature directly matches the claim language — the strongest basis for a chart.
Doctrine of equivalents: The product feature is substantially similar to the claimed element (performs substantially the same function, in substantially the same way, to achieve substantially the same result). Requires additional explanation in the chart.
Review for Completeness and Legal Sufficiency
Before using a chart in any legal or licensing context, review it for completeness. The all elements rule means that every element of the independent claim must be present in the accused product — missing even one element means the claim is not infringed. If you cannot find evidence for one element, you have two options: find better evidence, or document the element under doctrine of equivalents with explicit reasoning.
Have a registered patent attorney review the chart before any formal licensing demand or litigation filing. A Markman hearing may later affect claim construction — build the chart with that possibility in mind.
EoU Chart Example: Element-by-Element Mapping
The following is an illustrative evidence of use chart example showing element-by-element mapping for a hypothetical software patent claim. This format is the standard for both licensing negotiations and litigation exhibits.
Example patent claim (illustrative): “A method for processing data comprising: receiving input data from a user interface; applying a machine learning model to classify the input data; and returning a classification result to the user interface.”
| Claim Element (verbatim) | Target Product Evidence | Evidence Source |
|---|---|---|
| receiving input data from a user interface | Product accepts user text input via web form on dashboard at [URL]. Input field labeled 'Query' accepts free-text entry. | Product documentation, page 12; screenshot of dashboard input field dated March 2026 |
| applying a machine learning model to classify the input data | Engineering blog post states: 'Our system uses a fine-tuned BERT model to classify user queries into predefined categories.' Target company's US Patent 11,XXX,XXX, claim 1, recites the same classification method. | Company engineering blog, April 2024; US Patent 11,XXX,XXX (assigned to target company), claim 1, lines 42–58 |
| returning a classification result to the user interface | API response includes 'classification' field with category label. Product documentation shows result displayed in real-time on dashboard within 200ms of query submission. | API documentation v3.2, section 4.1; product demo video at [URL], timestamp 1:42 |
This example demonstrates the three requirements of a strong EoU chart: (1) claim element quoted verbatim — (2) specific evidence cited with source — (3) evidence language mirrors claim language. The AI-generated chart from Ipiry follows this exact format.
EoU Chart for Licensing vs. Litigation
EoU Chart for Licensing
- ✓Purpose: demonstrate to potential licensee that their product uses your patent claims
- ✓Format: two or three columns (element, evidence, optionally — notes on strength)
- ✓Evidence standard: credible, citable, and specific — but does not need to meet full litigation standard
- ✓Submitted alongside: licensing proposal with royalty rate and proposed terms
- ✓Legal status: not filed in court; protected by negotiation privilege in many jurisdictions
- ✓Attorney review: strongly recommended before sending, but not required for preliminary approach
EoU Chart for Litigation
- →Purpose: formal exhibit proving element-by-element infringement for the court
- →Format: structured per local patent rules (typically 3+ columns with claim construction column)
- →Evidence standard: specific product version, document version, and date for every citation
- →Filed with: infringement contentions, typically 14–28 days after service of complaint
- →Markman hearing: claim construction may require chart revisions after court's construction order
- →Attorney required: must be prepared or supervised by registered patent attorney
Ipiry's AI generates licensing-grade EoU charts. For litigation-grade charts that meet local patent rules requirements, use Ipiry's output as a starting point and have a registered patent attorney prepare the final version.
How Ipiry AI Generates EoU Charts Automatically
Building an EoU chart manually takes 4–20 hours of professional IP research, depending on the complexity of the patent and the amount of public documentation available for the target product. Ipiry's patent EoU analysis engine automates the first three steps of the process — claim parsing, product research, and element mapping — returning a preliminary chart in minutes.
Input
Patent number + target company URL or product description. The AI fetches the patent claims directly from USPTO and searches the target company's public documentation automatically.
Claim Parsing
The AI parses each independent claim into individual elements, quoted verbatim. Dependent claims are noted but independent claims are the primary analysis target.
Product Research
The AI searches the target company's patents, documentation, blog posts, and marketing materials for evidence of each claim element, prioritizing sources with the closest language match.
Output
A structured EoU chart with three columns: claim element, evidence, and source citation — in the standard licensing format. Available as on-screen display or PDF export (Professional plan).
For developers and AI agents:
Generate EoU chart: POST /api/eou/claim-chart with {patent_number, target_company_url} or {patent_number, target_product_description}. Returns [{claim_element, evidence, source, confidence}] for each independent claim element.
Download as PDF: GET /api/eou/claim-chart/{id}/pdf. See llms.txt.
Common EoU Chart Mistakes
Which Situation Applies to You?
Three use cases, three different approaches.
Approaching a Company to License
'I think Company X uses my patent — how do I approach them?'
Build a licensing-grade EoU chart documenting how their product performs each element of your independent claims. Submit the chart alongside a licensing proposal with your royalty rate anchor from Ipiry's free valuation. The chart transforms your licensing request from speculative to documented.
Generate EoU Chart with Ipiry →Building a Litigation Exhibit
'I need a formal infringement chart that meets court standards'
Use Ipiry's AI chart as the foundation — it produces a complete element-by-element mapping with cited sources. Your patent attorney then refines it to meet local patent rules requirements, adds claim construction positions, and prepares it for filing with infringement contentions.
Professional Plan for Attorney-Grade Output →Checking Your Own Product
'Does my product infringe this patent? Can I build a reverse chart?'
The same element-by-element methodology applies in reverse — instead of mapping someone else's product against your patent, you map your own product against a third-party patent to assess infringement risk. This is the core of an FTO (freedom to operate) analysis.
Run FTO Analysis Instead →Frequently Asked Questions
What is an evidence of use chart?
An evidence-of-use (EoU) chart is a formal patent claim chart that maps each element (limitation) of a patent claim to specific documented evidence showing that a product or process performs that element. The chart is presented as a two-column table: one column lists each claim element verbatim; the other column provides the corresponding evidence — product documentation, screenshots, technical specifications, or source code. EoU charts are used in licensing negotiations and patent litigation.
What is the difference between an EoU chart and a patent claim chart?
The terms are often used interchangeably, but there is a technical distinction. A patent claim chart is any structured comparison of a patent's claims against a product or prior art. An evidence-of-use chart is a specific type of claim chart focused on demonstrating actual product use of the claimed invention — it requires real, documented evidence for each element, not just an assertion. All EoU charts are claim charts; not all claim charts are EoU charts.
When do you need an evidence of use chart?
You need an EoU chart in three situations: (1) licensing negotiations — when approaching a company to license your patent, an EoU chart showing their product uses your claims is far more persuasive than a generic licensing letter; (2) litigation preparation — EoU charts are required exhibits in patent infringement cases, proving element-by-element infringement; (3) demand letters — a well-constructed EoU chart attached to a licensing demand letter significantly increases response rates and licensing closure rates.
How do you build an evidence of use chart?
Building an EoU chart requires four steps: (1) parse the patent claims into individual elements — each limitation of the independent claim becomes a separate row in the chart; (2) research the target product — gather technical documentation, product manuals, patent filings, published papers, and screenshots; (3) map each claim element to the corresponding product feature with specific, citable evidence; (4) review for completeness — every element of the independent claim must be mapped for the chart to support an infringement finding. Ipiry's AI automates steps 1–3 from a patent number and target company URL.
What evidence is used in an EoU chart?
Acceptable evidence in an EoU chart includes: product documentation and user manuals, technical specifications and data sheets, patents filed by the target company (which often describe their own technology), published academic papers or white papers, screenshots of product features or user interface elements, source code (if publicly available), marketing materials describing product features, and deposition testimony or public statements by company engineers. The strongest evidence is technical documentation that uses language mirroring the claim element language.
How is an EoU chart used in patent licensing?
In patent licensing, an EoU chart is submitted to the target licensee alongside a licensing proposal. It serves two functions: it demonstrates that the patent covers the licensee's product (establishing the legal basis for the license request), and it signals that the patent holder has done serious work — distinguishing the approach from speculative demand letters. Licensees who receive well-documented EoU charts are significantly more likely to engage in substantive licensing negotiations rather than ignoring the outreach.
What is claim element mapping?
Claim element mapping is the process of matching each individual limitation (element) of a patent claim to a corresponding feature of a product or process. Patent infringement requires that every element of at least one independent claim be present in the accused product — this is called the 'all elements rule.' Claim element mapping is the core analytical task in both EoU chart construction and patent infringement analysis.
Can AI generate an evidence of use chart?
Yes. Ipiry's AI generates a preliminary EoU chart from a patent number and target company URL. The AI parses the patent claims into individual elements, searches the target company's public documentation for evidence of each element, and produces a structured claim chart with cited sources. The AI-generated chart serves as a starting point for professional review — it requires attorney review before use in formal licensing demands or litigation. The AI chart is available to Professional and Enterprise subscribers.
Start Building Your Licensing Case
EoU chart → licensing approach → royalty income. Ipiry automates the first step.