Freeze the representative package and sales brief
Begin by inventorying the proposed agreement, territory or account schedule, product and pricing materials, commission schedule, order procedure, credit or return procedure, reporting instructions, sample or marketing rules, and every addendum or policy included with the package. Record the filename, version, sender, received date, and internal owner for each item. Preserve the originals rather than replacing them with a combined sales summary.
Add a short sales brief written by the owner and sales lead. Record the products and customer types in scope, the markets or accounts the team expects the representative to cover, the current order path, the internal people who approve pricing and exceptions, and the person authorized to approve a business change. Keep this brief labeled as context so it cannot be mistaken for agreement language.
- Name the exact agreement, account, territory, and commission versions under review.
- List every sales procedure, price document, and policy the package incorporates.
- Record the sales, finance, fulfillment, and approval owners.
- Keep recruiting conversations and sales forecasts separate from source-backed terms.
Trace the path from account activity to a recorded sale
Draw the sales sequence the grower can actually verify: prospect or account assignment, quote or price communication, customer order, internal review, availability confirmation, order acceptance, fulfillment, invoice, payment record, credit or return, and the sales report used for follow-through. For each stage, name the person and record involved and attach the proposed language that appears to describe it.
Leave a stage open when the package does not answer it. An expectation about account ownership, order credit, timing, or reporting should remain visibly separate from the proposed documents. The map is an operating fact record for counsel, not a conclusion about when a sale or commission legally exists.
- Use the grower's real order and reporting sequence rather than a generic funnel.
- Identify the document and exact source location behind every agreement-derived note.
- Name who can verify each account, order, fulfillment, and payment event.
- Preserve an unclear account assignment or missing record as an open item.
Pair accounts, territories, and commissions with source events
Create one table for every account category, territory description, amount, formula, date, statement, adjustment, and other commission event the package describes. Keep the smallest useful source passage beside each row, along with the record the business expects to use when administering it.
Place the sales forecast beside the source rather than inside it. Sales can identify expected account activity, finance can record its internal model, and operations can verify fulfillment or return records. Counsel can then inspect the proposed language without receiving an internal forecast or practice as though it were an agreed term.
- Keep a stated formula or account definition separate from the grower's forecast.
- Record the event, source location, evidence owner, and business owner for each row.
- Mark a missing account list, territory description, statement, or adjustment rule explicitly.
- Do not turn an incomplete event or formula into a confident commission result.
Walk account changes and transition scenarios through the record
Test the package with concrete sales scenarios: an existing account enters the proposed territory, two representatives touch the same customer, an order changes before fulfillment, a customer receives a credit, payment arrives later than expected, a product line moves, or the relationship transitions to a new representative. For each scenario, place the expected business response beside the source sections and procedures that appear relevant.
Route each unknown to the right lane. Sales can verify account history and communication, operations can confirm order and fulfillment facts, finance can confirm statements and payment records, leadership can own commercial choices, and counsel can address interpretation, drafting, and legal risk. Keep the question open when the source or business record is incomplete.
- What account, order, payment, or transition event is being tested?
- Which source passage or procedure appears to address it?
- Who can verify the record or approve a business change?
- What interpretation or drafting judgment remains for counsel?
Give counsel one account-to-commission packet
The handoff should include the frozen document inventory, sales brief, source-linked account-to-sale path, account-and-commission table, transition scenarios, missing materials, and the owner of every open decision. Keep superseded schedules, forecasts, and informal explanations available but distinguish them from the package counsel is being asked to review.
For each uploaded contract document, CounselOS can preserve source-linked clause extracts, surface playbook deviations, capture questions beside the relevant finding, and export selected material in a review packet. The sales path and commission records remain human-reviewed operating artifacts; CounselOS provides traceable contract evidence for the grower and attorney making the next decisions.
A note on legal judgment
This article describes a review and handoff workflow. It is general information, not legal advice. Contract meaning and acceptable risk depend on the agreement, the parties, and the applicable law; involve qualified counsel for legal decisions.