How to build a discovery request and response tracker for Commercial Arbitration Matters

Build the tracker around the arbitration’s actual procedural authority, not a federal discovery checklist. Give each request a stable identifier, preserve its exact wording, and connect it to authorization, service evidence, the operative deadline, objections, production commitments, and delivered records. Reconcile each response against the authorized scope and record unresolved differences without assuming missing documents exist. The deliverable is a counsel-controlled register showing what remains outstanding, why it matters, who must act, and the evidence supporting closure or a request for tribunal direction.

When to use this workflow

Use this workflow when preparing a document-exchange proposal, implementing a preliminary-hearing order, serving authorized requests, or assessing whether production fulfills an opponent’s commitments. Outside counsel can coordinate reviewers through the tracker; in-house teams can use incoming-request entries to assign collections across business units.

This guide uses US commercial arbitration, with AAA domestic commercial rules as a bounded example. Establish the agreement, applicable arbitration law, rules edition, procedural track, and tribunal orders first. AAA R-1 permits written procedural variations, subject to arbitrator consent after appointment; its default edition depends on satisfaction of administrative filing requirements. Do not simply select the newest edition. AAA Commercial Rules, R-1.

Federal Rule 26(b)(1) governs relevance, privilege, and proportionality in federal civil discovery; it does not independently establish arbitration disclosure scope. State-court procedures likewise should not be imported without identifying their applicable authority. Federal Rules of Civil Procedure, Rules 1 and 26(b)(1).

What you need

Assemble these inputs before populating deadlines:

• Procedural authority: signed arbitration clause, amendments, applicable rules edition, preliminary-hearing order, later directions, and exchange protocols.
• Requests and communications: versioned request sets, transmission evidence, responses, objections, narrowing correspondence, and production commitments.
• Collection information: custodians, systems, date ranges, contract versions, invoices, change orders, accounting exports, messages, and known collection gaps.
• Production records: cover letters, indexes, Bates ranges or stable document IDs, native-file references, confidentiality designations, and withholding descriptions.
• Responsibility map: responsible counsel, collection contacts, reviewers, escalation owner, and the separately maintained matter calendar.

Retain source documents separately. The tracker should point to evidence, not become the only place where an agreement, response, or production record survives. Establish access permissions before including links to restricted material.

Use the template

The Commercial Arbitration Matters — Discovery response tracker is a working template, not a prescribed tribunal form. Copy this table into your working document or spreadsheet.

Use one row per request, with linked subrows when categories have different commitments. “Direction” identifies incoming or outgoing requests. Preserve exact wording in the cell or link to a fixed served version and paragraph citation, including incorporated definitions.

“Authority / status” separates proposed requests from authorized ones. “Service / due” includes transmission evidence and deadline authority. “Response / commitment” distinguishes objections from promises to produce. “Production / gap” identifies delivered records and unresolved coverage. “Next action / owner” includes an internal target date; “Closure / basis” identifies the approving reviewer, date, and reason.

For repeated deliveries, maintain a linked production register using the same request IDs. Spreadsheet row numbers are not reliable identifiers after sorting. Keep historical events without obscuring the current scope or deadline.

Step by step

1. Establish the authorized exchange framework

Read the arbitration clause alongside the operative orders. Identify permitted requests, limits, sequencing, production formats, search parameters, and the dispute procedure. Flag conflicts for counsel rather than silently choosing one source.

AAA R-23 addresses arbitrator-directed reliance-document exchanges, reasonable document requests, electronic formats, and search parameters. It does not create an automatic entitlement to federal-style discovery. AAA Commercial Rules, R-23.

Record the controlling document and pinpoint citation in Authority / status. If authority remains unresolved, enter “proposed—authority unresolved,” not “overdue.” Separate party document requests from proposed nonparty demands, which require their own authority assessment.

2. Register each request without losing its wording

Assign identifiers such as OUT-001 and IN-001. Capture the issuing party, served version, wording, definitions, and incorporated limitations. Split invoices and related messages into linked subrows if their production commitments differ.

Add an internal annotation connecting the request to a disputed commercial issue: change-order approval, invoice credits, termination notice, or lost revenue. Keep that explanation separate from the request itself.

Record the fixed source in Request / cite. Preserve later narrowing as a dated event linked to its correspondence or order. Never replace served wording with a reviewer’s summary.

3. Verify service and the operative deadline

Locate the transmission record and confirm recipients, attachments, version, and date. Identify whether the deadline arises from an order, an agreed schedule, or another applicable source. Do not import a familiar federal response period.

Separate external deadlines from earlier collection and review targets. If an extension is requested but unconfirmed, retain the existing deadline and mark the replacement pending. Verify any applicable calculation convention rather than assuming calendar days, business days, or a particular time zone.

Enter service evidence and deadline authority in Service / due. Have the responsible lawyer reconcile the calculation with the matter calendar. Retain superseded dates in the history, clearly marked as nonoperative.

4. Separate objections, commitments, and protection issues

Read each response category separately. Record disputed scope, promised searches, production commitments, and ambiguities. A promise to produce responsive records does not establish which custodians, systems, or periods will be searched.

Treat confidentiality separately from privilege. AAA R-35 requires consideration of applicable privilege principles. Federal Rule 26(b)(5)(A) addresses disclosure of protection claims in federal court, not a universal arbitration log format. Determine the governing privilege law and arbitration directions. AAA R-35; Federal Rule 26(b)(5)(A).

Enter commitments in Response / commitment. Assign unclear scope, withholding descriptions, and redaction explanations to an owner. For incoming requests, distinguish the response actually served from an unapproved internal draft. Keep sensitive legal analysis in a restricted linked record.

5. Reconcile production against the commitment

Match deliveries to request IDs through cover letters, indexes, and document content. Record identifiers, native-file references, attachments, and delivery dates. A document may answer several requests; cross-reference it without counting those links as separate deliveries.

Test coverage against committed custodians, systems, categories, and periods. Check accounting-export fields and project filters. For messages, examine whether referenced attachments and relevant document families are available. For incoming requests, reconcile approved commitments with records actually transmitted, not merely reviewed.

Enter observed omissions in Production / gap. Distinguish “not located in this production” from “does not exist.” A small production or empty search result does not establish the latter.

6. Turn deficiencies into specific follow-up

Describe each deficiency through its request wording, operative limitation, response commitment, delivered evidence, and unresolved difference. Ask a focused question rather than demanding compliance generally.

For example, seek confirmation that an identified finance mailbox was searched before asserting that its messages were withheld. Link agreed narrowing and tribunal rulings to affected request IDs. Preserve the earlier scope alongside the operative revision.

Record the action, responsible lawyer, and internal target in Next action / owner. For incoming requests, this might be a supplemental collection or corrected delivery. Follow the matter’s dispute procedure; the tracker does not itself authorize a submission or additional discovery.

7. Close only the obligation actually resolved

Distinguish awaiting response, partial production, clarification pending, tribunal decision pending, production complete, and closed by narrowing. Avoid an unexplained “done” marker.

Verify that commitments, known deficiencies, and applicable withholding descriptions have been addressed or expressly reserved. A decision not to pursue a gap is not proof of complete production. Closure also does not resolve the evidentiary meaning of produced records.

Enter the reviewer, date, supporting evidence, and reservations in Closure / basis. Produce an open-items view showing each remaining decision, owner, and next action. Reopen the row if later evidence undermines its recorded closure basis.

Worked example

Fictional scenario: Alder Quay Components LLC claims Briar Signal Systems Inc. failed to pay $640,000 for equipment modifications. Briar disputes approval and asserts credits. All parties, amounts, documents, personnel, and procedural terms below are invented.

Assume Procedural Order 2 authorizes Set A requests and sets September 18, 2026, for responses and initial production. Paragraph 8 requires written identification of disputes before tribunal referral. Paragraph 9 incorporates a withholding-description protocol. T-01 records service of Set A on September 4. Counsel reviews the following entries on October 13, 2026:

OUT-001 supports a search-scope question, not a conclusion that approval emails exist or were improperly withheld. The initial deadline’s passage does not alone establish breach of a rolling-production commitment; counsel must inspect R-01 and later correspondence.

OUT-002 closes because V-02 records the completed filter and period checks. Whether the credits are justified remains a merits issue. Unlike a pending verification task, retaining the completed check does not contradict closure.

OUT-003 identifies a concrete protocol gap without deciding privilege. Counsel should request missing roles, then assess the claim under applicable law. No source establishes those roles yet, and the tracker should not invent them.

Common mistakes

• Treating proposals as obligations. Record authorization before labeling a request overdue or noncompliant.
• Replacing wording with summaries. Preserve the served version and definitions; keep summaries separate.
• Equating delivery with completion. Check each commitment, including native records and attachments.
• Importing federal deadlines or log practices. Identify the arbitration’s actual procedural source.
• Overwriting extensions or narrowing. Retain history while clearly displaying operative terms.
• Sharing internal strategy with status records. Separate restricted analysis and review every external extract.

Final quality check

• Each request has a stable ID, direction, and verified wording source.
• Authority citations identify operative documents and the applicable rules edition.
• Service evidence matches recipients, attachments, and request version.
• External deadlines have verified sources and calendar reconciliation.
• Production references resolve to accessible, correctly identified records.
• Gaps separate observed omissions from unsupported assumptions.
• Open issues have owners and next actions; closures have completed checks or express reservations.
• Counsel has approved external extracts, including confidentiality and privilege handling.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its document review, privilege and confidentiality analysis, evidence analysis, and tabular review capabilities can support examination of requests, responses, correspondence, and produced records. The tracker remains your team’s work product; lawyers retain responsibility for authority, deadlines, deficiencies, and closure. Explore litigation preparation capabilities or book a demo to discuss review of the documents underlying your arbitration tracker.

Frequently asked questions

Should incoming and outgoing requests share a tracker?

Yes, if direction is explicit and views are separated. Incoming entries track approved responses, collections, review, and delivery. Outgoing entries track commitments, reconciliation, and deficiencies. Different ID prefixes reduce confusion.

How should rolling productions be recorded?

Use a linked delivery register with transmission date, identifiers, stated coverage, and request IDs. Keep each request open until its commitment is verified. Record supplemental-production dates separately from the initial deadline.

Can a request close when no documents are found?

Counsel should assess the representation, reported search scope, and applicable directions first. Record accepted limitations and any reservation. Closure reflects the disposition of the obligation, not an independent finding that documents never existed.

Should deposition requests use this table?

Cross-reference them, but separately record authorization, scope, and scheduling. AAA L-3(f) permits arbitrator-ordered depositions in exceptional cases upon good cause within the large, complex track; it does not authorize depositions in every commercial arbitration. AAA Commercial Rules, L-3(f).

Sources

• AAA Commercial Arbitration Rules: R-1, R-23, R-35, and L-3(f); reviewed compilation states September 1, 2022 effectiveness.
• Federal Rules of Civil Procedure: Rules 1 and 26(b), used only as federal-court comparators.

Scope: General professional workflow guidance using the supplied research cutoff of October 13, 2026. Actual obligations depend on governing instruments, law, and tribunal directions.

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.