Sandbagging vs. late-surfacing deals: Keeping forecast categories honest

TL;DR: A forecast that should have added up didn't, and the two most common reasons are opposite behaviors. Sandbagging hides a winnable deal to protect a future quarter, while a late-surfacing deal pushes an unready deal into Commit or Best Case to save the current one. Both distort the same forecast categories from opposite directions, and both are rational responses to how comp plans and quota pressure are designed, not just bad behavior.

A CRO cannot run a quarter on a Commit number that hides unreported upside or includes late deals nobody saw coming. Both behaviors distort the forecast, but adding more dashboards will not fix them if the forecast categories are not governed by clear evidence.

For RevOps leaders, the first step is to identify the behaviors creating the gap between the forecast and reality. From there, build controls that surface them early.

That means defining the evidence required for each forecast category, tracking changes in deal confidence, and reviewing exceptions before they affect the number presented to leadership. The goal is a forecast that reflects what the pipeline can actually deliver.

What forecast categories are supposed to mean

Forecast categories exist to give the revenue team a shared language for how confident everyone is that a deal will close in a given period. When that language gets used inconsistently, or gamed deliberately, the categories stop meaning anything at all.

Sales stage and forecast category aren't the same thing

Sales stage describes where a deal sits in the seller's process. Forecast category describes how confident the team is that it closes within a specific period. Treating every late-stage deal as automatically Commit-worthy creates false confidence, since a deal can be far along in the sales process and still have real risk to closing on time.

A stage change and a category change need to stay two separate decisions, made on separate evidence, or the category stops meaning anything beyond a proxy for how far along the deal looks.

Give each category a precise business meaning

Category taxonomies vary by company, but Commit, Best Case, Pipeline, and Closed Won are the common labels. What matters more than the exact names is that leadership can trust what each one means.

What is sandbagging?

Sandbagging is deliberately understating near-term revenue by withholding a winnable deal, lowballing its amount, or pushing its close date to reduce expectations or manufacture an easier story next quarter.

What sandbagging looks like in practice

The behavior shows up in a handful of recognizable patterns.

• A deal sits in Best Case past its criteria: It meets every requirement for Commit but stays parked there until the final week of the quarter.
• A rep beats a suspiciously low Commit number: The deals that "surprise" everyone were already at a late stage when the number was submitted.
• Close dates slip without supporting evidence: The deal gets pushed to the next period despite signals that the buyer is on track to sign.

Why RevOps and CROs see sandbagging happen

This is a system-design problem more than an individual one, and the causes usually trace back to one of a few sources.

• Fear of a number that gets held against them: A rep who's been burned by an ambitious forecast learns to under-promise every quarter after.
• Comp mechanics that reward timing: A plan that pays out more for a dramatic beat than an accurate call makes manipulation the rational move.
• A culture that punishes misses harder than it rewards accuracy: When honesty and inaccuracy get treated the same, there's no incentive to report the real number.
• Category definitions vague enough to defend either way: If nobody's agreed what evidence Commit requires, holding a deal back isn't technically against any rule.

What sandbagging costs the business

Once the pattern is established, the cost shows up well outside the sales org.

• Underinvestment in winnable deals: Capacity, coaching, and executive support get withheld from deals leadership never saw coming.
• Conservative spend and hiring decisions: Finance plans against a revenue number that was never real to begin with.
• A distorted read on rep performance: Leadership mistakes a beat for great execution rather than a deliberately low initial call.

What are late-surfacing deals?

A late-surfacing deal is a recurring pattern where a deal appears as late-period upside or lands as Closed Won without being visible in the forecast early enough for anyone to plan around it.

What late-surfacing deals look like in practice

The pattern tends to show up in the same few ways every quarter.

• A deal jumps categories with no new evidence: It moves from Best Case or Pipeline straight to Commit days before quarter close, with no corresponding change in buyer engagement.
• A won deal has no forecast history: It closes with little or no prior visibility in any category.
• Amounts increase right before close: The deal size jumps shortly before it's marked won, with no documented reason.

Why deals surface late

The pattern usually comes from a mix of pressure and process gaps.

• Quota pressure at quarter close: A rep short of the number has every incentive to promote a marginal deal rather than report the shortfall.
• Managers who only inspect Commit: If nothing outside Commit gets reviewed, there's no check on what gets promoted into it late.
• Reps unclear on category ownership: Without guidance on when to create or categorize an opportunity, deals sit unclassified until someone needs them to count, a symptom of the kind of organizational silos that let inconsistent categorization go unnoticed.
• Optional CRM fields with no evidence requirement: A deal can jump categories without ever showing the activity that would justify it, which is ultimately a CRM adoption problem as much as a behavioral one.

What late-surfacing deals cost the business

The damage isn't limited to the one deal that got sniped.

• An unpredictable board number: A quarter that depended on late surprises reads as luck, not a repeatable process.
• No time for managers to intervene: A deal only becomes visible once it's nearly closed, past the point anyone could have helped or challenged it.
• Eroded trust in every other category: Once one deal appears out of nowhere, leadership starts questioning what else on the forecast might not be real.

How RevOps can detect both patterns in the data

Most teams watch for only one of these two patterns, which is exactly why the other goes unnoticed for so long.

Track conversion by forecast category

Break down historical close rates for Commit, Best Case, and Pipeline by rep, manager, segment, region, and product, the same sales metrics a regular pipeline review should already track. A Commit category that almost never misses signals a bar that's set too high, or sandbagging. One that converts poorly signals premature promotion into Commit.

Track timing and category-movement patterns

Watch for deals that jump from Best Case to Commit in the final week, Closed Won deals with no prior forecast visibility, and repeated close-date pushes followed by an early close the very next period. Pulling this apart deal by deal is exactly the kind of work covered in diagnosing deal risk.

Build a category-integrity view

Track a small set of things on a recurring basis rather than only at quarter close: category status at the start, middle, and end of each period, the dollar value of "surprise" Closed Won deals, Commit conversion variance by rep and manager, and the share of Commit deals meeting your evidence requirements. This is the same discipline behind good pipeline inspection, applied specifically to category integrity rather than deal count.

Building a forecast category governance framework

Detection surfaces the pattern, but only a framework turns it into something that actually changes behavior, which is why this comes right after detection rather than standing on its own.

Set evidence-based entry criteria for Commit and Best Case

The concrete artifacts here are a documented checklist, a confirmed decision process, an identified economic buyer, a multi-threaded engagement, and a mutual close plan, all of which are required before a deal can enter Commit. RevOps typically owns this document, and it works when two different managers categorize the same deal the same way.

Separate forecast accuracy from quota attainment

This is the most important lever in the whole framework. A rep can miss quota with an honest forecast, or beat quota with a misleading one, and if the organization rewards only the second outcome, sandbagging and late-surfacing deals will keep happening. This distinction matters just as much for how a team measures sales quota attainment as it does for the forecast itself.

Make managers accountable for category quality

Require a documented rationale whenever a deal enters Commit, exits Commit, or is omitted at late stage. RevOps supplies the data, but a manager coaching a repeat pattern is what actually changes it, which ties directly into how a team measures sales coaching effectiveness more broadly.

Run a weekly forecast rhythm built around what changed

The concrete artifact is an agenda that reviews the delta since the last call, including deals that were added, removed, or slipped from Commit, rather than only asking what's going to close.

This is a natural extension of standard pipeline management best practices, focused on category change rather than pipeline volume. Sales managers typically own running it, and it works when a category change gets caught the week it happens, not discovered at quarter close.

How Outreach exposes category mismatches

Neither behavior survives a system that checks a claimed category against what the buyer is actually doing, which is the specific gap this closes for revenue operations teams running the framework above.

Outreach, the only agentic AI platform for revenue teams, builds that check directly into the deal record rather than relying on a rep's self-report.

• Deal Insights: Scores every opportunity on engagement signals rather than rep self-reporting, surfacing the exact mismatch both behaviors create: a safe-looking category with stale activity, or a promoted category with no new engagement behind it.
• Deal Health Score: Rates each opportunity using 15 activity signals benchmarked against similar deals at the same stage, so a category claim has an objective number behind it.
• Deal Agent: Updates opportunity fields from actual conversation and engagement data rather than relying on a rep to self-report them, removing the manual entry step that both behaviors depend on.
• Outreach’s Sales Forecasting Software: Rolls up category-level conversion and variance by rep and manager, so a commit-variance pattern shows up in a report instead of only becoming visible at quarter close.

Outreach's own model for predicting close outcomes runs at 81 percent accuracy, independent of whichever category a rep assigned a deal, which is the kind of independent check that makes gaming a category harder to hide.

The boundary is still worth keeping clear. This surfaces the signal, but it doesn't replace the entry-criteria document or the coaching conversation a manager still needs to have.

Make honest forecasting the easier choice

Before building anything new, pull the last full quarter's category history and check it against two questions. Did any Commit deal have thin engagement evidence behind it, and did any won deal skip Commit and Best Case entirely on its way to closed?

The answers tell you which behavior is actually costing your forecast credibility right now. A trustworthy forecast isn't one that never misses. It's one where Commit means the same thing for every seller, every week of the quarter.

Frequently asked questions about sandbagging and forecast category integrity

What is sandbagging in sales?

Sandbagging is when a rep or manager deliberately understates a deal's likelihood or timing by holding it in a lower category, lowballing its amount, or delaying its close date to manufacture an easier result in a future period. It hides real, winnable revenue from the current forecast.

What is a late-surfacing deal?

A late-surfacing deal is one that appears as late upside or lands as Closed Won without having been visible in the forecast early enough to plan around. Where sandbagging understates the forecast, a late-surfacing deal keeps real pipeline invisible until it's too late to manage.

What are the standard sales forecast categories?

Most teams use some version of Pipeline, Best Case, Commit, and Closed Won, sometimes with an Omitted category for deals removed from active forecasting. See Outreach's full guide to forecast categories for how each one should be defined and used.

How do you stop sandbagging without punishing top performers?

Separate forecast accuracy from quota attainment as two distinct things a rep gets measured on, then require documented evidence for any deal entering Commit. This rewards honest reporting on its own terms instead of treating every conservative call as underperformance.

How can RevOps tell a legitimate late-quarter close from a late-surfacing deal?

Check whether the deal had prior visibility into the forecast and a documented trail of buyer engagement leading up to the close. A legitimate late close usually shows steady activity building toward it. A late-surfacing deal typically shows a sudden category jump with little or no engagement to support it.