How to organize communications about pricing decisions for Antitrust Conduct Disputes

Organize pricing communications around discrete decisions, not isolated emails or keyword hits. Preserve complete conversations, identify each participant’s commercial role, and separate competitor contacts from internal proposals, approvals, announcements, and implementation. Connect each communication to the relevant product, price component, supporting business records, and actual transaction data. The resulting pricing communications matrix should let counsel trace competing explanations to pinpoint sources, distinguish established facts from inference, and assign targeted follow-up without treating similar prices or ambiguous language as proof of coordination.

When to use this workflow

Use this workflow when litigation counsel or an in-house team must assess whether communications support or undermine alleged pricing coordination. Triggers include a complaint identifying synchronized increases, discovery revealing competitor contacts, or messages referring ambiguously to an industry understanding.

The scope is evidence analysis: organizing communications and identifying missing links, not determining liability. FTC guidance explains that agreements can be written, verbal, or inferred from conduct, while similar price changes can reflect independent market responses. Distinguish evidence of contact, agreement, and implementation. The guidance is not a complete claims-elements test. See FTC: Price Fixing.

The orientation is US federal civil litigation. Check controlling substantive law, local rules, and case-specific orders; do not carry federal civil procedures into state proceedings, arbitration, agency investigations, or criminal matters without separate analysis.

What you need

Start with the allegations, relevant products and territories, disputed period, and counsel’s issue list. Assemble:

• Complete email and messaging threads, attachments, calendar entries, meeting notes, and participant information.
• Pricing proposals, approval records, price lists, discount exceptions, rebates, credit terms, and freight-charge communications.
• Cost inputs, demand forecasts, customer negotiations, and contemporaneous explanations for changes.
• Transaction records distinguishing announced prices from actual charged prices, with field definitions.
• Custodian and repository information, document IDs or Bates numbers, native references, confidentiality restrictions, and privilege-review status.

Identify unreviewed repositories before interpreting silence. An unavailable messaging account does not establish that no conversation occurred.

Keep proposed collection expansion tied to disputed issues. Federal Rule 26(b)(1) limits discovery to nonprivileged material relevant to claims or defenses and proportional to case needs; discoverability does not require admissibility. See the Federal Rules of Civil Procedure, Rule 26.

Use the template

Antitrust Conduct Disputes — Pricing communications matrix

Copy this table into your working document or spreadsheet. Use one row per analytically distinct communication event. Link events concerning the same pricing decision through a shared decision ID.

“Time / stage” records the event date, timezone where relevant, and whether the event concerns contact, proposal, approval, announcement, or implementation. Distinguish a later document’s creation date from the event it describes.

“Actors / relationship” identifies employer and role at the relevant time. “Source / family” supplies document IDs, pinpoint citations, and thread or attachment links. Keep neutral summaries in “Fact / context” and interpretation in “Gap / competing reading.”

“Linked records” identifies cost models, approval versions, announcements, and transaction extracts, including spreadsheet tabs and cells. Assign an owner and status to each material gap. This is a user-created analysis tool, not automatically an exhibit or a protected document merely because counsel uses it.

Step by step

1. Define the pricing decision and review boundaries

Identify what allegedly changed: list price, net price, discounts, rebates, credit, or shipping charges. FTC guidance recognizes that price fixing can concern discounts, credit, and shipping fees, not just headline prices. See FTC: Price Fixing.

Define the product, customer class, geography, and decision window. Separate recurring reviews from exceptional increases when approval paths differ. Frame a neutral question, such as whether a proposed freight charge preceded or followed identified competitor information.

Record: the decision ID, price component, and review boundaries in the matrix or accompanying instructions.

2. Preserve conversational context and source identity

Review the full conversation, not only the search hit. Connect attachments to the version circulated; distinguish a draft spreadsheet from an approved schedule. Retain available message sequence, recipients, forwarding history, and native references.

Identify duplicates without losing meaningful differences, such as additional recipients or attachments. Mark truncated exports explicitly. Do not reconstruct missing text from a later reply as though it were the original. For chat exports, check whether quoted replies or linked files sit outside the collected conversation.

Record: pinpoint citations, family links, completeness status, and uncertainty about timing or versions. Assign retrieval of missing context.

3. Classify participants and the information channel

Determine whether the communication was internal, a private competitor exchange, customer-supplied intelligence, public information, or a supplier-distributor discussion. Record the classification’s basis. A forwarded competitor price sheet may have arrived through a customer rather than direct competitor contact.

Do not treat every supplier-dealer exchange as horizontal coordination. FTC guidance describes federal rule-of-reason treatment for vertical resale-price restraints, notes state-law differences, and distinguishes arrangements implementing coordination among competitors. Use these distinctions to route legal questions, not resolve them. See FTC: Manufacturer-imposed Requirements.

Record: contemporaneous roles, the apparent information route, and unresolved relationships requiring counsel’s assessment.

4. Separate contact, proposal, approval, and implementation

Build each decision’s sequence without collapsing stages. A salesperson’s suggestion is not necessarily authorized; an announcement is not necessarily the price paid.

Compare event dates, document dates, effective dates, and external contacts. Preserve original timestamps and explain timezone normalization. If an approval predates competitor contact, confirm that it concerns the same product, price component, and version. Distinguish the first documented contact from an assertion that it was the first contact ever.

Record: separate rows for material stages, linked by decision ID. Mark inferred dates and contradictions rather than selecting a convenient chronology.

5. Test competing explanations against business records

Link communications to contemporaneous costs, forecasts, approvals, and customer negotiations. Test both alleged coordination and asserted independent decision-making. A later explanation should not substitute silently for contemporaneous support. Separate evidence that a cost increased from evidence that the decision-maker relied on that increase.

Compare proposed terms with transactions consistently. Check units, currencies, customer classes, effective periods, rebates, and freight. Retain formulas and exclusions; an unexplained average can hide differing outcomes. A plausible cost rationale should not end the search for contrary communications.

Record: supporting and adverse evidence, the proposition each source supports, calculation references, and gaps preventing an assessment.

6. Review privilege, confidentiality, and evidentiary foundations

Route mixed legal/business communications and outside-recipient issues for privilege review. Do not classify an entire thread solely because counsel appears among recipients. Keep sensitive legal analysis separate from neutral source descriptions where appropriate.

For withheld, otherwise discoverable material, federal Rule 26(b)(5)(A) requires an express protection claim and a description permitting assessment without revealing protected information. The matrix does not replace the applicable logging process. Assess any claimed protection for the matrix separately, including Rule 26(b)(3) where applicable. See the Federal Rules of Civil Procedure.

Identify authentication witnesses or system evidence. Rule 901 requires sufficient evidence supporting a finding that an item is what its proponent claims; authentication does not independently resolve hearsay or other admissibility issues. See the Federal Rules of Evidence, Rule 901.

Record: access restrictions, foundation questions, and responsible reviewers without unnecessarily reproducing protected advice.

7. Convert gaps into targeted follow-up

Review the matrix decision by decision. Identify what additional source could change the assessment: an attachment, approval history, customer message, invoice adjustment, or witness explanation. Prioritize significance to the disputed inference rather than document volume.

Distinguish “not located,” “repository not reviewed,” and “source unavailable.” Each requires a different response. Keep assessments provisional where material sources remain missing.

Record: a concrete action, owner, and status. Prepare a short decision-level synthesis identifying the established sequence, competing explanations, and unresolved questions through matrix references.

Worked example

Fictional scenario: Larch Basin Packaging faces allegations that it coordinated a freight surcharge with competitor Cedar Vale Containers. The review concerns a proposed $24-per-pallet charge for industrial carton line C. All parties, documents, amounts, dates, and facts below are fictional.

Collected records include an internal proposal and attached model, an account manager’s message about Cedar Vale, a customer notice, and selected invoices. An initial review groups these as one implemented increase. Counsel separates the stages and tests the information route. Example dates are in 2025; the original message timezone is America/Chicago.

The matrix changes the assessment without deciding liability. It identifies a proposal preceding the reported competitor information, not a verified independent approval. It distinguishes a customer-mediated report from established direct contact. The notice also cannot establish uniform implementation: sampled invoices show different charges.

Carrier notices, the customer attachment, approval records, and adjustment data remain missing. Counsel can now target those gaps rather than describe the proposal as an approved decision or the notice as proof of prices paid. A fuller implementation review would receive separate event rows under D-07.

Common mistakes

• Treating a keyword hit as the conversation. Read the complete thread and attachments before interpreting references to alignment or industry pricing.
• Equating announcements with net prices. Reconcile rebates, waivers, freight, and customer transactions before describing implementation.
• Assuming the information route. Identify public materials, customers, distributors, or direct contact; flag uncertain provenance.
• Treating a cost model as proof of causation. Verify inputs, timing, decision-maker reliance, and contrary communications.
• Mixing evidence and advocacy. Separate sourced facts from interpretation so another reviewer can test each explanation.

Final quality check

• Every material proposition has a pinpoint citation checked against its source.
• Threads, attachments, and versions are linked; missing family members are identified.
• Participant roles and information routes are supported or expressly unresolved.
• Proposals, approvals, announcements, and implementation remain distinguishable.
• Transaction comparisons state components, units, periods, exclusions, and formulas.
• Supporting and adverse evidence receive equivalent treatment, including conflicting dates.
• Privilege, confidentiality, and foundation questions have reviewers; material open issues are resolved or assigned.

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 this user-created matrix to structure lawyer-directed analysis alongside chronology review and focused deposition preparation. Counsel retains responsibility for source verification, competing inferences, and legal assessment. To discuss this pricing-communications workflow, book a demo.

Frequently asked questions

Should every message receive its own row?

No. Separate rows when the event, stage, participants, or significance changes. A continuous exchange can share a row if its sequence remains clear and material statements have pinpoint references.

How should we organize public competitor prices?

Record the publication, date, captured version, and evidence of receipt by relevant personnel. Keep public intelligence separate from private exchanges. Public availability alone does not establish a decision-maker’s knowledge.

What if there is no approval record?

Mark approval as unverified. Identify likely repositories, custodians, and alternative evidence of authority or timing. Implementation may inform the sequence but should not be relabeled as a contemporaneous approval.

Can the completed matrix become a trial summary?

Not automatically. 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. Illustrative aids are addressed separately by Rule 107. Prepare a separate presentation version and assess its intended use under the Federal Rules of Evidence.

Sources

• FTC: Price Fixing — competitor agreements and independent pricing responses.
• FTC: Manufacturer-imposed Requirements — vertical pricing and distribution distinctions.
• Federal Rules of Civil Procedure — Rules 26(b)(1), 26(b)(3), and 26(b)(5)(A).
• Federal Rules of Evidence — Rules 901, 1006, and 107.

Scope: General professional workflow guidance, not advice for a particular matter.

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.