Claim Charting: Line-by-Line Patent Claim Analysis
Claim Charting Basics
Claim charting helps teams use claim charting search to compare patent claim elements with product features in a structured, evidence-based way. You’ve identified potentially relevant patents. You’ve screened them for relevance. Now comes the most critical step: detailed claim charting—a meticulous, element-by-element comparison of your product to patent claims.
Claim charting is where FTO analysis becomes precise. It’s the difference between a rough risk assessment and a detailed, defensible analysis. This article provides a comprehensive guide to conducting effective claim charting.
What is Claim Charting?
Claim charting is a detailed, structured analysis that maps each element of a patent claim to corresponding elements in your product. It’s designed to determine whether your product infringes the patent claim.
Why Claim Charting Matters
- Precision: Claim charting moves beyond general relevance assessment to precise infringement analysis
- Documentation: Claim charting creates detailed documentation of your analysis
- Defensibility: If FTO issues arise later, your claim charting provides evidence of your analysis
- Design-Around Opportunities: Claim charting identifies specific design modifications that could avoid infringement
- Licensing Decisions: Claim charting provides the basis for licensing negotiations
Understanding Patent Claims
What are Patent Claims?
Patent claims are the legal boundaries of a patent. They define what the patent covers and what it doesn’t. Claims are the most important part of a patent for FTO analysis.
Types of Claims
Independent Claims:
- Stand alone and don’t reference other claims
- Typically the broadest claims in a patent
- Define the core invention
- Most important for FTO analysis
Dependent Claims:
- Reference and narrow one or more other claims
- Add additional limitations to the claims they reference
- Narrower in scope than independent claims
- May be relevant if independent claims don’t cover your product
Claim Structure
Patent claims have a specific structure:
Preamble: Introduces the claim and may include limitations
- Example: “A framework for predicting occupancy comprising:”
Body: Lists the elements and their relationships
- Example: “a plurality of sensors configured to collect environmental data; a processor configured to execute a machine learning algorithm; a communication module configured to transmit predictions to a cloud server”
Transition Phrase: Connects preamble to body
- “comprising” (open-ended, may include additional elements)
- “consisting of” (closed-ended, includes only listed elements)
- “consisting essentially of” (semi-open-ended)
claim element extraction
Each claim contains multiple elements. For FTO analysis, you must identify and analyze each element.
Example Claim:
“A framework 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 algorithm that predicts occupancy based on sensor inputs; and (d) a communication module configured to transmit occupancy predictions to a remote server.”
Elements:
- Motion sensor
- Temperature sensor
- Processor with machine learning algorithm
- Communication module
- Remote server
The Claim Charting Process
Step 1: Understand the Patent
Read the entire patent:
- Read the title and abstract
- Read the specification (detailed description)
- Review the drawings
- Read all claims
Understand the invention:
- What problem does the patent solve?
- How does it solve the problem?
- What are the key technical features?
- What are the key innovations?
Identify the scope:
- What does the patent cover?
- What doesn’t it cover?
- How broad or narrow are the claims?
Step 2: Analyze the Claims
For each independent claim:
- Read the claim carefully
- Identify all elements in the claim
- Understand how elements relate to each other
- Understand any functional limitations
- Understand any structural limitations
Create a claim element list:
- List each element
- Describe what each element does
- Describe how elements relate to each other
Example Claim Element List:
Claim 1: “A framework 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 algorithm that predicts occupancy based on sensor inputs; and (d) a communication module configured to transmit occupancy predictions to a remote server.”
Elements:
- Motion sensor – detects movement in a room
- Temperature sensor – measures room temperature
- Processor – executes machine learning algorithm
- Machine learning algorithm – predicts occupancy based on sensor inputs
- Communication module – transmits predictions to remote server
Step 3: Understand Your Product
Document your product:
- How does your product work?
- What are the key technical features?
- What components does it include?
- How do components interact?
Create a product feature list:
- List each feature
- Describe what each feature does
- Describe how features relate to each other
Example Product Feature List:
Smart Home Occupancy framework:
- Passive infrared motion sensor – detects movement
- Temperature sensor – measures room temperature
- Cloud-based processor – runs machine learning model
- Machine learning model – predicts occupancy
- WiFi communication module – sends predictions to cloud
- Mobile app – displays occupancy status
Step 4: Map Product to Claims
For each claim element, identify the corresponding product element:
- Does your product include an element that corresponds to the claim element?
- If yes, how does your product element compare to the claim element?
- If no, does your product accomplish the same function in a different way?
Create a claim chart:
| Claim Element | Product Element | Literal Match? | Equivalent? | Analysis |
|---|---|---|---|---|
| Motion sensor | Passive IR sensor | Yes | N/A | Product includes motion sensor |
| Temperature sensor | Temperature sensor | Yes | N/A | Product includes temperature sensor |
| Processor | Cloud processor | Yes | N/A | Product includes processor |
| ML algorithm | ML model | Yes | N/A | Product includes ML algorithm |
| Communication module | WiFi module | Yes | N/A | Product includes communication module |
Step 5: Assess Infringement
For each claim element:
- Does your product literally include the element? (Literal infringement)
- If not, does your product include an equivalent element? (Doctrine of equivalents)
- Are there any design-around opportunities?
Literal Infringement:
- Your product includes an element that is identical or substantially similar to the claim element
- Literal infringement is the most straightforward form of infringement
- Your product includes an element that performs substantially the same function in substantially the same way to achieve substantially the same result
- Doctrine of equivalents extends patent scope beyond literal claim language
- More complex and fact-dependent than literal infringement
Example Analysis:
Claim Element: “A motion sensor configured to detect movement in a room”
Product Element: “A passive infrared sensor that detects heat signatures of moving objects”
Analysis:
- Literal Match: Yes – the product includes a motion sensor
- Function: Both detect movement
- Way: Both use sensor technology (PIR vs. other motion detection methods)
- Result: Both detect occupancy
- Conclusion: Literal infringement
Step 6: Document Your Analysis
Create detailed claim chart documentation:
- Patent number and claim number
- Claim language (full text)
- Product element description
- Infringement assessment (literal/equivalent/no infringement)
- Reasoning and analysis
- Design-around opportunities (if applicable)
- Confidence level (high/medium/low)
Example Detailed Claim Chart:
Patent: US 10,123,456
Claim: 1
Claim Language: “A framework 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 algorithm that predicts occupancy based on sensor inputs; and (d) a communication module configured to transmit occupancy predictions to a remote server.”
Product: Smart Home Occupancy framework v2.0
Element-by-Element Analysis:
Element (a): Motion sensor configured to detect movement in a room
- Product Implementation: Passive infrared (PIR) motion sensor
- Literal Match: Yes
- Analysis: Product includes a motion sensor that detects movement
- Confidence: High
Element (b): Temperature sensor configured to measure room temperature
- Product Implementation: Digital temperature sensor (DHT22)
- Literal Match: Yes
- Analysis: Product includes a temperature sensor that measures room temperature
- Confidence: High
Element (c): Processor configured to execute a machine learning algorithm
- Product Implementation: Cloud-based processor running TensorFlow model
- Literal Match: Yes
- Analysis: Product includes a processor that executes a machine learning algorithm
- Confidence: High
Element (d): Communication module configured to transmit occupancy predictions to a remote server
- Product Implementation: WiFi module transmitting to AWS cloud server
- Literal Match: Yes
- Analysis: Product includes a communication module that transmits predictions to a remote server
- Confidence: High
Overall Infringement Assessment: Literal infringement likely
Design-Around Opportunities:
- Use different sensor types (e.g., acoustic sensors instead of motion sensors)
- Process data locally instead of on remote server
- Use different machine learning algorithm architecture
Confidence Level: High
Common Claim Charting Errors
Error 1: Insufficient Understanding of Claims
Problem: You don’t fully understand what the claim covers.
Consequence: Inaccurate infringement assessment.
Solution: Read the entire patent, including specification and drawings. Understand the context and purpose of each claim element.
Error 2: Incomplete Element Identification
Problem: You miss some claim elements.
Consequence: Incomplete infringement analysis.
Solution: Carefully read each claim and identify all elements, including functional limitations.
Error 3: Oversimplified Infringement Assessment
Problem: You assess infringement as simply “yes” or “no” without detailed analysis.
Consequence: Oversimplified risk assessment.
Solution: Provide detailed analysis of each element, including literal infringement and doctrine of equivalents analysis.
Error 4: Ignoring Dependent Claims
Problem: You analyze only independent claims and ignore dependent claims.
Consequence: Incomplete analysis.
Solution: Analyze dependent claims as well, particularly if independent claims don’t clearly cover your product.
Error 5: Inadequate Documentation
Problem: You don’t document your analysis thoroughly.
Consequence: If FTO issues arise later, you can’t demonstrate your analysis.
Solution: Create detailed claim charts documenting your analysis thoroughly.
Doctrine of Equivalents Analysis
What is the Doctrine of Equivalents?
The doctrine of equivalents is a legal principle that extends patent infringement beyond literal claim language. Under this doctrine, you can infringe a patent even if your product doesn’t literally include every claim element, if your product includes equivalent elements.
The Equivalents Test
An element is equivalent if it performs substantially the same function in substantially the same way to achieve substantially the same result.
Three-Part Test:
- Function: Does the element perform the same function?
- Way: Does the element operate in substantially the same way?
- Result: Does the element achieve substantially the same result?
Example Equivalents Analysis
Claim Element: “A motion sensor configured to detect movement in a room”
Product Element: “An acoustic sensor that detects sound patterns associated with movement”
Equivalents Analysis:
- Function: Both detect movement (same function)
- Way: Motion sensor uses infrared; acoustic sensor uses sound (different way)
- Result: Both detect occupancy (same result)
- Conclusion: Likely not equivalent (different way)
Design-Around Opportunities
What is a Design-Around?
A design-around is a modification to your product that avoids infringement of a patent claim while maintaining the product’s functionality.
Identifying Design-Around Opportunities
For each claim element:
- Understand what the element does
- Identify alternative ways to accomplish the same function
- Assess whether alternatives would avoid infringement
- Assess whether alternatives would maintain product functionality
Example Design-Around
Claim Element: “A motion sensor configured to detect movement in a room”
Current Product: Uses passive infrared motion sensor
Design-Around Options:
- Use acoustic sensor instead of motion sensor
- Use video camera with computer vision instead of motion sensor
- Use pressure-sensitive floor sensors instead of motion sensor
- Use WiFi signal analysis to detect movement
Assessment:
- Option 1: Avoids claim element, maintains functionality
- Option 2: Avoids claim element, maintains functionality, but raises privacy concerns
- Option 3: Avoids claim element, maintains functionality, but more expensive
- Option 4: Avoids claim element, maintains functionality, but less reliable
Real-World Example: Claim Charting
The Scenario: A company developing a smart home framework conducted claim charting for a patent covering occupancy detection.
Patent: US 10,123,456 – “framework and Method for Predicting Room Occupancy”
Claim 1: “A framework for predicting room occupancy comprising: (a) a motion sensor; (b) a temperature sensor; (c) a processor executing a machine learning algorithm; and (d) a communication module.”
Product: Smart Home framework v2.0
Claim Charting Results:
- Element (a): Literal infringement (product includes motion sensor)
- Element (b): Literal infringement (product includes temperature sensor)
- Element (c): Literal infringement (product includes processor with ML algorithm)
- Element (d): Literal infringement (product includes communication module)
Overall Assessment: Literal infringement likely
Design-Around Options:
- Use different sensor types
- Process data locally instead of remotely
- Use different ML algorithm
Recommendation: Negotiate license or implement design-around
Best Practices for Claim Charting
1. Understand the Patent Thoroughly
Read the entire patent, including specification and drawings.
2. Identify All Claim Elements
Don’t miss any elements, including functional limitations.
3. Provide Detailed Analysis
Explain your reasoning for each element.
4. Consider Doctrine of Equivalents
Don’t assume literal infringement is the only form of infringement.
5. Identify Design-Around Opportunities
For each claim element, consider alternative approaches.
6. Document Thoroughly
Create detailed claim charts that document your analysis.
7. Involve Technical Experts
Have technical experts review your claim charting for accuracy.
8. Maintain Objectivity
Assess infringement objectively, not based on desired outcome.
Conclusion
Claim charting is the core of FTO analysis. By following the process outlined in this article, you can:
- Conduct precise infringement analysis
- Identify design-around opportunities
- Create defensible documentation
- Make informed decisions about product design and licensing
The time invested in thorough claim charting is essential for effective FTO analysis.
Key Takeaway: Claim charting is a detailed, element-by-element analysis of patent claims compared to your product. Conduct thorough analysis, consider doctrine of equivalents, identify design-around opportunities, and document everything.