Variance analysis compares the budgeted cost of a project with the actual and forecast cost, line by line, to find where it is over or under budget and why. It is the step that turns a cost report into decisions.
Worked example
A £705,000 budget is compared with the forecast final cost at month four:
| Package | Budget | Forecast | Variance |
|---|---|---|---|
| Groundworks | £120,000 | £134,000 | (£14,000) |
| M&E | £310,000 | £301,000 | £9,000 |
| Finishes | £180,000 | £197,000 | (£17,000) |
| Preliminaries | £95,000 | £99,500 | (£4,500) |
| Total | £705,000 | £731,500 | (£26,500) |
Brackets mean an overspend. The total is £26,500 over, 3.8% of budget. The M&E saving of £9,000 hides an overspend of £35,500 elsewhere, so the total alone says too little.
Variance analysis in the cost report
Look at variance on three bases, and always include the third:
- Actual to date against the budget for the same stage. This shows spending, but not what is coming.
- Committed against budget. This shows overspends at the moment of ordering.
- Forecast final cost against budget. This is the number that predicts margin.
For each line over the threshold, record the cause. The common ones are a rate higher than estimated, a quantity higher than estimated, work done outside scope, or timing, where cost has arrived early and will even out. Only the first three change the final margin, so separate them from timing.
Then decide what to do: recover the cost through a Variation, reduce spend on the remaining work, or accept it and update the forecast. A variance that is explained but not acted on is a record of lost margin.
Related terms
Cost to Complete, Cost Forecasting, Cost Value Reconciliation (CVR), Commitments and Liabilities.
Planyard's cost value reconciliation shows budget, committed cost, actual cost and forecast for each Cost Code, so variances are visible by package and not only in the job total.