How to prepare a document collection checklist for Patent Infringement Matters

Prepare a patent-infringement document collection checklist by mapping asserted claims, accused product versions, defenses, and damages questions to custodians and repositories. Define each collection unit’s records, period, method, handling controls, verification evidence, and responsible reviewer. Distinguish material located from material collected and checked, and keep preservation, privilege review, and production decisions separate. The deliverable is a source-linked checklist that directs collectors, identifies missing technical and commercial records, and documents counsel’s scope decisions without implying that collected material must be produced.

When to use this workflow

Use this workflow when pleadings, infringement contentions, discovery requests, or newly identified product versions must become concrete collection instructions. It serves outside counsel, in-house IP teams, and discovery professionals coordinating engineering, finance, licensing, and records personnel.

The procedural scope is US federal district-court litigation. Rule 26(b)(1) limits discovery to nonprivileged matter relevant to claims or defenses and proportional to the case. Use that framework to assess collection scope; relevance alone does not justify collecting every repository. See Federal Rule of Civil Procedure 26(b)(1). (uscourts.gov)

Check the assigned judge’s orders and applicable local rules. Northern District of California Patent Local Rules apply to the utility-patent actions described in Rule 1-2, and Rule 1-3 permits court modification of obligations. They are a district-specific example, not a nationwide collection mandate. See Patent Local Rules 1-2 and 1-3. Federal procedure should not be carried into state proceedings, arbitration, ITC investigations, or PTAB proceedings without separate analysis. (cand.uscourts.gov)

What you need

Gather five sets of inputs:

• Issue documents: operative pleadings, asserted patents and claims, current contentions, accused instrumentalities, and identified defenses.
• Scope instructions: requests, orders, protective provisions, discovery agreements, approved limits, and preservation instructions.
• Technical maps: product names, project names, model numbers, release histories, code repositories, schematic archives, test systems, and collaboration channels.
• People and business sources: inventors, engineers, sales staff, licensing and finance contacts, prosecution files, assignments, notices, marking records, sales data, and licenses.
• Collection history: previous collections, native locations, document IDs, exception reports, and unavailable or migrated sources.

Ask business contacts to explain system boundaries. The product name in a complaint may differ from its code branch, financial SKU, or engineering project name. Establish those crosswalks before selecting search terms. Treat an unconfirmed repository as an assigned question, not as a source searched with no results.

Use the template

Use the Patent Infringement Matters — Document collection checklist below. You can copy this table into your working document or spreadsheet. Create one row per collection unit: a record category, source, and scope that can be collected and verified independently.

ID / issue links the row to a claim limitation, defense, damages question, or request number. Records / version distinguishes released firmware from development branches or different hardware configurations. Period / limits records dates, exclusions, and the linked rationale.

Method / controls identifies the collection approach and approved handling restrictions. Evidence / locator points to manifests, native paths, document IDs, sheet names, or page citations. Use Bates references only after numbering exists; a collection ID is not a production number.

In Status / gap, distinguish planned, located, collected but unverified, verified, incomplete, and excluded by counsel decision. Owner / next action identifies a named person, the next task, and an approved target date. Link detailed instructions and approvals rather than compressing them into ambiguous shorthand. Keep legal analysis in appropriately restricted records.

Step by step

1. Translate the dispute into collection questions

Start with asserted claims and accused instrumentalities, not a company-wide document list. Identify which records could explain each disputed operation, configuration, transaction, or defense. For indirect-infringement allegations, consider relevant instructions, customer communications, and use evidence rather than limiting collection to internal design files.

In covered Northern District of California actions, Patent L.R. 3-1 addresses accused instrumentalities and charts locating claim limitations, among other infringement disclosures. Use the actual contentions to identify collection questions; do not assume another court requires the same disclosures. See Patent Local Rule 3-1. (cand.uscourts.gov)

Record: the issue reference, record category, and accused version. Flag uncertain mappings rather than treating counsel’s inference as technical evidence.

2. Map custodians to systems and historical versions

Interview people who understand the sources. Engineers can identify implementation records; release managers can explain what shipped. Sales and finance contacts can reconcile product identifiers. Inventors and licensing personnel can identify historical records outside current operational systems.

Ask about departed personnel, migrated repositories, archived branches, shared accounts, local storage, and inaccessible attachments. For code, identify release tags, commit identifiers where available, build information, and associated documentation. For hardware, distinguish revisions, schematics, bills of materials, and configuration changes. Do not assume a current repository represents the accused historical product.

Record: custodians, repository locations, crosswalk references, and historical-source gaps. Assign inaccessible sources to someone who can investigate them.

3. Set collection limits and handling instructions

Define the period and selection criteria for each source. Explain whether the task concerns a release, engineering team, customer transaction set, license family, or notice-related correspondence. For large sources, document the proposed search or staged collection method and how its coverage will be checked.

Keep preservation decisions distinct from collection limits: collecting selected branches must not silently authorize deletion of others. Escalate unavailable backups, disproportionate proposals, and preservation uncertainty to responsible counsel.

Before copying source code or sensitive technical records, check the governing protective order and approved protocol. Specify access, transfer, and storage arrangements; do not assume an external review service is authorized.

Record: limits, rationale, control references, and counsel’s approval or unresolved decision. If work is staged, identify the trigger for considering broader collection.

4. Cover patent-specific record families

Check technical, patent, and commercial sources separately. Technical records may include code, schematics, specifications, testing, manuals, and change histories. Patent-side records may include prosecution, invention development, assignments, and licensing. Commercial sources may include notices, marking records, sales, returns, and product-identifier tables, depending on the issues.

For an infringement claimant subject to Patent L.R. 3-2, accompanying production categories include specified invention-development, prosecution, ownership, and licensing records. Rules 3-3 and 3-4 address invalidity disclosures and supporting materials. These provisions identify district-specific obligations; they do not establish infringement or substantive prior-art status. See Patent Local Rules 3-2 through 3-4. (cand.uscourts.gov)

Record: separate rows for materially different families. Explain exclusions, and distinguish records held by the client from records that may require another discovery route.

5. Collect with provenance and verification evidence

Issue written instructions specifying sources, scope, controls, and exception reporting. Document what was collected, when, from where, by whom, and through which method. Preserve useful relationships, including email attachments and links between releases and build documentation. Request an inventory or manifest against which delivery can be checked.

Identify a potential knowledgeable witness for important sources. Evidence Rule 901 requires support for a finding that an item is what its proponent claims; knowledgeable-witness testimony is one recognized method. Collection documentation can assist later foundation work but does not establish admissibility by itself. See Federal Rule of Evidence 901. (uscourts.gov)

Record: manifest references, native locations, collector details, collection dates, potential foundation witnesses, and exceptions in linked records.

6. Route sensitive material for separate review

Separate collection from privilege and production decisions. Flag possible legal advice, patent-agent communications, third-party recipients, and advice-of-counsel issues for individualized assessment. Do not omit an engineering folder merely because some files involve lawyers, or decide protection from a message’s recipient list alone.

Rule 26(b)(5)(A) addresses express protection claims and descriptions permitting assessment without revealing protected information. Rule 26(f)(3)(D) addresses compliance timing and method in discovery planning. Neither prescribes this checklist’s format or decides substantive privilege entitlement. See Federal Rules of Civil Procedure 26(b)(5)(A) and 26(f)(3)(D). (uscourts.gov)

Record: restricted routing, the responsible reviewer, and links to separately maintained decisions. Keep protected substance out of broadly shared collection instructions.

7. Reconcile results and assign remaining gaps

Compare deliveries with instructions. Check that files open, expected attachments exist, periods are covered, and versions match. For sales data, obtain field definitions and test identifiers, filters, returns, and reporting coverage before treating an extract as complete. Investigate unexpected zero results with the source owner.

Keep request-response tracking separate. Rule 34(b)(2) addresses request-specific responses, specific objections, and whether responsive materials are withheld on an objection. A collection status does not answer those questions, and response dates should not be confused with production completion dates. See Federal Rule of Civil Procedure 34(b)(2). (uscourts.gov)

Record: verified coverage, deficiencies, owners, and next actions. Close a row only when its collection task is satisfied or counsel documents another disposition.

Worked example

Fictional scenario: Alder Circuit Labs accuses Baymere Instruments’ Harbor controller of practicing a claim concerning firmware-controlled sensor response. Counsel represents Baymere. The identified versions are 2.1 and 2.2, with relevant sales from January through December 2024. Engineering supplies only version 2.2. Finance supplies an extract with an unexplained product code. All parties, records, identifiers, and facts below are fictional.

ENG-04 identifies two releases but does not establish version 2.1’s operation. The missing historical code therefore changes collection priority, not the infringement conclusion. Counsel should not substitute version 2.2 without evidence supporting that comparison.

HBR-B prevents approval of the sales filter: its inclusion or exclusion remains unsupported. The email reference establishes an attachment-recovery task, not the missing attachment’s contents or protection status. These rows make the next decisions explicit without fabricating evidence.

Common mistakes

• Searching by patent number alone. Add verified product, component, project, and repository identifiers; technical records may use different names.
• Substituting current code for historical versions. Reconcile release history and collect the relevant materials, or assign the missing-version investigation.
• Accepting a sales spreadsheet without checking coverage. Verify fields, identifiers, filters, periods, and exclusions against the requested scope.
• Combining collection and production status. Link separate review, withholding, and production records to collection IDs.
• Calling absent records nonexistent. Identify sources checked, sources remaining, access problems, and the basis for any closure decision.

Final quality check

• Each row connects to a defined issue, request, or approved investigation question.
• Accused products, versions, and internal identifiers are reconciled or flagged.
• Sources and instructions are specific enough for another collector to act.
• Limits, preservation questions, and handling controls have documented dispositions.
• Manifests and cited document locations have been opened and checked.
• Governing rules and orders have been checked against the checklist’s obligations.
• Sensitive records have an assigned review route without premature protection conclusions.
• Open issues have owners and next actions; closed rows show verification or a reasoned disposition.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its document review, privilege and confidentiality analysis, and tabular review capabilities can support counsel’s assessment of collected materials. Bulk document classification can organize records and prioritize human review. Keep repository verification, collection scope, and legal decisions with the team. To discuss reviewing these collections within litigation preparation, book a demo.

Frequently asked questions

Should claimant and defendant checklists match?

No. Claimant collections may emphasize invention, prosecution, ownership, and licensing; defendant collections may emphasize accused implementations and commercial records. Both should follow actual claims, defenses, requests, and governing obligations rather than fixed party-role assumptions.

Must every code branch be collected?

Do not assume so. Identify accused releases, branch relationships, and the collection question. Document approved limits and separate preservation decisions, especially where an uncollected branch may contain historical implementation evidence. Escalate uncertain coverage rather than deleting the branch.

How should potentially relevant prior art be recorded?

Retain the reference, provenance, date evidence, and translation needs. Distinguish filing, publication, accessibility, sale, and use dates. Treat eligibility and invalidity as separate legal questions; collecting a reference is not a conclusion about either.

When is the checklist complete?

A collection unit closes after verification or a documented alternative disposition. A checklist may be ready for handoff with explicitly assigned open issues, but it should not be labeled fully collected while gaps remain. Neither status establishes completion of privilege review, production, or discovery.

Sources

• Federal Rules of Civil Procedure, December 1, 2025 edition: Rules 26 and 34.
• Northern District of California Patent Local Rules: Rules 1-2, 1-3, and 3-1 through 3-4.
• Federal Rules of Evidence: Rule 901.

Scope: General professional workflow guidance using the supplied research cutoff of October 13, 2026; apply the governing rules and orders for the particular proceeding.

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.