Key Takeaways
- 1. Caps are a tax on your best performers. In most cases, they cost you more in lost production and attrition risk than they save in comp expense. Default to uncapped unless you have a specific, defensible reason.
- 2. Gates are underused and powerful. Requiring minimum performance on one measure before paying on another prevents gaming without the negative signal a cap sends.
- 3. Clawbacks protect the business from paying for deals that do not stick, but the plan document language must be precise. Ambiguous clawback terms are the most common source of compensation disputes.
- 4. Windfall protection (for inherited pipeline, territory changes, or one-time events) should be handled separately from standard caps. Do not penalize consistently strong performers because of occasional outlier scenarios.
Caps, gates, and clawbacks are the guardrails of your compensation plan. They handle edge cases, prevent gaming, and protect the business from unintended payouts. But guardrails that are too tight restrict the road. A cap that is too low kills motivation. A gate that is too strict blocks legitimate payout. A clawback that is too aggressive erodes trust. The art is in calibration: tight enough to serve their purpose, loose enough to let the plan do its job.
Caps: the argument against
A cap is a maximum limit on variable pay earnings. Once the rep hits the cap, additional performance earns zero additional comp. The plan's motivational engine shuts off.
The argument against caps is simple and powerful: caps tell your best performers to stop selling. An AE who hits her cap in September will spend October, November, and December doing one of three things: coasting (losing productive selling time), sandbagging (pushing deals into January so they count toward next year), or interviewing (because a company that caps her upside does not value her enough). All three outcomes cost the company more than the comp dollars the cap saves.
A company capped variable pay at 120% of target. Their top AE hit the cap in Q3 and spent Q4 pushing deals into January. The company lost an estimated $180K in Q4 revenue from that single rep. The cap saved approximately $15K in comp expense. The net cost of the cap was $165K in deferred revenue, plus the signal it sent to every other ambitious rep on the team.
When caps are genuinely appropriate
There are legitimate scenarios where a cap makes sense, but they are narrower than most companies think.
Compliance-driven environments. Financial services, pharma, and other regulated industries sometimes require caps to prevent conflicts of interest or ensure reps do not over-push products to earn outsized commissions. This is a regulatory choice, not a plan design choice.
Windfall protection. When a rep inherits a massive deal they did not source, manage, or close, paying uncapped accelerated commission creates a fairness problem. But the right tool here is a windfall policy, not a blanket cap. "Deals exceeding $X that were in pipeline before territory assignment are paid at base rate" is more precise than "no rep can earn more than 200% of target variable."
Budget certainty in constrained environments. If the company genuinely cannot absorb the cost of outlier performance, a very high cap (250-300% of target variable) provides a ceiling while rarely affecting behavior. If fewer than 2-3% of reps would ever hit it, it functions as insurance, not motivation suppression.
If you must cap, set the cap so high that fewer than 5% of reps would ever reach it based on historical attainment data. A cap at 300% of target variable is rarely felt and provides the budget ceiling Finance wants. A cap at 150% is felt by 10-15% of your team and sends a clear signal that the company does not want anyone to earn too much. That is a culture-defining choice, not a plan design detail.
Gates: the underused power tool
A gate requires minimum performance on one measure before the rep earns payout on a different measure. Unlike a cap (which limits upside), a gate ensures baseline competence without dedicating variable pay weight to the gating metric.
Example: "You must achieve 80% of your revenue target before any payout on the customer satisfaction component." The gate prevents a rep from ignoring revenue and chasing easy satisfaction scores. Revenue remains the gating priority, and the rep must perform on the primary measure before benefiting from the secondary.
Gates are more elegant than adding weight because they do not consume variable pay dollars. They create a binary qualifier: meet the gate, and all measures pay normally. Miss the gate, and certain measures are blocked. This keeps the plan simple while adding a meaningful behavioral constraint.
A threshold is the minimum attainment on a measure before that same measure pays out. A gate is a minimum attainment on one measure that controls payout on a different measure. Thresholds are within-measure. Gates are cross-measure. A plan can have both: a 70% threshold on revenue (below which revenue variable pay is zero) and a gate requiring 80% revenue attainment before the satisfaction measure pays. They serve different purposes.
Clawbacks: recovering pay on deals that unwind
Clawbacks recover variable pay when a deal falls through: the customer cancels within a defined period, the deal is materially restructured, or the revenue is reversed for credit or refund. They protect the business from paying commissions on revenue that does not materialize.
The mechanics are straightforward: if a deal that triggered a commission is reversed within X days (typically 30-90 days for SaaS, up to 12 months for annual contracts), the commission is recovered from a future payout. The rep's next check is reduced by the amount of the clawed-back commission.
The complications are in the details. When does the clawback clock start: at booking, at revenue recognition, or at payment receipt? What if the deal is partially reversed (customer downgrades but does not cancel)? What if the rep has left the company? What about deals that are credited to the rep but managed by CS post-sale?
A plan document stated: "Commissions may be clawed back on deals that do not meet company standards." This language is so vague that it gives the company unlimited discretion to recover any commission for any reason. When a $120K deal was partially restructured 6 months after close, the company attempted to claw back the full commission. The rep argued the restructuring was a CS decision, not a deal quality issue. The dispute escalated to legal. The ambiguity cost more in legal fees and rep trust than the commission itself. Precise language matters: "Commissions will be recovered for deals cancelled within 90 days of booking date, pro-rated for partial cancellations."
Build the clawback into your calculation engine, not your exception process. If clawbacks are handled as manual adjustments after the standard calculation runs, they will be late, inconsistent, and prone to errors. The system should automatically flag deals reversed within the clawback window and apply the recovery in the next regular payout cycle. The rep should see the clawback as a line item on their statement, with the original deal details referenced.
Clawbacks create accrual complexity. If you accrue the full commission at booking but the deal reverses in a later period, the clawback creates a negative adjustment that crosses fiscal periods. For audit cleanliness, consider accruing commissions in two tranches: 70% at booking (most deals will stick) and 30% after the clawback window expires. This reduces the frequency and magnitude of cross-period adjustments.
Windfall protection
Windfalls happen. A rep inherits a territory with a $500K deal already in late-stage pipeline. A merger brings a book of business they did not develop. An industry tailwind produces a once-in-a-decade demand spike. In all of these cases, paying full accelerated commissions creates a fairness problem without rewarding the behavior the plan was designed to incentivize.
The right approach is a windfall policy, separate from the standard plan:
Inherited pipeline: Deals already in pipeline when a territory is assigned are paid at base rate (1.0x), not the accelerated rate. The rep gets credit for closing, but not the premium for sourcing.
Territory windfalls: If a deal exceeds a defined threshold (e.g., 3x the average deal size and was not sourced by the rep), a windfall review is triggered. A committee of Sales Ops, Finance, and Sales Leadership decides the appropriate credit.
Market events: If a category-wide event (regulatory change, competitor exit, pandemic demand spike) produces across-the-board overperformance, the plan can include a "market adjustment" clause that modifies the accelerator for that period. This is rare and should be pre-defined in the plan document, not decided after the fact.
Is your cap costing you more than it saves?
Upload your attainment data to see how many reps would hit various cap levels and the revenue impact of each scenario.
Try SalesComp Edge (free) Model cap scenarios🤖 Try This Prompt
You are a sales compensation consultant reviewing my plan's guardrails (caps, gates, and clawbacks). Here is my current setup: Cap: [e.g., 200% of target variable / No cap] Gates: [e.g., 80% revenue attainment required before satisfaction measure pays / None] Clawback window: [e.g., 90 days from booking / None] Target variable: [Amount] Accelerator: [e.g., 1.5x above 100%] Team size: [Number] Historical max attainment: [e.g., highest performer was at 160%] Please analyze: 1. If I have a cap: how many reps historically would hit it? What is the estimated revenue cost of the dead zone above the cap? 2. If I do not have a cap: should I add one? At what level? 3. Are my gates appropriately designed? Do they prevent gaming without blocking legitimate payouts? 4. Is my clawback language specific enough? Draft improved language if it is vague. 5. Do I need a windfall policy? If so, draft the key terms.
Need help with plan guardrails?
Book a 20-minute review. We will evaluate your caps, gates, and clawback terms and recommend adjustments that protect the business without suppressing motivation.
Book a guardrails reviewChapter Checkpoint
Test your understanding of caps, gates, and clawbacks.
Common Practitioner Questions
If you must cap, 250-300% of target variable is the minimum that avoids significant behavioral impact. At this level, only 1-3% of reps would ever hit it in a normal year. Below 200%, you are affecting 5-15% of your team and actively suppressing motivation among your best performers. Below 150%, the cap is a primary driver of attrition. The best answer remains "no cap" for most sales organizations.
Yes, and that is the most common pattern. Typically, the primary measure (revenue) serves as the gate for secondary measures. "You must hit 80% of revenue target before satisfaction, margin, or any other secondary measure pays out." This ensures the rep does the primary job before earning on supplementary metrics. You would not gate the primary measure itself; that is what the threshold does.
Match it to your contract and churn patterns. For SaaS with monthly contracts, 30-60 days is standard. For annual contracts, 90 days captures most early cancellations without creating prolonged uncertainty for the rep. Beyond 6 months, a clawback starts to feel punitive and shifts too much risk to the rep for decisions (like customer success) they may not control post-sale. If your average cancellation happens at month 8, consider whether that is a clawback issue or a product/CS issue.
This varies by jurisdiction. In most U.S. states, clawbacks are permissible when clearly documented in the comp plan that the rep signed. In some states (like California), there are restrictions on deducting from wages, which means clawbacks may need to come from future commission payments rather than salary. In the EU, labor laws create additional complexity. Always have legal counsel review clawback provisions for your specific jurisdictions. This is not an area for DIY plan language.
This should be addressed in the plan document before it happens. Common approaches include withholding a percentage of final payout until the clawback window expires, or deducting clawbacks from any unpaid commissions or accrued PTO at separation. If the rep has already received all pay, recovery is difficult and rarely worth the legal cost unless the amount is significant. Prevention through holdback provisions is cheaper than collection after the fact.