How to build a discovery request and response tracker for Patent Infringement Matters

Build the tracker around individual discovery requests, not production batches. For each request, identify the patent issue and accused product version, preserve the response and objections, separate response deadlines from production commitments, and link deliveries to verifiable document references. Record deficiencies, responsible lawyers, and the next action. The resulting deliverable is a request-level control record showing what was sought, what was promised, what arrived, and what remains unresolved—without treating a served response or a large production as proof of completeness.

When to use this workflow

Use this workflow when counsel serves or receives document requests in a patent infringement action, inherits a discovery record, or prepares for a discovery conference. It supports requesting and responding counsel, including in-house teams coordinating engineering, finance, and licensing personnel.

The focus is US federal district-court document discovery, not a comprehensive tracker for interrogatories, admissions, subpoenas, or depositions. Those instruments need separate records and rule-specific controls. Do not carry federal district-court procedures into state litigation, arbitration, ITC investigations, or PTAB proceedings without checking the governing framework.

Patent contentions and supporting disclosures may overlap with requested documents but remain separate obligations. Northern District of California Patent Local Rules 3-1 through 3-4 provide a district-specific example, subject to modification under Rule 1-3. Keep disclosure IDs distinct from request IDs. See Patent Local Rules 1-3 and 3-1–3-4.

What you need

Assemble operative requests, service records, signed responses, amendments, correspondence, production transmittals, and deficiency letters. Include the scheduling order, discovery orders, protective order, applicable local rules, and documented extensions.

Obtain the current asserted-patent and claim list, accused products and versions, relevant contentions, and financial periods under investigation. Identify repositories for source code, technical drawings, testing, sales, licensing, and ownership records where relevant to the requests.

Gather production indexes, Bates ranges, native-file identifiers, inspection inventories, and privilege-description references. These distinguish missing responses from incomplete deliveries, restricted access, or disputed searches. Do not infer that an unlisted repository was searched or that an unavailable release never existed.

Use the template

The Patent Infringement Matters — Discovery response tracker is a compact working template. Copy this table into your working document or spreadsheet. Use one primary row per request, with linked subrows for distinct versions, delivery stages, or deficiencies.

Assign stable IDs such as OUT-RFP-012; direction identifies outgoing or incoming discovery. Cite each request and response by document ID, item, and page. Connect the request to a limitation, accused version, invalidity position, ownership question, or damages issue without reproducing the claim chart.

In Dates / authority, distinguish response due, production promised, actual delivery, and follow-up. Link operative dates to their sources. Response / withholding preserves the served position, not counsel’s assumptions. Delivery / evidence identifies Bates ranges, native IDs, or inspection records. Status / gap / decision separates workflow status from unresolved facts and counsel’s judgment.

Use linked detail records rather than compressing conflicting commitments into one cell. Maintain access controls appropriate to the tracker’s contents. This is counsel’s work product, not a prescribed court format.

Step by step

1. Establish the controlling scope and obligation IDs

Identify the operative request set, responding entity, service event, and response version. Preserve superseded records while marking which document controls. Separate document requests from contention disclosures and informal requests.

Map each request to its patent issue. For technical materials, identify the accused product, release, component, and period. For financial materials, specify product identifiers, reporting period, and requested detail.

Rule 26(b)(1) makes relevance, proportionality, and nonprivileged status central to discovery scope; admissibility is not required. A patent-issue label alone does not justify every proposed search. See Rule 26(b)(1).

Record: stable IDs, controlling citations, issue mappings, and unresolved scope questions.

2. Enter dates with their documentary authority

Verify dates against applicable rules, service records, orders, and effective agreements. Do not populate every row using an assumed interval. Distinguish the written-response deadline from first delivery, staged deliveries, and production completion.

Mark proposed extensions as pending until their effectiveness is verified. Preserve prior dates and the basis for changes. Put internal review targets in the next-action field rather than presenting them as court deadlines.

Rule 34 distinguishes written responses from production timing and requires production by the requested inspection time or another reasonable time specified in the response. See Rule 34(b)(2)(A)–(B). A later promised delivery should not silently replace the operative obligation.

Record: date type, source, verification status, and responsible verifier.

3. Capture responses, objections, and withholding separately

For each item, identify objections, accepted scope, production commitments, and the statement concerning objection-based withholding. Avoid summaries such as “objected” or “agreed” that conceal qualifications.

Rule 34 requires specific objections and disclosure of whether responsive materials are withheld on those objections. See Rule 34(b)(2)(B)–(C).

A response may offer current schematics while objecting to historical versions. Record both positions. Silence about withholding is an ambiguity, not confirmation that nothing was withheld. Responding counsel should reconcile the tracker with the served language and intended production scope; the tracker does not amend the response.

Record: response citation, objection summary, withholding statement, commitments, and clarification questions.

4. Map deliveries to requests and technical versions

Match transmittals and production indexes to request rows. If the producing party supplies no mapping, label counsel’s mapping provisional rather than attributing it to the producer.

Check whether engineering records concern the accused release, sales extracts contain the requested product codes, and native data accompanies rendered reports where required by the operative scope. A Bates range alone does not establish coverage.

For controlled source-code access, record the inspection identifier, available release, access conditions, and unresolved logistics. Do not copy restricted code into a broadly shared tracker. One delivery can support several requests, but each requires its own coverage assessment.

Record: actual delivery date, transmittal citation, document or inspection IDs, version coverage, and mapping confidence.

5. Assess gaps and privilege-related dependencies

Compare the request, response, any agreed narrowing or ruling, and delivery. Classify gaps precisely: missing period, wrong release, absent attachment, unexplained product-code exclusion, disputed scope, unresolved withholding, or unavailable access. Separate “not located in this delivery” from “does not exist.”

Link privilege descriptions without reproducing sensitive analysis in broadly accessible cells. Rule 26(b)(5)(A) requires express protection claims and assessable descriptions; Rule 26(f)(3)(D) addresses compliance timing and method in discovery planning. See Rules 26(b)(5)(A) and 26(f)(3)(D). Evaluate the matter’s arrangements rather than assuming a universal log format or date.

Record: supporting evidence, uncertainty, scope disputes, privilege dependencies, and assessment owner.

6. Turn deficiencies into bounded follow-up

Identify the request, cite the response, state what arrived, and explain the unresolved difference. Ask a concrete question or seek a defined action rather than declaring the entire production deficient.

For an omitted code release, ask whether it was searched, whether it is available for inspection, and what explains the omission. For revenue data, identify missing product codes or periods. Distinguish requested relief from an opponent’s agreement and counsel’s escalation plan.

Before escalation, verify the court’s conference procedures and applicable motion requirements. A tracker entry is not authorization to file.

Record: follow-up citation, requested action, opposing position, responsible lawyer, and next review date.

7. Reconcile status before closing a row

Use distinct statuses: response received, production underway, review pending, deficiency open, and closed after verification. Do not let delivery trigger closure automatically.

Close a row after reconciling the operative scope, responses, deliveries, and unresolved questions. Closure may reflect agreed narrowing or a reasoned decision not to pursue a gap; it need not mean every originally requested document was produced.

Responding counsel should reconcile completion statements with production counsel and repository owners. Requesting counsel should preserve material limitations even when further pursuit is unwarranted. Reopen a row when later evidence undermines its closure basis.

Record: status, closure rationale, supporting citations, reviewer, and retained limitations.

Worked example

The parties, documents, dates, and facts below are entirely fictional. Kestrel Optics sues Morrow Sensor Systems over the filtering function in its Vela sensor. Counsel is investigating releases 2.1 and 2.4 and revenue for January–June 2025. Three requests concern code, sales, and licensing communications. Written responses arrived, but production coverage remains uncertain. All September dates below are in 2026.

The first row prevents an inspection appointment from being mistaken for access to both releases. Counsel should not infer release 2.1’s operation from 2.4 without support. The second focuses follow-up on a product-code mismatch rather than demanding another undifferentiated production. The third separates documents received from the ability to assess withholding.

These entries neither establish misconduct nor prove missing records exist. They support keeping the rows open, issuing focused follow-up, and warning technical and damages reviewers that specified inputs remain incomplete. No response deadline is supplied in the fictional record, so none is invented.

Common mistakes

• Using volume as completeness evidence. Reconcile each request’s scope and accused versions, not file counts.
• Merging contentions with request responses. Keep separate obligation IDs and cross-reference shared documents.
• Treating unilateral narrowing as agreed scope. Preserve the objection and disputed remainder until agreement, ruling, or counsel’s documented decision resolves pursuit.
• Equating inspection availability with completed code discovery. Verify available releases, inspection records, and unresolved restrictions.
• Overwriting dates. Preserve the prior date, revised date, and authority for the change.

Final quality check

• Every request has a stable ID and verified operative-text citation.
• Patent issues, accused releases, product codes, and periods match current records.
• Responses, objections, withholding, and commitments remain distinguishable.
• Dates resolve to supporting records; proposed changes remain visibly pending.
• Delivery references resolve to the correct documents, native files, or inspection records.
• Gaps distinguish evidence from inference and have accountable owners.
• Closure decisions preserve limitations; unresolved issues are resolved or expressly assigned.
• Tracker access and linked materials comply with applicable confidentiality restrictions.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its document review, privilege and confidentiality analysis, and evidence analysis capabilities can support review of materials referenced in this tracker. Counsel remains responsible for request coverage, deadline verification, and closure decisions. Explore litigation preparation capabilities or book a demo to discuss the underlying document-review workflow. The tracker remains your working record, not an automatic monitoring system.

Frequently asked questions

Should each patent claim have a separate tracker row?

Start with each request. Add linked subrows when a claim, limitation, or accused release creates a distinct commitment or deficiency. Keep detailed limitation analysis in a separate claim chart.

Can one production close several requests?

Yes, after a reviewer verifies each request’s coverage. Reuse delivery references but record separate assessments. Current design records may answer one request without resolving another seeking historical releases.

How should restricted source-code inspection be tracked?

Record requested and available releases, inspection references, conditions, and outstanding access questions. Keep code and sensitive analysis out of a tracker whose audience or storage conflicts with the protective order.

What if opposing counsel says production is complete?

Record the statement and source, then reconcile it against scope, responses, and deliveries. Ask focused questions about identifiable gaps. The statement records the producer’s position; it does not replace coverage review.

Sources

• Federal Rules of Civil Procedure, December 1, 2025 edition: Rules 26 and 34 support the federal discovery propositions discussed above.
• Northern District of California Patent Local Rules: district-specific contention and supporting-production obligations.

This is general professional workflow guidance, not advice for a particular matter. Verify the governing rules and 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.