Antitrust Conduct Disputes

How to organize witness statements and document references for Antitrust Conduct Disputes

Organize antitrust witness statements with a copyable evidence matrix linking source citations, knowledge gaps, conflicting accounts, and counsel’s next steps.

October 18, 2026  ·  10 min read
Book a Demo →

Organize witness evidence around discrete factual propositions, not witness biographies or document folders. For each proposition, identify the statement’s form, the witness’s knowledge basis, the exact source location, corroborating or conflicting records, and the next verification task. In an antitrust conduct dispute, separate competitor contact from internal pricing decisions, public announcements, and actual implementation. The resulting witness evidence matrix should let counsel trace an assertion to its source, assess alternative explanations, and assign unresolved questions without treating an allegation or recollection as established fact.

When to use this workflow

Use this workflow when litigation counsel or an in-house team must reconcile interviews, declarations, deposition testimony, and business records concerning alleged anticompetitive conduct. Triggers include conflicting accounts of a trade-association meeting, testimony about discount approvals, or dealer complaints preceding a distribution restriction.

The scope is witness evidence assessment and preparation—not a complete liability analysis or discovery plan. Start with the pleaded theories and defenses, then identify which witnesses can address the disputed facts.

This guide principally assumes US federal civil litigation. Confirm applicable state, arbitral, agency, or criminal requirements separately, along with controlling precedent and case-specific orders. In federal civil discovery, Rule 26(b)(1) limits discovery to nonprivileged matter relevant to claims or defenses and proportional to case needs; discoverable information need not be admissible. See Federal Rule of Civil Procedure 26(b)(1).

What you need

Gather the operative pleadings, counsel’s researched issue list, relevant orders, and available witness and document records. Prioritize materials addressing the disputed conduct rather than every document mentioning price.

Useful inputs include:

  • Interview notes, signed declarations, deposition transcripts, corrections, and exhibits, identified by version and statement date.
  • Complete competitor-contact threads, trade-association agendas, meeting notes, and attachments.
  • Pricing approvals, cost forecasts, discount exceptions, rebate records, shipping-fee changes, and transaction records.
  • Distribution agreements, amendments, dealer complaints, and termination communications where disputed.
  • A witness roster showing role, employment period, pricing authority, and relevant responsibilities.
  • Stable document IDs, page or line references, collection provenance, and access restrictions.

Keep attorney analysis separate from source testimony. An interview memorandum may contain both a witness account and counsel’s impressions; do not attribute the combined narrative to the witness. Confirm access permissions before circulating extracts or linking restricted materials.

Use the template

Use the Antitrust Conduct Disputes — Witness evidence matrix below. You can copy this table into your working document or spreadsheet. Create one row per witness-proposition relationship; use linked rows when several witnesses address the same event.

Row / issue Witness / role Proposition / event date Statement / pinpoint Knowledge basis Related records Conflict / gap Action / owner / status

Assign stable row IDs so an outline or chronology can reference an entry after sorting. In the statement field, distinguish contemporaneous communications, interview notes, declarations, and testimony. Include exact transcript page-and-line ranges or document IDs and pages—not just filenames.

The knowledge field distinguishes participation, observation, inference, and information attributed to others. Related records should include supporting and adverse evidence, with their significance explained. Use the conflict field for unresolved discrepancies; reference access restrictions through a linked source register. The final field needs a concrete task, responsible reviewer, and disposition.

For larger matters, link the matrix to a source register and witness roster. Store statement dates, source versions, restrictions, and verification history there rather than overcrowding each row. Use consistent identifiers throughout.

Step by step

1. Define the propositions that witnesses can actually address

Convert broad allegations into factual questions: who discussed future discounts, who approved a surcharge, what information was available at approval, and when implementation occurred? Keep alleged agreement separate from price movement and business justification.

FTC guidance explains that price-fixing agreements may be written, verbal, or inferred from conduct, while similar price changes may reflect independent responses to market conditions. Discounts, credit, and shipping fees can be price-related terms. This guidance is not a complete claims-elements test. See the FTC’s Price Fixing guidance.

Record: a neutral proposition and issue ID. Use “whether competitors discussed the proposed fee,” not “collusive meeting,” unless expressly identifying an allegation. For unilateral-conduct claims, select questions about decision authority, exclusions, and business explanations rather than forcing every account into an agreement theory.

2. Identify the speaker, statement form, and authority

Confirm the witness’s role at the event date, not merely their current title. A pricing analyst may explain model inputs without knowing why an executive approved a change. A sales manager may know discount practices but not competitor communications.

Distinguish personal testimony from organizational testimony. For federal organizational depositions, Rule 30(b)(6) requires reasonably particular examination topics, good-faith conferral, and designees who testify about information known or reasonably available to the organization. See Federal Rule of Civil Procedure 30(b)(6).

Record: role, statement type, source version, and knowledge basis. For a designee, link the relevant topic and distinguish direct involvement from information learned during preparation. Do not describe prepared organizational knowledge as personal recollection.

3. Anchor each account to exact source locations

Extract the narrow passage supporting the proposition, preserving qualifications about dates, participants, or certainty. For transcripts, retain enough surrounding questions and answers to preserve meaning. For interview notes, distinguish recorded wording from the note-taker’s summary; use quotation marks only for wording verified against the source.

Link complete message threads and attachments. Separate event date, statement date, and document date in linked source notes. Flag inferred dates and timezone ambiguities instead of selecting a convenient chronology. Preserve original testimony alongside any correction and flag substantive differences for counsel.

Record: a precise citation and stable source reference. If only an excerpt is available, identify missing context and assign retrieval; do not imply that the complete source was reviewed.

4. Match the statement to business records and competing explanations

For pricing disputes, compare the account with approval records, cost inputs, public announcements, and transaction records. Separate proposed list prices from realized prices after rebates or exceptions. For distribution disputes, compare enforcement testimony with the applicable agreement version, dealer communications, and actual decisions.

Classify related evidence as supporting, conflicting, or contextual, with a short explanation. Two witnesses repeating the same manager’s account are not independent firsthand sources. An attendance record supports presence, not necessarily the substance of a conversation. A later explanation should not silently become a contemporaneous reason for the decision.

Record: pinpoint references and the limited proposition each record supports. State when a record establishes timing but not agreement, motive, or implementation.

5. Preserve contradictions and missing knowledge

Keep conflicting accounts in linked rows rather than merging them into one narrative. Distinguish contradiction from differences in scope: one witness may describe national pricing policy while another describes a regional exception.

Design follow-up capable of resolving the discrepancy. Ask who attended, whether an account came from another employee, or which approval version the witness reviewed. Prioritize gaps affecting disputed competitor contact or decision timing over immaterial differences. Keep follow-up questions neutral; show the conflicting sources without supplying a preferred account.

Record: competing citations, uncertainty, and a specific task. Assign an owner and status. If a gap remains unresolved, preserve it in the handoff rather than filling it with an inference or treating missing evidence as proof that an event never occurred.

6. Assess source foundation and handling restrictions

Identify who could explain what each document is, where it came from, and how it was used. Rule 901(a) requires evidence sufficient to support finding that an item is what its proponent claims. Authentication does not independently resolve hearsay, relevance, or other admissibility questions. See Federal Rule of Evidence 901.

Separately assess confidentiality restrictions and potentially protected interview materials before circulation. Route privilege questions to counsel rather than deciding protection from a label or recipient list. Keep sensitive analysis in a restricted linked note.

Record: a possible foundation witness, the unresolved evidentiary question, and applicable handling restrictions. A business participant who explains a pricing decision may differ from the person who can explain the underlying system record.

7. Verify the matrix and prepare a bounded handoff

Have a reviewer reopen sources for material propositions, adverse evidence, and unresolved contradictions. Check that summaries preserve qualifications and distinguish witness statements from inference. Record the verified source version so later corrections do not silently alter the evidentiary trail.

Prepare a witness-specific view containing relevant rows, source references, and open questions. Maintain attorney analysis separately where necessary. The matrix is not automatically admissible evidence: Rule 1006 concerns summaries of voluminous admissible materials inconvenient to examine in court and requires access to underlying originals or duplicates. Purely illustrative aids fall under Rule 107. See Federal Rules of Evidence 1006 and 107.

Record: verification status, reviewer, and assigned questions before handing the matrix to examination counsel.

Worked example

Fictional scenario: Alder Carton and Bracken Packaging face allegations concerning coordinated freight surcharges. Alder proposed a $24-per-delivery surcharge. Sales director Mira Chen remembers discussing rising freight costs with a Bracken employee at an industry meeting. Pricing analyst Owen Vale says Alder’s proposal was already approved. Operations manager Lena Ortiz recalls customer exceptions after launch.

All parties, records, amounts, dates, and accounts below are fictional. The team has interview notes, an attendee list, a pending proposal, and a launch instruction. It lacks complete meeting notes, a final approval record, and customer-level billing extracts. All event dates are in 2025.

Row / issue Witness / role Proposition / event date Statement / pinpoint Knowledge basis Related records Conflict / gap Action / owner / status
W01 / Contact Chen / sales director Freight costs discussed, April 8 INT-01 p. 3; interview summary Participant; uncertain wording DOC-014 p. 1, attendee list Presence supported; conversation content uncorroborated Review full messages with Chen / counsel / open; distinguish costs from future fees
W02 / Approval Vale / pricing analyst Proposal approved before April 8 INT-02 p. 2; interview summary Prepared model; approval account from manager DOC-021 p. 4, April 4 draft marked pending Draft neither proves nor excludes later approval Obtain final approval and interview manager / associate / open
W03 / Implementation Ortiz / operations manager Exceptions followed April 15 launch INT-03 pp. 2–3; interview summary Supervised exception processing DOC-033 p. 2, launch instruction permitting exceptions Instruction permits discretion; actual charges unverified Retrieve billing and exception records / in-house lead / open

The matrix changes the inquiry. Chen’s attendance does not establish what was said. Vale’s account is secondhand, but the April 4 draft does not contradict an approval between April 4 and April 8. Ortiz’s account directs review toward actual transactions rather than uniform application of the announced fee. Counsel prioritizes communication content, approval timing, and realized charges without treating any missing record as evidence of coordination or independence.

Common mistakes

  • One row per witness: This buries conflicting propositions. Split accounts by event or assertion and retain shared identifiers.
  • Treating an interview summary as testimony: Label the form and note-taker; verify important wording rather than quoting paraphrases.
  • Using announcements as implementation proof: Link billing, rebates, and exceptions separately. Leave actual charges unresolved until supported.
  • Counting repeated accounts as independent corroboration: Trace each account’s origin and identify the original speaker where known.
  • Assuming every pricing contact involves competitors: Identify whether participants were competitors, suppliers, distributors, or customers at the relevant time; preserve overlapping roles where applicable.

Final quality check

  • Every material proposition has a stable row ID and neutral wording.
  • Each citation opens the correct source version at the identified page or lines.
  • Statement form and firsthand, secondhand, or organizational knowledge are distinguishable.
  • Contact, approval, announcement, and implementation dates remain separate.
  • Supporting and adverse records are linked without overstating their significance.
  • Confidentiality, protection, and foundation questions have identified reviewers.
  • Open issues are resolved or expressly assigned; missing records remain identified as missing.

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, chronology, evidence analysis, and deposition preparation. Use these capabilities to support source review while counsel maintains the matrix, verifies references, and evaluates competing explanations. Explore chronology work and trial preparation, or book a demo to discuss organizing witness accounts and document references for your dispute.

Frequently asked questions

Should the matrix include unfavorable witness statements?

Yes. Place adverse accounts beside the relevant proposition and records. Identify what they contradict and what remains unresolved, rather than relegating them to a separate folder.

How should counsel record a witness who cannot remember?

Preserve the precise limit: no memory of attendance differs from remembering attendance but not the discussion. Record any documents later shown to the witness and distinguish subsequent recollection from the initial account.

Can one document support several witnesses’ entries?

Yes. Reuse its stable ID, but explain its significance in each row. An approval email may support notice to one recipient while leaving another witness’s participation or understanding unresolved.

Should every pricing dispute use the same issue categories?

No. Competitor-contact disputes may emphasize private exchanges and independent pricing explanations. Distribution disputes may require dealer complaints, discount conditions, agreement versions, and enforcement decisions. Select factual categories from the pleaded theories, not a predetermined agreement narrative.

Sources

Scope: General professional workflow guidance as of October 13, 2026; matter-specific legal conclusions require separate analysis.

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.

Run this workflow in DecoverAI

Clause-quoted findings, missing-language flags, and tracked changes in your name — with your team deciding every call. Plans from $299 per seat per month, SOC 2 Type II certified.

Book a demo
to learn more.
Book a Demo