Product
Litigation
- Early Case Assessment
- Evidence Analysis
- Web Search
- Document Review
- Production Setup
- Connectors (Upcoming)
- Legal Research (Upcoming)
Transactional
- Contract Review
- Contract Intelligence
- Word Add-In
- Web Search (Upcoming)
- Connectors (Upcoming)
- Legal Research (Upcoming)
Solutions
Litigation
- Early Case Assessment
- Investigations & Subpoenas
- Trial Preparation
- Enterprise eDiscovery
- Cloud eDiscovery
Transactional
Who it’s for
Resources
Learn
Customers
Events & CLE
Extract distribution-agreement obligations from the executed document set, separating mandatory performance, restrictions, and discretionary rights. For each item, preserve the operative language and record the actor, product and territory scope, trigger, deadline formula, dependencies, owner, and completion evidence. Verify schedules, amendments, definitions, and notice mechanics before calculating dates. The resulting deliverable is a source-linked obligations register that supplier legal and commercial teams can use to assign work, substantiate completion, and identify questions that prevent reliable implementation.
When to use this workflow
Use this workflow when supplier counsel hands an executed distribution agreement to sales operations, finance, supply planning, or channel management. It also suits a portfolio cleanup where trackers contain dates without the language supporting them.
Keep the task focused on extraction and verification, not renegotiation. Include supplier commitments, distributor performance the supplier must track, and supplier rights requiring timely decisions. Prioritize order acceptance, forecasts, minimum purchases, exclusivity conditions, reporting, price changes, and termination inventory.
This is a US-oriented workflow guide, not advice on a particular agreement. Rights depend on wording, governing law, facts, and deal context. The New York provisions below illustrate state sales law, not nationwide distribution rules. Assign separate review of potentially applicable territorial, franchise, dealer-protection, and industry-specific requirements.
What you need
Start with a controlled executed package. Obtain:
- The signed agreement, signature pages, product and territory schedules, amendments, side letters, and incorporated order terms.
- Definitions of business days, contract years, accepted orders, net purchases, notices, and effective dates.
- Referenced forecast, pricing, sales-target, warranty, returns, and inventory procedures, with applicable versions.
- Trigger evidence, including written order acceptances, invoice receipts, approval records, and termination communications.
- Named business owners and the supplier’s interpretation and escalation checklist.
Assign stable document IDs and preserve originals. Reconcile execution changes where the signed package differs from the approved draft. A missing schedule is a document gap, not evidence that its expected obligations are absent.
Use the template
Use Distribution Agreements — Obligations register as the companion template. You can copy this table into your working document or spreadsheet. It is a user-maintained work product, not a dedicated software module.
| ID / type | Source / text | Actor / scope | Action / deliverable | Trigger / deadline | Dependencies / survival | Owner / proof | Status / question |
|---|---|---|---|---|---|---|---|
Give each independently actionable item an ID. Classify it as an obligation, conditional obligation, restriction, right, or legal-review question. Keep a decision to exercise a right separate from resulting performance.
In Source / text, record document ID, version, section, printed or PDF page, and operative wording. Label the page convention. Include amendment and cross-reference citations where they affect the result. Longer passages may sit in a source sheet keyed to the row ID; preserve access to the complete clause, not merely a document homepage.
Use Actor / scope for the contracting entity and relevant products, territory, channels, and exclusions. Owner / proof identifies the internal coordinator and completion evidence; the coordinator may differ from the contractual actor.
Preserve deadline formulas alongside calculated dates. Use Dependencies / survival for prerequisites, linked row IDs, exceptions, and post-termination treatment. Record uncertainty explicitly and distinguish an unverified extraction from a verified item awaiting performance.
Step by step
1. Establish the operative document set
Index the package and determine which version governs each item. Check amendment effective dates, replaced schedules, and order-of-precedence clauses. A revised product schedule may change reporting coverage without changing the reporting clause.
Verify signature dates separately from the effective date. Where attachments or precedence remain uncertain, extract the available language but flag affected scope and calculations as provisional. Do not silently select the convenient version.
Record: document/version citations and a gap row identifying each missing document, affected obligations, retrieval owner, and next review point.
2. Read by distribution function and follow cross-references
Review supply, order acceptance, forecasts, purchase targets, exclusivity, payment, marketing approvals, product support, compliance, reporting, and termination inventory. Follow definitions and cross-references until each instruction is complete.
Distinguish a nonbinding forecast from a purchase commitment and an order request from an accepted order. Do not infer a requirements contract from a forecast heading. Where New York UCC § 2-306(1) applies, quantity follows actual good-faith output or requirements, subject to its disproportionate-quantity limitation. That requires an applicability assessment, not an invented purchase target. See New York UCC § 2-306(1).
Record: candidate actions, operative clauses, definitions, scope limitations, and specific interpretation questions.
3. Separate duties, restrictions, and options
Classify the legal effect before paraphrasing. “Supplier may repurchase” calls for an election decision, not immediate payment. Exercising the option may activate return, inspection, and payment duties. A distributor shortfall may permit conversion to nonexclusive status without making conversion automatic.
Keep possible legal defaults separate from extracted contract terms. Under New York UCC § 2-306(2), lawful exclusive dealing in goods imposes seller best efforts to supply and buyer best efforts to promote sales unless otherwise agreed; it supplies no numeric target. See the statutory text.
Record: item type, downstream conditional rows, and separately labeled legal-review questions with their authority.
4. Split compound provisions without losing qualifications
Create separate rows where actors, triggers, deadlines, or completion evidence differ. Monthly inventory reports, a supplier inspection option, and credits following approved returns need separate statuses.
Retain qualifications when splitting. A shipment commitment may cover only accepted orders within a forecast band and exclude discontinued products. For exclusivity, retain products, geography, customer classes, reserved accounts, and channels rather than writing only “exclusive distributor.”
For recurring reports, keep the source obligation as a master record and identify each reporting period in linked task records. Otherwise, one completed report can incorrectly close the continuing duty.
Record: one independently verifiable action per row, prerequisite row IDs, exceptions, reporting period where relevant, and survival wording or an assigned survival question.
5. Capture deadline formulas and notice mechanics
Identify the triggering event, counting unit, applicable business-day definition, and prerequisite receipt or approval. Preserve “30 days after receipt of conforming inventory” before calculating a date. Record the relevant trigger evidence and any unresolved counting convention.
For notices, capture permitted method, recipient, address, receipt rule, and delivery proof. The SEC-filed Conor agreement illustrates the dependency: § 19 uses different receipt mechanics for international registered or recorded air mail and telecopy, with a next-Business-Day adjustment. These are agreement-specific terms, not instructions for another distribution contract. See the filed agreement, § 19.
Record: formula, verified event date, calculated deadline if supportable, notice requirements, and calculation reviewer.
6. Assign ownership and completion evidence
Route payment items to finance, accepted-order commitments to supply operations, brand approvals to marketing, and election decisions to legal and the authorized commercial decision-maker. Confirm a named owner rather than merely entering a department.
Define evidence that closes each item: a received report, approval record, dispatch record, delivery acknowledgment, payment confirmation, or inspection acceptance. “Email sent” does not establish contractual receipt without checking the operative provision. Reference evidence in its controlled location.
Record: owner, required proof, evidence location, and performance status—untriggered, triggered, completed, disputed, or blocked. Keep source-verification status distinct.
7. Verify material rows and assign unresolved issues
Have a reviewer compare each material row with the complete passage and referenced documents. Prioritize supply commitments, exclusivity conditions, payment security, renewal, termination, and inventory because omitted qualifications can change the supplier’s decision.
Do not supply a fixed termination notice period where none is established. When applicable, New York UCC § 2-309(2) addresses indefinite-duration successive-performance contracts; subsection (3) requires receipt of reasonable termination notification except upon an agreed event and qualifies agreements dispensing with notice. Neither sets fixed notice days. See New York UCC § 2-309(2)–(3).
Record: reviewer confirmation or the precise unresolved question, responsible lawyer, affected rows, and next review point.
Worked example
Fictional scenario: Alder Instruments supplies laboratory sensors to Beacon Channel Partners under fictional executed agreement DA-01. All parties, documents, clauses, and evidence identifiers below are invented. Schedule B is missing from the review package.
Section 5.2 requires Beacon to provide next-quarter product forecasts ten business days before each quarter begins and states that forecasts are not orders. Section 7.1 requires Alder to dispatch accepted orders within twenty business days after written acceptance, subject to Schedule B exclusions. Section 14.3 permits Alder to elect inventory repurchase within fifteen calendar days after termination; a valid election activates payment thirty calendar days after receipt of conforming returned goods.
The package includes written acceptance AC-07 for order PO-07, but its acceptance date has not been verified. No termination or returned-inventory evidence is supplied. Operations requests a calendar of forecast, dispatch, and repurchase dates.
| ID / type | Source / text | Actor / scope | Action / deliverable | Trigger / deadline | Dependencies / survival | Owner / proof | Status / question |
|---|---|---|---|---|---|---|---|
| O-01 / obligation | DA-01 § 5.2, printed p. 6: “provide next-quarter product forecasts” | Beacon / covered products | Submit quarterly forecast | Ten business days before quarter begins | Forecast is not an order; confirm calendar definition | Channel manager / received forecast | Unverified timing; confirm applicable quarter and calendar |
| O-02 / conditional obligation | DA-01 § 7.1, printed p. 8: “dispatch accepted orders”; AC-07 links PO-07 | Alder / covered accepted orders | Dispatch PO-07 goods | Twenty business days after written acceptance | Schedule B exclusions; attachment missing | Supply lead / dated acceptance and dispatch proof | Blocked; verify acceptance date and product coverage |
| R-03 / right | DA-01 § 14.3, printed p. 17: “may elect an inventory repurchase” | Alder / qualifying inventory | Decide whether to elect | Fifteen calendar days after termination | Valid election activates separate receipt-based payment duty | Legal and finance / termination and election proof | No trigger established; confirm termination status |
These entries change the requested handoff. The channel manager can prepare forecast collection, but the due date needs the applicable calendar. Supply operations must retrieve Schedule B and verify AC-07 before confirming coverage and dispatch timing. Legal should confirm whether termination has occurred; absence of evidence is not proof that the election window remains unopened.
Create a linked conditional payment row from § 14.3, but do not invent an election or inventory-receipt date. The three displayed entries are representative, not the complete register.
Common mistakes
- Tracking only supplier duties. Include distributor reports, purchase commitments, and other performance that triggers supplier decisions.
- Treating headings as operative language. Determine whether a purchase target creates a duty, conditions exclusivity, or activates a remedy.
- Removing scope during normalization. Preserve exclusions, reserved accounts, territorial changes, and order-acceptance conditions.
- Assigning dates without trigger evidence. Retain formulas and explicitly assign verification of acceptance, receipt, or termination.
- Conflating sell-off with buyback. Separate permissions, elections, return conditions, and payment duties. Conor’s negotiated § 15 makes sell-off conditional and subordinate to its repurchase option; it does not establish a universal entitlement. See §§ 15(a)–(c).
Final quality check
- Every material item has an operative document/version and clause/page citation.
- Source wording and cross-references support the action and retained qualifications.
- Product, territory, channel, and customer scope match applicable schedules.
- Duties, restrictions, rights, and legal-default questions remain distinguishable.
- Deadline formulas retain notice mechanics and verified trigger evidence before dates are finalized.
- Recurring duties retain period-specific completion evidence.
- Missing documents and interpretation issues are resolved or assigned, with affected rows visible.
Complete the workflow with DecoverAI
DecoverAI is the Legal Intelligence Platform for litigation and transactions. In its contract review workflow, lawyers can select the represented party in Word and give deal-specific instructions; findings quote clauses, locate text, rank severity, and identify missing language as not present. Tabular review supports work across documents, while due diligence classification can organize the source set and prioritize human review. Lawyers retain responsibility for interpreting and verifying register entries. Book a demo to discuss this supplier-side handoff.
Frequently asked questions
Should the register include distributor obligations?
Yes, where supplier decisions or performance depend on them. Forecasts, inventory reports, insurance evidence, and purchase commitments may require supplier follow-up even though the distributor performs them.
How much source text should each row retain?
Retain enough to substantiate the action and qualifications. Put longer passages in a source sheet keyed to the row ID, preserving exact clause access and amendment references.
What if a schedule or price formula is unavailable?
Mark it missing or redacted, identify affected rows, and assign retrieval or interpretation. Do not substitute an earlier draft or assumed practice without confirming applicability.
Can an unexercised supplier right be marked complete?
Close the decision task only with documented authorization and an accurate exercise, decline, or expiry status. Keep resulting performance duties separate; a decision not to exercise does not itself extinguish a still-open contractual right.
Sources
- New York UCC § 2-306 — Output, Requirements and Exclusive Dealings.
- New York UCC § 2-309 — Absence of Specific Time Provisions; Notice of Termination.
- SEC Exhibit 10.26 — Conor International Distribution Agreement, §§ 15 and 19; negotiated wording, not market-standard evidence.
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.
