1 / 10

How to Create a Claim Chart for Patent Infringement | IIP Search

Learn how to create a claim chart for patent infringement with this detailed guide. Understand each stepu2014from breaking down patent claims to mapping them against accused products using clear, factual evidence. Includes real examples, best practices, common pitfalls, and FAQs to help you build a strong, defensible claim chart for litigation, licensing, or valuation purposes. Whether you're a patent owner, attorney, or analyst, this resource provides the clarity and structure needed to prove or refute infringement effectively.<br><br>https://iipsearch.com/all-services/24/evidence-of-use-claim-chart

iipsearch
Download Presentation

How to Create a Claim Chart for Patent Infringement | IIP Search

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. How to Create a Claim Chart for Patent Infringement: Step-by-Step Guide with Examples and Best Practices IIP Search In patent litigation and licensing negotiations, one tool holds a central role: the claim chart. Whether you are enforcing your patent rights or defending against infringement allegations, a well-prepared claim chart can define the trajectory of your case. Photo by NEW DATA SERVICES on Unsplash This comprehensive guide walks you through the exact process of creating a claim chart for patent infringement. It includes practical steps, key insights, examples, common mistakes to avoid, tools, and

  2. FAQs — everything you need to build a strong, fact-based comparison of patent claims against an accused product or process. What is a Claim Chart and Why It Matters A claim chart is a structured document that aligns the elements of a patent claim with corresponding features in a potentially infringing product or process. Each row matches a claim element with supporting details, often including technical documentation, product descriptions, screenshots, or teardown analysis. Claim charts are used in: ● Patent infringement lawsuits ● Evidence of Use (EOU) presentations ● Licensing discussions ● Patent valuation exercises ● Inter partes reviews (IPRs) They help stakeholders: ● Determine whether all elements of a claim are present in a product ● Communicate findings clearly to courts, licensing targets, or opposing counsel ● Build or defend legal arguments based on objective comparisons Without a claim chart, patent assertions often lack clarity. With one, you present a logical, visual, and persuasive argument backed by evidence.

  3. Key Components of a Claim Chart A claim chart typically includes: 1.The patent claim language — Copied verbatim from the patent, broken into individual elements or limitations. Each limitation corresponds to a specific function or component. 2.Mapping to the accused product — A description of how each claim element is implemented or found in the target product or process. 3.Supporting evidence — This can include public documentation, teardown photos, user manuals, marketing brochures, API references, or source code. 4.Legal and technical annotations — Brief comments explaining how the mapping supports a finding of infringement, often from patent attorneys or technical experts. 5.A structured format — While many use two-column tables, the essence lies in clarity: each claim element must be addressed distinctly and backed by factual detail. Step-by-Step Process to Create a Claim Chart Step 1: Understand the Patent Claims Start by analyzing the claims, not just the patent summary. Claims define the scope of legal protection.

  4. Focus on: ● Independent claims, which provide broad coverage ● Dependent claims, which add specific features or limitations Break each claim into distinct elements. For example, a claim for a mobile phone might include: ● A touch-sensitive display ● A processor ● A memory storing executable instructions ● A wireless transceiver Each of these becomes a separate item to evaluate in the accused product. Use the patent specification to interpret any ambiguous language and review prior litigation to check if the claims have been construed by the courts. Example: If Claim 1 describes “a wireless transceiver configured to transmit digital packets,” make sure you understand what counts as a “wireless transceiver” and what “configured to” implies in legal terms. Step 2: Analyze the Accused Product or Process Thorough knowledge of the product under scrutiny is essential. Identify: ● How the product works ● What its components are ● How its features correspond to the claimed invention Gather sources such as: ● User guides ● Technical specifications ● Product teardown images ● Source code (when available) ● Marketing material

  5. ● Third-party reviews ● Product datasheets Publicly available materials are valuable in pre-litigation and licensing efforts. For litigation, discovery can be used to gather confidential documents under protective orders. Example: A teardown of a smartwatch may reveal a specific chip or component, helping confirm whether a processor matches the one mentioned in the patent claim. Step 3: Map Each Claim Element to the Product For each claim element, identify where that feature exists in the product. Use precise descriptions. Avoid vague phrases like “it seems like” or “it may include.” Instead, describe what the feature is, where it’s located, and how it functions in relation to the claim. Example: ● Claim Element: “A memory storing executable instructions for gesture recognition” ● Product Mapping: “Product X uses 128 GB onboard memory containing gesture recognition software, as shown in the instruction manual, p. 15.” This mapping should be logical, defensible, and based on observed or documented product features. Step 4: Add Supporting Evidence Each mapping must be backed by proof. This could include: ● Annotated product manuals ● Screenshots from the product UI ● Source code files

  6. ● Device teardown reports (e.g., iFixit) ● FCC filings ● Internal architecture diagrams (if available) The stronger your evidence, the harder it is for the opposing side to refute your chart. Evidence should be clearly linked to each claim element and include labels or citations. Example: To prove a “GPS module” is present, you might cite a teardown image showing the GPS chip, supported by the product manual stating GPS capabilities. Step 5: Format the Claim Chart Clearly Although traditional claim charts are often in table format, the goal is clarity. Present each claim element followed immediately by: ● The corresponding product feature ● Supporting explanation ● Evidence reference Ensure consistent terminology. Number each claim element and use headings or formatting to keep the structure easy to follow. Clarity helps both legal and technical teams quickly assess the logic and strength of the mapping. Real-World Example Case Study: A semiconductor company alleged that a competing device infringed its patent on a specific chip design. The plaintiff’s team built a claim chart that matched each claim element to the functions of the competitor’s chip, referencing die photos from a reverse engineering firm.

  7. The evidence included cross-sectional analysis, datasheets, and software behavior. When presented during licensing negotiations, the detailed claim chart led to a $12 million settlement without litigation. This case illustrates the power of a well-documented, technically accurate claim chart in asserting patent rights. Best Practices for Creating Effective Claim Charts ● Always use verbatim claim language ● Break claims into logical, discrete elements ● Collect multiple forms of evidence where possible ● Use plain language to explain mappings ● Avoid assumptions — base conclusions only on documented proof ● Involve both legal and technical experts to validate the chart ● Keep formatting consistent and easy to navigate ● Regularly review for completeness and accuracy These steps increase the credibility and usefulness of the chart in legal or business settings. Common Mistakes to Avoid ● Avoid these pitfalls when building a claim chart: ● Omitting a claim element entirely ● Combining multiple elements into one response ● Failing to provide clear evidence ● Using overly technical or vague language ● Interpreting claim terms without legal basis

  8. ● Over-relying on marketing language instead of technical specs One weak element can undermine the whole infringement argument. A comprehensive, element-by-element approach is essential. When and Why to Use a Claim Chart Claim charts are used at multiple points in the patent lifecycle: ● Before litigation: To evaluate potential infringement and approach potential licensees ● During litigation: As part of pleadings, infringement contentions, and trial evidence ● In licensing discussions: To show how an existing product uses your patented technology ● During portfolio analysis: To assess enforceability and monetization potential For patent holders, claim charts increase leverage. For accused parties, they help assess risk and form defenses. Tools and Resources for Building Claim Charts You don’t always need expensive software, but some tools can streamline the process: ● Microsoft Word / Google Docs: For custom formatting ● ClaimMaster: Claim parsing and formatting automation ● NLPatent / EOU Builder: AI-powered chart generation and EOU analysis ● USPTO Patent Database: For claim texts and file histories ● iFixit / FCCID.io: For product teardowns and documentation

  9. Regardless of the tool, what matters is accuracy, completeness, and clarity. Frequently Asked Questions Q1: Can I create a claim chart without a legal background? You can gather information and start mapping claim elements, but legal interpretation of claims should be handled by a patent attorney. Collaboration is key. Q2: Do I need access to the product’s internal documentation? Not always. Many claim charts rely on public data, especially in pre-suit analysis. For litigation, discovery can provide internal documents. Q3: What’s the difference between an EOU chart and a standard claim chart? An Evidence of Use (EOU) chart is a type of claim chart tailored for licensing or valuation, often with more business-oriented annotations. It serves the same core purpose: mapping claims to real-world use. Q4: Can software patents be charted effectively? Yes. Use screenshots, source code snippets, API documentation, and functionality descriptions. Software-based charts often require precise technical language and evidence. Q5: Is it worth outsourcing claim chart preparation? Absolutely. Professional services bring legal, technical, and formatting experience. This reduces errors and enhances the chart’s persuasiveness.

  10. Final Thoughts Creating a claim chart for patent infringement is both an art and a science. It requires a meticulous approach to parsing patent claims, a technical understanding of the accused product, and detailed documentation that maps every claim element to solid evidence. Done right, a claim chart becomes a powerful tool for proving infringement, driving licensing deals, or defending against accusations. It adds clarity, structure, and credibility to any patent enforcement or defense strategy. If you’re looking to build an effective, court-ready claim chart — whether for litigation, licensing, or valuation — consider working with professionals. Explore our Evidence of Use (EOU) Claim Chart Services to ensure your next chart is accurate, defensible, and persuasive.

More Related