UNDERSTAND THE CONCEPT
Budget variance compares actual results with an agreed budget for the same scope and period. Establish the sign convention before reporting: for an expense report, actual cost minus budget can show overspending as a positive number. The arithmetic is only the beginning. A meaningful explanation separates changes in activity volume, unit rates, productivity, scope and timing. Otherwise, a delayed invoice can look like a saving while a planned outage looks like poor control.
Compare like with like and preserve the approved budget version. If production volume changed, a flexible comparison may help distinguish activity effects from performance, while the original budget remains visible. Examine commitments and forecast consequences as well as posted costs. Assign actions to controllable causes and identify effects expected to reverse in a later period. A variance review should end with a better forecast or a concrete management decision, not merely a narrative describing the number again.
Questions to take back to your team
- Are actuals and budget aligned by scope, period and version?
- Can the variance be separated into quantity, rate and timing effects?
- Which causes change the forecast or require corrective action?
Further reading
Explore the primary references below. Requirements and applicability depend on your organization and jurisdiction.