How to prepare a deposition outline from case documents for Patent Infringement Matters

Prepare a patent-infringement deposition outline by connecting the witness’s knowledge to specific claim limitations, accused product versions, defenses, chronology disputes, and damages questions. For each topic, identify the testimony sought, attach exact document references, distinguish evidence from inference, and prepare follow-ups for contradictory or incomplete answers. The deliverable is a question sequence supported by an exhibit map and assigned open issues—not a document summary. Separate firsthand-knowledge questions from organizational testimony, and preserve uncertainties rather than embedding them in questions as established facts.

When to use this workflow

Use this workflow when litigation counsel has an identified deponent and documents supporting focused examination: an engineer’s records concerning accused functionality, an inventor’s development files, or an organization’s release and sales records.

This guide addresses taking fact depositions in US federal district-court patent litigation, not preparing expert examinations or defending witnesses. Check governing rules, the judge’s orders, the notice or subpoena, and protective orders. Do not apply this federal framework automatically to arbitration, state proceedings, ITC investigations, or PTAB proceedings. Federal Rules of Civil Procedure, Rules 1 and 30.

Rule 26(b)(1) permits discovery of nonprivileged matter relevant to claims or defenses and proportional to the case; information need not be admissible to be discoverable. Accordingly, distinguish exploratory questions from questions intended to establish a trial foundation. Rule 26(b)(1).

What you need

Assemble a controlled working set:

• Case positions: asserted claims and dependencies, operative infringement and invalidity contentions, claim charts, claim-construction orders, and disputed constructions.
• Witness materials: notice or subpoena, organizational topics and designation, role history, prior testimony, and records showing participation in relevant events.
• Technical records: specifications, schematics, release notes, source-code references, configurations, test conditions, and product-version mappings.
• Commercial records: sales-field definitions, product identifiers, licenses, notice correspondence, and relevant marking records.
• Exhibit controls: production numbers, native-file locations, confidentiality designations, privilege-review status, and source-code restrictions.

Select records for the witness’s role. A release engineer may explain deployment without knowing licensing decisions; a finance witness may explain reporting fields without knowing accused functionality. Treat missing documents as gaps, not proof that an event never occurred. Record the document and contention versions used.

Use the template

The companion template is Patent Infringement Matters — Deposition outline. Copy this table into your working document or spreadsheet. Use one row per examination objective and place longer question sequences beneath their topic IDs.

“Topic ID” connects questions, exhibits, and follow-up tasks. “Issue / version” identifies the limitation, defense, chronology dispute, or damages issue and relevant release or period. Preserve exact issued claim wording and applicable constructions in the supporting outline.

“Knowledge basis” distinguishes firsthand involvement, records-based knowledge, organizational preparation, and counsel’s inference. “Evidence cite” locates a Bates page, figure, code path and version, spreadsheet cell, or transcript page and line—not merely a document title.

Keep contrary evidence under “Conflict / gap.” Record handling restrictions under “Exhibit controls,” and give unresolved points an action and responsible reviewer. The table is counsel’s work product, not a substitute for examination questions.

Step by step

1. Define objectives and witness capacity

Write a factual objective for each topic: identify who approved a release, determine which component performs an operation, or establish whether a sales category includes nonaccused products. Avoid “prove infringement,” which obscures the facts sought.

Identify individual and organizational capacities separately. Rule 30(b)(6) requires reasonably particular examination topics, good-faith conferral about those matters, and designated testimony concerning information known or reasonably available to the organization. That is distinct from an individual witness’s personal knowledge. Rule 30(b)(6).

Template output: enter the objective, capacity, knowledge basis, and organizational topic number where applicable. Flag unresolved designation or scope questions.

2. Map topics to operative patent positions

Connect each technical topic to an asserted claim and limitation, accused instrumentality, version, and relevant configuration. Distinguish literal-infringement questions from equivalents questions where both theories are asserted. For invalidity topics, separate a reference’s technical content from evidence of its publication, accessibility, sale, or use dates.

Northern District of California Patent L.R. 3-1 requires specified infringement disclosures, including accused instrumentalities and limitation charts. Use it only as a district-specific example; Rule 1-3 permits court modification, and it is not a nationwide outline requirement. Patent Local Rules 1-3 and 3-1.

Template output: record the chart cell, limitation reference, construction, accused version, and factual question. Separate expert interpretation from direct documentary support.

3. Build a source-linked exhibit sequence

Choose an anchor document for each topic, then add supporting or contradictory records that advance the examination. Read surrounding pages, attachments, and relevant document families before extracting passages.

Verify that diagrams, code references, tests, and release notes concern the same version and configuration. For commercial exhibits, identify periods, units, product identifiers, and field definitions. Do not confuse a report’s creation date with its reporting period.

Prepare questions about recognition, authorship, maintenance, and familiarity. Rule 901 requires evidence supporting a finding that an item is what its proponent claims; knowledgeable-witness testimony is one method. This addresses authentication, not every admissibility issue. Federal Rule of Evidence 901.

Template output: enter exact citations, provisional exhibit IDs, handling controls, and missing foundation.

4. Draft questions from foundation to disputed operation

Establish the witness’s role and terminology, then the document’s context, before asking about disputed facts. Separate technical operations rather than combining several assumptions in one question.

For a routing feature, ask which component receives an instruction, what triggers selection, which configuration governs execution, and whether operation differs by release. Connect the answers to claim language without assuming agreement with counsel’s legal characterization.

Prepare branches for affirmative, negative, and uncertain answers. After “I do not know,” ask which records or people could supply the information. For organizational testimony, distinguish personal involvement from preparation for the noticed topic, without seeking protected communications.

Template output: record principal questions, follow-ups, and the factual endpoint that completes each topic.

5. Test contradictions and chronology

Compare questions against unfavorable documents and prior testimony. A draft specification may describe intended operation while a test report concerns a later implementation. Ask whether an apparent inconsistency reflects a version change, configuration difference, or genuine disagreement.

Separate event dates, document dates, and inferred dates. An email saying a feature is “ready” does not establish shipment. Ask what readiness meant and which records document deployment.

Establish each conflicting record’s context before requesting reconciliation. Keep the less favorable record visible rather than scripting only the preferred explanation.

Template output: cite both sources, describe the unresolved distinction, and draft a reconciliation question. Assign missing-source investigation separately.

6. Clear exhibits and prioritize examination time

Screen proposed exhibits and questions for privilege-sensitive subjects and handling restrictions. Escalate patent-agent communications, third-party participation, and advice-of-counsel subjects for individualized analysis; do not assume their status.

Check the actual protective order before planning source-code exhibits, copies, or witness access. Prepare questions about underlying technical events without assuming communications with counsel may be explored.

Prioritize unique witness knowledge and essential organizational explanations. Keep a shorter route through must-cover questions if background consumes more time than expected. Check applicable time limits and any modifications rather than assuming unlimited examination. Rule 30(d)(1).

Template output: record clearance status, unresolved restrictions, priority, and the responsible lawyer.

7. Rehearse and release the examination version

Have another reviewer test the questions using only cited documents. If an expected answer requires an unstated assumption, revise the question or mark the premise unresolved. Confirm that every exhibit is readily locatable.

Rehearse transitions between operation, release history, and commercial records. Keep expected answers separate from established evidence and preserve alternative branches. Add brief closing questions identifying other knowledgeable people and missing records for unresolved topics.

Template output: finalize topic order, exhibit references, issue assignments, and version ID. Produce a concise examination copy while retaining the source-linked working table.

Worked example

Fictional scenario: All parties, products, patent language, and records below are invented. Alder Circuit LLC accuses Beacon Devices Inc.’s RelayHub releases 4.1 and 4.2 of infringing a fictional patent. An asserted limitation concerns selecting a transmission path using stored priority information. Counsel will examine Beacon’s organizational designee on routing, releases, and product reporting.

The production contains a 4.2 specification, test exception, rollout email, and revenue workbook. The rollout attachment and workbook dictionary are missing. Organizational preparation and the witness’s firsthand involvement remain unconfirmed.

T01 changes an assumed admission into a sequence: “Which build was tested? What triggered fallback? In fallback, did selection still consult stored priority information?” The test alone does not answer the final question or establish operation across both releases.

T02 prevents readiness from becoming unsupported deployment evidence. T03 makes category definitions a prerequisite to using the workbook total as accused-product revenue. Counsel must not invent the missing attachment or dictionary; the outline instead assigns their pursuit and identifies questions that remain answerable.

Common mistakes

• Treating releases as identical. Add version and configuration to each technical topic; ask expressly about changes.
• Reading claim-chart conclusions as facts. Separate observed operation from counsel’s mapping and expert interpretation.
• Confusing individual and organizational knowledge. Label capacity and distinguish personal participation from organizational preparation.
• Using isolated technical excerpts. Review specifications, test conditions, and attachments before asserting a contradiction.
• Treating sales totals as self-explanatory. Establish product codes, periods, bundles, and category definitions before using totals.

Final quality check

• Each topic has a factual objective tied to a patent issue.
• Claims, dependencies, constructions, and accused versions match operative positions.
• Factual premises have exact citations or explicit uncertainty labels.
• Exhibit passages match originals and surrounding context.
• Contrary evidence and alternative explanations remain visible.
• Capacity, exhibit access, handling restrictions, and sensitive subjects are checked.
• Open issues are resolved or expressly assigned before examination use.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Use its document review, privilege and confidentiality analysis, evidence analysis, and deposition preparation capabilities to organize source material and examination topics. Its chronology viewer can support review of release-date disputes. Counsel retains responsibility for source verification, questions, and legal judgment; the outline and table remain counsel’s work products. To evaluate this workflow, book a demo.

Frequently asked questions

Should the outline follow the claim chart’s order?

Not necessarily. Preserve chart references, but organize around witness knowledge and product operation. A coherent account of data flow can support several limitation-specific follow-ups without reading limitations sequentially.

How should source code appear in the outline?

Identify version, file path, function, and relevant location, subject to protective-order restrictions. Connect code to operational questions. A function name alone does not establish what the software does or whether it satisfies a limitation.

What if the witness cannot explain a technical document?

Establish what the witness recognizes, where knowledge ends, and which records or people could explain it. For an organizational designee, separately explore preparation for the noticed topic. Preserve the gap for counsel’s assessment rather than inventing an explanation.

Should damages questions go into an engineer’s outline?

Include questions within the engineer’s demonstrated knowledge, such as release differences, optional functionality, and product identifiers. Direct accounting definitions and allocations to an appropriately knowledgeable witness, including an organizational designee prepared on those topics.

Sources

• Federal Rules of Civil Procedure: Rules 1, 26(b)(1), 30(b)(6), and 30(d)(1).
• Northern District of California Patent Local Rules: Rules 1-3 and 3-1; district-specific requirements.
• Federal Rules of Evidence: Rule 901.

Scope: General professional workflow guidance with an October 13, 2026 research cutoff; confirm applicable orders and rule versions for the matter.

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.