Forecast vs Actual: How to Measure and Close the Gap

Forecast vs actual analysis compares the revenue you expected to close with the revenue you did close, and explains the gap. Variance is actual minus forecast. A negative number means you over-forecast. A positive one means you under-forecast. Check it at set points in the quarter as well as at the end, and split it by segment. Updated October 2026: a variance formula table, which sign means what, Excel and Google Sheets formulas, a worked example, and what counts as an actual.

Most revenue teams make hiring plans, budget calls and board commitments on a forecast they will miss. Across ORM's customers, forecast accuracy on new and expansion revenue usually reaches about 90%, and only through heavy manual effort. The forecast vs actual gap is not a reporting problem. It is an operational problem that compounds every quarter.

The good news: forecast variance is diagnosable. Every miss has a root cause, and the causes cluster into a few patterns. ORM has built forecast models for B2B SaaS companies for more than 12 years, and most companies miss for the same five reasons. The teams that close the gap stop treating the forecast as a number and start treating it as a system.

This guide covers how to measure the gap, how to diagnose the cause, and how to build the system that prevents the next miss.

How Do You Calculate Forecast vs Actual Variance?

Subtract the forecast from the actual, then divide by the forecast for the percentage. Finance teams call this actuals vs forecast. Data teams call it actual vs predicted. The math is the same. What changes the meaning is the sign and the denominator, so both are spelled out below. Watch the sign. Variance and bias point in opposite ways. Variance is actual minus forecast, so an over-forecast shows up as a negative number. Bias is forecast minus actual, so the same miss shows up as a positive one. Pick one, put it in the report header, and never mix the two on one slide. The sign matters because over-forecasting and under-forecasting cost you in different ways. An over-forecast commits spend to revenue that never comes. An under-forecast leaves you short of the people you needed. Watch the denominator. Percent variance divides by the forecast. Accuracy and bias divide by the actual. On the same miss the two percentages differ slightly, as the example below shows. The sign also flips for cost lines: on revenue, a positive variance is good news; on expenses, it is not.

For the wider family of accuracy metrics (MAPE, WAPE and when each one fits), use the forecast accuracy guide. The table above is what a forecast vs actual review needs.

Forecast vs Actuals in Excel or Google Sheets

One row per segment, forecast in column B, actual in column C, and four formulas cover the review. They work the same in Excel and Google Sheets. For the total row, sum columns B and C and reuse the same formulas on the sums. Then add one more cell for segment-level accuracy, `=1-SUMPRODUCT(ABS(C2:C4-B2:B4))/SUM(C2:C4)`, so misses in different segments cannot cancel out. Add conditional formatting on column D so over-forecasts show in red. Keep one tab per snapshot (day 1, 30, 60 and 90) rather than overwriting the forecast column, or you lose the history the review depends on.

When the variance shows deals landing early, treat that as a cost rather than a win. Pulling deals forward has two effects in ORM's customer data. You typically discount them, so deal size erodes even where days-to-win improves slightly. And you shrink the starting pipeline for the next quarter. Pipeline for a future quarter is usually built 6 to 12 months before that quarter begins, so pulling from it means spending more on pipeline generation to refill what you borrowed.

Worked Example: One Quarter by Segment

The numbers below are illustrative. They show why the total alone is not enough.

How to read it:

- The total looks fine. A $0.5M shortfall is a 5.0% negative variance and 94.7% accuracy (1 - 0.5 / 9.5). Bias is +5.3% (0.5 / 9.5): the forecast ran high. Same miss, two percentages, because one divides by the forecast and the other by the actual. - The segments do not. Enterprise over-forecast by $0.9M. Mid-market and SMB beat their forecasts by $0.4M combined, which hid most of it. Add the absolute errors ($0.9M + $0.3M + $0.1M = $1.3M) and segment-level accuracy is 86.3% (1 - 1.3 / 9.5), not 94.7%. - The fix is in enterprise. Check deal amounts against what those deals closed for, and check how many enterprise deals slipped. Leave the other segments alone. - The snapshot matters. Say the forecast moved to $9.8M on day 30 and $9.6M on day 60. Accuracy then runs 94.7% on day 1, 96.8% on day 30 and 98.9% on day 60. A forecast that is only right near the end is describing the quarter, not forecasting it. Score the day-1 snapshot hardest, because that is when there is still time to act.

Then cut the same variance by where the revenue came from. I split every quarter into three sources: carry-over deals already in pipeline on day one, deals created and closed inside the quarter, and deals pulled forward from future quarters. Most teams over-trust the first and under-model the second. Across ORM's customers, only about 20% of the pipeline value carrying in-quarter close dates on day one usually closes in that quarter, so most of the number has to come from somewhere else. If your variance sits in in-quarter creation, the problem is pipeline generation, not deal execution.

What Counts as an Actual?

An actual is the result you recorded for a period that has closed, pulled from your system of record. For a sales forecast that is usually closed-won bookings. For finance it is often recognized revenue. Pick one before you measure, or the variance compares two different things.

This is harder than it sounds. In one ORM implementation, the customer could not say which field held the closed-won booking amount. It took five to seven iterations and custom logic to get it right. Another customer had nine amount fields, covering TCV, ACV, ARR, renewal amount and legacy fields nobody had filled in since 2021.

Before the first review, lock four things:

1. Which amount field counts as the actual. 2. Which date puts a deal in the period: close date or booking date. 3. Which revenue types are in scope. Keep new and expansion separate from renewals. Renewals have a known amount and a known date, so blending them in flatters the accuracy number. 4. Which snapshot you compare against. Freeze it on a set date so no one can change it later.

Why Do Forecasts Miss?

Underneath most misses is one mechanism: the business or the market changed, and the forecast still runs on old assumptions. A new competitor creates pricing pressure and average deal size falls. Buyers hesitate and cycles stretch. A territory change distracts reps while coverage still looks fine. The five patterns below are how that change shows up in the variance.

1. Deal Slippage

Deal slippage is the most common cause of forecast misses. Deals forecasted to close this quarter push to next quarter. They do not die. They slide.

The aggregate impact is brutal. Take an example with made-up numbers. You start the quarter at 3x pipeline coverage and expect about a third of it to close. Then 15% of that pipeline slips out of the quarter. You lose about 15% of the target. And the slipped deals pad next quarter's pipeline, which breeds false confidence.

How to detect it: Track the "vintage" of pipeline. Deals that entered this quarter versus deals carried over from last quarter. If a large share of your committed pipeline is carryover from previous quarters, your forecast leans on deals that have already slipped once, and a deal that moves from one quarter to the next is less likely to close, even in commit. How to fix it: Tie commit criteria to buyer actions, not rep judgment. A deal is "committed" when the economic buyer has verbally confirmed timing and budget, not when the rep believes it will close. ORM's models assign probability from buyer behavior data, not CRM stage alone.

2. Conversion Rate Drops

Your forecast model assumes certain conversion rates at each pipeline stage. When those rates decline without detection, the forecast inherits the error.

A 5-point drop in Stage 2 to Stage 3 conversion does not sound dramatic. In an illustrative pipeline with $20M in Stage 2, it means $1M less reaching Stage 3. At downstream conversion of 30% to 40%, that is $300,000 to $400,000 less closed revenue.

How to detect it: Monitor stage conversion rates weekly, not quarterly. Plot them as a rolling 90-day average. Any downward trend beyond one standard deviation from the trailing four-quarter mean warrants investigation. How to fix it: Break the drop down by segment and rep. Conversion drops are rarely uniform. They concentrate in specific segments (maybe enterprise is flat but mid-market dropped) or specific reps (new hires ramping slower than modeled). Fix the specific problem, not the average.

3. Pipeline Quality Degradation

Total pipeline value looks healthy. Coverage is 3.5x. But the composition has shifted. More early-stage deals, fewer late-stage deals. More small deals, fewer large ones. More competitive deals, fewer uncontested ones.

The aggregate number hides the quality decline. A $40M pipeline with a healthy stage distribution produces a very different outcome than a $40M pipeline front-loaded with Stage 1 opportunities.

Amounts mislead too. Most deals close for less than the value they carry in the CRM: for example, a pipeline averaging $80,000 per deal against closed-won deals averaging $40,000. A forecast built on pipeline amounts shows a miss even when the deal count was right. Measure your amount realization rate and apply it by segment.

How to detect it: Weight pipeline by stage and deal quality indicators. Compare the weighted pipeline to the unweighted number. If the gap is growing, quality is declining. Also track "pipeline created this quarter that closed this quarter" as a leading indicator of pipeline freshness. How to fix it: Separate pipeline quantity targets from pipeline quality metrics. Measure your demand gen team on pipeline that converts as well as pipeline created. ORM's prescriptive models flag pipeline quality issues before they hit the forecast.

4. Rep Sandbagging and Happy Ears

Human bias is baked into any forecast that relies on rep input. Reps who have been burned by missed commits in the past will sandbag. Reps chasing accelerators will over-commit. Both distortions hit the forecast.

Sandbagging creates the illusion of overperformance ("we beat forecast!") while masking the real pipeline health. Happy ears create the opposite problem: inflated commitments that evaporate in the final weeks of the quarter.

How to detect it: Compare each rep's forecast accuracy over the trailing four quarters. Reps who beat their forecast by a wide margin quarter after quarter are likely sandbagging. Reps who miss by a wide margin every quarter likely have happy ears. Both patterns are fixable. How to fix it: Reduce reliance on subjective rep input. ORM's models generate forecasts from pipeline data (stage, age, engagement signals, historical conversion) rather than asking reps what they think will close. The model does not have emotions.

5. Coverage Gaps

Sometimes the forecast misses because there simply was not enough pipeline to hit the target at any reasonable conversion rate. This is the most avoidable cause because it is detectable months in advance.

Take an illustrative case. If your historical pipeline-to-revenue conversion rate is 25% and you need $10M in closed revenue, you need $40M in pipeline at the start of the quarter. If you enter the quarter with $30M, the math says you will close $7.5M. No amount of deal acceleration changes that arithmetic.

How to detect it: Track pipeline coverage by segment at the start of each quarter. Compare to the coverage ratio required to hit target based on your historical conversion rate (not the industry average). How to fix it: Build pipeline coverage requirements into planning as well as monitoring. Set coverage targets by segment and track them as a leading indicator 90 days before the quarter starts. ORM's models calculate the exact coverage needed per segment based on your specific conversion rates.

Budget vs Forecast vs Actual: What Each One Is

The three get used interchangeably in conversation and mean different things on a report. Getting them straight is what makes a variance number interpretable.

Two variances fall out of that, and they answer different questions. Budget variance is actual minus budget. It asks whether the year is on plan, and it is the number a board usually wants. Forecast variance is actual minus forecast. It asks whether your prediction was any good, and it is the number that tells you whether the forecasting process is working.

A team can hit budget while missing forecast badly, which means the plan was right and the process is blind. The reverse, forecasting accurately into a miss, means the process works and the plan was wrong. Those call for opposite responses, and reporting only one variance hides which situation you are in. For how the forecast and the plan relate before the period closes, see forecast vs budget.

What Drives the Gap in 2026

Most forecast variance traces to conditions moving under a model that did not move with them.

The clearest example is timing. The median B2B SaaS sales cycle runs 84 days and has lengthened 22 percent since 2022 across 939 companies. A model carrying a 2022 cycle length expects revenue earlier than it arrives, then reads the shortfall as a pipeline problem rather than a timing one.

Across ORM's customers, cycle length has been the lever that moved first in 2026. Buyers are delaying decisions, often waiting to see whether AI will solve their problem a different way before they commit to a known solution. Read the other levers the same way. Pressure on deal size or win rate usually points to competition. A low deal count points to pipeline generation, so look at marketing and the BDR team.

The fix is cadence. Companies that track pipeline velocity each week reach 87 percent forecast accuracy, against 52 percent for teams that track it now and then. Their revenue grows 34 percent against 11 percent. Digital Bloom links that 35-point gap to how often teams track, so it is the cheapest gain most teams can make.

Why Can the Forecast Miss When the Pipeline Was There?

Because the forecast assumed an execution pace that did not happen. One ORM customer had a quarter where the forecast fell apart even though the pipeline was mostly there. Coverage was tight but sufficient. The problem was that deals did not move through the quarter the way the forecast assumed. More of them slipped, and the team did not win or lose as many as expected. Too much stayed stuck in the middle.

It was Q1, the organization was not as focused early in the quarter as it needed to be, and by the time that was obvious there was little room to recover. The tell everyone missed was velocity. The opportunities were there. They were not progressing, closing or being disqualified at the expected rate.

Add three questions to every forecast vs actual review:

If those signals break, the forecast is in trouble well before the top-line number shows it.

What Should You Do When You Fall Behind Mid-Quarter?

At week six, the answer is better focus, and more activity rarely helps.

1. Find the gap. Is it deal size, win rate, pipeline, time to close, or a mix? 2. Decide what can still be sold this quarter. Focus on open deals with a credible path to close. Stop spending time on the rest. Deals you can pull forward without heavy discounting are on the table too. 3. Put executive support where it moves the most. Remove a blocker, reach the right decision-maker, reinforce value or create urgency on the deals that matter.

How Do You Build a Forecast vs Actual System?

Run the comparison on a fixed rhythm: a weekly health check, a monthly variance breakdown, a quarterly review and a yearly reset of the model. One variance review helps. A review you run every time changes how the business runs. Weekly: Pipeline health check. Check how deals sit by stage against what you need to hit the target. Flag any stage that fell more than it usually does in a week. Watch conversion by stage. Monthly: Variance breakdown. Compare month-to-date actuals to the pace the forecast requires, and make that pace seasonal, not a straight line. Across ORM's customers, the third month of the quarter is always the largest and the first month the smallest, so ORM splits each quarter into a 13-week seasonal curve. Against a flat pace, the early weeks look like a miss even when the quarter is on track. Break any variance down by segment, rep, deal type and revenue source. Identify whether the issue is pipeline quantity, quality or conversion. Quarterly: Full forecast vs actual review. The comprehensive analysis. Compare the forecast to the actual by every dimension: segment, stage, rep, deal size, deal type, new vs expansion. Identify the top three root causes. Update the model assumptions for next quarter. Annually: Model recalibration. Review trailing four quarters of forecast vs actual data. Identify systematic biases. Recalibrate conversion rate assumptions, coverage requirements, and seasonal adjustments.

How ORM Closes the Gap

ORM builds custom forecast models that target the most common sources of forecast error. Our approach works in three layers.

Layer 1: Data-driven forecasting. We build the forecast from your pipeline data. The models are tuned to your own win rates, sales cycle length and deal patterns. That takes most of the guesswork in rep calls out of the number. Layer 2: Variance breakdown. When the forecast and actual diverge, our models break the variance down by segment, stage and rep. You do not have to hunt for the root cause. Layer 3: Prescriptive analytics. The model tells you where the gap is and what to do about it: which deals to prioritize, where to add pipeline, how to reallocate resources. The gap between forecast and actual becomes a specific action plan, not a number on a slide.

We target 95% accuracy on new and expansion revenue. Getting there comes from better modeling (more accurate predictions) and better execution (prescriptive actions that close the gaps the model identifies).

The Bottom Line

Every forecast will be wrong. The questions are by how much, in which direction, and whether you find out on day one or on the last day of the quarter.

Forecast vs actual analysis is not a post-mortem. It is an operating rhythm: break variance down weekly, find root causes monthly, recalibrate models quarterly. Gartner puts median sales forecast accuracy at 70% to 79%, with only 7% of sales teams at 90% or better (Gartner). ORM targets 95%. Most of that gap is discipline, not tooling. Build the system. Run the system. The accuracy follows.

Related reading: - Best RevOps Tools - Sales Forecasting: Complete Guide - Forecast Accuracy - Pipeline Coverage Ratio - Deal Slippage - Revenue Variance - Stage Conversion Rate