Pre-suit infringement investigation is driven by Federal Rule of Civil Procedure 11, which requires that a complaint be well-grounded in fact before it is filed; a patent owner cannot sue first and investigate later. The investigation is built around producing a good-faith, claim-by-claim infringement analysis for at least one representative accused product before the complaint is drafted, and typically proceeds through the following stages:Claim selection and construction: identifying which claims of which patents in the portfolio are worth asserting, and construing the key disputed terms of each against intrinsic evidence before mapping begins.Target identification: confirming the exact accused product, model number, and version, since a company's product line frequently spans multiple implementations that may practice a claim differently.Public-evidence gathering: collecting datasheets, manuals, marketing material, regulatory filings (e.g., FCC ID records), and the target's own patent filings describing its product architecture.Product acquisition and testing: purchasing a representative unit, and, where feasible without violating any applicable law or contract term, performing physical teardown, black-box behavioral testing, or protocol analysis to fill evidentiary gaps documentation leaves open.Preliminary claim charting: building an element-by-element chart against the accused product to confirm, before filing, that a good-faith basis exists for every limitation of every asserted claim.Damages and standing groundwork: confirming clean chain of title to the patent, reviewing licensing history, and beginning a preliminary damages analysis (sales volume estimates, comparable license rates) that will support the case beyond the liability question alone.Because pre-suit investigation cannot rely on discovery tools like depositions or document requests that only become available after filing, it necessarily leans more heavily on public documentation, reverse engineering, and inference than the far more thorough investigation that follows once the case is in active litigation and formal discovery opens up access to the defendant's internal engineering documents and source code.

A patent infringement investigation is a fact-finding process used to determine whether a specific product or process falls within the scope of one or more patent claims. It combines legal analysis with technical investigation and typically begins with claim construction: determining what the relevant claim terms mean based on the claim language, specification, and prosecution history. The investigator must then precisely identify and scope the accused instrumentality, including the exact product model, software or firmware version, hardware revision, and configuration, because infringement conclusions can differ between variants marketed under the same product name.The investigation then proceeds through evidence collection and element-by-element mapping. This may involve reviewing technical documentation, conducting or commissioning reverse engineering, capturing behavioral or protocol-level test data, and examining the target company's patent filings and technical publications. Each limitation of the asserted claim should be tied to specific evidence, with the strength or confidence of the mapping identified where appropriate. The investigation should also consider the strongest potential non-infringement and invalidity arguments, rather than testing only the theory supporting infringement. An early assessment of accused sales or usage may also be performed to understand the potential commercial significance and allocate investigation resources appropriately.Patent infringement investigations are rarely completely linear. Findings during claim mapping may reveal that additional technical evidence is needed, prompting further testing or research. Conversely, a limitation that cannot ultimately be supported with adequate evidence may lead the investigating party to abandon a particular claim, product, or potential dispute before litigation is initiated. The investigation is therefore both a technical assessment of infringement and an iterative process for determining whether the available evidence justifies proceeding.

Attorneys typically direct and structure the infringement investigation rather than performing all of the technical investigation themselves. They commonly coordinate patent agents, technical specialists, engineers, reverse-engineering firms, and, where necessary, damages or other specialized experts. The attorney and technical team first establish the scope of the asserted claims and identify what technical evidence would satisfy each limitation, allowing the investigation to focus on the facts that could actually affect the infringement analysis.The attorney then directs evidence-gathering priorities, often concentrating first on limitations that are particularly difficult to establish or potentially dispositive. Technical staff may investigate product documentation, conduct testing, perform reverse engineering, analyze the target company's patent filings, or prepare preliminary claim charts. Attorneys review these mappings for legal sufficiency, ensuring that each limitation is properly supported and cited, that the claim construction is consistent with the position being developed, and that the investigation satisfies the applicable pre-filing requirements. They also manage privilege and work-product considerations and coordinate communications and engagements with outside technical experts in accordance with the anticipated litigation posture.Ultimately, the attorney evaluates the technical findings together with litigation cost, potential damages, validity risks, business considerations, and the strength of anticipated defenses. This assessment determines whether the evidence is sufficient to justify further action, such as sending a demand letter or filing a complaint. Thus, the attorney's role is not simply to review a completed claim chart, but to ensure that the entire investigation is legally disciplined, technically credible, and strategically appropriate.

Useful technical evidence in patent litigation spans several categories, and the relative value of each depends heavily on the technology at issue and the specific claim limitations in dispute.Product documentation: datasheets, service manuals, API and developer documentation, and internal engineering specifications obtained through discovery, which are often the most direct evidence of a product's actual design.Source code: for software and firmware claims, source code obtained through discovery (typically reviewed under a protective order in a secured environment) is frequently the single most probative evidence available, since it shows the actual implementation rather than an inference from external behavior.Physical evidence: teardown photography, die cross-sections, and delayering analysis for hardware and semiconductor claims, which directly show physical structure a claim may recite.Test data: laboratory test results, protocol captures, and benchmarking data showing how a product actually behaves under controlled conditions, useful for functional and performance-based claim limitations.Regulatory and certification filings: FCC equipment authorization records, standards-compliance certifications, and similar filings, which often contain internal photographs, block diagrams, and test reports not available anywhere else.Internal company documents: design documents, engineering emails, meeting notes, and product-development records obtained in discovery, which can reveal not just what a product does but why it was designed that way—evidence that is often decisive for both infringement and willfulness determinations.Deposition and fact-witness testimony: sworn testimony from the accused party's own engineers describing how the product works, which can be used to fill gaps that documentary evidence alone leaves ambiguous.Expert analysis and testimony: a qualified technical expert's independent examination and opinion, translating the raw technical evidence into a formal opinion on infringement, validity, or damages that a judge or jury can rely on.

Software patent investigations are often more difficult than hardware investigations because the claimed functionality may depend on internal algorithms, data structures, control flow, or processing logic that cannot be directly observed from the running product. The investigation therefore generally uses multiple complementary sources of evidence. Public technical documentation, including API references, SDK and developer documentation, technical articles, engineering publications, and research papers authored by the target company's engineers, can provide useful information about architecture and implementation. Controlled black-box testing can then be designed to determine whether the product exhibits behavior consistent with the claimed mechanism, although observed behavior alone may not establish the specific internal implementation.Where appropriate, investigators can supplement behavioral evidence with network and API traffic analysis, which may reveal data structures, parameters, processing sequences, and interactions between client and backend systems. Publicly distributed application binaries or firmware may also be subjected to binary analysis or decompilation, where legally permissible, to identify functions, control-flow structures, and other implementation details without access to the source code. These techniques can be particularly useful for narrowing the technical questions that remain unresolved after reviewing public documentation.If litigation proceeds, source-code discovery can provide more direct evidence of software implementation and is typically conducted under appropriate protective restrictions, often with review by a technical expert in a controlled environment. Version analysis is equally important: release notes, changelogs, archived documentation, and archived software versions can establish when a particular feature was introduced or modified. This can be critical not only to determining whether the accused software practices the claim, but also to establishing whether the relevant functionality existed during the period for which infringement or damages are alleged.

When accused technology is proprietary, its internal architecture may not be publicly documented, standardized, or otherwise accessible, making direct claim mapping difficult. The investigation therefore relies on triangulating multiple sources of indirect evidence. The first step is to exhaust publicly available technical material, including regulatory filings, the target company's own patent filings, industry conference presentations, and technical publications by the company's engineers. A company's patent portfolio can be particularly useful because proprietary mechanisms that are not described in commercial documentation may nevertheless be disclosed in the company's own patent applications or issued patents.Where public sources are insufficient, targeted physical or behavioral investigation can provide additional evidence. Hardware may be examined through teardown, component identification, or other appropriate analysis, while software and systems may be subjected to carefully designed black-box testing intended to distinguish the claimed mechanism from plausible alternatives. If the proprietary system incorporates a known underlying platform, chipset, framework, or other non-proprietary technology, analysis of that underlying technology may also provide useful context, although any inference about the proprietary layer must be clearly identified as an inference. Where appropriate and legally compliant, individuals or third parties with legitimate technical visibility into the system, such as component suppliers or contract manufacturers, may provide additional factual information.The investigation should also anticipate formal discovery if litigation is contemplated. Before filing, the objective may be to establish a sufficient good-faith basis for the allegations rather than conclusively reconstruct every aspect of a proprietary system. The investigation should therefore identify precisely which internal documents, source code, engineering records, or other materials would need to be requested through discovery. Throughout the process, direct observations should be distinguished from reasonable but unconfirmed inferences, because that distinction can become important during expert discovery, depositions, and cross-examination.

Reverse engineering can provide direct physical or behavioral evidence of how an accused product is actually constructed or operates when public documentation is incomplete, inaccurate, or silent about the relevant implementation. During a pre-suit investigation, it can help establish whether an accused product actually practices disputed claim limitations, particularly where the relevant features concern internal hardware structures or other characteristics that cannot be established from external documentation alone. The resulting teardown photographs, die cross-sections, decompiled-code excerpts, protocol captures, measurements, or other technical findings can also provide concrete evidence for individual rows of an infringement claim chart.During litigation, reverse engineering can serve several additional purposes. It can test a defendant's assertion that its product uses a different, non-infringing architecture and can provide independent evidence for a technical expert's opinions. It can also corroborate discovery materials: internal source code and engineering documents may show what a company intended to build, while examination of the actual shipped product can establish what was ultimately implemented and sold. This distinction can become important where products change across revisions or where the documented design does not perfectly match the commercial implementation.Because reverse-engineering evidence may be challenged on both methodology and reliability grounds, litigation-related work requires careful procedural discipline. The specific unit examined should be preserved and documented through purchase records, identifying information, serial numbers where relevant, photographs, and other records establishing its provenance. The examination methodology, equipment, testing conditions, software versions, and analytical steps should be documented in sufficient detail for another qualified examiner to understand or reproduce the work. The examiner should also be prepared to explain and defend the methodology and findings, since the evidentiary value of reverse engineering depends not only on what was discovered but also on the reliability and reproducibility of how it was discovered.

This is a portfolio-scanning exercise conducted from the patent owner's side, working outward from an owned patent portfolio to identify which competitor products might practice which claims, and it generally follows a structured funnel:Portfolio triage: reviewing the patent owner's own portfolio and identifying claims covering technology categories where competitors are known to be active, prioritizing patents with broad, clearly-infringed-looking independent claims over narrow or easily-designed-around ones.Competitor product mapping: building an inventory of competitor products in the relevant technology space, prioritized by commercial significance (revenue, market share, strategic importance) since litigation and licensing resources are typically allocated toward the highest-value targets first.Preliminary functional screening: for each high-priority patent, quickly checking whether a candidate competitor product appears, from public information alone, to offer the claimed functionality at all — a fast filter that eliminates clearly non-infringing candidates before committing to a full investigation.Deeper technical investigation: for products surviving the preliminary screen, conducting the fuller evidence-gathering and claim-mapping process (documentation review, reverse engineering where warranted) to build an actual infringement position.Business and legal risk assessment: weighing the strength of the technical case against practical factors — the competitor's litigation history, the patent's remaining term, potential countersuit or invalidity exposure, and the strategic value of a license versus a lawsuit — before deciding how, or whether, to proceed.This process runs in the opposite direction from an infringement investigation aimed at a single already-identified target: rather than starting with one product and asking which claims it might infringe, it starts with the full patent portfolio and systematically asks which competitor products, across an entire market, might practice each claim, which requires a scalable triage process rather than deep investigation of every candidate.

Analyzing a competitor's product for patent infringement follows the same fundamental element-by-element methodology used in other infringement investigations, but it requires particular care in defining the product being analyzed and the provenance of the evidence. The first step is to identify the exact product, SKU, regional variant, hardware revision, software or firmware version, and configuration under investigation. Competitors may sell multiple generations or variants under similar branding, and a finding established for one version should not automatically be extended to an entire product family without separate technical confirmation.The investigation should then make efficient use of the competitor's own publicly available disclosures, including patent filings, technical papers, investor presentations, regulatory submissions, product documentation, and other technical materials. These sources can reveal aspects of product architecture that are not apparent from marketing materials. Where physical examination is necessary, the product should be obtained through lawful channels, and any testing or reverse engineering should comply with applicable law and binding contractual restrictions. The investigation should focus specifically on the limitations of the asserted claim rather than on broad similarities between the competitor's product and the patented invention. For each limitation, the analyst should identify the corresponding technical feature and supporting evidence, while distinguishing direct evidence from inference.The entire investigation should be documented contemporaneously. Purchase records, product identifiers, photographs, test procedures, results, source documents, and analysis dates can become important if the findings are later challenged. This is particularly relevant for competitor products because hardware, software, documentation, and even product availability may change over time. A defensible competitor analysis therefore establishes not only what the product appears to practice, but exactly which version was examined, what evidence supports each claim limitation, and how that evidence was obtained.

Preparing technical evidence for litigation means converting raw investigative material — documents, test results, teardown photographs, code excerpts — into a form that is admissible, well-organized, and persuasive to a judge, jury, or PTAB panel, which involves several distinct preparation tasks.Authentication and chain of custody: for physical evidence (purchased products, teardown units) and digital evidence alike, maintaining clear records of where each item came from, when it was obtained, and how it was handled, since evidence that cannot be authenticated may be excluded regardless of its substantive value.Exhibit organization: assembling evidence into clearly labeled, cross-referenced exhibits tied to specific claim limitations, so that a claim chart's citations point to identifiable, produced exhibits rather than vague or unlocatable sources.Version and date documentation: recording the precise version, date, and configuration each piece of evidence corresponds to, since technical evidence gathered at different times can reflect different product states, which matters for both infringement and damages timing.Expert packaging: organizing raw technical findings into a form a testifying expert can efficiently review, verify, and build an independent opinion around, since an expert's opinion needs to reflect their own analysis rather than simply adopting counsel's conclusions.Demonstrative preparation: developing diagrams, animations, or simplified visual aids that accurately translate complex technical evidence (circuit structures, data flows, protocol sequences) into a form a lay judge or jury can follow, without overstating or distorting what the underlying evidence actually shows.Consistency review: checking that the prepared evidence and the claim construction positions it supports are consistent across every filing and expert report in the case, since inconsistency between documents is a standard and effective cross-examination target.

A technical expert in patent litigation is a subject-matter specialist — typically an engineer, scientist, or other technically qualified professional — retained to provide an independent, qualified opinion on technical questions the court or jury cannot be expected to resolve on its own. The role generally covers several distinct functions across a case:Claim construction support: helping counsel understand the technical meaning of disputed claim terms and how a person of ordinary skill in the art would have understood them at the relevant time, often through a declaration submitted for the Markman hearing.Infringement or non-infringement analysis: independently examining the accused product (through documentation, testing, and source code review) and forming an opinion on whether it practices each limitation of the asserted claims, documented in a formal expert report.Invalidity or validity analysis: independently assessing whether prior art anticipates or renders obvious the asserted claims, or defending the claims' validity against an opposing invalidity expert, again documented in a formal report.Damages support: for damages experts specifically, analyzing the technical basis for apportionment — determining what portion of a product's value is attributable to the patented feature versus other features — which frequently requires close collaboration with a technical expert even when a separate damages expert leads the ultimate royalty calculation.Deposition and trial testimony: sitting for deposition by opposing counsel and, if the case proceeds to trial or a PTAB hearing, testifying and being cross-examined on the opinions in their report.Rebuttal analysis: reviewing and responding to the opposing side's expert reports, identifying methodological or factual weaknesses in the other side's technical analysis.A technical expert's opinions must be their own independent analysis, not merely an adoption of positions counsel supplies, both as a matter of professional ethics and because an expert whose report reads as attorney argument rather than independent technical judgment is a standard target for a motion to exclude under the reliability standards governing expert testimony.

Expert preparation is a structured process aimed at ensuring the expert forms an independent, well-supported, and defensible opinion and is able to explain and defend that opinion under adversarial questioning. The process typically includes the following stages:Qualification review: confirming and documenting the expert's relevant technical background, publications, and experience in the specific field at issue, since an expert's qualifications are themselves subject to challenge before their opinions are even considered.Independent evidence review: giving the expert direct access to the full evidentiary record — product documentation, source code, discovery materials, prior art — and ensuring their opinion is built from their own review of that material rather than handed to them pre-formed.Methodology documentation: having the expert clearly record the analytical method used to reach each conclusion (how claim terms were construed, what evidence supported each limitation, what testing was performed and how), since a reliable, disclosed methodology is central to surviving a reliability challenge.Draft report review: iterative review of the expert's draft report by counsel for clarity, internal consistency, and alignment with the case's overall legal theory, while preserving the expert's independent conclusions rather than substituting counsel's preferred conclusions for the expert's own.Deposition preparation: mock examination sessions that expose the expert to the kind of aggressive, detail-focused questioning opposing counsel is likely to use, so the expert is comfortable defending their methodology, acknowledging genuine limitations in their analysis, and avoiding overstatement under pressure.Demonstrative and testimony preparation: working with the expert to develop clear, accurate visual aids and a coherent narrative for trial or hearing testimony that communicates technically complex conclusions to a non-technical judge or jury without oversimplifying past the point of accuracy.Throughout this process, counsel must be careful to avoid directing the expert's substantive conclusions, since doing so undermines the independence the expert's opinion depends on and creates a significant risk that the opinion will be excluded or given little weight if that direction becomes apparent during discovery or cross-examination.

Claim charts serve as the structural backbone of a patent case from the earliest pre-suit investigation through trial, and their specific function shifts as the case progresses through several distinct stages.Pre-suit investigation: an internal, attorney-directed chart establishing the good-faith basis required before filing a complaint, generally not shared with the opposing party at this stage.Infringement and invalidity contentions: formal charts served on the opposing party early in the case (often required by local patent rules within weeks of the case being filed or the answer being served), which lock in the asserting or challenging party's element-by-element theory and, in most jurisdictions, can only be amended later with the court's permission and a showing of good cause.Claim construction (Markman) briefing: charts and supporting technical explanations submitted to help the court understand how disputed terms should be construed, often accompanied by expert declarations.Expert reports: detailed claim charts embedded within or attached to expert reports on infringement, invalidity, and damages, representing the fully developed, evidence-supported version of the earlier contentions.Summary judgment briefing: charts used to argue that no genuine dispute of material fact exists on a given limitation, potentially resolving individual claims or the entire case without trial.Trial exhibits: simplified, jury-friendly versions of the underlying technical claim charts, used as demonstrative exhibits during opening statements, witness examination, and closing argument to walk the jury through the element-by-element infringement or invalidity theory in an accessible form.Because contentions filed early in a case are difficult to amend later, the charting work done at the contentions stage carries disproportionate weight for the rest of the litigation — a limitation inadequately supported in the initial infringement contentions can become very difficult to strengthen later, even if better evidence subsequently emerges through discovery.

Infringement contentions are formal, court-filed documents required by the local patent rules of many US district courts (for example, N.D. Cal. Patent L.R. 3-1 and its counterparts in other districts), and the claim chart is their central component. In this specific context, the chart functions as a binding disclosure of the asserting party's theory of the case, with several particular requirements and consequences.Particularity requirement: the chart must identify, for each asserted claim, where and how each limitation is found in the accused instrumentality, with specificity — a chart that merely restates claim language without tying it to specific accused-product features or structures typically does not satisfy the rule.Coverage requirement: contentions generally must address every asserted claim individually, not just representative claims, and every limitation of each claim, not just the elements the asserting party considers strongest.Timing and rigidity: contentions are typically due early in the case, often before full discovery has occurred, yet in most jurisdictions cannot be freely amended afterward — amendment usually requires a motion showing good cause, such as the discovery of previously unavailable information, and courts frequently deny amendment requests that appear to reflect a change in litigation strategy rather than genuinely new facts.Doctrine of equivalents disclosure: where the asserting party intends to rely on the doctrine of equivalents for any limitation, most local rules require this to be identified explicitly in the contentions on a limitation-by-limitation basis, rather than raised for the first time later in the case.Reciprocal invalidity contentions: the accused infringer typically must serve invalidity contentions on a set schedule following the infringement contentions, identifying the specific prior art and combinations it intends to rely on, which are subject to similar particularity and amendment restrictions.Because of this rigidity, contentions-stage charts are built to the most defensible evidentiary standard the pre-filing investigation can support, often erring toward including every plausible mapping and construction the asserting party might later need, since the ability to add new theories once the case is underway is narrow and frequently contested by the opposing side.

Reviewing an opposing claim chart for weaknesses is itself a structured, element-by-element exercise, and a competent review generally works through the following checkpoints for every row of the chart:Claim construction mismatches: check whether the chart's implicit reading of each disputed term is consistent with the intrinsic evidence (claim language, specification, prosecution history), and flag any row that only works under a construction broader or narrower than what the specification actually supports.Missing or thin evidentiary support: identify rows citing only conclusory language, marketing material, or a restatement of the claim term itself rather than a specific, checkable technical source, since these rows are the most vulnerable to a direct rebuttal.Evidence that doesn't actually say what the chart claims: independently pull the cited source and confirm it says what the chart represents — misquotation, selective excerpting, or citing a source that describes a different feature than the one at issue is a common and highly effective point of attack.Version and configuration mismatches: check whether the cited evidence actually corresponds to the specific product version accused, since evidence drawn from a different version, region, or configuration than the one actually at issue can invalidate an otherwise well-sourced row.Internal inconsistency: compare the construction implied by the infringement chart against the construction the same party is using in any related invalidity or validity argument elsewhere in the case, since a party arguing for a broad construction in one context and a narrow one in another creates strong impeachment material.Reliance on inherency or aggressive inference: scrutinize any row relying on an inherency argument or a behavioral inference rather than direct evidence, and test whether the cited source truly necessitates the claimed feature or merely makes it a plausible or common implementation choice — the legal standard for inherency is necessity, not likelihood.Gaps between limitations and combined-evidence overreach: check whether the chart is improperly combining evidence from different rows to cover a single limitation, or importing a feature disclosed in one product embodiment to support a different embodiment actually at issue.All-elements coverage: confirm every single limitation of the claim has its own row and its own evidence — a chart that silently omits a limitation, or treats two separate limitations as a single combined row, may be concealing a limitation it cannot actually support.The output of this review is typically its own internal memo, ranking each weak row by how dispositive it is (a completely unsupported limitation is far more valuable to attack than a well-supported one with a minor citation error) and prioritizing deposition questions, rebuttal expert analysis, and summary judgment arguments around the weakest and most consequential rows first.