Plan vs actual reporting sets a period's delivered results against the operating plan approved for it, then accounts for the difference driver by driver. Subtracting one number from another takes a second. The reporting is everything that comes after: which component of the plan moved, by how much, and whether the cause is likely to repeat next period.
The variance has to decompose
A total-line gap tells a board nothing about what to do. Revenue is a product of how many deals closed and how large they were, so the first cut splits volume from value.
- Volume variance. Closed deal count against planned deal count. - Value variance. Average closed deal size against planned deal size. - Timing variance. Value that slipped out of the period rather than disappearing. - Retention variance. Churn and contraction against the plan assumption.
The volume and value split changes the response entirely. Fewer deals at planned pricing is a pipeline problem. Planned deal count at lower pricing is a discounting and qualification problem. A pipeline carrying an average deal size of $80,000 against closed-won averages near $40,000 posts a value variance quarter after quarter until someone reads the two numbers side by side.
Freeze the categories
Variance reporting only compounds in value when the categories stay identical across periods. Fix the buckets at the start of the year, cover new business, expansion, renewal, contraction, and churn, and report the same shape every time. A board reading the fourth version of the same layout spots the pattern before the commentary does.
The pattern is the real output. One period of unfavorable timing variance is noise. Four periods of unfavorable timing variance in a row means close dates in the CRM are systematically early, which is a forecast accuracy problem masquerading as a plan problem.
Plan variance and forecast variance are separate grades
They fail independently, so report both. Plan vs actual answers whether the company is delivering the year the board approved. Forecast vs actual answers whether the company can see the year coming. A team can hit plan every quarter while its forecast swings wildly, which means the results are luck rather than management.
When the miss traces to conversion rather than volume or price, the win rate breakdown by segment usually holds the answer, since an aggregate rate hides a single segment collapsing. The habits that keep this reporting honest are covered in sales forecasting best practices, and most of them come down to fixing definitions early and refusing to rewrite the baseline once results are known.
Frequently Asked Questions
What is plan vs actual reporting?
It is the comparison of a period's delivered revenue against the plan approved for that period, presented with the drivers that produced the difference. A report that shows only the two totals and the gap has done the arithmetic without doing the reporting. The useful version names whether the gap came from deal count, deal size, win rate, timing, or retention.
How do you decompose a revenue variance?
Split it into volume and value first. Compare closed deal count against plan and average deal size against plan, since those two multiply into the total. Then layer in win rate, cycle length, and slipped value. A shortfall from fewer deals at planned pricing needs pipeline. A shortfall from deals closing under planned pricing needs discount control. The two look identical at the total line.
What counts as an acceptable variance to plan?
Direction matters more than size for any single period. A variance explained by a named driver that does not repeat is manageable. A variance in the same direction three periods running signals the plan was built on assumptions that no longer hold, and the correct response is fixing the assumptions rather than asking the team to work harder against them.
How is plan vs actual different from forecast vs actual?
Plan vs actual grades the year against what the board approved. Forecast vs actual grades the forecasting process against what the team predicted weeks earlier. Both belong in reporting because they fail independently. A team can hit plan while forecasting badly all year, and a team can forecast a miss with precision months ahead.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like plan vs actual reporting into prescriptive action for your team.
Schedule a Demo