What Is Budget Variance?

Budget variance is the difference between the costs planned for a project at a given time and the costs actually incurred. A positive (or favourable) variance means you've spent less than planned; a negative (or unfavourable) variance means you've spent more.

Formula: Budget Variance = Planned Cost − Actual Cost

If a project was planned to cost £25,000 in its first six weeks and actually cost £28,000, the budget variance is −£3,000 - an unfavourable variance of 12%.

Budget variance is a point-in-time measure. Unlike cost overrun, which describes the final outcome at project close, budget variance is a live signal you can act on.

How Budget Variance Is Calculated and Interpreted

The calculation is simple. The interpretation is where most PS firms go wrong.

Step 1 - Establish the baseline: your approved project budget broken down into time periods (weekly, monthly, or by phase) based on when costs are expected. This is your planned spend curve.

Step 2 - Track actuals: Record  costs as they're incurred, primarily through time tracked against the project, plus any direct expenses in PS firms. to date minus actual cost to date = budget variance.

The interpretation problem: a −£3,000 budget variance (you've spent £3,000 more than planned) isn't automatically alarming. It depends on how much work has been completed. If you've spent 12% more but completed 20% more work than expected, you're ahead. If you've spent 12% more and completed only 5% more work, you have a serious problem.

This is why budget variance should always be read alongside percentage complete or progress metrics. A project 50% complete and 45% through its budget is in a strong position. A project 50% complete and 65% through its budget is heading for a cost overrun. The variance is the early warning.

Earned Value Management formalises this comparison with two indices:

• Cost Performance Index (CPI) = Earned Value ÷ Actual Cost. CPI > 1.0 is good; CPI < 1.0 means you're spending more than the work is worth.
• Schedule Performance Index (SPI) = Earned Value ÷ Planned Value. SPI > 1.0 means ahead of schedule.

Why Budget Variance Matters for PS Firms

Professional services margins are tight and project-based. A 35% gross margin on a £60,000 project means £21,000 in gross profit. A −20% budget variance, £12,000 in unplanned overspend, wipes out more than half that margin.

Budget variance monitoring prevents cost overruns from being surprises. Firms that review budget variance weekly per project can intervene while there is still time to adjust scope, rebalance resources, or raise a change order. Firms that review budgets monthly typically discover overruns after the point of no return.

​The other reason it matters: budget variance at the project level aggregates into margin performance at the firm level. A pattern of small negative variances across a portfolio, each dismissed as "within acceptable range," can translate into meaningful margin underperformance by year-end.

‍

Favourable vs Unfavourable Budget Variance

‍

‍

A favourable variance isn't automatically good news. If costs are below plan because activity hasn't happened yet, such as a phase running late, resources unavailable, or client approvals delayed, the variance will flip negative later when that work is delivered. Always check whether a positive variance reflects genuine efficiency or deferred work.

Examples in Practice

Example 1 - Weekly variance review prevents a cost overrun. A consultancy runs a 12-week transformation programme with a £90,000 budget, planned at approximately £7,500 per week. At week 5, the finance manager's weekly review shows actual spend of £45,000 against planned £37,500, a −£7,500 variance. At the current pace, the project will cost approximately £108,000. The project lead reviews where the extra hours have gone: three unplanned client working sessions and a strategic review that ballooned in scope. A change order is prepared for £18,000. The client accepts. Final project cost: £93,000 against a revised budget of £108,000. The variance is converted from a loss into a managed change.

Example 2 - Positive variance masks a schedule problem. An engineering consultancy's monthly budget review shows a favourable variance of £12,000 on a major infrastructure project, ahead of budget at the midpoint. The project manager flags this as good news. In fact, a key deliverable phase has been delayed by four weeks due to client information not arriving on schedule. The £12,000 "saved" will be spent in the back half of the project, now compressed into a shorter timeframe requiring more expensive resources to meet the deadline. The favourable variance was a schedule problem in disguise.

Example 3 - Portfolio-level variance analysis. A digital agency reviews budget variance across its 22 active projects. Of those, 14 are within ±5% of planned spend (on track), 5 have negative variances of 10–25% (at-risk, being monitored), and 3 have negative variances above 30% (escalated for account director review). The 3 escalated projects account for £45,000 in projected overrun. Of these, two involve the same client, suggesting a pattern of scope absorption specific to that relationship that needs to be addressed at the account level.

Common Mistakes

Reviewing budget variance without reference to completion is a mistake. A £5,000 negative variance means nothing without knowing how much of the project is done. Always pair variance with a completion percentage or earned value metric.

Treating favourable variance as a success signal is a mistake. Underspend can reflect efficiency but can also reflect delayed activity, understaffed delivery, or scope never executed. Dig into the cause before celebrating.

Only reviewing variance at the total project level is a mistake. Aggregate project variance can mask significant variance within specific phases or roles. A project on budget overall might have a cost centre 40% over, while another is 40% under. Phase-level and role-level variance analysis reveals where intervention is needed.

No response protocol for threshold variances is a mistake. Negative variance only triggers action if someone acts on it. Best-practice PS firms define variance escalation thresholds: any project hitting −10% variance triggers a project manager review; any project at −20% variance triggers an account director review; any project at −30% variance triggers a client conversation.

‍