How to build a clause extraction table for Reseller Agreements

Build a reseller agreement clause extraction table by identifying the controlling documents, separating operative rights and obligations into source-linked records, and recording conditions, exceptions, and unresolved dependencies alongside the wording. Start with appointment scope and economics, then extract supply, customer, support, liability, and termination provisions. The deliverable is a verified, versioned table showing what the reseller may sell, where and to whom, what it earns or owes, and which answers remain provisional because evidence or interpretation is unresolved.

When to use this workflow

Use this workflow when reseller counsel or an in-house legal team needs a reliable account of an arrangement before negotiation, renewal, acquisition diligence, or comparison across suppliers. It is especially useful when product appendices, discount schedules, partner policies, or end-user terms qualify the master agreement.

The scope is extraction and verification, not a complete negotiation or compliance program. This guide uses a US transactional orientation. Contract rights depend on the language, governing law, facts, and deal context. State franchise, dealer, restrictive-covenant, and choice-of-law questions may require separate analysis. The process recommendations below are working practices, not legal requirements.

What you need

Collect the documents establishing the agreement and its commercial operation:

• The executed master or identified negotiation draft, amendments, signatures, and incorporated schedules.
• Product lists, territory and channel authorizations, reserved accounts, and deal-registration rules.
• Discount tables, rebate plans, purchase commitments, price-change policies, and payment terms.
• Customer licenses, warranties, support allocations, returns policies, and reporting requirements.
• The reseller’s review questions, internal approval thresholds, and commercial and legal decision-makers.

Assign each file a stable document ID and version. Record whether it is signed, proposed, superseded, or supplied only for context. Request missing incorporated materials. Do not substitute a supplier’s current website policy for the applicable version without examining the incorporation and change provisions.

Use the template

The Reseller Agreements — Clause extraction table is a working structure. You can copy this table into your working document or spreadsheet.

Use stable row IDs such as R-001 so references survive sorting. Identify a specific file in “Source / version”; include clause numbers and PDF pages where available.

Separate source wording from interpretation. Use a short exact excerpt and a faithful summary for lengthy provisions. Preserve qualifications such as accepted orders, authorized products, and during the term. Record definitions, exceptions, incorporated documents, and linked row IDs under dependencies.

“Trigger / timing” captures events as well as periods. The final column should distinguish verified text, ambiguity, missing documents, redactions, and provisions not located in the reviewed set. Record an owner and next action. Text verification does not mean legal interpretation or commercial approval is complete.

Step by step

1. Establish the document hierarchy

Read integration, incorporation, amendment, and precedence provisions before extracting commercial terms. Maintain a source register identifying each file’s date, status, and relationship to the master. A later date alone does not establish priority.

Section 20.4 of the SEC-filed Avaya Reseller Agreement generally prioritizes product appendices over product group attachments and those attachments over the agreement, subject to express overrides. That illustrates a document-specific hierarchy, not a universal rule.

Record: a hierarchy row identifying controlling provisions, overrides, and missing attachments. Mark affected conclusions provisional until the relevant text is available.

2. Define the questions and row boundaries

Organize extraction around reseller decisions: authorization to sell, margin entitlement, supply continuity, customer obligations, exposure, and exit rights. Split provisions when actors, triggers, or consequences differ, even within one paragraph.

Monthly reporting and suspension for nonpayment require separate records. Link a discount entitlement to its eligibility definition rather than reproducing that definition inconsistently.

Use a coverage list spanning appointment, territory, exclusivity, reserved accounts, order acceptance, pricing, rebates, returns, warranties, support, audits, indemnities, liability, renewal, termination, and post-termination treatment.

Record: topic rows with stable IDs and linked dependencies. For an expected topic not found, specify the searched documents rather than asserting that no provision exists anywhere in the contractual relationship.

3. Extract appointment and customer boundaries

Capture authorized products, territories, channels, customer classes, affiliates, and subreseller restrictions. Separate the supplier’s reserved right to sell directly from any reseller compensation entitlement. Extract deal-registration protection, renewal eligibility, and customer nonsolicitation separately.

Describe restrictions before evaluating them. The FTC’s manufacturer-imposed requirements guidance distinguishes manufacturer-imposed restrictions from competitor coordination. It describes federal rule-of-reason analysis for vertical minimum resale-price arrangements while noting different treatment under some state and international regimes. The guidance does not resolve a particular customer nonsolicitation covenant’s enforceability.

Do not collapse suggested resale prices, advertised-price conditions, and binding resale-price restrictions into one category.

Record: the restricted actor, conduct, products, customers, geography, and duration. Assign legal escalation separately from confidence that the wording was extracted correctly.

4. Separate each economic entitlement

Create distinct records for purchase discounts, rebates, referral commissions, renewal compensation, and promotional support. Extract eligible transactions, calculation basis, thresholds, exclusions, claim or payment triggers, currency, taxes, returns, and clawbacks where addressed.

Customer origination does not establish a contractual commission entitlement. Sections 3(c)–(d) of the historical Agilent value added reseller agreement exclude compensation for direct end-user purchases and condition certain add-on or upgrade discounts on an original reseller sale and continuing support. These are examples of wording, not customary entitlements.

Test a representative transaction against the extracted conditions. If a tier could apply marginally or retroactively, retain the uncertainty and request clarification instead of selecting the more favorable calculation.

Record: the economic rule, eligibility dependencies, unresolved inputs, and finance owner. Label any illustrative calculation as a calculation, not extracted contract text.

5. Capture operational obligations and risk allocation

Extract each obligation as actor–action–trigger–timing. Include training, certification, customer reporting, license flow-downs, first-line support, audit cooperation, payment, and supplier performance dependencies.

For supply continuity, distinguish forecasts from binding commitments and accepted orders from unaccepted requests. Capture discontinuation rights, allocation provisions, and order-cancellation consequences where present.

Read warranties, indemnities, and liability provisions together while keeping their effects distinct. Link customer commitments to supplier remedies and identify gaps, such as reseller support promises without corresponding supplier escalation obligations. Preserve cap exclusions, claim categories, and qualifications rather than summarizing everything as “liability capped.”

Record: responsible party, action, trigger, period, linked remedy, and internal owner. Identify internal completion-evidence recommendations as recommendations, not contractual duties.

6. Extract termination consequences without inference

Separate termination rights, notice requirements, cure opportunities, and consequences. Review accepted orders, unpaid invoices, inventory returns, sell-off rights, customer licenses, renewal revenue, support, and continuing restrictions individually.

The Avaya filing illustrates the distinction: sections 17.1–17.3 redact several notice and cure periods; section 17.4 accelerates invoices; section 7.7 preserves properly granted existing end-user licenses. License survival alone does not establish continuing support, renewal compensation, or inventory sell-off rights.

Record: each consequence and dependency. Mark redacted periods unavailable. Where timing is visible, retain the delivery method, recipient, receipt rule, and relevant definitions needed for later deadline analysis; do not calculate from assumed periods.

7. Verify and release the table

Check rows against original documents, including schedules, footnotes, definitions, exceptions, and cross-references. Search related terms across the file set for qualifications elsewhere. Visually inspect scanned text and economic tables where extraction quality is uncertain.

For portfolio comparisons, align products, territories, channels, and contract layers before comparing results. Repeated wording in the reviewed files is not market-standard evidence. Separate source certainty from business significance: a clear exclusion may matter more than an ambiguous administrative provision.

Record: verification status, reviewer, unresolved issue owner, and next action. Release a dated, versioned table with its reviewed-document list and review scope.

Worked example

Fictional scenario: All parties, documents, wording, and amounts below are fictional. Alder Quay Solutions resells warehouse scanners and accompanying software supplied by Valecrest Devices. Counsel is extracting terms before renewal. The supplied set contains signed master M-01 v2, signed product appendix P-02 v1, and discount schedule D-03 v1. M-01 incorporates a support policy that has not been supplied.

P-02 provides a 16% discount on accepted orders for scanners listed in D-03. M-01 excludes compensation for supplier direct sales. Sales nevertheless forecasts commission from an introduced customer. Another provision preserves existing customer software licenses after termination, while support obligations refer to the missing policy.

The entries change three decisions. Finance can model discounts only for qualifying accepted orders, not all pipeline revenue. Sales should not treat an introduction as protected commission on the supplied evidence. Operations needs the support policy before promising post-termination coverage. The table identifies evidence gaps without inventing the missing terms.

Common mistakes

• Extracting headings instead of entitlements. Replace “discounts apply” with eligibility conditions, calculation basis, and exclusions.
• Treating the master as the entire contract. Check hierarchy and incorporated schedules before finalizing affected conclusions.
• Combining direct-sale and renewal compensation. Separate transaction types and their respective eligibility rules.
• Converting silence into permission. Label an unlocated sell-off right or missing support term accurately and assign follow-up.
• Treating extraction confidence as legal approval. Verify the text, then separately assign enforceability, competition, or commercial decisions.

Final quality check

• Every substantive row identifies a specific source version and clause or page.
• Wording and summaries match the original, including qualifications.
• Appointment scope identifies relevant products, territory, customers, and channel.
• Discounts, commissions, rebates, and renewal rights have separate conditions.
• Material definitions, precedence rules, and incorporated documents are linked.
• Missing, redacted, ambiguous, and unlocated provisions are distinguished.
• Calculations disclose assumptions, and internal recommendations are not presented as contract terms.
• Open issues are resolved or assigned; the released table states document coverage and version.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its transactional capabilities include tabular review across multiple documents. For related contract review in Word, counsel can choose the reseller as the represented party and provide deal-specific instructions. Findings quote clauses, locate text, rank severity, and identify missing language as not present. Lawyers retain responsibility for source verification, document hierarchy, and commercial decisions. To assess the workflow against your reseller documents, book a demo.

Frequently asked questions

Should every clause receive a row?

Cover each topic within the agreed scope. Split distinct entitlements and obligations, but link shared definitions rather than repeatedly copying them. Administrative wording needs a separate row when it changes a substantive answer.

How should online partner policies be recorded?

Identify the incorporated policy, available version, and incorporation and change language. Preserve the reviewed copy. Flag uncertainty about the governing version instead of silently using today’s policy.

Can the table include proposed negotiation positions?

Yes. Distinguish requested changes from source facts in the action field, or link a separate negotiation checklist. Preferred wording must not appear as existing protection.

What if two documents appear to conflict?

Extract both provisions, link the rows, and examine precedence, amendment language, and express overrides. If these do not resolve the issue, mark the conclusion provisional and assign counsel’s next action.

Sources

• FTC — Manufacturer-imposed Requirements: federal competition guidance, not approval of particular restrictions.
• SEC — LSCA Value Added Reseller Program Agreement: historical Agilent contractual wording, not market-standard evidence.
• SEC — Avaya Reseller Agreement: historical hierarchy, termination, and license provisions, including redactions.

Scope date: October 13, 2026. Live guidance pages do not independently establish their exact text on that date.

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.