How to map distribution restrictions across contracts for Antitrust Conduct Disputes

Map distribution restrictions by comparing operative contract language with evidence of how each restriction was communicated, applied, waived, or enforced. Use one row per materially distinct restriction and effective period, linking agreements, amendments, side letters, and implementation records through pinpoint citations. The resulting comparison identifies who restricted whom, the affected products and channels, applicable exceptions, and incomplete evidence. Keep contractual obligations, observed conduct, and counsel’s analysis separate so the map supports evidence assessment without implying that a clause establishes an antitrust violation.

When to use this workflow

Use this workflow when litigation counsel or an in-house team needs to compare dealer, reseller, franchise, or other distribution agreements in a conduct dispute. Triggers include allegations of restricted online sales, territory allocation, exclusive dealing, resale-price controls, discount conditions, or termination following dealer complaints.

The scope is a defined contract population and disputed period—not a complete antitrust assessment. Start with the products, counterparties, channels, and conduct implicated by the claims or defenses. Include evidence contradicting the asserted restriction as well as evidence supporting it.

This guide principally addresses US federal civil litigation. FTC guidance describes federal rule-of-reason treatment of vertical resale-price restraints, warns that state laws may differ, and identifies distinct concerns when distribution arrangements implement coordination among competitors. Party relationships and relevant jurisdictions therefore belong in the comparison; they do not establish legality from wording alone. See FTC, Manufacturer-imposed Requirements. (ftc.gov)

What you need

Assemble these inputs before comparison:

• Executed agreements, product schedules, incorporated policies, amendments, renewals, side letters, and available assent records.
• A counterparty list showing supplier, distributor, retailer, and competing-sales roles, with disputed relationships flagged.
• Product identifiers, territory definitions, customer categories, approved channels, and relevant contract periods.
• Dealer communications, exception approvals, rebate and transaction records, enforcement notices, and termination materials.
• A source register containing document IDs, production references, version status, custodians, and access restrictions.
• Counsel’s working questions: alleged restrictions, alternative explanations, geographic scope, and unresolved governing-law issues.

Preserve complete document families. A pricing-policy attachment or product schedule may change the meaning of a short clause. Identify missing material rather than treating the main agreement as complete. Record production confidentiality designations and restrict access to counsel’s analysis according to the matter’s protocols.

Use the template

The Antitrust Conduct Disputes — Distribution restriction comparison is a working evidence table. Copy this table into your working document or spreadsheet; no dedicated software module or download is required.

Use one row for each materially distinct restriction, scope, and effective period. Split rows when an amendment changes the obligation or enforcement differs materially across channels. Do not compress an entire dealer agreement into one entry.

“Scope / period” identifies products, territory, customer class, channel, and dates. “Restriction / trigger” captures the obligation and activating condition, such as loss of a rebate after unapproved marketplace sales. “Contract evidence” records document ID, clause, page, and version; “Conduct evidence” records implementation separately, with event dates and pinpoint references.

Use “Exceptions / gaps” for waivers, conflicting sources, unavailable schedules, and uncertain dates. In “Assessment / action,” distinguish the supported proposition from counsel’s inference, then name the reviewer and next task. Stable row IDs let witness questions and follow-up correspondence reference the same issue. Maintain the population definition and source register alongside the table rather than repeating them in every cell.

Step by step

1. Define the comparison population and questions

Write a scope statement identifying the disputed restriction, products, geography, counterparties, and time window. Decide whether comparison requires all dealers or a reasoned subset, such as terminated dealers and retained dealers with comparable terms. Explain exclusions and avoid selecting only agreements supporting the allegation.

For federal civil discovery, relevance alone does not define scope: Rule 26(b)(1) also addresses privilege and proportionality, and discoverability does not require admissibility. Apply that framework when considering additional discovery, not as a mandate to collect every distribution record. See Federal Rules of Civil Procedure, Rule 26(b)(1). (uscourts.gov)

Record: scoped rows, comparison rationale, exclusions, and unresolved population questions in “Assessment / action.”

2. Establish the operative contract chain

Group each agreement with schedules, amendments, side letters, policy versions, and renewal documents. Read effective-date, incorporation, modification, and precedence language together. Distinguish executed amendments from unsigned proposals, and execution dates from the periods when restrictions purportedly operated.

Where documents conflict, preserve the conflict rather than selecting the version most favorable to the case theory. Whether a policy became binding depends on the actual language, governing law, and facts; flag the question for counsel. A later policy notice is not, by itself, proof that an earlier agreement changed.

Record: operative-source citations, effective periods, version status, and missing links. Create separate rows for materially changed terms.

3. Classify restrictions without losing their mechanics

Read each provision for actor, obligation, trigger, consequence, and exception. Compare territorial limits, customer restrictions, channel approvals, exclusivity, pricing language, discount eligibility, and termination rights separately. A rebate condition and an outright prohibition may affect similar conduct but require different descriptions.

Distinguish suggested prices, advertised-price conditions, and obligations addressing actual resale prices. Likewise, record an approval right as an approval right—not proof that approval was always refused. Identify whether a termination provision specifically addresses the restriction or merely supplies a general contractual remedy.

Record: a neutral description in “Restriction / trigger,” supported by clause citations and linked definitions. Cross-reference related rows rather than applying a premature liability label.

4. Map coverage and competitive relationships

Resolve product schedules, territory boundaries, customer categories, channels, duration, and exceptions. A restriction on third-party marketplaces may leave a dealer’s own website untouched. Exclusivity may cover only a named product line rather than every competing product.

Identify each party’s role for the activity at issue. Ask whether the supplier sells directly to the same customers and whether communications involve competing dealers. FTC guidance explains that contractual labels do not resolve concerns about competitor coordination, including arrangements involving businesses operating at multiple distribution levels. See FTC, Manufacturer-imposed Requirements. (ftc.gov)

Record: precise coverage and relationship facts, distinguishing verified facts from questions requiring further evidence. Identify sources supporting direct-sales or competitor relationships rather than inferring them from company names.

5. Compare contractual rights with actual conduct

Link restrictions to communications, approvals, transaction records, rebate adjustments, warnings, or termination decisions. Trace policy announcement through implementation rather than assuming conduct followed the document’s effective date. Look for exceptions, nonenforcement, inconsistent treatment, and alternative commercial explanations.

Separate a dealer complaint, internal recommendation, authorized decision, and completed action. Each supports a different proposition. A termination threat does not establish termination; a rebate ledger may establish a deduction without its reason. Preserve complete threads and attachments so isolated communications do not conceal qualifications.

Record: conduct citations, event dates, contrary evidence, and the precise proposition each source supports. Distinguish document dates from implementation dates and mark unavailable evidence as a gap.

6. Test differences and assign targeted follow-up

Compare similarly situated entries while preserving differences in product, period, channel, and version. Ask whether apparent inconsistency reflects a waiver, negotiated exception, expired provision, or genuinely different enforcement. Review adverse evidence before describing a pattern.

Convert uncertainty into a bounded task: obtain a named attachment, reconcile a particular rebate entry, or identify who approved a specified exception. Assign an owner instead of writing “investigate.” If counting restrictions, state the denominator and distinguish agreements, dealers, and restriction rows; multiple rows for one dealer should not inflate dealer counts.

Record: supported comparisons, competing explanations, missing evidence, and accountable follow-up. Keep broader liability analysis in a separate legal work product linked to the rows.

7. Verify the map for its intended use

Have a second reviewer trace important rows to complete sources, including definitions and attachments. Check that citations establish the stated proposition and selected entries fairly represent the reviewed population. Preserve a dated version and document material corrections.

Maintain separate versions for internal analysis and proposed courtroom use. Rule 1006 addresses summaries of voluminous admissible materials, whether or not introduced, and requires underlying originals or duplicates to be available to other parties. Rule 107 separately addresses illustrative aids. An internal comparison is not automatically admissible. See Federal Rules of Evidence, Rules 1006 and 107. (uscourts.gov)

Record: verification status, unresolved limitations, and intended use in “Assessment / action.”

Worked example

Fictional scenario: Alderwick Tools supplies cordless workshop equipment to Fenmere Supply and Bracken Retail in fictional North State. Counsel is assessing an allegation that Alderwick used distribution restrictions to suppress online discounting during March–June 2025. All parties, documents, provisions, and events below are fictional; no governing-law conclusion is assumed.

Fenmere’s executed agreement requires written approval for third-party marketplace sales. A signed side letter effective March 1 permits one marketplace for specified drill kits. Bracken’s agreement conditions a quarterly rebate on avoiding unapproved marketplaces. A separate policy lists suggested resale prices, but an email warns Bracken about discounting. Counsel lacks the warning’s referenced attachment and records establishing a resulting sanction. The available contracts identify no direct-sales role for Alderwick; that relationship remains unverified.

The comparison changes the next decision. DR-01 rules out describing Fenmere’s restriction as an unqualified marketplace ban. DR-02 identifies a financial consequence but not its cause. DR-03 separates advisory wording from potentially relevant pressure without inventing the missing attachment’s contents. None establishes a uniform practice of enforced price restrictions. Counsel now has targeted evidentiary questions and a separate relationship gap to resolve.

Common mistakes

• Comparing master forms instead of operative agreements. Check execution, amendments, schedules, and side letters before describing shared terms.
• Treating every distribution limit as a pricing restraint. Preserve differences among price, advertising, channel, territory, and rebate provisions; investigate related effects separately.
• Combining different periods in one row. Split entries when amendments, policy changes, or waivers materially alter coverage.
• Equating contractual rights with enforcement. Cite actual decisions or implementation separately and identify missing proof.
• Counting clauses as competitive effects. Clause frequency describes the reviewed documents, not market consequences. Identify additional evidence needed for the proposed inference.

Final quality check

• Each substantive row identifies parties, roles, products, channel or territory, and period.
• Contract citations resolve to the operative version or identify uncertain status.
• Incorporated policies, amendments, and exceptions are checked or marked missing.
• Contract wording, implementation evidence, and counsel’s inferences remain distinct.
• Contrary evidence and material differences accompany the comparisons they qualify.
• Material open issues are resolved or assigned to a named reviewer with a concrete task.
• Population, exclusions, counting method, and intended use are clear.
• A second reviewer has verified consequential propositions against complete sources.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its contract review and tabular review capabilities can support comparison across distribution documents, while litigation evidence analysis can support assessment of related communications and enforcement records. Keep the table as your work product and retain counsel’s judgment over operative language, exceptions, and inferences. To discuss this contract-to-conduct evidence workflow, book a demo.

Frequently asked questions

Should suggested prices appear in the map?

Yes, when relevant, but label them accurately. Record advisory wording separately from pressure, threatened consequences, or sanctions. Later communications may raise questions without establishing a contractual price obligation.

How should we handle missing side letters?

Identify the missing document and evidence suggesting it exists. Specify which scope, exception, or effective-period question depends on it. Qualify affected conclusions until the contract chain is resolved.

Can identical clauses establish identical enforcement?

No. Identical wording supports a textual comparison, not an implementation finding. Examine approvals, warnings, rebates, and termination records for each relevant dealer and period before describing consistent practice.

Can the comparison become a trial exhibit?

Potentially, but assess its intended use separately. Rule 1006 summaries and Rule 107 illustrative aids have different requirements. Review underlying records and applicable evidentiary requirements; removing internal analysis alone does not establish admissibility. See Federal Rules of Evidence. (uscourts.gov)

Sources

• FTC: Manufacturer-imposed Requirements — agency guidance on vertical pricing and competitor coordination, not a finding about this fictional dispute.
• Federal Rules of Civil Procedure — Rule 26(b)(1), federal civil discovery scope.
• Federal Rules of Evidence — Rules 1006 and 107, evidentiary summaries and illustrative aids.

Scope: General professional workflow guidance as of October 13, 2026. Controlling precedent, state law, arbitral requirements, and case-specific orders require separate assessment.

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.