Mastering Patent Claim Construction with LLMs (3): Injecting Guidelines for Claim Chart Drafting

Practical Framework Part 3

Mastering Patent Claim Construction with LLMs (3)

Injecting Claim Chart Drafting Guidelines Drawn from Practical Experience

The next step is a research phase aimed at establishing the format of the final deliverable.

Rather than organizing claim construction results into a simple narrative report, I prefer to structure them in the form of a Claim Chart specifically designed for claim interpretation. This is not merely to make the output look polished, but to secure a practical tool that can be used under a consistent standard in all downstream tasks, including infringement analysis, invalidity review, and opinion drafting.

1. Why Claim Chart Standards Must Be Established First

There is one important point here. A Claim Chart is not just a “format for organizing results,” but a core framework that determines the quality of the interpretation itself.

The problem, however, is that the method for decomposing claims, the standards for extracting elements, and the actual drafting approach are not systematically organized in textbooks or case law. In other words, this is an area where methodology is built largely 👉 through practical experience.

Through handling a wide range of cases, I have gradually developed my own standards for claim decomposition, element extraction, and chart structure in a way that is suitable for claim construction.

2. Teaching the LLM the “Drafting Method” First

At this stage, what I do is simple. I organize the standards I use in practice 👉 the way I would teach a junior associate, and then register them as a source in NotebookLM.

A Critically Important Point

This step is not simply about “adding reference materials.” It is the process of pre-training the LLM on the interpretive framework and the output format so that it will reason under the same standards in all later interpretation tasks.

• This is the step where you inject, before adding any source materials, how the analysis should be conducted and how the results should be organized.
• If this step is skipped, the LLM will analyze each task under a different set of standards, which in turn prevents the overall work product from losing consistency.

3. Claim Chart Drafting Guidelines (Draft)

Below is a draft of the practical Claim Chart drafting guidelines that I prepared and asked the model to review.

DRAFT INSTRUCTION

**1. Methods for Claim Decomposition and Extraction for a Claim Chart Used in Claim Construction** Claims should be broken down into the smallest units that serve as the basis for invalidity and infringement analysis. The language of the claim should be separated according to context, while also being divided into sub-elements in a way that clearly reveals the invention’s distinctive features. The specific methods of decomposition and extraction are as follows. * **Structure- and Function-Based Decomposition:** Break the claim down into **structure**, which reflects the physical form of the elements and how they are connected, and **function**, which reflects the operation and role performed by each element. * **Identifying Organic Relationships:** Go beyond merely listing the components and derive the relationships showing how each component connects with the others and contributes to solving the technical problem. * **Extracting Interpretive Terms and Limitations:** From among the separated sub-elements, extract as the key interpretive targets those terms that **specifically require claim construction or are directly tied to the invention’s distinctive features**. In particular, major extraction targets include terms expressed functionally (for example, “means for ~”) that may need to be examined to determine whether limiting interpretation to the embodiments is required, as well as terms to which the principle of claim differentiation may apply because of dependent claims. **2. The Most Desirable Methodology for Drafting a Claim Chart** The most practical and desirable output format for visualizing claim construction results in a logical and clear manner is to prepare a **Claim Chart** in tabular form. For that purpose, I propose the following table format composed of **six items (columns)** as the output format. | No. | Claim Language | Claim Element (Interpretive Target) | Specification / Drawing Support | Interpretation Result and Legal Analysis (from the PHOSITA Perspective) | Notes (Prosecution History / Limiting Construction) | | :-- | :--- | :--- | :--- | :--- | :--- | | 1 | Decomposed claim language | (e.g., screw) | [paragraph number], [figure number] | (e.g., a low-speed pressing member having a spiral structure) | (e.g., vertical-type limitation based on an argument submission) | **[Drafting Guide and Explanation for Each Column]** * **Claim Language:** Set out verbatim the minimum unit of claim language as decomposed in a way that clearly reveals the invention’s distinctive features. * **Claim Element (Interpretive Target):** Extract from the decomposed language the core target terms or limitations that especially require interpretation or are written as functional expressions (e.g., “means for ~”). * **Specification / Drawing Support (Mapping of Intrinsic Evidence):** Identify and map the specific [paragraph numbers] and [figure numbers] in the detailed description of the invention that define or support the meaning of the term. * **Interpretation Result and Legal Analysis:** From the perspective of a person having ordinary skill in the art, apply intrinsic evidence first and clearly state the objectively and substantively established technical meaning of the claim element. * **Notes (Review of Prosecution History and Limiting Construction):** Record legal points of note, such as any intentional exclusion (prosecution history estoppel) reflected in the submission of arguments or amendments during prosecution, or any reason why, due to a clear disavowal of claim scope in the specification, limiting construction to the embodiments should apply.

This type of Claim Chart format allows intuitive one-to-one textual mapping between the relevant product (or prior art) and the claim elements in later infringement litigation or invalidity proceedings, making it the most effective practical analytical tool for preventing errors caused by improper narrowing or overbroad claim interpretation.

4. The Process of Validation → Refinement → Redesign

Rather than simply using the above guidelines as-is, I validated them in the following way.

“Are these guidelines sufficiently valid under actual legal doctrine and case law standards?”

To answer that question, I instructed the model in the chat to reflect the points requiring refinement and present again the most appropriate concrete Claim Chart format and drafting guide.

5. Refined Claim Chart Drafting Guidelines (Final Version)

The result is as follows, and this too was saved as a memo and then converted back into a source and integrated into the knowledge base. This process of turning good results into knowledge that can be continuously reused rather than a one-off answer is extremely important.

FINAL FRAMEWORK

**1. Methods for Claim Decomposition and Extraction for a Claim Chart Used in Claim Construction (Reflecting Special Issues)** When decomposing claims to apply the All Elements Rule (AER), which is central to infringement and invalidity analysis, it is essential to go beyond a simple listing of claim language and instead perform a more multidimensional extraction that reflects the legal characteristics of **special types of claims (functional claims, PbP claims, and numerical limitation claims)**. * **Identifying Structure, Function, and Organic Relationships:** Break the invention down into the physical structures that make it up and the functions those structures perform, while clearly deriving the relationships showing that each element does not exist in isolation but is organically connected with other elements to solve the technical problem. * **Extracting Targets for Limiting Construction of Functional Claims:** Because elements expressed in abstract or functional terms, such as “means for ~” or “~ step,” carry a risk of making the claim scope unduly broad, they should be extracted as targets for focused review to determine whether there are clearly unreasonable circumstances requiring the claim to be limited to the embodiments disclosed in the specification. * **Extracting the “Structure / Properties” of PbP (Product-by-Process) Claims:** Even when a manufacturing process is recited in the claim, the subject of the invention is still a “product,” so the manufacturing process itself should not be mechanically extracted as an independent element. Instead, the true technical element to be extracted is the “structure or properties of the product” ultimately defined by that manufacturing process. * **Extracting the “Critical Significance” of Numerical Limitation / Parameter Inventions:** Where a specific numerical range or a newly created parameter is involved, it should be separated as a core interpretive target in order to assess whether the specification enables the full claimed range without undue experimentation (support requirement), and whether the claimed range or parameter shows a remarkable effect (critical significance) that distinguishes it from the prior art. **2. The Most Desirable Concrete Claim Chart Format (Top-Tier Practical Template)** By upgrading the existing six-column structure, I propose a **seven-column framework that can fully map both Doctrine of Equivalents (DOE) defense / attack logic in cases of literal non-infringement and the analytical guidance for special types of claims**. | No. | Decomposed Claim Language (Including Organic Relationships) | Core Interpretive Target (Special Issue: Functional / PbP / Numerical) | Specification / Drawing Support (Mapping of Intrinsic Evidence) | Objective Technical Meaning and Result of Literal Interpretation (from the PHOSITA Perspective) | DOE Comparison: Identification of the Principle for Solving the Problem | Defense Logic: Prosecution History Estoppel and Grounds for Limiting Construction | | :-- | :--- | :--- | :--- | :--- | :--- | :--- | | 1 | (e.g., a cleaning unit that supplies cleaning water by electrolyzing filtered water) | cleaning unit (functional claim) | [paragraph 0045], [figure 3] | (e.g., an internal module that performs physical cleaning through electrodes without sterilizing chemicals) | (e.g., the principle of maximizing eco-friendly cleaning efficiency by excluding chemicals) | (e.g., conscious exclusion of a “chemical additive method” during argument submission) | | 2 | (e.g., a tablet manufactured by direct compression) | manufactured by direct compression (PbP claim) | [paragraph 0022] | (e.g., a porous tablet structure having a 15% inter-particle porosity formed by the direct compression process) | (e.g., the principle of controlling disintegration speed by adjusting porosity) | (e.g., structurally / physically different from tablets made by wet granulation) | | 3 | (e.g., a lens assembly having TTL ≤ 6.5 mm) | TTL ≤ 6.5 mm (numerical limitation) | [paragraph 0110], [Experimental Example 2] | (e.g., the physical limit of a miniaturized lens with a total track length of 6.5 mm or less) | (e.g., the principle of achieving an ultra-short focal length through refractive-index redistribution) | (e.g., target for lack of enablement across the full range of 6.5 mm or less) | **3. [Drafting Guide and Explanation for Each Column]** * **Decomposed Claim Language:** Set out verbatim the claim language decomposed into the minimum unit defining the scope of the invention, while describing it in a way that reveals not just a simple list but also the physical and functional relationships among the elements. * **Core Interpretive Target (with Special-Issue Label):** From the decomposed language, extract the key terms that present issues—such as functional expressions (“means for ~”), product-by-process (PbP) language, or numerical limitations / parameters—and identify the type in parentheses so the focus of the analysis is clear. * **Specification / Drawing Support (Mapping of Intrinsic Evidence):** Map the specific [paragraph numbers] and [figure numbers] in the specification that show where the term is defined under the lexicographer rule, where embodiments support a functional claim, where a manufacturing process in a PbP claim causes a specific change in physical properties, or where the technical threshold for a numerical limitation is demonstrated. * **Objective Technical Meaning and Result of Literal Interpretation (from the PHOSITA Perspective):** From the perspective of a person having ordinary skill in the art, apply the principle of construing the claim in light of the specification and describe the objectively and reasonably derived substantive meaning of the element. In the case of PbP claims, the description should not merely repeat the manufacturing process itself, but should clearly translate the structure or properties defined by that process. * **DOE Comparison: Identification of the Principle for Solving the Problem (New):** This column is used to assess possible infringement under the Doctrine of Equivalents when differences are found in a literal one-to-one comparison with the accused product. By considering both the content of the specification and the prior art existing at the time of filing, this column states in advance the “core of the technical idea underlying the specific means for solving the problem unique to the patented invention” (i.e., the principle for solving the problem) to which the relevant element belongs. * **Defense Logic: Prosecution History Estoppel and Grounds for Limiting Construction (New / Refined):** Record the history of any intentional exclusion (prosecution history estoppel) of specific subject matter reflected in arguments or amendments submitted throughout the prosecution of the original application and any divisional applications. Also record whether a functional claim should be limited to a specific embodiment because a broader reading would be clearly unreasonable in light of the specification, or whether a numerical limitation invention may be invalid for failure to satisfy disclosure requirements (such as enablement) because the full claimed range cannot be practiced without undue experimentation.

6. The Core Meaning of This Stage

The most important insight to gain at this stage is the following.

“A Claim Chart is not merely an organizational tool, but a structural mechanism that controls the accuracy of claim interpretation.”

And when using LLMs, the key is not simply getting good results, but building a system in which the results are always generated under the same standards.

7. Key Points for Practical Application

When this process is applied directly in practice, it can be summarized as follows.

1. First, establish the “drafting format” (the structure of the table).
2. Next, inject the “interpretive standards” (legal doctrine and drafting guidelines).
3. Then, input the “source materials” (the specification and evidence).
4. Finally, carry out the “claim interpretation and chart drafting”.

Most people reverse this order. Because they start by asking for the interpretation right away, the results become unstable and lose consistency.

This stage is not simply about creating a Claim Chart, but about designing how the LLM will think. When this work is done properly, all later analytical work becomes far more stable.

© 2026 ChinSu Lee. All rights reserved.