Patent disputes often sound abstract from the outside. Then the documents arrive: a complaint, a demand letter, infringement charts, product manuals, engineering diagrams, release notes, source code references, maybe a stack of patent claims written in dense technical language. At that point, the core question becomes practical: how do you compare what the patent actually covers with what the accused product actually does?
That comparison sits at the center of many patent cases. Under 35 U.S.C. § 271, infringement analysis turns on whether an accused product or process falls within the scope of one or more patent claims. In court, judges often resolve the meaning of disputed claim terms through a Markman claim construction process, and the outcome of that step can reshape the rest of the case. The review also happens inside modern discovery rules, where parties can seek relevant, proportional technical materials under Rule 26 and Rule 34.
In this post you’ll learn how companies, inventors, in-house teams, and litigators often review patent claims, accused product features, and technical documentation in a structured way. If you’re looking for a broader overview of how these disputes fit together, this plain-English breakdown of the moving parts in a patent case provides helpful context before diving into the technical comparison itself.
<aside> 💡 Scroll to the bottom for every post in this series.
</aside>
In many patent disputes, the early review is where risk starts to become measurable. A patent owner may be trying to determine whether a filing has factual support. An accused company may be trying to figure out whether the allegation is narrow, overbroad, or aimed at the wrong product generation. Investors, boards, insurers, and business teams often want quick answers, but patent analysis usually resists shortcuts.
That is partly because claims drive the analysis, not marketing language. Product brochures can help, but they rarely answer the full question. Technical documents can help, but they may reflect planned behavior instead of shipped functionality. Engineers may understand the system, yet not speak in the vocabulary of patent law. By the time those pieces are reconciled, the case theory may look very different from the initial accusation.
A careful review also affects discovery scope, settlement posture, claim construction positions, expert strategy, and damages analysis. Some courts move these issues quickly through local patent rules. For example, the Northern District of California’s Patent Local Rules require early infringement and invalidity contentions and call for production of materials such as source code, specifications, schematics, flow charts, and other documents sufficient to show how accused instrumentalities operate. That kind of structure often pushes parties to get specific early.
A common instinct is to begin with the accused product because it feels tangible. In practice, experienced patent teams usually begin with the asserted claims.
That is because a patent does not cover a general idea in the abstract. It covers what is claimed, as properly construed. The Supreme Court explained in Markman v. Westview Instruments that claim construction is a matter for the court, and the Supreme Court later noted in Teva v. Sandoz that claim construction can involve subsidiary factual issues even though the ultimate construction remains a legal determination.
When reviewing claims at the outset, teams often ask:
Not every patent claim is in play. A patent may include dozens of claims, but only a subset may be asserted in a complaint, demand letter, or infringement contentions. The first practical task is identifying the exact claims at issue.
Each asserted claim is typically broken into limitations or elements. That element-by-element structure matters because infringement analysis generally asks whether each limitation is present in the accused product, either literally or, in some cases, under the doctrine of equivalents.
Some terms will look straightforward. Others may be packed with technical meaning, industry shorthand, or prosecution-history baggage. If a term is likely to control the outcome, it often becomes a claim construction battleground later.
At this stage, many teams create a working chart with three columns: