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

Build the tracker around individual requests, not production batches. Give each request a stable identifier, connect it to a pleaded trademark issue, and record its verified response deadline, objections, withheld categories, production evidence, and unresolved gaps. Separate service of a response from delivery of production and delivery from counsel’s adequacy determination. The resulting deliverable is a request-level control sheet that identifies missing or unexplained packaging versions, customer communications, sales records, and other evidence, with a documented follow-up, owner, and status.

When to use this workflow

Use this workflow when counsel serves or receives discovery in a trademark infringement action, particularly where rolling productions span multiple marks, products, territories, or sales channels. It supports outside counsel managing responses and in-house teams coordinating marketing, sales, customer service, and record custodians.

The core workflow covers party document requests in US federal district court. Keep interrogatories, admissions, subpoenas, and deposition topics identifiable as separate instruments; their requirements are not interchangeable. Check local rules, standing orders, stipulations, and case-specific orders. Do not automatically apply federal district-court procedure to state court, TTAB proceedings, or arbitration. The Federal Rules of Civil Procedure supply the federal procedural framework discussed here.

Map requests to actual claims rather than resemblance alone. Section 1114(1)(a) addresses specified unauthorized commercial uses of registered marks likely to cause confusion, mistake, or deception. Section 1125(a)(1)(A) also addresses affiliation, origin, sponsorship, and approval confusion without making federal registration a textual prerequisite.

What you need

Collect the served requests, definitions, attachments, service records, responses, amendments, extension correspondence, production letters, and governing orders. Preserve earlier versions.

Also assemble:

• Issue boundaries: pleaded claims and defenses, disputed marks and variants, products, territories, channels, and requested periods.
• Evidence inventories: packaging, website captures, marketplace listings, campaigns, sales records, customer contacts, and relevant assignment or licensing records.
• Collection information: custodians, repositories, retention settings, missing accounts, search limitations, and access constraints involving distributors or licensees.
• Review records: production indexes, Bates ranges or stable document IDs, confidentiality designations, privilege decisions, and logging arrangements.

Assign a lawyer to decide scope, privilege, adequacy, and escalation. Administrative maintenance can be delegated; those decisions should not disappear into status updates.

Use the template

Use the Trademark Infringement Matters — Discovery response tracker below. You can copy this table into your working document or spreadsheet. It is a user-maintained work product, not a dedicated software module.

Use identifiers distinguishing direction, party, set, and number, such as OUT-DEF-RFP1-07. Keep the identifier across amended responses and supplemental productions. Add linked subrows for materially different products or periods without losing the parent request.

Service / due basis holds service details, the verified deadline, its source, and extensions. Distinguish procedural deadlines from internal targets. Response / withholding cites the response page and captures objections, search limits, and withholding positions.

Evidence / range identifies production ranges and representative pinpoints, not merely “received.” Gap / uncertainty distinguishes demonstrated shortfalls from unanswered questions. Action / owner / date identifies the next task and target. Keep lengthy conferral and version histories in linked notes keyed to the request ID.

Step by step

1. Register each request and verify its timing

Create one row per request. Identify the requesting and responding parties, direction, instrument, and exact request citation. Link the served text, including definitions and instructions, rather than relying on a shortened description.

Verify timing against the rule, service facts, orders, and documented stipulations. Rule 34(b)(2) addresses response and production timing; do not assume every request has the same deadline. See Federal Rule of Civil Procedure 34.

Record: service evidence, verified response deadline, extension source, separately stated production commitments, and any timing question assigned to counsel.

2. Translate the request into trademark-specific scope

Identify the subject, period, products, mark variants, geography, channels, and likely custodians. Advertising requests may involve package designs, marketplace listings, and regional campaigns with different repositories and coverage.

Connect each request to a pleaded issue: adoption, disputed use, customer perceptions, overlapping channels, ownership, or damages. Do not substitute a universal confusion-factor checklist for controlling authority.

Federal discovery must concern nonprivileged material relevant to claims or defenses and proportional to case needs; discoverability does not require admissibility. See Rule 26(b)(1).

Record: issue mapping, scope boundaries, and any disputed relevance or proportionality question. Treat these boundaries as review criteria, not unilateral changes to the served request.

3. Parse responses without treating objections as outcomes

Separate the substantive response, objections, search limitations, promised production, and withheld categories. A promise to produce does not establish delivery or search completion.

Rule 34(b)(2) requires specific objections and a statement whether responsive materials are withheld on an objection. See Rule 34(b)(2)(B)–(C). Identify exactly where the response supplies—or leaves unclear—those points.

For requests received by your client, substantiate proposed scope statements with the collection team. For responses received from another party, flag ambiguities without assuming responsive documents exist.

Record: response version and pinpoint, withholding position, production commitment, and unresolved ambiguity. Keep counsel’s assessment separate from the responding party’s statement.

4. Reconcile production against requested categories

Map each delivery to the requests it addresses. A document can support several rows while retaining one stable identity. Compare production with the products, periods, channels, and other boundaries recorded earlier.

For packaging, distinguish drafts, approved artwork, and evidence of actual use. For marketplace captures, retain URL, capture date, product identifier, context, and seller identity. For sales data, identify covered products, periods, territories, channel fields, and unexplained definitions. Test whether files are readable and attachments or linked records are available.

Volume does not establish completeness. An absent category may reflect nonexistence, disputed scope, an unsearched source, or withholding.

Record: delivery date, ranges, representative pinpoints, covered categories, usability problems, and the evidentiary basis for each suspected gap.

5. Track privilege and confidentiality separately

Do not equate a confidentiality designation with privilege. Link affected requests to restricted review or logging records without copying protected substance into broadly shared tracker notes.

Rule 26(b)(5)(A) requires express privilege or protection claims and descriptions permitting assessment without revealing protected information. Rule 26(f)(3)(D) addresses compliance timing and method. See Rule 26.

For mark-clearance materials, distinguish asserted protection from ordinary business records; a title alone does not resolve the issue. Use the applicable protocol rather than assuming one universal log format.

Record: affected categories, linked review records, redaction questions, protocol, and decision owner. Keep confidentiality restrictions visible separately.

6. Turn gaps into focused follow-up

Pair the request citation with the response commitment and production evidence. Replace “missing advertising” with a precise question: “No prelaunch marketplace listings identified; response does not explain whether that repository was searched.”

Distinguish clarification, additional search, corrected data, supplemental production, and legal resolution. Capture actual conferral commitments rather than treating discussion as agreement. Before escalation, check applicable conferral and motion requirements against the case’s rules and orders.

Prioritize gaps affecting disputed use, customer incidents, channel overlap, or the ability to interpret sales data. Do not give every clerical discrepancy equal weight.

Record: proposed action, owner, target date, conferral reference, commitment, and remaining disagreement.

7. Close rows only after an adequacy decision

Use distinct statuses: response pending, production pending, under review, deficiency open, and closed with basis. Keep current resolution separate from later supplementation review.

Confirm that promised deliveries arrived, mapped categories were reviewed, and open questions were answered or expressly accepted by responsible counsel. A “closed with limitation” entry must identify the limitation and who accepted it.

Retain earlier responses and production references so later evidence can reopen the same row without erasing history. Schedule human review where continuing commitments require it; the spreadsheet itself does not monitor compliance.

Record: closure basis, reviewer, review date, residual limitation, and assigned follow-up.

Worked example

Fictional scenario: Larkglass Outfitters sues Fenwick Trail Goods over LARKGLEN-branded insulated bottles. Counsel tracks requests for packaging and listings, customer communications, and channel-specific sales. All parties, documents, request descriptions, identifiers, and dates below are fictional.

The requests were served August 3, 2026. Written stipulation EXT-01 establishes September 18, 2026 as the response deadline. Fenwick timely responds and produces final carton artwork, a customer-service summary, and annual sales totals. Counsel reviews production on September 24. The available record does not establish which repositories were searched or whether additional records exist.

The entries change counsel’s next decision. Artwork prompts actual-use and repository questions rather than a launch-date conclusion. The customer summary requires source and duplication checks before incident counting. Annual sales totals prompt a field-availability inquiry, not an accusation that channel records were withheld. The internal targets are not procedural deadlines or agreed production dates.

Common mistakes

• One row per production: Unanswered requests disappear. Maintain request-level rows and map deliveries back to them.
• Artwork dates treated as launch dates: Record what the document establishes and identify missing actual-use evidence.
• All customer reports counted together: Distinguish affiliation or source confusion from inquiries and duplicates; retain source references.
• Every absent category labeled withheld: Separate established shortfalls from uncertainty about existence, search, scope, or withholding.
• Closure upon response service: Track service, delivery, substantive review, and remaining commitments separately.

Final quality check

• Every row links to the served request and correct response version.
• Deadlines and extensions have verified sources; internal targets are labeled.
• Marks, products, periods, territories, and channels remain distinguishable.
• Objections, withholding, confidentiality, and privilege remain separate.
• Production ranges resolve correctly and support claimed coverage.
• Gaps distinguish evidence from inference and do not invent missing records.
• Open issues have owners and targets; closures identify reviewer and basis.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its litigation capabilities include document review, privilege and confidentiality analysis, evidence analysis, redaction, and production. Use those capabilities to examine evidence underlying tracker entries while counsel retains responsibility for deadlines, objections, adequacy, and follow-up. Document-linked gaps can inform later deposition preparation. To discuss this discovery-review workflow, book a demo.

Frequently asked questions

Should incoming and outgoing requests share a tracker?

They can, with distinct identifiers and assignments. Requests received by your client require collection and response work; requests served on another party require response reconciliation and adequacy review. Shared statuses must preserve that distinction.

How should rolling productions be recorded?

Retain each delivery date, range, covered category, and remaining commitment in linked history. Do not overwrite earlier ranges or close the request merely because another batch arrived.

Can the tracker cover organizational deposition topics?

Use separate topic identifiers and fields for conferral, designation, and preparation. Rule 30(b)(6) addresses particularized topics, organizational designation, good-faith conferral, and reasonably available organizational information. See Rule 30(b)(6). A document-production status cannot establish topic completion.

What if no responsive documents are found?

Record the actual response and available search information. “None identified in production” does not mean “none exist.” Assign unresolved search questions and have counsel determine whether clarification or additional work is appropriate.

Sources

• 15 U.S.C. § 1114: registered-mark infringement provision.
• 15 U.S.C. § 1125: affiliation, origin, sponsorship, and approval confusion provision.
• Federal Rules of Civil Procedure: Rules 26, 30, and 34.

Scope: General professional workflow guidance using an October 13, 2026 research cutoff, not advice for a particular 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.