How to organize witness statements and document references for Patent Infringement Matters

Organize witness evidence by factual proposition, asserted patent claim, and accused product version—not merely by witness name. For each proposition, distinguish what the witness actually said from counsel’s interpretation, identify the witness’s knowledge basis, and attach exact document and testimony references. Record contradictory evidence and missing foundations alongside supporting material. The resulting witness evidence matrix lets counsel trace a proposed assertion to its source, assess its limits, and assign focused follow-up for claim-chart review, deposition preparation, or evidentiary analysis.

When to use this workflow

Use this workflow when litigation counsel or an in-house team receives technical interviews, declarations, deposition transcripts, or productions bearing on disputed product operation. Concrete triggers include engineers describing different releases, inventors discussing development history, and commercial witnesses connecting product records to sales periods.

The task is to identify who can support which proposition and with what records. The matrix does not replace claim construction, expert analysis, infringement contentions, or damages methodology. The same structure can organize defense evidence, provided each row identifies the defense issue rather than forcing every proposition into an infringement limitation.

This guide addresses US federal district-court litigation. Check governing local rules, assigned judge’s orders, and protective orders; do not carry this procedural framework into state proceedings, arbitration, ITC investigations, or PTAB proceedings without checking their requirements. The federal rules and district-specific patent rules have defined scopes. See the Federal Rules of Civil Procedure, Rule 1, and Northern District of California Patent Local Rules, Rule 1-2. (uscourts.gov)

What you need

Assemble these inputs before building substantive entries:

• Issue references: asserted claims and dependencies, applicable constructions or disputed terms, contention versions, and claim-chart cell IDs.
• Product identifiers: models, releases, configurations, relevant periods, and source-code or schematic revisions.
• Witness materials: declarations, signed statements, interview notes, transcripts and available corrections, organizational designation topics, and relevant employment periods.
• Document sources: Bates-stamped productions, native-file IDs, technical specifications, release records, sales worksheets, and repository indexes.
• Review controls: confidentiality designations, access restrictions, document versions, and responsible legal or technical reviewers.

Reuse existing production identifiers. If a repository uses different names, maintain a crosswalk rather than replacing the original references. Identify unavailable material expressly: a witness’s mention of a release log does not supply the log’s contents.

Use the template

The companion template is Patent Infringement Matters — Witness evidence matrix. You can copy this table into your working document or spreadsheet. Create one row per factual proposition; split rows when the limitation, product version, or knowledge basis changes.

Assign stable IDs such as W-014 and link them to chart cells or defense issues. In Statement / cite, identify the source type and date, distinguish quotation from paraphrase, and supply transcript page-and-line references, declaration paragraphs, or interview-note sections.

Knowledge basis distinguishes participation, observation, record review, organizational preparation, and an unknown basis. Document / pinpoint contains the Bates page, figure, native location, worksheet cells, or code path and revision. Identify a potential authentication witness there if different from the speaker.

Conflict / gap holds contrary evidence, missing connections, and counsel’s expressly labeled inference. Action / owner / status states the next task, accountable reviewer, and whether reliance is supported, qualified, or withheld. Keep access controls and review history with the matrix; a filename or “internal” label is not a substitute for handling decisions.

Step by step

1. Define the proposition and its patent context

Start narrowly: who can explain whether release 3.2 stores calibration values in device memory? Do not start with “the product infringes.” Link that factual question to the asserted claim and limitation, preserving issued wording, dependencies, and applicable construction in the underlying chart.

Northern District of California Patent L.R. 3-1 requires identification of accused instrumentalities and limitation charts, alongside specified infringement positions. It is a district-specific example for actions within Rule 1-2, and Rule 1-3 permits court modification—not a nationwide matrix requirement. See Patent Local Rules 1-2, 1-3, and 3-1. (cand.uscourts.gov)

Record: row ID, chart-cell or issue reference, claim number, accused version, and the proposition requiring support. Keep separate rows for materially different infringement theories or defense questions.

2. Register the statement without upgrading its status

Classify the source as a signed statement, declaration, interview note, deposition testimony, or counsel inference. Capture the speaker, date, source ID, and exact location. For interview notes, identify the note-taker and whether the witness confirmed the wording; counsel’s shorthand must not become a purported quotation.

Preserve qualifications such as “usually,” “in the prototype,” and “I was not involved after launch.” Distinguish independent recollection from an inference prompted by a document. Read surrounding transcript testimony and any available corrections before relying on an excerpt.

Record: a short quotation or labeled paraphrase, source type, date, and pinpoint. Put counsel’s interpretation in Conflict / gap, expressly attributed to counsel.

3. Identify the basis and limits of knowledge

Ask how the witness knows the fact. An engineer may have written a module without knowing which build customers received. A sales manager may explain shipment records without understanding firmware behavior. Capture supported responsibilities and role dates, not assumptions based on job title.

Separate individual knowledge from organizational testimony. Federal Rule 30(b)(6) requires reasonably particular topics, good-faith conferral, and designated testimony about information known or reasonably available to the organization. It does not govern every individual deposition. See Federal Rule of Civil Procedure 30(b)(6). (uscourts.gov)

Record: knowledge basis, relevant period, designation topic where applicable, and the limits of the account. Flag an organizational witness’s personal recollection separately from information acquired during preparation.

4. Verify document references and version boundaries

Open each cited record and confirm what the passage supports. For schematics, identify figure and revision. For source code, identify the production or repository reference, file path, function or lines, and version. For sales records, specify worksheet, cells, product mapping, and period.

Distinguish document creation dates from the events described. A later manual does not, without a supported connection, establish earlier product behavior. Identify whether a specification states intended design, tested behavior, or deployed configuration. Follow applicable source-code handling restrictions rather than copying restricted material into a broadly shared matrix.

Record: precise location, supported version and period, and any unresolved link to the accused implementation. Mark a reference “not verified” when access or missing material prevents inspection.

5. Test corroboration, contradiction, and foundation

Compare supporting and contrary material. A release note may qualify recollection; a test report may concern a configuration absent from the relevant shipments. State whether the apparent conflict concerns timing, terminology, configuration, or genuinely inconsistent accounts.

Identify who could explain a document’s identity and provenance. Evidence Rule 901 requires sufficient support for finding that an item is what its proponent claims; knowledgeable-witness testimony is one listed authentication method. Authentication does not itself resolve hearsay or other admissibility questions. See Federal Rule of Evidence 901. (uscourts.gov)

Record: corroborating and contrary citations, potential authentication witness or alternative foundation, and unresolved evidentiary questions. Avoid the unqualified status “admissible.”

6. Turn gaps into bounded follow-up

Convert uncertainty into a specific task: locate a release manifest, verify deployment responsibilities, or retrieve an email attachment. Separate questions answerable from existing records from those requiring interviews, organizational testimony, or additional discovery. State what the requested evidence would establish.

Federal Rule 26(b)(1) limits discovery to nonprivileged matter relevant to claims or defenses and proportional to the case; discoverability does not require admissibility. A matrix gap therefore does not automatically justify additional production. See Federal Rule of Civil Procedure 26(b)(1). (uscourts.gov)

Record: missing fact, proposed source, owner, and next review point. Specify whether reliance remains qualified or should be withheld pending verification.

7. Review and prepare the limited handoff

Have a second reviewer trace consequential assertions to their sources. Check for silent combinations of prototype testimony and commercial-release records. Preserve prior assessments in a revision history, identifying what new evidence changed the conclusion.

Prepare witness-specific or issue-specific views without changing row IDs. Label the handoff as internal analysis. It is not automatically an evidentiary summary: Rule 1006 addresses voluminous admissible materials and requires underlying originals or duplicates to be available for examination or copying. Rule 107 separately governs illustrative aids. See Federal Rules of Evidence 1006 and 107. (uscourts.gov)

Record: reviewer, review date, intended use, reliance status, and each remaining assigned issue. The output should support a focused witness plan, not a premature merits conclusion.

Worked example

Entirely fictional scenario: Aster Circuit Labs asserts claim 7 of a fictional patent against Brindle Instruments’ Beacon sensor. Counsel’s chart identifies a disputed limitation concerning storage of calibration values in device memory. Accused releases are 3.1 and 3.2; the applicable construction remains unresolved.

Former engineer Lena Orr discussed prototype behavior in an interview. Firmware engineer Mateo Vale testified about release 3.2. Sales operations manager Iris Chen supplied a declaration identifying shipment data. Every party, witness, document, reference, and technical description below is fictional. Statement entries are paraphrases, not quotations.

The matrix changes the witness plan. Orr can explain prototype history but cannot yet connect it to release 3.1. Vale is the priority witness for distinguishing retrieval from persistence: those functions are not necessarily mutually exclusive, and the supplied evidence does not answer the question. Chen can explain shipment reporting, but the records cannot yet be allocated between releases.

Counsel therefore separates three uncertainties instead of combining them into an infringement narrative. No release manifest, persistence record, or serial-to-build mapping has been supplied; their contents remain unknown. Follow-up should address those missing connections before expanding reliance.

Common mistakes

• Organizing only by witness. A narrative can conceal version changes. Split by proposition and implementation, then create witness-specific views.
• Treating notes as adopted testimony. Preserve source and confirmation status; attribute counsel’s inference to counsel.
• Citing an entire technical production. Replace broad ranges with pages, figures, code locations, and revisions a reviewer can inspect.
• Inferring deployment from design intent. Seek configuration or deployment evidence and retain the gap until supported.
• Hiding contradictions elsewhere. Place the contrary reference beside the proposition and explain its effect on reliance.

Final quality check

• Every material proposition has a stable ID and exact statement citation.
• Quotations, paraphrases, source types, and counsel inferences remain distinguishable.
• Knowledge bases, role periods, and organizational topics are accurately recorded.
• Claim references preserve the limitation, dependencies, construction status, and accused version.
• Document pinpoints have been inspected, or unavailable access is expressly recorded.
• Contradictions and foundation questions are resolved or remain visibly qualified.
• Each open issue has an owner and review point; access restrictions and intended use are confirmed.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Use the lawyer-maintained matrix to direct document review and evidence analysis, then carry verified references into deposition preparation. Where timing affects a witness account or product-version connection, chronology work can support the review. Counsel retains source verification and legal judgment. To discuss this workflow, book a demo.

Frequently asked questions

Should the matrix follow witnesses or claim limitations?

Use proposition-level rows linked to both. Claim references reveal missing support; witness references support focused preparation. Maintain common row IDs across views and separate materially different versions.

Can an interview note fill a missing document reference?

It can preserve the witness’s account, but it does not replace inspection of the referenced document. Record the account’s limits, identify the missing material, and assign retrieval or clarification without inventing corroboration.

How should source-code testimony be recorded?

Identify version, path, and function or lines where permitted. Separate the technical account from counsel’s limitation mapping. Record access constraints and unresolved links between the reviewed code and deployed builds.

Is this matrix a claim chart or trial exhibit?

Neither automatically. It connects propositions to witnesses and records for further analysis. Courtroom use requires separate consideration of purpose, foundation, admissibility, and applicable rules; internal annotations should not be carried forward unexamined.

Sources

• Federal Rules of Civil Procedure: Rules 1, 26(b)(1), and 30(b)(6).
• Federal Rules of Evidence: Rules 901, 1006, and 107.
• Northern District of California Patent Local Rules: Rules 1-2, 1-3, and 3-1.

Scope: this general workflow uses the October 13, 2026 research cutoff; confirm applicable rule versions and case-specific orders before implementation.

This guide is general information about legal workflows, not legal advice for any matter. It was drafted and reviewed with AI assistance. The worked example is fictional. Contract rights and procedure depend on the governing law, the actual wording, and the facts, so check the cited sources and the rules that apply in your jurisdiction before relying on it.