Claim Charting Basics for FTO Analysis
Claim charting maps each patent-claim limitation to controlled product evidence so FTO reviewers can see matches, gaps, assumptions and open legal questions.
Freedom to Operate · Claim AnalysisYou have identified potentially relevant patents and screened them for technical relevance. The next step is a limitation-by-limitation comparison between an asserted claim and a specific product or process. A useful chart records evidence and reasoning; it does not turn technical similarity into an automatic infringement conclusion.
In U.S. litigation, literal infringement is assessed after claim construction by comparing the properly construed claim with the accused product. Every limitation must be found in the accused product.1 Other jurisdictions apply their own rules, so the governing law, claim version, territory and relevant acts must remain visible throughout the review.
What is claim charting?
Claim charting is a structured comparison that places each claim limitation beside the corresponding product or process evidence. It helps reviewers determine which limitations appear present, which appear absent, which require interpretation and which lack enough evidence for a conclusion.
The chart supports an infringement-risk assessment but is not itself a court finding or legal opinion. Eureka FTO Search builds and refines searches from a product description, screens potentially relevant patent claims with legal-status context and organizes evidence into claim-level comparisons.2 Users and qualified professionals must still verify claim meaning, product facts, status and jurisdiction-specific conclusions.
Why claim charting matters
- Precision: moves the review from general technical similarity to individual limitations.
- Documentation: records sources, assumptions, missing evidence and reviewer reasoning.
- Reviewability: lets technical and legal reviewers challenge a specific row rather than an unexplained risk label.
- Design alternatives: shows which product features might be changed and then re-charted.
- Business decisions: supplies evidence for counsel-led licensing, redesign, challenge or residual-risk discussions.
Understanding patent claims
What patent claims do
Claims define the matter for which patent protection is sought or granted, but their operative scope requires interpretation under the applicable legal framework. Read the claim language together with relevant intrinsic evidence and do not import a preferred embodiment merely because it appears in the description.
Independent and dependent claims
An independent claim does not incorporate another claim by reference. A dependent claim adds a further limitation and incorporates the limitations of the referenced claim. Under 35 U.S.C. § 112(d), a U.S. dependent claim must be construed to include all limitations of the claim to which it refers.3 Therefore, if a product lacks a required limitation of the parent claim, the narrower dependent claim does not cure that missing limitation. Review dependent claims when the product may satisfy the inherited limitations and the added limitation.
Claim structure
- Preamble: introduces the claimed subject matter; its limiting effect is context-specific.
- Transition: connects the preamble to the body.
- Body: states components, steps, functions, relationships and conditions.
USPTO guidance treats “comprising” as generally open-ended, while “consisting of” is generally closed to unrecited matter. However, the effect of transitional language is assessed case by case in the complete claim.4 Open-ended language allows additional features; it does not make any recited limitation optional.
Extract every limitation
Before mapping a product, preserve each structural, functional, relational, temporal, quantitative and conditional requirement. The related Patsnap guide to extracting claim limitations explains how to choose rows without detaching modifiers from the language they qualify.
“A device for predicting room occupancy comprising: (a) a motion sensor configured to detect movement in a room; (b) a temperature sensor configured to measure room temperature; (c) a processor configured to execute a machine-learning model that predicts occupancy based on sensor inputs; and (d) a communication module configured to transmit occupancy predictions to a remote server.”
The claim charting process
Step 1: understand the patent record
Read the claims, description and drawings. Review the prosecution history when it may affect claim meaning or equivalents. Confirm the patent family, relevant jurisdiction, current legal status, ownership record, asserted or selected claim version and review date. Keep validity, enforceability and infringement as separate questions.
Step 2: analyze the complete claim
Identify every limitation and dependency. Preserve verbatim language beside any normalized label. Record disputed terms and possible constructions instead of silently choosing the interpretation that produces a preferred outcome.
- motion sensor configured to detect movement in a room;
- temperature sensor configured to measure room temperature;
- processor configured to execute the stated model and prediction function; and
- communication module configured to transmit the stated output to the stated destination.
Step 3: document the controlled product
Use a dated product version and reliable evidence: specifications, architecture records, source-code references, test results, supplier documentation, photographs or process instructions. Describe what the product actually does, where each function occurs and which facts remain unverified. A marketing label is rarely enough evidence for a claim limitation.
Step 4: map evidence to each limitation
For every row, cite the exact product evidence and classify the mapping as supported, apparently absent, disputed or unresolved. Avoid a bare “Yes/No” column. Eureka FTO Search organizes patent-search evidence and claim-level comparisons.2 Its output remains subject to source verification and professional review.
| Claim limitation | Product evidence | Preliminary mapping | Reasoning / open question |
|---|---|---|---|
| motion sensor configured to detect movement in a room | Controlled specification identifies a passive infrared detector | Potentially supported | Confirm the construed meaning of “motion sensor” and actual operating mode |
| temperature sensor configured to measure room temperature | Bill of materials and test record identify a temperature sensor | Potentially supported | Verify measured location and use |
| processor configured to execute the stated prediction model | Architecture record identifies remote model execution | Unresolved | Does the construed “processor” limitation cover the distributed implementation? |
| communication module configured to transmit predictions to a remote server | Interface log shows data transmission | Unresolved | Confirm that the transmitted data are the claimed predictions |
Step 5: assess literal infringement and equivalents separately
For U.S. literal infringement, ask whether every limitation, as properly construed, is present. If one limitation is not literally met, do not relabel technical similarity as literal infringement. Any doctrine-of-equivalents review should use a separate column or memorandum because it applies different, fact-specific legal questions.
Step 6: document conclusions and next actions
Record the patent and claim identifiers, source links, product version, evidence citations, constructions used, legal status date, jurisdiction, assumptions, unresolved facts and reviewer. State conclusions at the level supported by the record, such as “requires counsel review” or “one limitation appears absent under the stated construction.” Manage confidentiality, privilege and distribution with counsel; a detailed chart can become sensitive evidence.
Patsnap’s five-step FTO workflow shows how detailed charting connects with earlier search and screening and later mitigation decisions.
Common claim charting errors
Error 1: insufficient claim understanding
Problem: mapping plain-English concepts before resolving important claim terms.
Correction: read the intrinsic record and flag interpretation questions for qualified counsel.
Error 2: incomplete limitation identification
Problem: charting nouns while omitting functions, relationships, sequence or conditions.
Correction: preserve the complete limitation text and dependency chain.
Error 3: oversimplified infringement labels
Problem: calling an item a literal match because it is similar or serves a similar business purpose.
Correction: cite product evidence, apply the stated construction and explain each row.
Error 4: mishandling dependent claims
Problem: charting only the added words or assuming a dependent claim can cover a product that misses a parent limitation.
Correction: assemble all inherited and added limitations.
Error 5: weak documentation
Problem: omitting product versions, evidence citations, status dates, assumptions or reviewers.
Correction: use a controlled record that another qualified reviewer can reproduce.
Doctrine of equivalents analysis
What the U.S. doctrine addresses
Under U.S. law, a product that does not literally meet a limitation may, in some circumstances, still infringe through an equivalent. The Supreme Court requires the inquiry to operate element by element rather than on the invention as a whole. It explained that function-way-result and insubstantial-differences formulations may be useful depending on the facts, but neither is an automatic checklist.5
Questions for a separate equivalents review
- What role does the claimed limitation play in the claim as a whole?
- What role does the accused feature play?
- Are the differences substantial under the applicable test?
- Would the proposed equivalence effectively eliminate a claim limitation?
- Does the prosecution history indicate surrendered subject matter?
- Do other limits, including prior-art constraints, affect the permissible range?
Prosecution history estoppel can restrict reliance on equivalents after a narrowing amendment made for a reason related to patentability, subject to the framework and rebuttal routes described in Festo.6
Design-around opportunities
What a design-around review does
A design-around review explores product changes that may avoid one or more claim limitations while preserving acceptable performance. It is an engineering and legal iteration, not a one-time list of substitutes.
How to evaluate candidates
- Identify the limitation driving the concern.
- Develop technically feasible alternatives.
- Update the product description and evidence.
- Re-chart the complete claim, including relationships and dependent claims.
- Review literal infringement, equivalents and other relevant patent families.
- Document business, safety, privacy, regulatory and performance trade-offs with the responsible teams.
Acoustic sensing, image-based detection, pressure sensing or radio-signal analysis may be engineering candidates in the teaching example. None can be declared a successful design-around without reviewing the actual claim, product implementation and applicable law.
Worked example: claim charting
Assume a company is developing an occupancy-detection product and is reviewing the fictional teaching claim above. The team charts each complete limitation against a controlled product version rather than using the fabricated patent number that often appears in informal examples.
The motion- and temperature-sensor rows have supporting technical records. The processor and transmission rows remain unresolved because computation occurs remotely and the content of transmitted data needs verification. The team therefore does not record “literal infringement likely.” It identifies the disputed constructions and missing evidence for counsel and technical reviewers.
Potential design alternatives are treated as candidates. Each candidate receives a new product version and a fresh chart. Licensing, redesign, validity work or residual-risk acceptance is considered only after legal status, jurisdiction, claim scope and business facts have been reviewed.
Best practices for claim charting
- Understand the full patent record. Review claims, description, drawings and relevant prosecution history.
- Identify every limitation. Include functions, relationships, conditions and dependent-claim inheritance.
- Use controlled product evidence. Cite dated, version-specific technical records.
- Separate fact from interpretation. Mark assumptions and competing constructions.
- Separate literal and equivalents analysis. Do not use “substantially similar” as a literal-infringement test.
- Re-chart design alternatives. A substitute component may affect several limitations or other patents.
- Involve technical experts and counsel. Each reviews a different part of the evidence and legal framework.
- Maintain objectivity and confidentiality. Record adverse evidence and manage privilege and distribution deliberately.
Conclusion
Claim charting makes FTO analysis reviewable by connecting every limitation to product evidence, reasoning and open questions. It can reveal missing facts, disputed interpretations and possible design alternatives more clearly than a single risk label.
However, claim charting does not independently establish infringement, noninfringement or freedom to operate. Qualified professionals must apply the governing law to verified claims, status, jurisdiction and product facts.
Sources and verification
- Zip Top, Inc. v. SC Johnson & Son Inc., No. 2024-1661, slip op. at 14 (Fed. Cir. Dec. 30, 2025). Opinion.
- Patsnap, “Eureka IP Searching.” Accessed August 3, 2026. Source.
- 35 U.S.C. § 112(d), “Reference in Dependent Forms.” Source.
- USPTO, MPEP § 2111.03, “Transitional Phrases.” Source.
- Warner-Jenkinson Co. v. Hilton Davis Chemical Co., 520 U.S. 17 (1997). Opinion.
- Festo Corp. v. Shoketsu Kinzoku Kogyo Kabushiki Co., 535 U.S. 722 (2002). Opinion.
Sources verified August 3, 2026. The occupancy claim and product examples are fictional teaching materials. This article provides general information, not legal advice, an infringement opinion or an assurance of freedom to operate. Consult qualified counsel in each relevant jurisdiction.
