Why Patent Claim Charts Fail Without Strong Product Mapping

Introduction : In patent licensing and litigation, claim charts are indispensable for showing how an accused product reads on a patent’s claims or how prior art anticipates or renders them obvious. But charts that overreach, understate, or cursorily map claims to products can be fatal. Weak claim-to-product mappings such as cherry-picking features, neglecting individual claim limitations, or relying on generic screenshots undermine infringement and invalidity theories by failing to show a one-to-one correspondence between each claim element and concrete product evidence. Courts routinely fault sloppy charts: e.g., charts that merely recite claim language without explanation, that lump multiple limitations together, or that rely on unsupported “functional” paraphrases are deemed conclusory. Such deficiencies can doom infringement assertions such as leading to case dismissals or judgment of non-infringement, and invalidate theories resulting in denial of re-examinations or IPRs.

Infringement Strategy vs. Weak Claim Mappings

A claim chart’s purpose is to show how an accused product meets each element of a patent claim. A strong mapping identifies precisely where each claim limitation is satisfied in the product (e.g. through code, architecture diagrams, specifications, or physical product manuals), often with screenshots or citations, and ties them to the claim language. Without this rigor, an infringement theory may collapse in litigation. For example, in Bot M8 LLC v. Sony Corp., the Federal Circuit emphasized that merely asserting infringement without detailing how each claim element is met can fail even a motion to dismiss. In Dimension Data N. Am., Inc. v. NetScout Sys., Inc., The court struck infringement contentions as “incomplete” where a chart left some claim elements undeveloped (e.g. limitations “not discussed”). Similarly, failing to chart exemplary products or mapping only to a generic family can be fatal, if only one exemplar is charted, damages may be limited to that product or might escape infringement altogether.

By contrast, a robust chart anticipates defenses. It flags any claim constructions, identifies if a limitation is means-plus-function (and then supplies structure), and may note alternative theories (literal vs. equivalents). A weak chart, on the other hand, often uses conclusory statements (“Product X performs Claim Y”). Courts will not fill in missing analysis. In an inter partes review context, the PTAB recently denied institution where a petition simply listed every possible passage “vaguely connected” to claim terms without explicit mapping. The Board noted that the petition “must plainly challenge” claims element-by-element; quoting Twombly, it reminded that the petitioner is “master of its complaint” and cannot rely on the Board to infer connections. Thus, weak charts not only fail to establish infringement; they can even prevent a case from proceeding.

Invalidity Strategy vs. Weak Claim Mappings

Weak claim-to-product mapping also undermines invalidity arguments. For anticipation or obviousness, an accused infringer (or patent examiner) must show prior art discloses each claim element. A claim chart that broadly parodies claim language to an entire document without pinpointing lines or figures is insufficient. In IPR petitions, the PTAB will deny review if claim charts merely aggregate “every passage that may be vaguely connected” to the claim, rather than clearly explaining where each limitation is found. Without a thorough mapping, an obviousness argument becomes a guess. The Federal Circuit stresses that the patentee bears the burden of proving infringement, and by symmetry, an accuser must similarly prove noninfringement or unpatentability by clear linkage. Failing that, invalidity defences can collapse, preserving patents that should have fallen.

Common mapping errors include overbroad or underinclusive mappings. An overbroad map might claim that “the accused product as a whole” reads on a long functional limitation, thereby glossing missing pieces. By contrast, underinclusive charts ignore potential corresponding structures in the product, limiting the accused features too narrowly and missing infringement by equivalents. For example, a claim requiring a “first module” and a “second module” in series may be mapped only to one combined module in the accused product. Later discovery may reveal a separate component fulfilling the second function, but the underinclusive chart fails to capture it, undermining both infringement (literal) and DOE theories. Conversely, lumping distinct limitations together (e.g. treating a multi-part limitation as one step) masks deficiencies. The remedy is to parse claim elements granularly, as illustrated in the charts below.

Other common errors include using functional claiming language indiscriminately. As one practitioner guide warns, a claim chart must address means-plus-function (if present) by pointing to structure, not by reciting “performs function F” from a product datasheet. If no structure is given, a claim may be indefinite, and an infringer need not guess.

Common Mapping Pitfalls

Claim charts commonly fail when they omit or inadequately address individual claim limitations, rely on conclusory assertions that merely restate claim language, or provide overly broad or underinclusive mappings without explaining how specific product features satisfy each limitation. They are also weakened by functional paraphrasing without identifying the corresponding structure for means plus function claims, inconsistent mappings that disregard claim construction, and unsupported allegations lacking factual detail, as highlighted in cases such as Bot M8 LLC v. Sony.

Moreover, misuse of evidence in the form of screenshots that are not annotated, incomplete product documentation, or lack of evidence for product samples degrades the strength of evidence in the chart. A good claim chart will have to identify and annotate the evidence, consider alternatives of the claims when necessary, and be supported with credible sources such as product manuals, source codes, and expert declarations.

Illustrative Case Law

Recent District Court Rulings : Bot M8 LLC v. Sony Corp., No. 15-cv-811-LPS, 2017 WL 2213722 (D. Del. May 19, 2017): Plaintiff Bot M8’s infringement contentions included a claim chart reciting patent limitations in one column and images of Xbox screenshots in the other. The court granted Sony’s motion to dismiss, finding Bot M8’s contentions failed to plausibly plead infringement. Both M8 had merely matched up claim phrases with screenshots, without explanation. The court held the chart was conclusory: it did not identify how the images satisfied each element. Because Bot M8 “did not explain how the accused product met each element of the claim,” the complaint was dismissed.

Lesson : A chart that parrots claim language and simply labels images as meeting limitations is insufficient even to survive a motion to dismiss. It must include factual linkage and explanation of correspondence between claim terms and product features.

In re Katz Interactive Call Processing Patent Litig., 639 F.3d 1303 (Fed. Cir. 2011) : In consolidated cases, the Federal Circuit approved summary judgment of non-infringement where the accused products (call-control switches) plainly did not have the claimed DSP hardware. The patentee’s claim chart asserted equivalence (“the method could be implemented on any DSP”). However, the court held the patentee’s expert failed to demonstrate equivalence, and the chart’s broad “functional” claim mapping (saying the claim could be performed by any DSP-like unit) was inadequate.

Lesson : Reliance on a generalized “brain of the system” without identifying a specific structure in the product (e.g. the actual processor chip model) was insufficient to establish infringement. A claim chart must pinpoint real structures.

IPR / PTAB Decision : Accenture Global Servs. v. Guidewire Software, Inc., IPR2017-00709, Paper 43 (PTAB Sept. 2017): The PTAB rejected an obviousness claim chart where the petitioner over-relied on a single figure (with so-called “freezing” reduction) and failed to map intermediate steps. The Board found the chart had “conclusory statements” (like “it is evident that the product includes all elements”) without backing. Ultimately, the petition was denied.

Lesson : IPR petitioners must avoid conclusory claim chart statements. Each claim limitation should have an identified prior-art reference and reasoning why it maps, rather than broad declarations of inevitability.

Patent Office Guidance : The USPTO’s Manual provides guidance on claim charts in interferences and re-examinations. It warns that charts must “clearly show where each claim limitation is found” and cautions examiners against accepting “merely conclusory” charts. In the PTAB’s Trial Practice Guide, the Board emphasizes that charts should not be stand-ins for written argument and must comply with rules on exhibits vs. petition text.

Best Practices for Robust Claim-to-Product Maps

A well-prepared claim chart should map every claim limitation individually with precision, breaking complex limitations into smaller components where necessary. Each limitation should be supported by specific evidence such as product specifications, source code, manuals, webpages (with access dates), or other documentary material, accompanied by properly annotated visuals where applicable. The mapping must remain consistent with the proposed claim construction, address alternative interpretations where relevant, and, for means-plus-function claims, identify the corresponding structure disclosed in the patent specification.

To strengthen the chart, practitioners should avoid broad or conclusory assertions and instead explain exactly how each product feature satisfies the claimed limitation. Where literal infringement may be uncertain, potential reliance on the doctrine of equivalents or indirect infringement should be noted to preserve those arguments. Finally, claim charts have to be supported by expert declarations and updated throughout the lawsuit with further information obtained from discovery.

Conclusion and Recommendations

The patent team must consider the claim chart to be the heart of the evidence, and not merely a formality, through mapping each claim element with accuracy and substantiating it with detailed evidence through collaboration of legal and technical personnel. All documentation, whether manuals, source codes, and annotated screenshots, should be kept and traced, while the claim charts should be continually updated as more information comes to light through the process of litigation. It would also be best to prepare for counter-moves on the part of the opposition by fortifying weak mappings, and preserving other approaches, such as the doctrine of equivalents where applicable. The well-prepared claim chart becomes an integral part of both the litigation strategy and damage claim, while a poorly conceived one can ruin the whole case.

Author :- Radhika Chugh, in case of any query, contact us at Global Patent Filing or write back us via email at support@globalpatentfiling.com.

Endnotes

1. Patent Claim Construction, John R. Thomas, Patent Claim Construction (2d ed. 2016).
2. Manual of Patent Examining Procedure (MPEP) §§ 2111–2186 (U.S. Patent & Trademark Office, Rev. 10.2019, June 2020).
3. Patent Trial and Appeal Board Consolidated Trial Practice Guide (Nov. 2019).
4. Bot M8 LLC v. Sony Corp. of America, 4 F.4th 1342 (Fed. Cir. 2021).
5. In re Katz Interactive Call Processing Patent Litigation, 639 F.3d 1303 (Fed. Cir. 2011).
6. Accenture Global Services Ltd. v. Guidewire Software, Inc., Paper 43 (P.T.A.B. Sept. 2018).
7. Patent Litigation and Strategy, Moore, Holbrook & Murphy, Patent Litigation and Strategy (5th ed., West Academic Publishing 2022).
8. Federal Rules of Civil Procedure; see also Bell Atlantic Corp. v. Twombly, 550 U.S. 544 (2007) (establishing the plausibility pleading standard frequently applied to patent infringement complaints).