Key Takeaways
- 1. The plan document is the contract between the company and the rep. If it is not clear, specific, and readable, it will produce disputes, confusion, and distrust.
- 2. The one-page visual summary matters more than the 15-page legal document. Every rep should be able to answer "how do I get paid?" in 30 seconds by looking at one page.
- 3. Write for comprehension, not legal protection. A document written at Grade 16 reading level protects nobody because nobody reads it. The same terms can be expressed at Grade 8.
- 4. The word "discretionary" is the most dangerous word in a plan document. Every instance of it creates unlimited dispute surface area. Replace it with specific criteria.
You have designed a brilliant plan. The OTE is market-aligned. The mix is calibrated. The measures are strategic. The curve rewards overperformance. Now you need to communicate all of this to the people whose behavior the plan is supposed to shape. If the plan document fails, all of the design work is wasted. A plan that reps do not understand is a plan that does not motivate.
Most plan documents fail at one of two extremes. Some are written by lawyers for lawyers: 15-page dense legal documents that no rep has ever read cover-to-cover. Others are too casual: a one-page email summary that omits critical details and creates ambiguity. The right answer is both: a comprehensive document for the record and a one-page visual summary for the desk.
What belongs in the plan document
Every plan document should include these elements, in this order:
1. Plan summary (one page). Role, effective dates, OTE, mix, measures with weights, payout curve (visual), threshold, accelerator, cap (if any), payment frequency. This is the page reps pin to their monitor. It should answer "how do I get paid?" completely.
2. Detailed plan mechanics (2-5 pages). How each measure is calculated. What counts as a credited deal (trigger events). The exact payout formula at each attainment level. Example calculations showing payout at 80%, 100%, 120%. Timing: when deals are credited, when payouts are processed.
3. Edge cases and exceptions (1-2 pages). Clawback terms (specific triggers, window, pro-ration). Windfall policy. What happens during territory changes, leaves of absence, or mid-year plan modifications. How disputes are escalated and resolved.
4. Administrative and legal (1-2 pages). Plan effective dates and termination terms. Acknowledgment and signature section. Relationship to employment agreement. Amendment rights. Governing jurisdiction.
These should be separate documents. The employment agreement covers the employment relationship (at-will status, non-compete, benefits). The plan document covers the incentive structure. Combining them creates legal entanglement: changing the comp plan could be interpreted as modifying the employment agreement, which has different legal requirements. Keep them separate, with the plan document referencing the employment agreement for general terms.
The one-page summary
A 22-page plan document sat in a Docusign queue. Every rep signed it without reading it. Next to each rep's monitor was a printed one-page summary with their name, OTE, measures, and a visual payout curve. Every rep had memorized the summary. They could tell you their accelerator rate and threshold off the top of their head. They could not tell you the clawback window because it was buried on page 14.
The one-page summary should include: the rep's name and role, effective dates, OTE with base and variable split, each measure with its weight and a one-sentence explanation, the payout curve as a visual chart (not a table of numbers), the threshold and accelerator clearly labeled, and the payment frequency. It should be designed visually, not typed as a Word document. A well-designed one-pager communicates more in a glance than a 15-page document communicates in an hour.
Writing for comprehension
Most plan documents are written at a Grade 14-16 reading level. The people reading them are smart, but they are not lawyers. They are sellers who want to know how they get paid. Rewriting a plan document from Grade 16 to Grade 8 does not reduce legal coverage. It reduces the chance of misunderstanding.
"Notwithstanding any provision herein to the contrary, the Company reserves the right, in its sole and absolute discretion, to modify, amend, or terminate this Incentive Compensation Plan at any time, with or without notice, for any reason the Company deems appropriate."
"The company may change or end this plan at any time. If changes affect your current-period earnings, you will be notified at least 30 days before they take effect. Changes will not reduce pay you have already earned."
"Commissions may be subject to clawback in the event that a transaction is determined to not meet established criteria, as assessed by management."
"If a customer cancels within 90 days of the booking date, the commission on that deal will be deducted from your next payout. If the customer downgrades, the commission will be adjusted proportionally based on the reduced deal value."
A plan document used the word "discretionary" in 6 places. "Discretionary bonus for exceptional performance." "Discretionary adjustment for deal quality." "Discretionary review of attainment calculation." Each instance gave the company unlimited, undefined authority. When a rep earned what they believed was their accelerated commission and the company applied a "discretionary adjustment," the dispute escalated to legal. The rep's lawyer focused on the vagueness of "discretionary." The fix: replace every "discretionary" with specific criteria. "Bonus of $X awarded when team exceeds 120% of target" is clear. "Discretionary bonus" is a lawsuit waiting to happen.
Including visual payout curves
A table of payout rates is data. A visual curve is comprehension. Include a chart in the plan document showing the payout curve from 0% to 150%+ attainment. Label the threshold, target, accelerator, and cap (if any) on the chart. Show dollar amounts, not just percentages. A rep looking at the chart should immediately see: "If I hit 120%, I earn $X."
The chart also makes behavioral cliffs visible. If the curve has a sharp jump at 100%, the chart shows it. This transparency is intentional: if you are comfortable with the cliff when it is visible, keep it. If it looks unfair when you see it, redesign the curve.
Handling "what about..." questions
Every plan rollout produces "what about..." questions from reps. What if a deal straddles two quarters? What if I go on parental leave mid-quarter? What if a customer pays late? What if my territory changes?
You cannot anticipate every scenario, but you can address the most common ones in a dedicated FAQ or edge-case section of the document. For truly novel scenarios, the document should specify a resolution process: "Situations not covered by this plan will be reviewed by Sales Ops and the VP of Sales within 5 business days of the question being raised." The key is that the process is defined, even if the outcome is not.
Every "what about..." question that comes in during the year should be logged, answered, and stored. At year-end, review the log and incorporate the most common scenarios into the next plan document. After 2-3 years, your document will cover 90% of edge cases, and "what about..." questions will drop significantly. The Plan Document Builder below includes a template for this log.
Do not send the plan document as an email attachment and hope reps read it. Schedule a 30-minute rollout meeting. Walk through the one-page summary. Show the payout curve. Run through two example calculations. Take questions. Then distribute the full document with a 5-day signature deadline. The 30-minute investment in communication prevents months of confusion and disputes.
Before publishing the plan document, run it through two tests. First, the "new hire test": give it to someone who has never seen your plan and ask them to explain how they get paid. If they cannot do it in 2 minutes, the document needs simplification. Second, the "example test": calculate the payout for 3 attainment levels using the document's instructions. If you get stuck or produce different results than your calculation engine, the document does not match the system.
Need help with your plan document?
We review plan documents for clarity, completeness, and legal exposure. Common fixes include removing vague language, adding visual summaries, and closing edge-case gaps.
Get a document review Build your documentSignature and acknowledgment workflow
The plan document should be formally signed by every participant. This is not optional. An unsigned plan creates ambiguity about whether the rep agreed to the terms. The signature confirms: "I have read and understand this plan. I agree to the terms. I acknowledge that my variable compensation will be calculated according to this plan for the stated period."
Use an e-signature tool (Docusign, HelloSign, or equivalent). Set a 5-business-day deadline. Send two reminders. If a rep does not sign, have their manager follow up personally. Track completion at the team level and report to leadership. Unsigned plans are ticking compliance risks.
🤖 Try This Prompt
You are a sales compensation expert helping me create a plan document. Here are my plan parameters: Role: [Title] OTE: [Amount] Pay mix: [e.g., 60/40] Measures: [List with weights] Threshold: [e.g., 70%] Accelerator: [e.g., 1.5x above 100%] Cap: [e.g., 300% of target variable / No cap] Measurement period: [Monthly / Quarterly / Annual] Clawback window: [e.g., 90 days] Effective dates: [Start - End] Please generate: 1. A one-page visual summary I can share with reps (using simple formatting) 2. The full plan document with all required sections 3. Three example calculations at 80%, 100%, and 120% attainment 4. An FAQ section covering the 5 most common "what about..." questions for this role type 5. Flag any terms that are vague and suggest specific replacements 6. Write everything at Grade 8 reading level or below
Module 2 complete!
You now have the full toolkit for designing a compensation plan from scratch. Module 3 takes these principles and applies them to specific sales motions and industries.
Start Module 3: Plan Design by Context →Chapter Checkpoint
Test your understanding of plan documentation.
Common Practitioner Questions
8-12 pages is the sweet spot for most plans. Page 1 is the visual summary. Pages 2-6 cover mechanics and calculations. Pages 7-9 cover edge cases. Pages 10-12 cover administrative and legal terms. Below 5 pages, you are likely missing important details. Above 15 pages, the document is doing the work of a legal agreement that should be separate. The one-page summary is always a separate deliverable, not just the first page of the longer document.
Yes, but with clear guardrails. Legal should review for legal compliance (wage laws, jurisdiction requirements, clawback legality). Legal should not rewrite the document to sound like a contract. The tension is real: legal wants protective language, comp wants comprehensible language. The resolution is simple. Write the document in plain language. Have legal review it. Where they flag legal risks, find language that addresses the risk without reverting to legalese. If legal insists on complex language for a specific clause, keep it but add a plain-English summary in parentheses next to it.
You can, but you should not unless there is a significant business change (acquisition, market disruption, product pivot). Mid-year changes erode trust. If you must change, give 30 days notice, do not reduce pay already earned, and re-issue the document with clear redline of what changed. If you find yourself changing plans mid-year regularly, your planning process needs improvement, not your plan document.
Grade 8 (8th grade reading level). This does not mean dumbing down the content. It means using short sentences, active voice, specific terms instead of jargon, and examples instead of abstractions. A rep with an MBA can read a Grade 8 document faster than a Grade 16 document and understand it better. You can test reading level with free tools like Hemingway Editor or the Flesch-Kincaid score in Microsoft Word.
Both. The one-page summary should include the rep's specific dollar amounts (their OTE, their base, their target variable). The full document can use both dollars and percentages. Example calculations must use specific dollars: "At 120% attainment, your variable pay is $96,000" is immediately actionable. "At 120% attainment, you earn 120% of your target variable component multiplied by the applicable rate" requires a calculator and a PhD in parsing legalese.