Claim Mapping

A patent claim chart (also called a claim map or infringement chart) is a table that systematically maps each limitation (element) of a patent claim to corresponding features in an accused product or prior art reference: STRUCTURE: typically a two-column table: left column = claim language (the claim, broken into its individual limitations); right column = corresponding evidence (product features, source code, product specifications, prior art disclosures, or technical documentation); each limitation of the claim gets its own row; USES: (a) PATENT INFRINGEMENT CONTENTIONS: in litigation, plaintiffs must serve detailed infringement contentions (charts showing how each element is met by the accused product); local patent rules in most districts require this early in the case; (b) INVALIDITY CONTENTIONS: defendants must serve invalidity contentions (charts showing how each element is disclosed in prior art references — for anticipation, or how elements are distributed across references — for obviousness); (c) IPR PETITIONS: the PTAB requires claim charts in IPR petitions mapping each claim element to disclosures in the prior art; (d) FREEDOM-TO-OPERATE (FTO) OPINIONS: patent counsel prepares a claim chart showing whether each element of a potentially blocking patent reads on the client's product; (e) PATENT LICENSING: claim charts are used in licensing negotiations to show a potential licensee that their product meets the patent's elements, or to show why it doesn't; (f) DUE DILIGENCE: claim charts are used in M&A and investment contexts to assess whether a target company's products infringe third-party patents or whether the target's own patents are enforceable; THE ALL-ELEMENTS RULE: to infringe a patent claim, ALL elements of the claim must be present in the accused product or process; if even ONE element is absent, there is no infringement; this is why claim charts are element-by-element.

Building an infringement claim chart requires understanding both the claim language (after Markman construction) and the accused product's technical details: STEP 1 — CLAIM PARSING: take the independent claim and break it into its individual limitations; conventional format: preamble, transition (comprising/consisting), element 1, element 2, etc.; each limitation is placed in its own row; METHOD VS. APPARATUS CLAIMS: for method claims, map each step to the accused party's process; for apparatus claims, map each structural limitation to the accused product's structure; STEP 2 — CLAIM CONSTRUCTION: before mapping, determine the proper construction of disputed claim terms; 35 U.S.C. § 112 and the Philips standard (intrinsic evidence first: claims, specification, prosecution history; then extrinsic evidence); PTAB uses BRI (broadest reasonable interpretation) during examination and IPR; district courts use Philips construction; STEP 3 — GATHER PRODUCT EVIDENCE: collect detailed technical documentation of the accused product: product manuals, technical specifications, reverse engineering reports, source code (for software), SEC filings, marketing materials, published technical papers; depositions and responses to interrogatories provide additional evidence during litigation; STEP 4 — LITERAL MAPPING: for each claim element, identify whether the product literally (directly) has that exact structure or performs that exact step; if it does, quote the evidence in the chart (with document and page/line citation); STEP 5 — DOE (DOCTRINE OF EQUIVALENTS): if a product feature does not literally meet a claim element, analyze under DOE: does the accused feature perform substantially the same function, in substantially the same way, to achieve substantially the same result? if yes, it may still infringe under DOE; the claim chart should note whether mapping is literal or under DOE; STEP 6 — DEPENDENT CLAIMS: if the independent claim is infringed, also check whether dependent claims are infringed (they require ALL independent claim elements PLUS the additional elements of the dependent claim); some cases focus on dependent claims for higher royalty rates.

Invalidity claim charts map patent claim elements to prior art references to establish anticipation or obviousness: ANTICIPATION CHART (§ 102): (a) one prior art reference per chart; (b) map EVERY element of the claim to disclosures in that one reference; (c) if any element is missing from the reference, there is no anticipation; (d) cite specific page, figure, paragraph, line, or column/line of the reference for each element; (e) expert declaration typically accompanies the chart explaining how a POSITA would understand the cited disclosure to teach the claim element; INHERENT DISCLOSURE: if an element is not explicitly disclosed but necessarily follows from what is disclosed, it is inherent in the prior art; note inherent disclosures in the chart with an explanation of why the element necessarily results; OBVIOUSNESS CHART (§ 103): (a) uses multiple references combined; (b) one chart typically maps the primary reference, with a separate column (or separate supplemental chart) showing where secondary references supply missing elements; (c) a separate motivation-to-combine section explains why a POSITA would have combined the references; (d) must address secondary considerations (commercial success, long-felt need, failure of others) if the patent owner raises them; IPR PETITION FORMAT: PTAB's IPR petition rules require claim charts to identify each prior art reference for each claim element in a required exhibit format; excess pages require petitioner to pay for additional pages; the chart must be highly specific and cite the reference precisely; CLAIM CHART VS. EXPERT DECLARATION: in most contentions, the claim chart is submitted with an expert declaration; the chart provides the structural mapping; the expert explains the technical meanings and how a POSITA would understand the prior art; INVALIDITY CONTENTIONS IN LITIGATION: must be served per local rules (often with initial disclosures); cannot be amended freely — most districts require good cause to amend.

A claim chart must clearly distinguish whether each claim element is mapped literally or under the doctrine of equivalents (DOE): LITERAL INFRINGEMENT: the accused product or process directly has the structure, function, or step described by the claim element; example: claim element is 'a fastener comprising a threaded bolt'; the product has a threaded bolt → literal; DOCTRINE OF EQUIVALENTS: the accused feature does not literally meet the claim element BUT performs substantially the same function, in substantially the same way, to achieve substantially the same result (the FUNCTION-WAY-RESULT test from Graver Tank v. Linde Air Products, S.Ct. 1950); example: claim says 'threaded bolt'; product uses a press-fit pin; pin performs the same FUNCTION (fastening), same general WAY (mechanical connection), same RESULT (joined components) → potential DOE; LIMITATIONS ON DOE: (a) ALL-LIMITATIONS RULE: each equivalent must replace only one missing element; cannot use DOE to eliminate whole claim elements; (b) PROSECUTION HISTORY ESTOPPEL (Festo Corp. v. Shoketsu Kinzoku, S.Ct. 2002): if a claim was narrowed by amendment during prosecution to overcome a rejection, DOE is presumptively surrendered for the amended element; the patentee must rebut the presumption by showing the amendment was for an unrelated reason, the equivalent was unforeseeable, or the literal language could not have been framed to encompass the equivalent; (c) KNOWN EQUIVALENTS: if the equivalent was known at the time of patenting, there is no reason to have omitted it from the claim → DOE less likely; CLAIM CHART FORMAT FOR DOE: the DOE section of the chart explains the function-way-result analysis for the element; it also addresses whether prosecution history estoppel applies; DAMAGES: DOE infringement is full infringement — same damages as literal infringement; DOE must be pled and proved by the patentee.

Claim chart errors can result in contentions being stricken, claims being narrowed, or patents being found invalid or not infringed — even when the underlying merits are strong: MISTAKE 1 — CONCLUSORY MAPPING: writing 'this element is present because the product performs the claimed function' without citing specific evidence; courts and PTAB require specific, pinpoint citations to product documentation or prior art disclosures; fix: quote specific text from the product manual, source code, or prior art, with precise document and page/line citations; MISTAKE 2 — IGNORING CLAIM CONSTRUCTION: mapping the claim's plain English meaning when the court has already construed (or is likely to construe) the claim differently; fix: apply the court's claim construction or the most likely construction when building the chart; update the chart after Markman; MISTAKE 3 — MISSING THE PREAMBLE LIMITATION: assuming the preamble is not limiting; in many cases the preamble IS a claim limitation (Catalina Mktg. v. Coolsavings: preamble is limiting when it gives life and meaning to the claim); fix: analyze whether the preamble is limiting and map it; MISTAKE 4 — DOE WITHOUT PROSECUTION HISTORY ESTOPPEL ANALYSIS: asserting DOE for an element that was narrowed during prosecution without addressing estoppel; fix: for each DOE mapping, check the prosecution history for amendments to that element; MISTAKE 5 — SINGLE-REFERENCE ANTICIPATION CHART THAT COMBINES REFERENCES: in an anticipation chart, citing two different embodiments from the same reference as if they were a single disclosure of a complete invention; some combinations within a single reference may be improper; fix: verify that the reference discloses the combination as a single system; MISTAKE 6 — FAILURE TO ADDRESS ALL INDEPENDENT CLAIMS: focusing only on Claim 1 and ignoring other independent claims that may be easier to design around; fix: chart all independent claims (and commercially important dependent claims); MISTAKE 7 — STALE CHARTS: failing to update the chart after the product or prior art arguments change; fix: review charts before each major litigation milestone.