Sandbagging is rational behavior. When the incentive system rewards over-delivery and penalizes misses, reps protect themselves by committing low. The manager adds an informal haircut. The VP adds another. By the time the number reaches the board, it has been adjusted so many times that no one knows what the underlying commit actually means.
The fix is not closer inspection of individual reps. It is removing the conditions that make sandbagging the rational choice.
Step 1: Separate Structural Sandbagging from Behavioral Sandbagging
These two types look similar on a report but require completely different interventions.
Structural sandbagging is caused by quota and comp design. When committing accurately puts a rep at risk of a raised quota mid-year, or when comp accelerators only trigger after a certain threshold, reps have a financial reason to manage their numbers. This is a design problem, not a behavior problem. Behavioral sandbagging is a learned response to a cultural norm. On teams where beating the number is celebrated and missing is punished, reps adopt sandbagging as a survival strategy. Even when the quota and comp design are neutral, the cultural reward system creates the same outcome.Applying a behavioral fix to a structural problem (coaching reps to commit accurately when comp design punishes it) will not work. Apply the structural fix first.
Step 2: Fix the Structural Causes
Audit the quota and comp design for the conditions that incentivize undercommitting.
| Condition | What to change |
|---|---|
| Quotas raised after strong quarters | Set annual quotas in writing; define in-year revision criteria explicitly |
| Accelerators that trigger at a fixed cliff | Use ratchet-style accelerators that reward all incremental performance above and beyond the cliff |
| No upside for over-delivery beyond a ceiling | Remove or raise the payout cap |
| Commit reviewed in isolation from activity data | Require activity-validated commits, not self-reported |
Step 3: Detect Sandbagging with CRM Signal, Not Judgment
Once structural changes are in motion, use objective CRM data to identify behavioral sandbagging without making it personal.
Build a simple rep-level metric: commit variance rate. For each rep, calculate the average difference between their weekly commit and their actual close over a rolling period.
A rep with a positive, consistent variance across multiple periods is systematically undercommitting. This is the data point to bring into a coaching conversation, not anecdotes about specific deals.
Additional CRM signals worth tracking:
Late-stage commit timing. Deals that appear as commits in the final week of a quarter but show stage-advancement activity from several weeks prior indicate that the rep was holding back a deal that was already effectively won. Multi-period deal holds. Deals that have been in the same late stage for multiple forecast periods without any commit classification are candidates for investigation. They may be held back intentionally. Commit-to-close gap by rep. Track the average number of days between when a rep first commits a deal and when it closes. Reps with consistently longer gaps are likely using the commit timing strategically.Step 4: Create a Forecasting Culture That Doesn't Punish Accuracy
After fixing the structural layer, address the cultural layer. The goal is to make accurate forecasting safe.
Define what it means to miss a forecast versus what it means to sandbag. A rep who commits 80 and delivers 78 has done the job well. A rep who commits 60 and delivers 90 has a forecasting problem regardless of the positive outcome.
Separate the performance conversation from the forecast accuracy conversation. Discuss deal outcomes in pipeline reviews. Discuss forecast accuracy as a separate metric. When reps see that accurate commits are evaluated independently of whether they beat the number, the incentive to sandbag diminishes.
Make forecast accuracy a visible metric alongside quota attainment in rep-level reviews. Not punitive. Informational. Reps who see their own bias patterns have more reason to correct them than reps who are simply told to commit accurately.
Step 5: Run a Bias Audit Quarterly
Once the process is in place, run a quarterly forecast bias audit. For each rep and each manager, calculate:
- Average commit submitted at period open - Average commit submitted at period close - Actual delivered - Variance at each point
Publish the results at the team level (aggregate, not individual). Show the pattern across the org. When everyone sees the systemic bias in aggregate, the conversation moves from accusation to process improvement.
Common Mistakes
Calling out individuals without addressing the system. Identifying a sandbagger by name without first changing the incentive structure is counterproductive. The rep will become more cautious, not more accurate. Using manager haircuts as the long-term fix. A manager who adds an informal multiplier to commits is acknowledging sandbagging without eliminating it. The distortion moves up one layer. Conflating sandbagging with bad deals. A rep may commit conservatively because the deal is genuinely uncertain, not because they are sandbagging. Use activity data and stage completeness to distinguish the two before making a judgment.Frequently Asked Questions
What is forecast sandbagging?
Sandbagging is the practice of committing to a number lower than what a rep believes they will close. It creates a buffer so the rep can over-deliver to plan. It distorts forecasts upward relative to what reps actually commit, which makes pipeline coverage ratios unreliable and forces managers to apply informal haircuts.How do I distinguish sandbagging from genuine uncertainty?
Genuine uncertainty produces a wide variance in both directions. Sandbagging produces a systematic bias in one direction: commits that consistently land above the committed number by a similar margin. If a rep always beats their commit by a similar percentage, and rarely misses, the commit is not a real estimate.Will fixing sandbagging hurt rep morale?
Only if the fix is punitive rather than structural. Reps sandbag because the incentive system rewards it or because the forecasting process penalizes accuracy. Fix the incentive first. A rep who no longer needs to sandbag to look good will stop sandbagging.What CRM signals indicate sandbagging?
Look for deals that were submitted as commit-category in the week they closed, when CRM activity data shows they had been in an advanced stage for several weeks. Late-stage commits on deals that were clearly progressing are a classic sandbagging pattern.For related concepts, see forecast sandbag detection, forecast bias, and commit forecast category.
Frequently Asked Questions
What is forecast sandbagging?
Sandbagging is the practice of committing to a number lower than what a rep believes they will close. It creates a buffer so the rep can over-deliver to plan. It distorts forecasts upward relative to what reps actually commit, which makes pipeline coverage ratios unreliable and forces managers to apply informal haircuts.
How do I distinguish sandbagging from genuine uncertainty?
Genuine uncertainty produces a wide variance in both directions. Sandbagging produces a systematic bias in one direction: commits that consistently land above the committed number by a similar margin. If a rep always beats their commit by a similar percentage, and rarely misses, the commit is not a real estimate.
Will fixing sandbagging hurt rep morale?
Only if the fix is punitive rather than structural. Reps sandbag because the incentive system rewards it or because the forecasting process penalizes accuracy. Fix the incentive first. A rep who no longer needs to sandbag to look good will stop sandbagging.
What CRM signals indicate sandbagging?
Look for deals that were submitted as commit-category in the week they closed, when CRM activity data shows they had been in an advanced stage for several weeks. Late-stage commits on deals that were clearly progressing are a classic sandbagging pattern.
See how ORM turns these insights into action
ORM builds custom revenue forecast models for B2B SaaS companies. Not dashboards. Prescriptive analytics that tell you what to do next.
Schedule a Demo