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

Build the tracker around each discovery request, then connect it to the asserted work, disputed conduct, response obligations, and source documents. Record service and deadline authority separately from production commitments; distinguish objections, withheld material, partial production, and unresolved deficiencies. For copyright disputes, identify exact work versions and the ownership, access, permission, use, or damages issue each request addresses. The deliverable is a source-linked working table that lets counsel determine what was requested, what remains missing, who must act, and whether a response is actually complete.

When to use this workflow

Use this workflow when litigation counsel or an in-house team serves or receives discovery concerning allegedly copied photographs, software, music, audiovisual works, or text. It is particularly useful when requests cover multiple works, production arrives in installments, or a party objects while promising a narrower search.

The procedural discussion assumes US federal district-court litigation and concentrates on document requests. The same organizational structure can track interrogatories or admissions, but their response requirements require separate analysis; Rule 34 is not a universal discovery-response rule. Federal procedure does not automatically govern state proceedings, arbitration, Copyright Claims Board matters, or informal exchanges. Confirm the applicable rules and orders. See Federal Rules of Civil Procedure, Rules 1 and 34. (uscourts.gov)

What you need

Collect operative requests, service records, responses, amendments, extension correspondence, discovery orders, and production cover letters. Include the pleadings and current asserted-work list so descriptions remain tied to the dispute.

Assemble copyright-specific reference material:

• Work identifiers, registration records and deposits, native creative files, revision histories, and publication records.
• Authorship records, executed assignments, employment or commissioning agreements, licenses, amendments, and schedules.
• Evidence of alleged access, uploads, distribution, disputed uses, permissions, and sales or licensing activity.
• Custodian and repository lists, search records, production indexes, privilege records, and deficiency correspondence.

Maintain an evidence index with stable document IDs. A filename such as “final image” is inadequate when several revisions exist. Identify the version each request concerns and keep untouched source files distinct from review copies. Include production specifications and protective-order restrictions in the reference set.

Use the template

The companion template is Copyright Infringement Matters — Discovery response tracker. Copy this table into your working document or spreadsheet. Start with one row per request; create linked subrows when works, objections, or commitments require different follow-up.

Use identifiers such as OUT-RFP-014 or IN-RFP-006, not row numbers that change when sorted. Direction identifies whether the team served or received the request. Include the parties and request-set ID where multiple parties are involved.

The deadline cell should contain service date, verified response date, controlling source, and extension reference. Link response positions to paragraphs; “objected” alone is insufficient. Record withheld categories separately from promised production.

Distinguish promised scope from delivered material using Bates ranges or native-file IDs. Give unresolved gaps an owner, next action, and target date. Store detailed search records and privileged analysis in appropriately restricted companion records, linked by ID. The eight-column table is an index to those records, not a substitute for them.

Step by step

1. Establish request identity and procedural controls

Inventory each request set and operative version. Record request number, direction, parties, service evidence, and response document. Preserve amended or withdrawn requests as historical records rather than silently overwriting them.

Have counsel verify response dates and modifications against controlling sources, including applicable computation rules and orders. Treat the written-response deadline, rolling-production commitment, and internal follow-up date as separate events. Never calculate an enforceable deadline from the template alone.

Record: request ID, source location, service citation, verified response deadline, extension history, and separate production dates. Identify internal targets expressly so they are not mistaken for legal deadlines.

2. Map each request to a work and disputed issue

Assign stable work IDs and identify versions, excerpts, timestamps, or code locations. Tag ownership, access, reproduction, distribution, display, permission, fair use, or remedies as appropriate. Avoid a generic “copyright evidence” category.

Sections 102(b) and 106 distinguish excluded subject matter from enumerated exclusive rights. Identify the asserted right and allegedly protected material rather than treating resemblance as the issue itself. The statutory text is not a substitute for governing similarity precedent. See Copyright Act §§ 102 and 106. (copyright.gov)

Record: work/version ID, disputed issue, and what the request is intended to establish or test. For a licensing dispute, identify the alleged use and relevant license period, not merely the artwork title.

3. Identify expected records and search boundaries

For incoming requests, identify likely custodians, repositories, file types, and periods. For outgoing requests, describe expected evidence without assuming it exists. Source-artwork requests may implicate layered files and revision histories; software requests may implicate particular repositories and commits.

Rule 26(b)(1) limits discovery to nonprivileged, relevant, proportional material. Assess proposed searches against those limits and applicable orders; a broad request is not itself an approved collection instruction. See Federal Rules of Civil Procedure, Rule 26(b)(1). (uscourts.gov)

Identify the requested or agreed production form separately from the evidence category. Do not label flattened files deficient solely because native files would be more useful; first compare the request, response, and production requirements.

Record: search-scope reference, responsible reviewer, production-form reference, and unresolved scope questions.

4. Separate the response position from actual withholding

Read each response against its request. Capture accepted scope, objections, promised searches, and withholding. Rule 34(b)(2) requires specific objections and a statement whether responsive materials are withheld on their basis. See Federal Rules of Civil Procedure, Rule 34(b)(2). (uscourts.gov)

Distinguish “no records identified,” “search incomplete,” and “withheld.” For privilege or work product, Rule 26(b)(5)(A) requires express claims and descriptions permitting assessment without revealing protected information. Rule 26(f)(3)(D) addresses planning for compliance timing and method. Check orders rather than assuming a universal log format. See Rule 26(b)(5) and (f)(3)(D). (uscourts.gov)

Record: response pinpoint, objection category, withholding position, and linked privilege issue. Preserve uncertainty when the response does not answer whether excluded repositories contain responsive records.

5. Reconcile commitments with delivered evidence

Compare commitments with the production index and actual files. Check work and date coverage, attachments, native versions, and referenced schedules. A large Bates range does not establish satisfaction of a particular request. Link documents responsive to multiple requests without double-counting their delivery.

For ownership requests, distinguish a creative file from an ownership instrument. Section 202 separates object ownership from copyright ownership; § 204(a) generally requires signed writings for copyright ownership transfers other than by operation of law. Do not apply that requirement indiscriminately to nonexclusive permissions. See Copyright Act §§ 202 and 204. (copyright.gov)

Record: checked Bates ranges or file IDs, version coverage, outstanding commitments, and reconciliation note. Mark unreadable files or missing attachments as specific exceptions rather than rejecting an entire production.

6. Convert gaps into specific follow-up decisions

Describe gaps through comparison: requested scope, stated response, delivered evidence, and remaining uncertainty. Replace “production inadequate” with “license §2 references Schedule B; the schedule is absent from the identified production.”

Unfavorable evidence is not a production deficiency. A missing record may reflect an incomplete search, nonexistence, disputed scope, withholding, or a future tranche; do not select an explanation without support.

Choose a bounded action: clarify search coverage, request an attachment, resolve an objection, reconcile privilege treatment, or seek counsel’s decision about procedural action. Separate a clarification request from an assertion that the opposing party violated an obligation.

Record: gap, supporting citations, requested resolution, owner, and follow-up date. Link later correspondence to the same row so the issue’s history remains reconstructable.

7. Close rows against a defined completion test

Use controlled statuses such as awaiting response, partial production, clarification pending, counsel decision required, and closed. “Produced” describes an event; it should not automatically close the request.

Before closure, reconcile the response, withholding position, commitments, and identified gaps. If counsel accepts a limitation or elects not to pursue a gap, record the decision and scope. Do not describe that decision as proof that all requested records were produced.

Record: completion basis, responsible reviewer, remaining qualification, and assigned supplementation follow-up where appropriate. Reopen the row when later material changes its reconciliation; retain the earlier closure decision and date.

Worked example

Fictional scenario: Larkspur Illustration LLC alleges that Cobalt Trail Outfitters Inc. used three illustrations in printed retail displays beyond a limited web-use license. Larkspur’s counsel tracks outgoing requests for permissions, native campaign assets, and campaign-linked sales records. Every party, document, identifier, date, and fact below is fictional.

Service record SR-01 records August 3, 2026 service. Extension EX-02, verified by counsel, sets September 14 for written responses. Production letter PC-01 promises tranches on September 18 and October 2. At the September 21 review, only the first tranche has arrived; the second is not yet overdue.

The entries change the next discussion from a complaint about volume to three bounded questions. Schedule B may affect permission analysis, but its contents cannot be inferred. The native-file issue warrants a search and production-form inquiry, not an accusation of deletion. Company-wide totals do not isolate campaign sales. Counsel requests clarification now while reserving reconciliation of the promised second tranche until delivery.

Common mistakes

• Combining all works indiscriminately. Create linked subrows when versions or commitments differ; retain the parent request ID.
• Treating an objection as proof of withholding. Record the stated position and seek clarification where it is unclear.
• Demanding natives without checking production terms. Verify the request, response, agreed specifications, and orders before classifying the form as deficient.
• Closing a request when production arrives. Reconcile actual files against scope, commitments, and exceptions first.
• Calling every absent item overdue. Distinguish future tranches, disputed scope, reported nonexistence, and unfulfilled commitments; retain deadline-source history.

Final quality check

• Every operative request has a stable ID, direction, parties, and source link.
• Relevant works, versions, uses, and disputed issues are identified.
• Service, response dates, extensions, and commitments have verified sources.
• Objections, withholding, search limitations, and privilege issues remain distinguishable.
• Production citations were checked against actual files, including attachments and specified formats.
• Gaps distinguish absent evidence from adverse evidence and future commitments.
• Open issues have owners, next actions, and target dates, or express decisions not to pursue them.
• Closed rows state their basis, qualifications, and any assigned supplementation review.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its document review, privilege and confidentiality analysis, evidence analysis, redaction, and production capabilities can support the source review underlying this tracker. Use its litigation preparation capabilities to support examination of response gaps and evidence. The tracker remains the team’s work product; lawyers verify scope, deadlines, withholding, and closure. To discuss this workflow, book a demo.

Frequently asked questions

Should incoming and outgoing requests share one tracker?

They can if direction and parties are explicit. Separate access-controlled records where incoming collection instructions or privileged analysis should not circulate with outgoing deficiency tracking. Preserve stable IDs across records.

How should one request covering hundreds of images be recorded?

Keep a parent row linked to a work-level index. Create subrows for disputed versions, missing attachments, or separate commitments. Record unresolved coverage by work ID rather than duplicating identical procedural details hundreds of times.

What if the response says no responsive documents exist?

Record the statement and pinpoint source. Examine whether it addresses the relevant works, repositories, custodians, and periods. Ask for clarification where necessary; do not reclassify reported nonexistence as withholding without evidence.

Should the tracker decide whether a use was licensed or fair?

No. Link evidence to counsel’s separate assessment. Section 107 identifies purpose and character, nature of the work, amount and substantiality, and market effect; it does not supply a mechanical outcome. Organize requests around those evidentiary questions. See Copyright Act § 107. (copyright.gov)

Sources

• Federal Rules of Civil Procedure: Rules 1, 26, and 34.
• Copyright Act, Chapter 1: §§ 102, 106, and 107.
• Copyright Act, Chapter 2: §§ 202 and 204.

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.