Patent Claim Construction: A Step-by-Step Guide

Claim construction is arguably the most critical step in patent law. It determines the meaning and scope of patent claims — which in turn determines whether a product infringes and whether the patent is valid. The Federal Circuit has called claim construction "the single most important event in the life of a patent."

This guide walks through the process step by step, from the basics of claim language to the frameworks courts use to interpret disputed terms.

What Is Claim Construction?

Claim construction is the process of defining the meaning of the words and phrases used in patent claims. It answers the question: what exactly does this claim cover?

This matters because patent claims are written in a peculiar hybrid of technical and legal language. A single word can make the difference between a patent that covers a competitor's product and one that doesn't.

For example, does "connected to" mean directly connected, or does it include indirect connections through intermediate components? Does "continuously" mean without any interruption, or does it allow brief pauses? These are the kinds of questions claim construction resolves.

The Legal Framework

The Supreme Court's Markman v. Westview Instruments (1996) established that claim construction is a question of law for the judge, not a question of fact for the jury. This means the judge interprets the claims, and that interpretation controls the rest of the case.

The Federal Circuit's Phillips v. AWH Corp. (2005) established the modern framework for claim construction, prioritizing intrinsic evidence:

1. The claim language itself
2. Other claims in the patent
3. The specification
4. The prosecution history
5. Extrinsic evidence (dictionaries, expert testimony) — only as a last resort

Let's walk through each source.

Step 1: Start with the Claim Language

Read the claim carefully. Every word matters. Patent claims are drafted with precision, and courts give every word its "ordinary and customary meaning" as understood by a person of ordinary skill in the art (POSITA) at the time of the patent's filing.

Key principles:

Every word carries weight. If a claim says "a plurality of sensors," it means more than one. If another claim says "one or more sensors," that's a deliberately different scope.

Claim differentiation. If two claims use different language, they presumably mean different things. If Claim 1 says "transmitting data" and Claim 3 says "wirelessly transmitting data," the word "wirelessly" in Claim 3 suggests Claim 1 is not limited to wireless transmission.

Preamble vs. body. The preamble ("A method for wireless communication, comprising:") may or may not limit the claim. If the preamble merely states the intended use, it's usually not limiting. If it provides essential structure or context, it may be.

Transitional phrases:

• "Comprising" = open-ended. The claim covers devices with the listed elements plus additional elements.
• "Consisting of" = closed. Only the listed elements, nothing more.
• "Consisting essentially of" = allows additions that don't materially affect the basic characteristics.

Step 2: Read the Other Claims

Other claims in the same patent provide context. This is especially important for claim differentiation — the principle that each claim should have a different scope.

Look for:

• Dependent claims that add limitations — what they add tells you what the independent claim doesn't require
• Parallel claims in different categories (method vs. apparatus) — they often mirror each other and clarify what each element means
• Claims that use similar but different language — the differences are intentional

Step 3: Consult the Specification

The specification is "the single best guide to the meaning of a disputed term" (Phillips). It describes the invention in detail, provides examples, and often explains why certain design choices were made.

What to look for:

Explicit definitions. If the specification says "as used herein, 'widget' means...," that definition controls. Patent applicants can be their own lexicographers.

Consistent usage. How does the specification use the disputed term? If "connected" always appears in the context of direct physical connections, that informs its meaning in the claims.

Embodiments and examples. Be careful here — the specification may describe specific embodiments, but claims should not be limited to those embodiments unless the language requires it. A common error is reading limitations from the specification into the claims.

The problem/solution. The background section describes the problem the invention solves. This context helps interpret what the claims are trying to capture.

The specification trap

One of the most common mistakes in claim construction is importing limitations from the specification into the claims. Just because the specification only describes one way of doing something doesn't mean the claim is limited to that way — unless the claim language itself requires it.

The Federal Circuit has repeatedly warned against this: "It is the claims that define the invention, not the specification."

Step 4: Review the Prosecution History

The prosecution history (also called the "file wrapper") is the record of everything that happened between the applicant and the patent office during examination. It includes:

• Office actions — the examiner's rejections and objections
• Applicant responses — amendments and arguments made to overcome rejections
• Interviews — summaries of discussions with the examiner

Prosecution history estoppel

If the applicant narrowed a claim during prosecution to overcome a rejection, they generally can't later argue for a broader interpretation. This is prosecution history estoppel.

For example, if the examiner rejected a claim as obvious over a reference, and the applicant added "wherein the sensor operates at a frequency above 5 GHz" to distinguish, the applicant can't later argue the claim covers sensors operating below 5 GHz.

Where to find prosecution history

The USPTO's Patent Application Information Retrieval (PAIR) system contains the complete prosecution history for most patents. Patent Bear provides direct links to PAIR from every patent page.

Step 5: Extrinsic Evidence (If Necessary)

If the intrinsic record doesn't resolve the dispute, courts may consider extrinsic evidence:

• Technical dictionaries and treatises
• Expert testimony about how a POSITA would understand the term
• Prior art showing how the term was used in the field

Extrinsic evidence is always subordinate to intrinsic evidence. It can help inform the court's understanding but cannot contradict the patent's own record.

Practical Claim Construction Checklist

When analyzing a claim term:

1. Identify the disputed term — what word or phrase is at issue?
2. Read it in context — how is it used in the full claim?
3. Check other claims — does claim differentiation inform the meaning?
4. Search the specification — is there an explicit definition? How is the term used?
5. Read the prosecution history — did the applicant narrow the term?
6. Consider the POSITA perspective — how would a skilled person understand this term at the time of filing?
7. Construct the meaning — write a clear, concise construction that accounts for all the evidence

Common Pitfalls

Importing limitations from the specification. The #1 error. Don't assume the claims are limited to the specific embodiments described.

Ignoring dependent claims. If a dependent claim adds a feature, the independent claim doesn't require that feature.

Overlooking prosecution history. Arguments made to the examiner are binding. Always check the file wrapper.

Dictionary-first approach. Some practitioners start with dictionary definitions. The Federal Circuit in Phillips explicitly rejected this approach — start with intrinsic evidence.

Ignoring the preamble. While preambles are often not limiting, sometimes they are. Don't automatically dismiss preamble language.

Tools for Claim Construction

Effective claim construction requires access to:

• The full patent text with structured claims
• The prosecution history via USPTO PAIR
• Related patents through citation analysis
• A way to track and annotate claim terms across the document

Patent Bear provides all of these in one interface — structured claims with proper nesting, direct links to PAIR and prosecution history, citation lists, and claim term tracking that highlights a term across all claims and lets you navigate between occurrences. Try it free at patentbear.com.