How to create a claims and defenses evidence matrix for Antitrust Conduct Disputes

Build the matrix around the pleaded theories and researched legal elements, not document topics alone. For each disputed proposition, record supporting evidence, adverse evidence, missing proof, source limitations, and a responsible reviewer. In antitrust conduct disputes, distinguish evidence of coordination from parallel commercial behavior and separate distribution-contract wording from actual enforcement and competitive effects. The deliverable is a source-linked working assessment showing what counsel can support, what remains contested, and which targeted evidence task would most improve the analysis.

When to use this workflow

Use this workflow when litigation counsel or an in-house team needs to assess a complaint, evaluate a production, prepare a dispositive-motion record, or identify evidentiary gaps before depositions. It is particularly useful when competitor communications, pricing approvals, transaction data, and dealer complaints suggest competing explanations for the same conduct.

This guide principally addresses US federal civil litigation. Federal Civil Rules govern district-court civil proceedings; do not assume they govern state actions, arbitration, agency investigations, or criminal prosecutions (Federal Rules of Civil Procedure, Rule 1). Confirm the pleaded federal and state theories, controlling precedent, procedural posture, local rules, and case-specific orders before selecting issues. The steps below are workflow recommendations, not additional legal requirements.

What you need

Assemble a defined review set rather than waiting for the entire record:

• Theory materials: operative pleadings, relevant orders, asserted defenses, and counsel’s researched issue list identifying elements, burdens, and applicable restraint analysis.
• Conduct records: complete competitor communications, trade-association materials, pricing approvals, dealer complaints, executed distribution agreements, amendments, and enforcement correspondence.
• Commercial evidence: transaction prices, discounts, rebates, delivery charges, cost inputs, demand forecasts, and explanations of data fields.
• Source controls: document IDs or Bates numbers, spreadsheet versions, transcript citations, collection boundaries, and privilege or confidentiality restrictions.
• Review responsibilities: a lawyer responsible for each theory and reviewers assigned to pricing, distribution, witness, and economic evidence.

Define the products, customers, channels, and periods under review. Missing discount data or an uncollected messaging account should remain a specific limitation. Identify the immediate decision the matrix must support, such as selecting deposition topics or evaluating proof for a motion.

Use the template

Use the Antitrust Conduct Disputes — Claims and defenses matrix below. You can copy this table into your working document or spreadsheet. Create one row for each testable factual proposition under a claim issue or defense; split rows when products, periods, or evidentiary foundations materially differ.

Tie Theory / issue to counsel’s researched issue list, including its authority references. Evidence of agreement should not silently become a finding about causation or damages. Label defense propositions separately, and distinguish a competing factual explanation from an affirmative defense.

In the evidence columns, provide a document ID, pinpoint citation, and short factual description. For spreadsheets, identify the file version, tab, cells, and filters; for testimony, use page and line references. Gap / limit captures missing attachments, uncertain authorship, incomplete populations, and competing interpretations.

Use Assessment for a bounded judgment such as “mixed evidence; approval timing unresolved,” not an unexplained confidence score. Action / owner identifies the next task, responsible reviewer, and completion trigger. Keep review date, version, audience, and scope in the working document’s control information.

Step by step

1. Establish the legal issue map

Start with the operative allegations and defenses. Prepare an authority-linked issue list identifying the applicable analysis, procedural posture, burdens, and unresolved legal questions. Do not import an elements list from a different restraint theory or treat pleading sufficiency as the evidentiary standard for a later motion.

Keep agreement, market power, competitive effects, antitrust injury, causation, and damages distinct where relevant. For distribution disputes, identify whether the allegation concerns a supplier-dealer restraint, competitor coordination, or both. FTC guidance describes federal rule-of-reason treatment of vertical resale-price restraints, warns that some state laws differ, and distinguishes arrangements implementing coordination among competitors. That guidance is not a complete elements test (FTC, Manufacturer-imposed Requirements).

Record: stable row IDs, each theory or defense, and its researched issue-list reference.

2. Convert each issue into factual propositions

Replace labels such as “price fixing” with propositions that evidence can test: who communicated, which pricing term was discussed, who authorized a change, and when implementation occurred. Separate proposed, approved, announced, and realized prices.

FTC guidance explains that price-fixing agreements can be written, verbal, or inferred from conduct, while similar price changes can reflect independent responses to market conditions. Price-related terms include discounts, credit, and shipping fees (FTC, Price Fixing). Accordingly, parallel list-price movement should prompt testing, not an automatic “agreement established” assessment.

For a monopolization or exclusionary-conduct theory, frame separate propositions about the challenged practice, market evidence, alleged exclusion, and asserted business explanation rather than forcing the dispute into a competitor-contact model.

Record: one neutral proposition per row, specifying actors, product, period, and disputed conduct.

3. Attach support and contrary evidence together

Review complete threads, attachments, and surrounding pages before summarizing an excerpt. Place adverse evidence beside support. An email reporting a competitor discussion may support an inference of coordination; an earlier internal proposal or cost forecast may support independent decision-making without conclusively establishing it.

For distribution restraints, compare executed wording with amendments, dealer communications, and enforcement. Permission to discount does not establish whether staff honored that permission. A dealer complaint likewise does not establish the supplier’s response.

Check whether apparent corroboration comes from independent sources or merely repeats the same account. Link related rows rather than copying a favorable excerpt into several issues without explaining its relevance to each.

Record: pinpoint citations, concise source descriptions, and unresolved contradictions in Gap / limit.

4. Separate chronology and data inferences from source facts

Identify the sequence of competitor contact, internal recommendation, authorization, public announcement, and implementation. Preserve uncertain dates rather than ordering events by assumption. Distinguish message timestamps from attachment dates and identify timezone uncertainty where sequencing matters.

For pricing evidence, specify whether a field reflects list, invoice, or net realized price. Retain formulas and note omitted rebates, freight, credits, customers, and periods. Keep an observed price change separate from the inference about its cause.

Do not use a fee total as a substitute for analyzing causation, antitrust injury, or damages. Where economic analysis is needed, identify the question and relevant dataset for the responsible reviewer rather than declaring competitive effects from a simple chart.

Record: source facts in the evidence columns, inference limitations in Gap / limit, and a qualified assessment.

5. Test source usability and restrictions

Identify who can explain each important record, whether its origin is documented, and whether the copy is complete. Federal Evidence Rule 901 requires sufficient evidence to support finding that an item is what its proponent claims; authentication does not independently resolve hearsay or other admissibility objections (Federal Rules of Evidence, Rule 901).

Distinguish contemporaneous records, interview notes, declarations, and deposition testimony. Flag firsthand knowledge, secondhand accounts, and missing foundations. Keep potentially privileged analysis and restricted commercial information within the appropriate review audience. Do not assume that labeling the matrix “work product” resolves protection; refer that question to responsible counsel.

Record: source-usability questions, knowledge limitations, access restrictions, and the lawyer assigned to assess them.

6. Turn missing proof into targeted tasks

Convert “need more evidence” into a bounded task: obtain a specified attachment, identify the pricing approver, reconcile a rebate field, or examine a witness about a dealer instruction. Prioritize gaps that could change a disputed proposition’s assessment, not merely increase document volume.

In federal civil discovery, Rule 26(b)(1) limits discovery to nonprivileged matter relevant to claims or defenses and proportional to case needs; discoverability does not require admissibility (Federal Rules of Civil Procedure, Rule 26). Explain why a proposed request matters and its practical scope without treating every possible lead as a justified demand.

Record: missing proof, proposed source, collection or inquiry boundaries, owner, and review trigger. Keep this matrix focused on evidence priorities rather than turning it into a discovery-response tracker.

7. Reassess and preserve the decision trail

Have the theory owner challenge the strongest and weakest rows. Would the assessment change if adverse evidence were accepted? Are several rows dependent on one source? Is support for conduct being mistaken for proof of injury or loss?

Update assessments when new records arrive, preserving the prior version and explaining material changes. Distinguish “no supporting evidence identified in the reviewed set” from “the event did not occur.” Keep unresolved legal questions separate from collection gaps.

Before using the matrix for a motion or witness preparation, check that its assessments answer the stated decision and do not exceed the reviewed record.

Record: revised assessment, reason for change, remaining action, and review date.

Worked example

Fictional scenario: Counsel represents Larch Quay Components in a purchaser action alleging coordination with competitor Meridian Rivet over industrial-fastener prices and delivery fees. Purchasers also allege that dealer pricing provisions implemented the arrangement. All parties, records, clauses, and events below are fictional.

The initial set contains emails, a distribution agreement, a cost forecast, and an invoice extract. A draft pricing memorandum precedes a reported competitor call, but final approval is absent. The invoice extract covers one channel and omits credits. Counsel records three representative propositions rather than adopting a single narrative of coordinated increases.

The matrix changes the immediate decision. Counsel prioritizes approval timing and call substance rather than treating contact followed by a fee as established agreement. The earlier proposal does not prove independent action because final authorization remains unknown. The dealer row directs review toward enforcement; the loss row prevents gross fees from becoming an unsupported damages assertion. No gap is filled with an assumed document or explanation.

Common mistakes

• One row for the entire scheme. Split contact, decision, implementation, effects, and loss so evidentiary strength is not transferred between issues.
• Parallel prices treated as established coordination. Compare contacts with cost inputs, approval history, demand explanations, and transaction terms.
• Dealer wording treated as actual practice. Link clauses to exceptions, complaints, responses, and termination decisions.
• Duplicates counted as corroboration. Identify forwarded emails and reports derived from the same account before assessing independent support.
• Unreviewed repositories treated as negative evidence. State collection boundaries and assign a targeted task where the missing source could matter.

Final quality check

• Every row maps to a researched claim issue, defense, or competing explanation.
• Material citations resolve to the correct pages, transcript lines, or spreadsheet cells.
• Threads, attachments, and operative versions are checked where they affect meaning.
• Adverse evidence and competing explanations appear beside support.
• Pricing fields, formulas, credits, exclusions, and population limits are explained.
• Legal questions, factual gaps, and usability concerns remain distinguishable.
• Each open issue is resolved or assigned to an owner with a review trigger.
• Assessments do not equate discoverability, authentication, and admissibility.

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 the Chronology Viewer when contact and approval sequencing matters, and trial preparation when converting evidence gaps into witness questions. The matrix remains the team’s work product; legal theories, evidentiary judgments, and contradictions remain counsel’s responsibility. Book a demo to discuss this evidence-analysis workflow.

Frequently asked questions

Should claims and defenses use separate matrices?

A shared matrix with distinct claim and defense rows makes competing explanations easier to compare. Separate versions may suit access restrictions or workstreams. Preserve common row IDs, and distinguish affirmative defenses from factual rebuttals.

How should counsel record missing competitor communications?

Specify reviewed custodians, repositories, and periods. Write “no responsive communication identified in this review set,” not “no communication occurred.” Assess whether a targeted collection or witness inquiry could materially change the row.

Does every row need a liability conclusion?

No. State what the evidence supports and what remains uncertain. Counsel must connect the researched framework with the record; individual source findings should not outrun that analysis or substitute for distinct injury and causation inquiries.

Can the matrix become a trial exhibit?

Not automatically. Separate attorney analysis from a proposed evidentiary summary. Federal Rule 1006 permits 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. A purely illustrative aid falls under Rule 107 and is not itself evidence (Federal Rules of Evidence, Rules 1006 and 107). Assess the intended use separately.

Sources

• Federal Rules of Civil Procedure: Rules 1 and 26, federal civil scope and discovery limits.
• Federal Rules of Evidence: Rules 901, 1006, and 107, authentication, evidentiary summaries, and illustrative aids.
• FTC: Price Fixing: agency guidance distinguishing agreement from independent pricing.
• FTC: Manufacturer-imposed Requirements: agency guidance on distribution restraints and state-law differences.

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.