How to prepare a clause-level risk assessment for Reseller Agreements

Prepare a reseller-side clause-level risk assessment by establishing the controlling contract package, extracting operative provisions, and testing them against the reseller’s economics, customer commitments, and ability to perform. Record each material finding’s source, exposure, uncertainty, proposed response, and decision owner in a clause risk register. Review connected provisions together: a discount may lose value through direct-sales exclusions, while surviving customer licenses may not preserve support. The deliverable is a traceable register supporting targeted redlines, business approvals, and assigned legal questions—not simply a list of unfavorable clauses.

When to use this workflow

Use this workflow when commercial counsel or an in-house team receives a new reseller agreement, material amendment, or revised product terms. It also supports reassessment before accepting expanded territory, exclusivity, sales targets, or customer-support responsibilities.

This is a reseller-side, US-oriented review guide, not advice for a particular transaction. Use the federal competition guidance cited below for issue identification, not as a substitute for transaction-specific analysis. Identify governing law, operating territories, and any state franchise/dealer or restrictive-covenant questions requiring separate research. Contract rights depend on the wording, applicable law, facts, and deal structure.

Keep the task focused on deciding which clauses to accept, revise, investigate, or escalate. A complete post-signature obligations calendar is a separate deliverable.

What you need

Collect the master agreement, amendments, product appendices, discount schedules, incorporated policies, order forms, and proposed customer terms. For an existing relationship, obtain the executed package and the draft under review. Identify unavailable incorporated materials and their referenced versions.

Ask the business team to confirm products or subscriptions, territory, customer segments, inventory commitments, direct-sales competition, renewal responsibilities, and support arrangements. Obtain representative purchase costs, resale revenue, rebates, freight, returns, and payment timing.

Establish the reseller’s negotiation checklist: preferred position, acceptable fallback, escalation threshold, and approval owner. This is the team’s own playbook. Identify any dated standard form used as a comparison baseline; prior agreements alone do not establish an acceptable position.

Use the template

Use Reseller Agreements — Clause risk register. You can copy this table into your working document or spreadsheet. Assign stable row IDs so findings and redlines remain connected across revisions.

In Source / version, include a document ID, version, clause, and page where useful. Operative term captures the allocation or obligation, including triggers and exceptions—not merely the heading.

Use Dependencies / gaps for defined terms, controlling schedules, customer commitments, and missing evidence. Distinguish language absent from an available document from an attachment never supplied, ambiguous wording, or a redacted term.

Severity / confidence separates potential impact from confidence in the evidence and interpretation. Response / fallback records the requested change and acceptable alternative. Owner / status identifies the decision-maker, next action, and disposition; add a target decision date within that cell where needed.

Step by step

1. Establish the controlling document package

Assign document IDs and map incorporation and precedence before assessing isolated clauses. Check whether a product appendix overrides the master, which policies may change unilaterally, and what amendment mechanism the agreement specifies.

The filed Avaya agreement illustrates the issue: section 20.4 generally prioritizes product appendices over product-group attachments and those attachments over the agreement, subject to express overrides. Section 20.5 requires signed written amendments. These are example-specific terms, not default rules (Avaya Reseller Agreement, §§20.4–20.5).

Record conflicts and unavailable materials as register rows. Identify which conclusions remain provisional until controlling language is obtained.

2. Extract decision-relevant provisions and dependencies

Read each provision alongside definitions, exceptions, cross-references, and schedules. Separate findings when decisions or owners differ: customer reporting and payment suspension should not become one generic operational-risk row.

Cover appointment, territory, exclusivity, pricing discretion, discounts, commissions, ordering, supply, returns, warranties, support, intellectual property, indemnities, liability, audits, policy changes, and termination. Include customer-license flow-downs, customer-data reporting, and solicitation restrictions.

Record a concise paraphrase or short excerpt with a precise citation. For performance obligations, capture actor, action, trigger, and deadline in the operative-term cell. Note missing exceptions or inconsistent cross-references in the dependencies cell rather than silently resolving them.

3. Test the reseller’s economics and customer position

Separate purchase discounts from commissions, rebates, and renewal compensation. Identify eligible transactions, thresholds, marginal versus retroactive calculations, refunds, clawbacks, currency, and taxes. Test whether account registration protects initial sales, direct purchases, upgrades, and renewals separately.

Sections 3(c)–(d) of the filed Agilent–O.I. agreement exclude compensation on direct end-user purchases and condition certain add-on or upgrade discounts on the reseller’s original sale and continuing support. This illustrates wording to inspect, not customary entitlement (LSCA Value Added Reseller Program Agreement, §§3(c)–(d)).

Model representative transactions using confirmed inputs. Compare supplier payment timing with customer collections and test price changes against outstanding customer quotes. Record the exposure and assumptions; do not treat forecast renewal income as protected revenue without supporting language.

4. Separate commercial restrictions from unresolved legal questions

Identify whether pricing language concerns suggested prices, advertised-price conditions, or binding minimum resale prices. The FTC explains that manufacturer-imposed vertical minimum-price arrangements receive federal rule-of-reason analysis, while some state and international regimes differ. Its guidance also distinguishes vertical restrictions from coordination among competitors (FTC manufacturer-imposed requirements guidance). Record the required conduct, parties’ competitive relationships, and relevant jurisdictions before escalating.

For exclusivity, assess product scope, territory, duration, alternative suppliers, and exit options. FTC guidance describes exclusive dealing as generally lawful under rule-of-reason analysis but identifies foreclosure concerns where a manufacturer with market power blocks rivals’ distributor access (FTC exclusive-dealing guidance). Breadth alone does not establish illegality.

For customer nonsolicitation, map protected accounts, prospects, affiliates, prohibited conduct, and duration. Record the commercial burden separately from the assigned state-law enforceability question; the cited federal guidance does not resolve that question.

5. Assess connected downside and rank findings

Test adverse scenarios across clauses. If deliveries stop, can the reseller meet customer commitments? If warranty relief is replacement only, who bears removal, installation, or customer service credits? Does an indemnity escape the liability cap, and can the reseller control the conduct creating exposure?

Read termination with inventory returns, invoice acceleration, licenses, support, renewals, and sell-off rights. In the Avaya example, section 17.4 accelerates invoices and section 7.7 preserves properly granted existing end-user licenses after termination of the reseller’s license. Those provisions do not themselves establish continuing support or renewal compensation (Avaya Reseller Agreement, §§7.7, 17.4).

Use a consistent internal scale: high for exposure requiring approval or blocking a material commitment; medium for manageable exposure needing mitigation; low for limited residual exposure within delegated authority. Consider impact, plausible likelihood, operational burden, and mitigation. Record the reason and evidentiary confidence separately.

6. Convert findings into targeted responses

Choose accept, clarify, redline, obtain evidence, or escalate for each material row. Tie the response to the consequence. A direct-sales exclusion may require protected-account compensation; a support gap may require transition assistance rather than a general objection to termination.

Write the preferred change, fallback, and approval threshold. Check dependent definitions and schedules so the fix works. Distinguish a negotiated protection from an internal mitigation: removing assumed revenue from a forecast does not create compensation rights.

Record the proposed disposition and owner. If the business accepts residual exposure, identify the supporting assumptions and authorized approver. Sending a redline does not resolve the risk.

7. Verify dispositions against the current draft

Recheck material findings after revisions. Confirm changes appear in the controlling document and that another schedule has not preserved the problem. Combine text comparison with visual review of tables, attachments, and cross-references.

For notice-dependent protections, verify the trigger, delivery method, recipient, deemed receipt, and relevant time definitions. Do not infer missing or redacted periods.

Update each row with accepted wording, rejected requests, residual exposure, or an assigned open decision. Include the reviewed version and approval evidence so the register does not imply that an earlier approval covers later changes.

Worked example

Fictional scenario: Cedarline Distribution is reviewing a hardware reseller agreement with Northbank Devices. All parties, documents, clauses, and amounts below are invented. The package includes master M-01 v3 and discount schedule D-02 v1; incorporated support policy P-03 is missing.

Cedarline expects to purchase equipment for a customer for $72,000 and resell it for $90,000. Its forecast assumes compensation on later supplier-direct purchases. Proposed customer terms C-01 promise twelve months of support. M-01 permits supplier support to end at termination, subject to P-03. The sales director treats the later-purchase income as material to approval, and the service lead has not confirmed independent support capacity.

R1 preserves the initial transaction’s spread but removes an unsupported forecast assumption; it does not quantify unknown future losses. R2 blocks a confident support conclusion until P-03 and service capacity are checked. R3 requires narrower commercial wording and separate legal analysis. None is closed by a severity label.

Common mistakes

• Reviewing only the master. A controlling product or discount schedule can change the conclusion. Map precedence first.
• Treating discounts as protected margin. Direct sales, freight, returns, and rebate conditions affect economics. Model identified transactions and disclose assumptions.
• Combining exit rights. License survival does not answer support, renewals, or inventory disposal. Separate findings where remedies differ.
• Equating severity with certainty. Missing support terms may conceal substantial exposure. Record provisional impact and low confidence together.
• Closing findings when redlines are sent. Verify accepted wording and record residual exposure or an authorized decision.

Final quality check

• Every material finding cites the correct document version and clause.
• Precedence, incorporation, and missing schedules are accounted for.
• Economics distinguish discounts, commissions, and assumed revenue.
• Liability, warranty, support, and termination findings reflect connected provisions.
• Legal propositions match sources; filed examples are not presented as standards.
• Severity and confidence have separate reasons.
• Open issues have owners and next actions; accepted residual risks have recorded approvals.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. In its Word contract review workflow, choose the reseller as represented party and provide deal-specific instructions. Findings quote and locate clauses, rank severity, and identify missing language as not present. Lawyers can edit or insert suggestions as ordinary tracked changes under the signed-in Word user’s name, or dismiss findings with reasons. Tabular review supports work across documents; the register, verification, and legal judgments remain the team’s responsibility. Book a demo to discuss this review workflow.

Frequently asked questions

Should every clause receive a register row?

No. Review the complete package, but reserve rows for material exposures, meaningful deviations, missing protections, and unresolved dependencies. Routine summaries should not obscure approval decisions.

How should we score missing schedules?

Record plausible exposure provisionally and confidence separately. Identify the missing document, the person obtaining it, and the decision it blocks. Do not describe unavailable wording as an established contractual omission.

Can earlier reseller agreements establish an acceptable position?

Use them as internal comparisons only after checking product, territory, channel, term, and hierarchy. Prior acceptance is a business data point, not proof that present exposure is acceptable or wording is market standard.

When is the assessment complete?

When material findings are source-verified and each has a recorded disposition or assigned open decision. If approval remains conditional on a missing schedule or legal analysis, state that condition expressly rather than describing the agreement as cleared.

Sources

• FTC — Manufacturer-imposed Requirements
• FTC — Exclusive Dealing or Requirements Contracts
• SEC — LSCA Value Added Reseller Program Agreement
• SEC — Avaya Reseller Agreement

Scope: The supplied research cutoff is October 13, 2026. Live FTC pages do not independently establish their exact historical wording on that date; filed agreements illustrate contractual language only.

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.