How to prepare a document collection checklist for Antitrust Conduct Disputes

Prepare the checklist by translating the alleged conduct into custodians, repositories, date ranges, and collection instructions. Connect competitor contacts and pricing decisions to transaction data, cost explanations, distribution terms, and implementation records—not just emails containing antitrust terminology. For each source, record its evidentiary purpose, technical boundaries, preservation questions, collection owner, and verification status. The deliverable is a source-level collection plan that counsel can approve, the collection team can execute, and reviewers can use to distinguish missing evidence from material not yet collected.

When to use this workflow

Use this workflow when litigation counsel or an in-house team must scope an initial collection, investigate an evidence gap, or expand collection after identifying additional pricing channels or competitor contacts. It addresses alleged coordination over commercial terms and distribution conduct involving dealer complaints, discount conditions, or termination decisions. For other conduct theories, adapt the source map to the pleaded issues rather than treating pricing records as a complete collection universe.

The procedural baseline is US federal civil litigation. Rule 26(b)(1) limits discovery to nonprivileged matter relevant to claims or defenses and proportional to the case’s needs. This is not a standalone preservation standard. State proceedings, arbitration, agency investigations, and criminal matters require separate analysis.

The checklist organizes collection, not liability findings or production decisions. The steps below are practical recommendations; applicable law, local rules, and case-specific orders control legal obligations.

What you need

Assemble these inputs before assigning collection work:

• Matter scope: operative pleadings, discovery requests, orders, stipulations, products, territories, channels, and alleged conduct periods.
• Decision map: personnel who propose prices, approve discounts, manage rebates, change distribution terms, handle dealer complaints, and attend trade-association events.
• System inventory: email, messaging, CRM, pricing engines, shared drives, rebate databases, contract repositories, and relevant business communications on other devices or accounts.
• Data documentation: identifiers linking quotes to invoices, field definitions, pricing-rule versions, export limits, retention settings, and historical snapshots.
• Existing records: custodian interviews, preservation instructions, collection manifests, inaccessible-source reports, and privilege or confidentiality protocols.

Ask business owners to distinguish formal authority from actual practice. Committee minutes may explain pricing policy, while exception logs show its application to customers. Escalate threatened deletion or account closure immediately rather than waiting for checklist approval.

Use the template

The Antitrust Conduct Disputes — Document collection checklist uses one row per custodian–repository combination with a distinct collection boundary. For shared systems, identify the system owner instead of assigning an artificial individual custodian. You can copy this table into your working document or spreadsheet.

Assign stable IDs such as COL-001. “Basis / citation” identifies the request subpart, interview passage, or document supporting collection. Use document IDs and page references rather than descriptions such as “important pricing evidence.”

“Bounds / format” captures dates, products, channels, accounts, and native-file or relational-field requirements. Link detailed extraction specifications. “Retention / gaps” distinguishes known deletion settings, unavailable history, and unresolved preservation questions.

In “Owner / action,” name the responsible person and target date; link counsel’s scope approval where separate. Use statuses such as identified, approved, collected, verified, or blocked. A successful transfer does not establish complete or usable coverage.

Step by step

1. Translate alleged conduct into collection questions

Start with factual questions: Who approved the surcharge? Were competitor communications private or based on public announcements? Did dealer complaints precede discount restrictions? What records explain independent business reasons?

FTC Price Fixing guidance explains that agreements may be written, verbal, or inferred, while similar price movements may reflect independent market responses. It also addresses discounts, credit, and shipping fees. Parallel pricing alone should not be labeled proof of agreement.

Use those distinctions to identify competing explanations, not to decide liability from the checklist.

Record: a focused issue and evidentiary purpose for each proposed source, including records that could undermine the working theory.

2. Map decision-makers to actual repositories

Interview pricing, sales, finance, distribution, and trade-association personnel. Ask where proposals, exceptions, complaints, and approvals actually occur. Identify relevant shared mailboxes, departed employees, assistants, and system accounts.

For each structured system, identify its administrator and business owner. Distinguish company-held association agendas and notes from records held only by the association. Route questions about third-party access and legal control to counsel; do not assume those records are internally available.

Separate email and chat rows when their retention, access, or extraction methods differ.

Record: custodian or system owner, repository identifier, interview citation, and a person able to explain the records.

3. Set boundaries and expansion triggers

Choose dates covering proposals, contacts, approval, announcement, and implementation. Explain collection periods extending beyond the alleged conduct window. Consider whether shared pricing rules or cross-channel discounts require adjacent product records.

If collection is staged, identify what would trigger expansion. Keep that execution choice separate from counsel’s preservation decisions. Keywords alone may miss pricing rules, approval fields, and transaction tables.

For distribution disputes, pair executed terms with enforcement records. FTC Manufacturer-imposed Requirements guidance describes federal rule-of-reason treatment of vertical resale-price restraints, warns of state-law differences, and distinguishes arrangements implementing competitor coordination. It does not establish that a particular restraint is lawful.

Record: approved boundaries, exclusions, rationale, approval reference, and expansion triggers.

4. Resolve retention and access risks

Ask system owners about current retention settings, substantiated historical changes, account closures, backups, and expiring links. Establish whether exporting data omits prior versions or changes available history. Escalate disappearing messages and business records outside centrally managed systems for counsel’s assessment.

Separate what exists from what might once have existed. “No archive identified” does not mean “no messages exchanged.” Specify whether an access problem concerns permissions, credentials, unavailable software, or absent historical copies. Avoid altering source records while troubleshooting.

Preservation questions should receive prompt legal assessment even if the collection scope remains disputed.

Record: retention facts and their sources, access barriers, preservation questions, escalation owner, and next action date.

5. Specify methods that retain context

Provide instructions for threads, attachments, document families, and metadata needed to understand sequence and participants. For spreadsheets, address formulas, hidden sheets, and linked inputs. For pricing data, specify transaction identifiers, effective dates, discounts, rebates, and available rule-version history.

Request data dictionaries and document extraction filters. Test whether transactions can be connected to proposals or approvals. A current-price PDF cannot substitute for historical rule changes or actual transaction records when those are the collection objective.

Retain logs identifying the source, operator, collection date, method, and exceptions. Document timezone treatment where timing matters.

Record: format requirements, field specifications, attachment handling, extraction method, and manifest reference.

6. Separate collection from privilege and production decisions

Plan restricted handling for potentially protected communications and sensitive pricing information. Retain family relationships so reviewers can examine attachments with covering messages. Route messages involving counsel for contextual assessment rather than automatic privilege designation.

For withheld, otherwise discoverable material, Rule 26(b)(5)(A) requires an express protection claim and descriptions permitting assessment without revealing protected information. The checklist does not replace that assessment.

Likewise, distinguish a scope objection from a technical collection failure. For party production requests, Rule 34(b)(2)(B)–(C) requires specific objection grounds and disclosure of whether responsive materials are withheld because of an objection. Subpoenas require separate analysis.

Record: handling restrictions and links to privilege or response decisions, without unnecessarily exposing protected substance.

7. Verify coverage and assign gaps

Compare manifests with approved accounts, dates, file types, and filters. Sample known messages, attachments, price changes, and transactions. Investigate empty periods and distinguish creation, modification, effective, and export timestamps.

If interviews identify weekly discount reports but none appear, check naming, repository, and retention before closing the row. Document sample-based verification limits. Reconcile total record counts or known transactions where practical, without treating matching totals as proof of substantive completeness.

Record: verifier, checks performed, supporting references, exceptions, and closure decision. Every unresolved row needs a next action and responsible person, not merely “pending.”

Worked example

Fictional scenario: Northmere Components faces a federal civil claim alleging that it coordinated a shipping surcharge with rival Alder Peak Supply. A related allegation concerns Northmere’s response to dealer discount complaints. All parties, documents, dates, and facts below are fictional.

The initial collection contains a surcharge announcement, a trade-association calendar entry, and a dealer complaint. It lacks historical pricing rules and a referenced approval attachment. Counsel prepares these representative entries; separate linked rows cover chat, cost workbooks, and executed dealer agreements.

The checklist changes the immediate decision from reviewing announcement emails to investigating three defined gaps. The meeting entry justifies searching for contacts but does not establish attendance or agreement. The current pricing export cannot explain superseded decisions. The complaint identifies a potential decision sequence, not why a restriction occurred.

Counsel prioritizes retention clarification and historical-data access. Separate collection of contemporaneous cost records tests an independent explanation. The missing approval remains unresolved rather than being replaced with a presumed business rationale.

Common mistakes

• Collecting only competitor communications. Add approvals, cost inputs, forecasts, and implementation data to test competing explanations.
• Treating list prices as transaction prices. Specify discounts, rebates, credits, and shipping charges, with definitions linking them to transactions.
• Combining systems with different limitations. Split rows when ownership, retention, historical coverage, or extraction methods differ.
• Collecting contracts without enforcement records. Add relevant complaints, exceptions, notices, amendments, and termination decisions.
• Closing rows after transfer. Verify coverage, attachments, native usability, and filters; record unresolved exceptions explicitly.

Final quality check

• Each row answers a defined conduct, defense, or scope question.
• Identifiable source owners have confirmed custodians and repositories.
• Collection boundaries and exclusions have recorded rationales and approvals.
• Basis citations resolve to the correct request, document, or interview passage.
• Pricing exports document fields, filters, historical limits, and timezone treatment.
• Retention risks, inaccessible sources, and missing attachments have assigned actions.
• Privilege and confidentiality handling remain distinct from production decisions.
• Verified rows identify checks performed; open issues have owners and next-action dates.

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, and evidence analysis. Counsel can use these capabilities to examine collected records and identify further collection questions. The chronology viewer can support examination of contacts, approvals, and implementation. Keep the checklist as a team work product and retain counsel’s control over scope and verification. To discuss this collection-to-review workflow, book a demo.

Frequently asked questions

Should the checklist use one row per document?

Usually not. Use source-level rows with distinct collection boundaries. Link document manifests and evidence references. Split rows when different extraction methods or retention problems require independent tracking.

Should collection begin with pricing keywords?

Map repositories first. Rebates, pricing rules, and transaction tables may contain relevant evidence without expected terminology. Test search terms against known records and document exclusions and limitations.

What if a competitor-contact thread is missing?

Identify participants, accounts, dates, and references to the thread. Check alternate company-held sources and retention facts. Record search coverage; unsuccessful retrieval does not establish that no contact occurred.

Does verified collection mean production-ready?

No. Verification establishes what was retrieved and its known limits. Responsiveness, privilege, confidentiality, objections, and production requirements remain separate decisions. Link those work products instead of embedding unsupported production conclusions.

Sources

• Federal Rules of Civil Procedure, Rules 26 and 34 — federal discovery scope, protection claims, and party-request objections.
• FTC: Price Fixing — competitor agreements, independent explanations, and price-related terms.
• FTC: Manufacturer-imposed Requirements — distribution restraints and federal/state distinctions.

Scope: General professional workflow guidance as of October 13, 2026, 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.