Quota is the target you set. Forecast is your honest estimate of what will actually close.
Treating them as the same number produces a corrupted forecast and a false sense of security. When forecast equals quota, you have a commitment document, not a prediction. The distinction matters because the actions you take in response to each are completely different.When forecast falls below quota, the right response is to investigate and address the pipeline gap: build more pipeline, accelerate late-stage deals, or adjust capacity. When forecast equals or exceeds quota, the right response is to confirm that the underlying deal-level evidence actually supports the number. If it does not, the forecast is being driven by target pressure, not pipeline reality.
How each number is set
| Dimension | Quota | Forecast |
|---|---|---|
| Set by | Management, usually top-down with rep input | Rep and manager, based on pipeline |
| Timing | Start of period (annual, quarterly) | Updated weekly or monthly during the period |
| Purpose | Define the performance standard | Estimate the likely outcome |
| Input | Business targets, capacity, market | Deal stage, deal size, close date, rep judgment |
| Changes during period | Rarely | Regularly |
The sandbagging and padding problem
The gap between quota and forecast reveals two common behavioral distortions.
Sandbagging happens when reps underforecast relative to their actual conviction about deals. They do this to manage expectations, create upside surprises, or protect themselves from close-date pressure. The result is a forecast that is systematically below what the pipeline actually supports.
Forecast padding is the inverse: managers or reps inflate their forecast to close the gap to quota, even when deal-level evidence does not support the numbers. This makes the forecast useless as a planning tool and leads to under-prepared operational responses when the quarter closes light.
Both distortions are easier to detect when quota and forecast are treated as distinct numbers with distinct accountability owners. Forecast accuracy degrades when the two are conflated.
Using the gap productively
The gap between forecast and quota is one of the most actionable numbers in a revenue operation. If forecast is materially below quota with six weeks left in the quarter, you know exactly what problem to solve: close the gap through pipeline acceleration, not through forecast revision.
That discipline requires leaders to hold the tension between the two numbers rather than collapsing them. See Quota Attainment and Sales Forecasting for how each is measured and managed separately.
Frequently Asked Questions
What is the difference between quota and forecast?
Quota is a target: it is set in advance, usually top-down or through a collaborative planning process, and it represents the outcome you are trying to achieve. Forecast is an estimate: it is updated continuously based on what is actually in the pipeline and how deals are progressing. The gap between them is meaningful information, not noise to be managed away.
Why shouldn't forecast equal quota?
When reps or managers anchor their forecast to quota rather than to actual pipeline evidence, the forecast loses its predictive value. It becomes a commitment signal, not an estimate. Leaders then can't distinguish between a team that is genuinely on track and one that is sandbagging or hoping deals will materialize. Honest forecasts that fall short of quota are more useful than optimistic forecasts engineered to look like quota.
What is the right relationship between quota and forecast?
Quota should be set based on capacity, market opportunity, and business targets. Forecast should be set based on current pipeline reality and deal-level confidence. The two numbers can and should diverge. When the forecast falls short of quota, that is a signal to act on pipeline gap, not a reason to inflate the forecast.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like quota vs forecast into prescriptive action for your team.
Schedule a Demo