How to build a document-backed case chronology for Antitrust Conduct Disputes

Build an antitrust conduct chronology by separating competitor communications, internal decisions, public announcements, and actual implementation, then linking each event to pinpoint evidence. Record event dates separately from document dates, preserve competing explanations, and identify what the reviewed record does not establish. The deliverable is a source-linked table that lets counsel test sequence, attribution, and possible causal connections without treating parallel conduct as proof of coordination. Distinguish documented acts, reported accounts, and attorney inferences, and assign each material unresolved issue to a responsible reviewer.

When to use this workflow

Use this workflow when a complaint, investigation, production, or witness account raises timing questions about pricing decisions, competitor contacts, dealer pressure, distribution restrictions, or enforcement against customers. It serves litigation counsel and in-house teams assessing facts, identifying targeted discovery, and preparing witness examinations.

Define the products, channels, actors, and periods at issue. A company-wide business history rarely answers whether a disputed decision preceded a competitor exchange or followed an independently documented cost change. For exclusionary-conduct allegations, the relevant sequence may instead run from adoption of a restriction through enforcement, customer response, and observed commercial consequences.

This guide principally addresses US federal civil litigation. State proceedings, arbitration, agency investigations, and criminal matters require separate procedural analysis. The federal rules cited below have their own applicability limits. Check controlling law and case-specific orders separately; the organizational steps here are recommended work methods, not prescribed legal requirements.

What you need

Start with the pleaded or investigated conduct, factual questions, and a defined source set. Identify:

• Relevant entities, competitors, dealers, products, territories, and pricing or distribution authorities.
• Complete email and messaging threads, attachments, meeting records, calendars, and trade-association materials.
• Pricing proposals, approval histories, cost forecasts, discount exceptions, rebate schedules, and transaction records.
• Distribution contracts, amendments, dealer complaints, enforcement notices, and termination records where relevant.
• Production identifiers, native-file references, metadata, collection boundaries, and missing repositories.
• Witness accounts, transcript citations, confidentiality restrictions, and a restricted location for attorney analysis.

Create a source register recording each document’s identifier, version, family relationship, custodian, and accessible location. Identify the reviewed production cutoff and known exclusions. Missing attachments and unavailable pricing-system records limit the chronology; they do not permit reconstruction of unseen contents.

Use the template

The companion template is Antitrust Conduct Disputes — Case chronology. Copy this table into your working document or spreadsheet. Use one event per row, with linked rows when a communication reports an earlier event or describes a later implementation.

Assign stable identifiers such as AC-001; do not renumber when sorting. Event time / basis records the date, available time and timezone, and whether timing is explicit, inferred, or a supported interval. Preserve unknown timezones as unknown. Document time identifies the source’s date, not automatically the date of the reported conduct.

Actor / relationship distinguishes competitors, suppliers, dealers, and internal decision-makers. Event / type gives a neutral statement and category: contact, proposal, approval, announcement, implementation, or observed outcome.

Source pinpoint resolves to an exact document page, message, transcript lines, or spreadsheet sheet and cells. Status / conflict distinguishes documented conduct, reported accounts, and inference, including contrary evidence. Action / owner records the verification task, responsible reviewer, and disposition. Keep lengthy reasoning and related event IDs in linked notes, not crowded factual descriptions.

Step by step

1. Define the sequence you need to test

Frame factual questions before extracting dates. Did pricing approval precede a competitor meeting? Did dealer complaints precede enforcement? Did an announced restriction reach actual transactions? For alleged exclusion, what happened between implementation and the claimed customer loss?

Define the products and conduct period, including a justified lead-in for proposals and background conditions. In federal civil discovery, Rule 26(b)(1) limits discovery to nonprivileged matter relevant to claims or defenses and proportional to case needs. A useful chronology does not itself justify unlimited collection. See Federal Rule of Civil Procedure 26(b)(1).

Record: Put scope, source cutoff, and sequence questions above the template. Tag each event with the question it addresses in a linked note.

2. Establish source identity and boundaries

Confirm that each identifier retrieves the correct version, not a similarly titled file. Preserve thread order, attachments, and native spreadsheet references. Distinguish contemporaneous records from later recollections. A repeated forwarded message does not create a second occurrence of the underlying event.

For pricing data, identify whether fields represent list price, invoice price, discounts, rebates, freight, or another term. Do not compare a public list-price announcement with net transaction prices without explaining the difference. For restrictions, distinguish the executed agreement from a draft and actual enforcement from contractual permission.

Record: Populate source pinpoints and document times. Assign missing-family, version, and unavailable-data issues before describing the source set as complete.

3. Extract events without collapsing business stages

Separate proposal, approval, customer notice, system activation, and first observed transaction. Distinguish an invitation to a competitor meeting from evidence of attendance or discussion. For distribution conduct, separate the dealer complaint, internal response, enforcement instruction, and resulting customer action.

Capture participants, contact method, and subject only as supported. An internal message reporting a competitor’s statement establishes that the report was made; its accuracy and the underlying conversation require separate assessment. Use neutral verbs such as “proposed,” “reported,” and “approved,” rather than “colluded” or “excluded.”

Record: Create separate IDs for supported stages. Link related events and state when participation, content, authority, or implementation remains unverified.

4. Normalize dates while retaining uncertainty

Sort primarily by event time, not file-modification time. A September memorandum may describe a July discussion. Inspect headers and system metadata before converting timezones, retaining the original timestamp and conversion basis in the source note.

Do not derive an exact date from “after the quarterly meeting.” Use an interval only when the evidence supplies boundaries; otherwise mark the date unresolved. Same-day events with unknown times should not imply an unsupported order. Separate a stated effective date from evidence that a system or employee actually implemented the change.

Record: Enter the timing basis, original timezone, normalized time where appropriate, and explanation for any inference. Flag unresolved ordering in Status / conflict.

5. Test coordinated and independent explanations

Read competitor communications alongside cost inputs, demand forecasts, preexisting plans, and approval records. FTC guidance explains that similar or simultaneous price changes can reflect independent responses to market conditions. Parallel pricing alone should not be labeled proof of agreement; price-related terms also include discounts, credit, and shipping fees. See FTC: Price Fixing.

For distribution disputes, distinguish manufacturer-dealer events from competitor contacts. FTC guidance describes federal rule-of-reason treatment for vertical resale-price restraints and warns that some state laws differ. It also discusses distribution arrangements implementing competitor coordination. Those distinctions warrant accurate relationship labels, not a liability conclusion from chronology alone. See FTC: Manufacturer-imposed Requirements.

Record: Identify competing explanations and supporting or adverse sources with equal precision. Keep legal characterization in separate attorney notes.

6. Resolve contradictions through targeted follow-up

Compare accounts proposition by proposition. A manager’s recollection that a decision was “final” may conflict with a later approval record, but the sources may use that term differently. Determine what authority remained, which price term was settled, and whether implementation was conditional.

Convert gaps into narrow tasks: retrieve the attachment, inspect approval history, identify attendees, or ask what a witness personally observed. Prioritize uncertainty that could change the order of contact and decision. Do not close an issue merely because the preferred explanation seems plausible.

Record: Preserve both accounts, identify the exact conflict, and assign an owner. Close only with a cited resolution or retain an explicit unresolved disposition.

7. Verify the chronology for its intended use

Check material propositions against their sources, including adverse entries and derived observations. Separate factual entries from attorney analysis and review privilege, confidentiality, and protective-order restrictions before sharing. Separation is an access-control measure, not a determination that either version is privileged.

A source-linked chronology is not automatically admissible. Rule 901 requires sufficient evidence that an item is what its proponent claims; authentication does not resolve other admissibility objections. Rule 1006 concerns summaries of voluminous admissible materials inconvenient to examine in court, whether or not introduced, and requires underlying originals or duplicates to be available to other parties. Purely illustrative aids fall under Rule 107. See Federal Rules of Evidence 901, 1006, and 107.

Record: State intended use, verification status, source boundaries, and unresolved authentication or presentation questions in the cover note and affected rows.

Worked example

Fictional scenario: Alderwick Components and Bracken Vale Parts compete in industrial fittings. A customer alleges coordination of delivery surcharges. Counsel reviews fictional Alderwick records concerning a proposed $14 surcharge per shipment. The initial theory places the decision after an April 9, 2026 competitor dinner.

The records show an earlier internal proposal, a later message reporting the dinner, and subsequent approval. No invitation, attendee list, or direct competitor exchange has been located in the reviewed set. An invoice extract covers only two customers and excludes credit adjustments. Every party, document, amount, and event below is fictional.

The pre-dinner proposal supports investigating independent planning, but does not establish that later approval was unaffected by contact. The dinner report warrants follow-up without establishing agreement. The invoice extract should produce separate implementation rows for supported transactions, not expand AC-003 into a universal implementation finding. Counsel’s next inquiries concern proposal development, the dinner account, approval deliberations, and actual net charges.

Common mistakes

• Using email dates as event dates. Preserve the message date and separately date the conduct it reports.
• Combining proposal and implementation. Split stages so a pre-contact draft does not become a pre-contact final decision.
• Tracking only headline prices. Include disputed rebates, freight, credit terms, or discount exceptions and identify the measure used.
• Treating silence as a negative fact. State that no record was located within the reviewed boundaries, not that contact never occurred.
• Discarding inconsistent evidence. Preserve competing accounts and explain their precise disagreement rather than choosing the favorable source.

Final quality check

• Each material event has a stable ID and retrievable pinpoint source.
• Event dates, document dates, timezones, and inferred intervals are distinguishable.
• Contacts, proposals, approvals, announcements, and implementation remain separate where appropriate.
• Pricing observations identify the measure, coverage, adjustments, and calculation basis.
• Reports, documented acts, and attorney inferences are visibly distinct.
• Adverse evidence and competing explanations are included.
• Material gaps have cited resolutions or assigned owners and explicit unresolved status.
• Intended use, version cutoff, source boundaries, and access restrictions are stated.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its document review, chronology, and evidence-analysis capabilities can support this source-based work. Use its chronology capabilities for event-based review and trial preparation capabilities when preparing witnesses from verified events. Counsel retains responsibility for source verification, competing explanations, privilege, and evidentiary use. To discuss this antitrust chronology workflow, book a demo.

Frequently asked questions

Should every document become a chronology entry?

No. Record material events, not an inventory. Several documents may support one event; one document may support several events. Preserve a separate source register and explain material exclusions so the chronology’s boundaries remain clear.

How should an undated competitor conversation appear?

Use an unresolved date or supported interval. Identify the dated reporting source, speaker, and basis of knowledge. Do not position the conversation definitively before approval merely because that order supports a theory.

Can a pricing spreadsheet establish implementation?

It may support observations within its coverage. Determine whether it contains proposed prices, invoices, or net transactions. Check credits, rebates, missing periods, and customer coverage. Preserve formulas and cell references, and record implementation separately from approval.

Should dealer complaints and competitor contacts share one chronology?

Yes, when their sequence bears on the disputed conduct. Keep relationship labels distinct. Link complaints to enforcement or termination records without treating sequence as proof of causation; identify evidence of competitor involvement separately.

Sources

• Federal Rules of Civil Procedure: Rule 26(b)(1), federal civil discovery scope.
• Federal Rules of Evidence: Rules 901, 1006, and 107, authentication and presentation distinctions.
• FTC: Price Fixing: competitor conduct and independent pricing explanations.
• FTC: Manufacturer-imposed Requirements: vertical restraints and jurisdictional distinctions. FTC guidance is not an adjudicated finding about any business.

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.