Budget · forecast · decisions
Plan-versus-actual analysis:
from variance to action
A budget is useful not when actual matches plan, but when the team understands the reasons for the variance, updates expectations and makes a decision. For that, planning, analysis and forecasting must operate as a single cycle.
Anton Konnov · 20 August 2026 · 9 minutes
Purpose
A budget is a coordinated model of actions
Financial line items reflect operational decisions: sales volume, prices, headcount, procurement, capacity, timelines and investment. If the budget is built merely by rolling forward past figures, the link to real accountability is lost.
Before the cycle begins, it is useful to establish who uses the report, which decisions are made monthly or quarterly and which variances trigger a response.
Six steps
How to connect plan-versus-actual analysis to management
Define the decision cycle
Record the calendar, participants, level of detail and list of decisions. Cadence must match the speed of the business: a report that arrives too late explains the past but cannot influence the outcome.
Build a driver-based budget
Link revenue and cost to operational drivers: volume, price, sales mix, productivity, rates, timelines and resources. This allows you to explain variances without manually inspecting every line item.
Separate accountability
Every material line item and assumption must have an owner. Distinguish between controllable factors, external conditions and joint responsibility across several functions.
Decompose the variance into causes
Separate the impact of volume, price, product mix, efficiency, timing and one-off events. The net difference without causes rarely points to the right action.
Update the forecast
Plan-versus-actual shows what has already happened; the forecast shows the expected result by period end. New information should change the forecast and the range of possible outcomes, not the approved budget.
Lock in the decision and follow-up
For a material variance, record the action, owner, deadline and expected effect. At the next cycle, verify not only the metric but also whether the decision was executed.
Cause structure
How to read a variance
Volume
Change in sales quantity, operations, customers or utilisation.
Price and rate
Change in selling price, tariff, purchase price or resource cost.
Mix
Shift in product, customer or channel composition.
Efficiency and timing
Resource consumption, productivity, transfer of an operation between periods.
Report
What should reach the manager
A small set of material variances, not a full accounting register.
The cause and its quantitative contribution to the result.
Updated forecast through period end and the range of uncertainty.
The accountable person, the corrective action and the expected effect.
Status of last cycle's decisions and the remaining risk.
Mistakes
What undermines the budget process
You cannot simultaneously use the budget as a realistic forecast, an unattainable motivational target and a spending cap without explicitly separating these functions. Otherwise participants start defending the number instead of the quality of the decision.
It is also dangerous to backdate changes to the approved budget: the baseline for analysis disappears. New expectations require a separate forecast, and the reasons for the change must remain visible.
Methodological reference
The management loop
IFAC IES 2: budgeting, forecasting and variance analysis as decision-making tools ↗
ACCA: planning, budgeting, forecasting and performance reporting ↗
This material is educational and does not replace analysis of a specific organisation, its contracts, tax regime or accounting policies.
First step
Choose one recurring decision
We will link metrics, variance causes, forecast and actions into a single management cycle.