How to build a discovery request and response tracker for Antitrust Conduct Disputes

Build the tracker around each served request and subpart, then connect the operative response, objections, withholding position, production references, deficiencies, and next action. For an antitrust conduct dispute, identify the pricing decision, competitor contact, distribution practice, or economic dataset each request addresses. The deliverable is a source-linked control document that distinguishes completed discovery from partial production, disputed scope, and missing evidence. It should show both what remains unresolved and who must resolve it, without treating document volume as proof that a request has been satisfied.

When to use this workflow

Use this workflow when litigation counsel or an in-house team coordinates document responses, evaluates an opponent’s production, or prepares a focused discovery conference. It is particularly useful when pricing records, competitor communications, dealer complaints, and transaction data sit with different custodians and reviewers.

This guide principally addresses party document requests in US federal civil litigation. Third-party subpoenas, state proceedings, arbitration, and agency investigations require separate procedural analysis; do not apply the party-request framework to them without checking the governing requirements. Federal Rules of Civil Procedure, Rules 1, 34, and 45. (uscourts.gov)

Start with the pleaded conduct and defenses. Rule 26(b)(1) limits discovery to nonprivileged matter relevant to claims or defenses and proportional to case needs; discoverability does not require admissibility. Record why the category matters and which boundaries remain disputed. Rule 26(b)(1). (uscourts.gov)

What you need

Assemble the materials establishing the obligation and the evidence sought:

• Served requests, service records, operative responses, amendments, and scope correspondence.
• Discovery orders, local requirements, stipulations, and verified deadline calculations.
• Pleadings and an issue list separating alleged coordination, independent pricing, distribution restrictions, competitive effects, and damages where relevant.
• Custodian and repository maps covering sales, pricing, finance, distribution, trade associations, messaging, and pricing systems.
• Production manifests, stable document identifiers, native-file references, data dictionaries, privilege-log references, and known collection gaps.
• Protective-order restrictions and production or privilege protocols.

For pricing datasets, identify the period, products, geography, customer coverage, discount treatment, and version. A file labeled “sales data” may not answer a request for net transaction prices. Check definitions and coverage rather than relying on filenames. Assign tracker access consistently with the sensitivity of customer-level pricing and attorney analysis.

Use the template

The companion template is Antitrust Conduct Disputes — Discovery response tracker. Copy this table into your working document or spreadsheet. Use one row per request and formal subpart. Where a request has no subparts, link a coverage checklist rather than inventing served numbering.

Use a stable ID identifying direction, responding party, set, and subpart, such as OUT-R-S1-R07(a). “Served source” identifies the operative document and page; retain that ID when responses change.

“Dates / basis” distinguishes the written-response deadline, production dates, and internal checkpoints, each with its source. “Response / withholding” links the response paragraph and separates objections, production commitments, and withholding status. Do not convert “unclear” to “none.”

“Production refs” identifies Bates ranges, document IDs, native files, or dataset versions. “Gap / supplement” states missing coverage, uncertainty, and supplementation history. “Owner / action” records responsibility, the next checkpoint, and status. For closed rows, link a dated closure note identifying the reviewer, basis, and qualifications. Use linked records for details that would overwhelm the main table.

Step by step

1. Establish the request universe and date basis

Reconcile every served set against the tracker. Capture parties, direction, service evidence, numbering, subparts, and operative versions. Keep incoming obligations distinguishable from outgoing requests so an opponent’s deficiency cannot appear as your team’s unfulfilled production task.

Have counsel verify dates against governing rules, orders, stipulations, and service facts. Preserve original and modified dates with their supporting sources. Label response deadlines separately from production commitments and team review targets; an internal checkpoint does not alter a legal obligation.

Record: stable IDs, served-document pinpoints, separately labeled dates, and calculation or modification references.

2. Map requests to conduct and boundaries

Identify the factual question: private competitor exchanges, internal pricing approval, discount exceptions, dealer enforcement, or data needed to evaluate pricing effects. Extract products, channels, geography, period, custodians, and repositories from the request and any agreed limitations. Mark disputed boundaries separately.

Do not label simultaneous price changes established coordination. FTC guidance recognizes that similar pricing can reflect independent market responses and that price-related terms extend to discounts, credit, and shipping fees. Use those distinctions to organize coverage, not determine liability. FTC, Price Fixing. (ftc.gov)

Record: the issue, requested and agreed boundaries, disputed limits, and supporting citations.

3. Capture the response and withholding position

Read each response alongside its request. Separate the production commitment, objection grounds, and explanation of withheld material. A promise to produce documents does not necessarily establish coverage of every period or repository.

Rule 34(b)(2)(B)–(C) requires specific objection grounds and disclosure of whether responsive material is withheld because of an objection. It also addresses production timing and objections to part of a request. Capture the actual position; do not infer withholding from silence. Rule 34(b)(2). (uscourts.gov)

Record: response pinpoint, production commitment and timing, objection grounds, and withholding status. Where necessary, enter “unclear—clarification requested” and assign follow-up.

4. Reconcile production to requested coverage

Link each tranche to the requests it appears to address, then test it against step 2’s boundaries. Competitor email may omit attachments or messaging; a pricing export may contain invoice prices but omit rebates or freight adjustments.

Use a linked coverage worksheet for file-level checks. Identify reviewed samples, dataset cells, and exclusions. Separate producing-party mappings from your team’s independent assessment. If one tranche addresses several requests, link it to each row but evaluate coverage separately.

Record: production references, versions, sampled coverage, and unresolved gaps. Keep partial production open even when some responsive material has arrived.

5. Separate privilege issues from collection gaps

Distinguish privilege withholding, objection-based scope limits, inaccessible repositories, uncollected sources, and unexplained absences. Each requires different follow-up. A missing attachment is not automatically privileged, and a log entry does not account for every related business record.

Rule 26(b)(5)(A) requires express protection claims and descriptions permitting assessment without revealing protected information. It prescribes no universal spreadsheet format. Link the applicable log and protocol without placing privileged substance in broadly shared fields. Rule 26(b)(5)(A). (uscourts.gov)

Record: gap category, log or response reference, and lawyer responsible for assessment. Keep confidentiality designations distinct from privilege claims.

6. Convert deficiencies into answerable follow-up

Describe a discrepancy another lawyer can resolve. Replace “pricing production inadequate” with “export lacks rebate fields; confirm whether rebates are maintained separately and covered by the production commitment.”

State the source, missing coverage, proposed clarification or cure, and checkpoint. Distinguish an agreed limitation, unilateral response position, and proposed compromise. Preserve conference outcomes with documentary support rather than overwriting the disagreement. Before escalating, check applicable conference requirements and case-specific discovery procedures.

Record: deficiency, proposed resolution, owner, checkpoint, and any confirmed agreement or unresolved position.

7. Verify closure and preserve supplementation history

Compare the final response position with production and resolved scope. Require a reviewer to explain why coverage satisfies the obligation as resolved, or why a limitation was accepted. Identify whether closure rests on direct review, a responding-party representation, or a documented agreement.

Maintain dated supplementation entries instead of replacing earlier references. Reopen affected rows when later material changes the assessment. Closing a tracking task does not establish that the evidence proves or defeats an antitrust claim.

Record: closure basis, reviewer, verification date, qualifications, and supplementation or reopening references.

Worked example

Fictional scenario: Marlow Components alleges that competing industrial-fastener suppliers coordinated price increases. Counsel tracks outgoing requests to fictional defendant Ridgeway Supply. All parties, documents, dates, identifiers, and facts below are invented.

Ridgeway promises competitor emails and transaction-level pricing records for January–June 2025, but chat coverage remains unclear. Its first tranche contains email, a pricing workbook, and a privilege log. Fictional stipulation STIP-01 establishes September 8, 2026, as the response deadline; conference record CONF-02 separately sets an October 6 production checkpoint for pricing data. Counsel reviews representative records without assuming the tranche completes every request.

The evidence changes the follow-up. Request 4(a) warrants attachment and repository clarification, not an accusation that missing chat proves coordination. Request 9 requires data definitions before net-price coverage can be assessed. Request 12(b) calls for privilege assessment and clarification about nonprivileged approval records, not an indiscriminate demand for logged communications.

No source establishes whether responsive chat exists, whether rebates affected these transactions, or what withheld records contain. The tracker preserves those uncertainties and assigns action rather than supplying missing evidence.

Common mistakes

• Treating Bates volume as completion. Test periods, custodians, repositories, and data fields against the production commitment.
• Combining distinct pricing evidence. Separate competitor contacts, public intelligence, internal approvals, and actual transaction terms.
• Recording objections without withholding status. Capture both or assign clarification expressly.
• Calling every absence a deficiency. Check agreed scope and sequencing before characterizing missing material.
• Overwriting dates or conference outcomes. Preserve the original obligation, modifications, and supplementation history.

Final quality check

• Every request and subpart has a stable row and operative source citation.
• Response deadlines, production commitments, and checkpoints are distinguished and sourced.
• Issue labels follow pleaded conduct without assuming agreement from parallel pricing.
• Response summaries accurately capture objections, commitments, and withholding positions.
• Production links resolve; dataset versions and sampled coverage are identifiable.
• Privilege, confidentiality, scope, collection, and unexplained gaps remain distinct.
• Open issues have owners and next actions; closed rows have dated, qualified closure records.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Document review, privilege and confidentiality analysis, evidence analysis, and tabular review across multiple documents can assist examination of the source materials underlying this tracker. Counsel maintains the working table, verifies citations, and decides scope and sufficiency. Where unresolved requests affect witness examination, connect reviewed evidence to deposition preparation. To discuss this discovery workflow, book a demo.

Frequently asked questions

Should incoming and outgoing requests share a tracker?

They can share a workbook if direction, parties, and IDs are unmistakable. Separate working views prevent an opponent’s deficiency from appearing as your team’s production obligation.

How should one production covering multiple requests be recorded?

Link the same references to each relevant row, but assess coverage separately. A pricing workbook may answer transaction-data questions without supplying internal approvals or competitor communications.

Can a row close when no responsive documents are found?

Counsel can approve internal closure after reviewing the stated position and basis. Identify whether it rests on a party representation, collection review, or agreed scope resolution. Do not describe it as independently verified unless it was.

How much pricing-data detail belongs in the main table?

Include version, coverage, material missing fields, and next action. Link field mappings, sample cells, exclusions, and reconciliation notes separately so the tracker remains readable without concealing limitations.

Sources

• Federal Rules of Civil Procedure, particularly Rules 26 and 34: discovery scope, protection claims, and party production responses.
• FTC, Price Fixing: agency guidance distinguishing coordinated pricing from independent market responses.

Scope: General professional workflow guidance using October 13, 2026, as the research cutoff; controlling authority, local requirements, and case-specific orders require matter-level verification.

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.