Patent Claims Explained: Independent, Dependent, and Scope
How patent claims work: independent and dependent claims, why claim scope matters more than the description, and common claim formats for software inventions.
General information about patent law and practice, not legal advice about your situation. How these rules apply depends on the facts.
Patent claims are the numbered sentences at the end of a patent. They define what the patent covers. The description and drawings explain the invention, but when a question arises about whether something infringes, or whether the patent is valid, the analysis starts with the claims. Reading a patent well, and drafting one well, both depend on understanding how claims are built.
A claim is a list of elements
Each claim describes the invention as a set of elements, or steps for a method. A product or process generally falls within a claim only if it includes every element of that claim. If a competitor’s product lacks one element, that claim is generally not literally infringed, although the doctrine of equivalents can sometimes reach close substitutes, within limits.
That all-elements rule explains most of what follows. As a general rule, adding an element to a claim narrows it and makes it easier to avoid, and leaving an element out broadens it but makes it more likely to read on something that already existed, which would make it unpatentable. Claims are construed as a whole, in light of the specification and the prosecution history, so the effect of a particular word or element is not always that simple.
Independent and dependent claims
Independent claims stand on their own. A typical application has two or three, often in different categories, such as a method and a system.
Dependent claims refer back to an earlier claim, which can be an independent claim or another dependent claim, and add a limitation, for example “The method of claim 1, wherein the threshold is updated based on prior readings.” Under 35 U.S.C. 112(d), a dependent claim incorporates all the limitations of the claim it refers to and specifies a further limitation, so it is narrower than its parent.
Dependent claims serve as fallback positions. If an examiner, or later a court or the Patent Trial and Appeal Board, finds a broader claim unpatentable over the prior art, a narrower dependent claim may still survive. A useful set of dependent claims adds features that matter commercially or technically, not just details that happen to appear in the description.
Why the description still matters
Claims can only be as broad as the description supports. Under 35 U.S.C. 112(a), the application needs to describe the claimed invention and teach a skilled person how to make and use it. If a claim recites a broad category but the description shows only one narrow example, the claim may be rejected or later held invalid.
The description also supplies the vocabulary. Terms in a claim are generally read in light of the specification, so how the description uses a word can affect how broadly the claim is interpreted. Defining important terms, and describing alternatives, gives the claims room.
Common claim formats for software
Software inventions are commonly claimed in three ways:
- Method claims: the steps a computer performs.
- System claims: a processor and memory storing instructions that cause the processor to perform the steps, sometimes with other hardware such as sensors or network interfaces.
- Computer-readable medium claims: a non-transitory storage medium holding instructions that, when executed, perform the steps.
These formats cover the same underlying idea but can matter differently in enforcement. A method claim may be infringed only by whoever performs the steps, while a system or medium claim may reach whoever makes or sells the product. When steps are split across a client device and a server, claims may be drafted from the perspective of one party to avoid gaps; our article on divided infringement explains why.
Claim scope and detectability
A claim is most useful when you could tell whether someone is using it. A claim to an internal server-side computation may be hard to detect in a competitor’s product, while a claim to an observable behavior, interface, or output may be easier to prove. Our article on patent value and detectability covers this in more depth.
How claims change during examination
Claims are rarely allowed exactly as filed. In response to Office actions, applicants often amend claims, for example by adding a limitation from a dependent claim to an independent claim, or argue that the prior art does not teach what the examiner says it does. Amendments and arguments become part of the public file history and can affect how the claims are interpreted later.
Fees and claim count
USPTO fees increase for more than three independent claims or more than 20 total claims, and multiple dependent claims carry their own fee. Claim sets are usually planned within those limits, with continuation applications available to pursue additional claims while an application in the family remains pending.
A practical takeaway
When you review a draft application, read the independent claims first and ask two questions: would a competitor’s likely product include every element, and is there anything in the claim that is not necessary to distinguish the prior art? Then check that the description supports the claims and their likely amendments. A patent attorney or agent can walk you through the trade-offs for your specific invention.