Getting the Board's Comp Committee to Approve Your Sales Plan
By the time a sales comp plan reaches the board's compensation committee, the CRO has usually already spent weeks getting the plan right operationally. The part that trips people up is presenting it in a way the committee can actually govern, which is a different skill than designing the plan itself.
Here's what a comp committee typically checks, and how to prepare so the first presentation doesn't turn into a second round of follow-up questions.
Vendors Covered in this Article
Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.
What the Committee Is Actually Checking
A compensation committee isn't reviewing whether your comp plan will motivate reps, that's the CRO's job to have already solved. They're checking three things: whether the plan is affordable under the budget the board already approved, whether it creates risk the company hasn't accounted for, such as an accelerator that pays out disproportionately in an unusual quarter, and whether it's consistent with how the company has represented compensation practices to investors or in prior board materials.
Bring the Cost Model, Not Just the Plan Document
A plan document describes rates and thresholds. A cost model shows what those rates and thresholds actually cost under a few scenarios: quota fully attained, quota missed broadly, and one outlier scenario where a small number of reps significantly overperform. Committees approve faster when they can see the company can afford the plan even in the scenario where it pays out the most, not just the expected case.
Build the outlier scenario honestly rather than dismissing it as unlikely. Uncapped accelerators exist specifically so a rep who lands one exceptional deal isn't penalized for the company's own forecasting miss, but that same design means the committee needs to see, in dollar terms, what the plan pays if that exceptional case actually happens, not just be told it's rare.
Flag Anything That Changed From Last Year
If this year's plan changes accelerator thresholds, shifts commission weighting between new business and expansion, or adjusts the pay mix between base and variable, call it out explicitly rather than letting the committee find it by comparing documents. A committee that discovers an unflagged change on their own tends to ask why it wasn't mentioned, which slows approval regardless of whether the change itself was reasonable.
Bring these items to the committee meeting:
- The plan document describing rates and thresholds, alongside a cost model rather than in place of one.
- Three cost scenarios: quota fully attained, quota missed broadly, and an outlier where a few reps significantly overperform.
- An explicit list of anything that changed from last year, including accelerator thresholds, weighting or pay mix.
- For a mid-year change, a before-and-after comparison and a plan for telling affected reps before it takes effect.
- A plan to record the approval and the exact version of the plan document that was approved.
Document the Approval, Not Just the Decision
Once the committee approves the plan, the approval itself, along with the version of the plan document that was actually approved, needs to be recorded somewhere durable. This matters later if a rep disputes a payout calculation, or if an auditor asks to see evidence that compensation decisions followed proper governance. A verbal yes in a meeting, without a documented trail, leaves you unable to prove what was actually approved months later.
For example, after the committee approves the plan, the CRO's team can save the approved plan document, the date of approval, and the meeting minutes or email confirmation together in one folder or policy system, named by plan year. If a rep disputes a payout months later, or an auditor asks for evidence of governance, that folder answers the question in minutes. Without it, someone has to reconstruct events from email threads and memory, and the company may struggle to show which version of the plan the committee actually saw. Store the record where finance and HR can also find it, and note who owns it.
Where Vanta and Drata Fit
Compensation plan approval is exactly the kind of governance event that audit frameworks expect evidence for. Compliance platforms like Vanta and Drata can help track policy approvals, so the record of when a comp plan was presented, what changed, and when the committee signed off is ready if a SOC 2 or similar audit asks for it, rather than reconstructed from old email threads; confirm the current features with the vendor.
Handling a Mid-Year Plan Change
Sometimes a plan needs to change after the year has already started, for instance if a territory realignment makes the original quota assignments unworkable. Mid-year changes get more scrutiny than annual approvals because they affect reps who are already partway through earning under the original terms. Bring the committee a clear before-and-after comparison, an explanation of what specifically broke in the original plan, and a plan for communicating the change to affected reps before it takes effect, not after.
A mid-year change that reaches committee without a communication plan attached tends to generate a second round of questions specifically about how reps will be told, which is often the part that actually determines whether the change lands well internally.
What Good Looks Like
A governance-ready sales comp plan reaches the committee with a cost model covering multiple attainment scenarios, explicit callouts of anything changed from the prior year, and a documented approval trail that survives being asked about months later.
Building The Capability (5-Stage Skill Ladder)
How to Get Started
Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.
Frequently Asked Questions
How far in advance of the plan year should the comp plan go to committee?
Send it early enough to complete one full review cycle before the plan must be communicated to reps. Build in time for at least one round of questions and a follow-up answer, rather than presenting it days before reps need to see it.
What if the committee asks for a change after reps have already seen a draft plan?
This is uncomfortable but not unusual. Communicate to reps that the plan is still pending final approval before sharing any draft externally, so a committee-requested change doesn't read as the company reneging on a promise already made.
Does a small company with an informal board still need this level of documentation?
It's worth the habit even informally, since the documentation matters most exactly when a dispute or audit happens, which is rarely predictable in advance. A brief written record of what was approved and when costs little to maintain and is expensive to reconstruct later.
About the numbers
This guide doesn't quote a sourced benchmark. Figures in it are estimates or general guidance, so check them against your own numbers.
Related Guides
Why Reference Programs Run Out of Willing Customers
Why customer advocacy boards for sales references tend to collapse once a company scales, and how to structure one that keeps a fresh supply of advocates.
Building a Customer Success Scorecard the Board Will Actually Trust
What belongs on a customer success scorecard for the board, which metrics tend to mislead, and how to present retention numbers without hiding weak spots.
Presenting Sales Forecasts to the Board When the Market Wobbles
How to present a revenue forecast to the board when macro conditions are shaky, including how to show a range honestly instead of a single misleading number.
A CRO's Map of How Sales Compensation Actually Works
An overview of how the pieces of a sales comp system fit together, from pay mix and quota to governance and payroll, with pointers to the detail on each.
Building a Customer Advisory Board That Actually Deepens Relationships
A customer advisory board with no real work becomes a listening session nobody prioritizes. Here is how to build one that deepens relationships.
How to Pay Sales Engineers Without Killing Their Objectivity
Why heavy deal-based bonuses can undermine a sales engineer's technical credibility, and how to structure pay that still rewards their impact on wins.