Product
Litigation
- Early Case Assessment
- Evidence Analysis
- Web Search
- Document Review
- Production Setup
- Connectors (Upcoming)
- Legal Research (Upcoming)
Transactional
- Contract Review
- Contract Intelligence
- Word Add-In
- Web Search (Upcoming)
- Connectors (Upcoming)
- Legal Research (Upcoming)
Solutions
Litigation
- Early Case Assessment
- Investigations & Subpoenas
- Trial Preparation
- Enterprise eDiscovery
- Cloud eDiscovery
Transactional
Who it’s for
Resources
Learn
Customers
Events & CLE
Organize arbitration submissions around the directions they answer, not just filing dates. Build a register linking each operative instruction to an accountable lawyer, verified deadline, submission version, supporting evidence, and transmission record. Preserve earlier orders and submitted documents without presenting superseded requirements as current. The resulting submissions tracker should show what remains due, reproduce what the tribunal received, and distinguish a party’s request from an actual direction. It should also expose evidentiary gaps before they become unsupported assertions in a brief.
When to use this workflow
Use this workflow when procedural orders begin coordinating document exchanges, witness statements, expert reports, or merits submissions. It is particularly useful when successive directions change dates or authorize supplemental evidence on limited issues.
Outside counsel and in-house teams can use the register to coordinate procedural compliance and evidence review. Its scope is submissions and their supporting record, not the entire arbitration lifecycle.
This guide uses US practice and AAA domestic commercial arbitration as a bounded example. Identify the agreement, seat, applicable arbitration law, rules edition, procedural track, and tribunal directions. AAA R-1 permits written procedural variations, requiring arbitrator consent after appointment; its default edition provision turns on satisfaction of administrative filing requirements, not simply the contract date. See AAA Commercial Arbitration Rules, R-1.
What you need
Collect these controlled inputs:
- Authority documents: arbitration agreement, amendments, procedural agreements, applicable rules, and track designation.
- Tribunal record: orders, written directions, hearing records, clarification correspondence, and pending requests for changes.
- Submission record: pleadings, briefs, witness statements, expert reports, exhibit lists, and original and corrected submitted versions.
- Evidence references: stable document IDs, Bates numbers, source passages, witness paragraphs, calculation cells, and adverse records.
- Transmission evidence: delivery records, service confirmations, recipient lists, and administrator or tribunal acknowledgments.
- Responsibility information: drafting owner, evidence reviewer, approving counsel, and internal review targets.
Keep internal strategy and draft annotations separate from tribunal-facing material. Track confidentiality restrictions independently of privilege assessments, and control access to the internal register accordingly.
Use the template
The companion template is Commercial Arbitration Matters — Arbitration submissions tracker. You can copy this table into your working document or spreadsheet. Use one row per independently actionable direction or submission component.
| Item / status | Direction / citation | Required act / destination | Due / basis | Owner | Evidence / gaps | Submitted version / delivery | Next action / reason |
|---|---|---|---|---|---|---|---|
Assign stable row IDs. Direction / citation identifies the source document and paragraph or page. Required act / destination distinguishes tribunal submissions from party exchanges and records scope limitations. Due / basis captures the operative deadline, stated time zone, and calculation source; label internal targets separately.
Use Evidence / gaps for source pinpoints, contrary records, and unresolved foundation questions. Link a separate evidence matrix where necessary. Submitted version / delivery identifies the actual transmitted package, not the latest draft. Next action / reason records the decision needed and why. Put reviewer assignments and supporting links in the relevant cells rather than expanding the main table indefinitely.
Step by step
1. Establish the procedural source map
Read the agreement and procedural record together. Identify the rules edition, track, variations, and unresolved conflicts. Do not resolve competing instructions through an assumed universal hierarchy.
Separate party proposals, administrative messages, and tribunal directions. An extension request is not a granted extension. AAA P-2(b) requires a written order memorializing preliminary-hearing decisions and agreements. Compare that order with hearing notes and flag discrepancies for clarification. See AAA Commercial Arbitration Rules, P-2(b).
Record: source IDs and pinpoints, applicable procedure, unresolved authority questions, and the lawyer responsible for clarification.
2. Break each direction into actionable entries
An order may require a brief, damages schedule, witness statement, and joint exhibit list on different terms. Separate rows where the owner, deadline, evidentiary dependency, or completion test differs. Link related row IDs.
Capture limitations: permitted issues, response scope, stated page limits, and whether additional evidence requires permission. Distinguish exchanges from submissions. AAA R-23 gives the arbitrator authority to direct document exchanges; it does not create an automatic entitlement to federal-style discovery. See AAA Commercial Arbitration Rules, R-23.
Record: required act, destination, authorized scope, dependencies, and status: proposed, operative, completed, or superseded.
3. Verify deadlines and assign accountability
Transcribe fixed dates exactly. For event-based deadlines, preserve the triggering record and calculation under the applicable directions and procedures. Do not silently supply missing time zones, holiday treatment, or service assumptions. Escalate ambiguity while retaining visibility of the existing requirement.
Assign one accountable owner, even where several lawyers contribute. Set internal evidence-review and approval dates separately. When a direction changes a deadline, preserve the earlier requirement as superseded, link its replacement, and exclude the obsolete date from the active work list.
Record: operative deadline and basis, internal targets, owner, reviewer, and unresolved calculation questions.
4. Map submissions to supporting and adverse evidence
For each material proposition, identify the source passage, witness foundation, and contrary evidence. A produced document does not necessarily support the sentence citing it. Check attachments, referenced schedules, and whether the account is contemporaneous or retrospective.
Connect witness paragraphs to documents and identify knowledge gaps. AAA R-35 does not require conformity to legal evidence rules but requires consideration of applicable privilege principles. Under R-36, a statement witness’s failure to attend after the specified notice may lead the arbitrator to disregard the statement or make another appropriate order. See AAA Commercial Arbitration Rules, R-35–R-36.
Record: supporting and adverse pinpoints, witness-attendance dependencies, uncertainty, and responsibility for each gap.
5. Validate schedules, summaries, and exhibit references
Reproduce material calculations from identified records. Reconcile invoices, credits, currencies, exclusions, and totals. Separate advocacy explanations from source-derived figures. Verify that each exhibit citation identifies the version in the submission package.
Correct arithmetic alone does not establish admissibility. As a federal-court comparator, Evidence Rule 1006 concerns summaries of voluminous admissible materials that cannot conveniently be examined in court and requires access to underlying originals or duplicates. The underlying materials need not themselves have been introduced into evidence. That rule does not automatically govern arbitration; check the tribunal’s directions and proposed foundation. See Federal Rules of Evidence, Rule 1006.
Record: source cells or passages, reconciliation results, exhibit versions, and unresolved foundation or access arrangements.
6. Preserve the submitted package and transmission record
Before transmission, approving counsel should compare the package against every applicable row. Check scope, recipients, required delivery method, attachments, exhibit identifiers, redactions, and confidentiality markings. Preserve the approved package separately from editable drafts.
After transmission, record what was sent, to whom, when, and by which method. Keep delivery evidence distinct from acknowledgment; do not treat either as establishing every completion requirement. If an attachment is missing or incorrect, preserve the original transmission and assign counsel to determine the correction procedure rather than silently replacing files.
Record: package IDs and contents, transmission evidence, acknowledgment if received, and corrective action.
7. Reconcile later directions and close verified items
Compare each new direction with the register. A supplemental submission may narrow an issue, invite a response, or require a revised exhibit. Link it to earlier entries so reviewers can reconstruct the sequence without treating superseded requirements as operative.
Close a row only against its defined completion test. “Draft approved,” “sent,” and “acknowledged” describe different events. A completed submission may still leave an evidence question or response obligation; retain that work in an open linked row.
Record: completion evidence, final status, replacement references, and separately assigned follow-up.
Worked example
Fictional scenario: Harborline Packaging LLC claims $840,000 from Cedar Vale Foods Inc. for supply invoices. Harborline’s counsel maintains the tracker below. Fictional Procedural Order 3, paragraph 8, requires a revised damages schedule and supporting records by November 6, 2026, at 5 p.m. Eastern. Paragraph 9 permits Cedar Vale to respond only to the revised calculation by November 13. Later Direction D-04 replaces that response date with November 18 at the same time, leaving the scope unchanged.
The team finds an omitted $60,000 credit memorandum. The accounts manager’s draft statement also references an uncollected workbook. These are representative entries; the response row tracks an opponent’s submission for monitoring, not drafting responsibility.
| Item / status | Direction / citation | Required act / destination | Due / basis | Owner | Evidence / gaps | Submitted version / delivery | Next action / reason |
|---|---|---|---|---|---|---|---|
| S-12 / Open | PO3 ¶8 | Schedule and support to tribunal and parties | Nov. 6, 2026, 5 p.m. Eastern; ¶8 | Harborline damages counsel | INV-041–056; CM-007 p.1: $60,000 credit; allocation unresolved | Not submitted | Reconcile credit; claim may be overstated |
| S-13 / Open | Internal verification supporting S-12; draft WS-04 ¶14 | Verify workbook basis; internal task | Nov. 3 internal target; S-12 controls submission | Harborline evidence counsel | WS-04 cites WB-02; workbook not collected | Draft only; not submitted | Obtain source or revise explanation; calculation unverified |
| S-14 / Monitor | D-04 ¶2 replaces PO3 ¶9 date | Monitor Cedar Vale response; calculation only | Nov. 18, 2026, 5 p.m. Eastern | Harborline response-monitoring counsel | Depends on S-12; response not yet available | None received | Review on receipt; retain Nov. 13 as superseded |
The credit changes the approval decision, not automatically the claimed amount. If fully allocable to the disputed invoices, with no other adjustment, the total would be $780,000. Counsel must verify allocation first.
The missing workbook prevents a claim that the statement’s calculation has been reproduced. Obtain it or revise the explanation; do not invent missing support. The response entry also shows why an opponent’s deadline needs an internal monitoring owner without suggesting that Harborline must prepare Cedar Vale’s submission.
Common mistakes
- Treating an extension request as effective. Keep the operative date visible and track the request separately until a verified change applies.
- Using one row for an entire order. Separate requirements so a completed brief does not hide an unfinished exhibit list.
- Citing filenames alone. Add stable IDs, pinpoints, and version references; confirm the cited passage supports the proposition.
- Replacing submitted documents with corrected drafts. Preserve both versions and the transmission history; obtain counsel’s correction decision.
- Importing court procedures automatically. Identify the actual arbitration requirement before applying court discovery or evidence concepts.
- Closing submissions with unassigned gaps. Give every unresolved calculation, witness, or source issue an owner and next action.
Final quality check
- Every operative requirement has a checked source and pinpoint.
- Requests, internal tasks, and tribunal directions are distinguishable.
- External deadlines have verified bases; internal targets are labeled.
- Superseded requirements remain reconstructable but not operative.
- Material assertions and calculations trace to reviewed sources, including adverse records.
- Submitted versions, exhibit lists, recipients, and transmission records reconcile.
- Privilege, confidentiality, redaction, and witness dependencies have been reviewed.
- Open issues are resolved or assigned, and counsel approval precedes transmission.
Complete the workflow with DecoverAI
DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its document review, evidence analysis, privilege and confidentiality analysis, chronology, and redaction capabilities can support review behind the tracker. Use its chronology capabilities when organizing procedural events and explore trial preparation for related evidence work. The tracker remains counsel’s work product; lawyers verify directions, deadlines, and submission decisions. Book a demo to discuss this workflow.
Frequently asked questions
Should every tribunal email receive its own row?
Preserve relevant correspondence, but create an actionable row when it directs work, changes an obligation, or resolves a question. Link informational messages to affected entries. Assess substance rather than assuming every email is either a formal order or merely administrative.
How should an oral direction be recorded?
Record the hearing date, speaker, available transcript or note, and uncertainty. Compare it with written confirmation. Assign discrepancies for prompt clarification; do not assume the absence of a written order permits ignoring the direction.
Can party exchanges and tribunal submissions share a tracker?
Yes, if destination, scope, and completion tests remain explicit. An exchanged document does not automatically become a tribunal exhibit. Link the exchange to the later submission without merging their distinct obligations.
What if an evidence gap remains near the deadline?
Escalate before approval. Counsel should decide whether to narrow the assertion, explain the limitation, seek procedural relief, or take another permitted step. Record the decision and basis without treating an unresolved relief request as changing the deadline.
Sources
- AAA Commercial Arbitration Rules, R-1, R-23, R-35–R-36, and P-2(b).
- Federal Rules of Evidence, Rule 1006; federal-court comparator only.
This is general professional workflow guidance, not advice for a particular matter; the governing agreement, applicable law, rules, and directions control.
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.
