Why Cost Variance matters
Cost Variance becomes decision-useful when teams can explain which input moved, where it moved, and whether the definition stayed stable.
- Business question
- What does Cost Variance tell us about performance in the selected scope and period?
- Teams that use it
- Project managers, delivery leads, finance, operations, and project sponsors.
- Decisions it supports
- Schedule recovery, budget control, scope choices, staffing, and delivery-risk management.
Cost Variance formula
EV - Actual Cost
Formula components
- Actual Cost
- The monetary amount assigned to actual cost for the same scope and reporting period used by Cost Variance.
- Measurement scope
- The business unit, product, channel, team, or process included in both the input data and the result.
- Reporting period
- The consistent day, week, month, quarter, or year covered by every input.
How to calculate Cost Variance
- Define the business scope, reporting period, and the event or status that qualifies for Cost Variance.
- Remove duplicates and exclusions according to the documented rule, while retaining a reconciliation count.
- Collect each input in the workbook formula from systems that use the same cut-off and unit.
- Apply EV - Actual Cost and label the result with its period, unit, and relevant segment.
Cost Variance example
A fictional organisation compares the two documented inputs used for Cost Variance.
- Actual Cost = £122,528.
- Total eligible records = £104,000.
- Cost Variance = £122,528 − £104,000 = £18,528.
Cost Variance is £18,528.
The sign and size of the difference should be read against the exact order of the workbook formula and the plan for the period.
How to interpret the result
Compare Cost Variance over a consistent cadence and break it down only by segments large enough to support a decision. Review the formula inputs beside the result so teams can distinguish a real operating shift from a denominator or mix effect.
There is no single target that fits every organisation. Interpretation depends on project type, delivery method, scope, complexity, team capacity, and reporting date. Document the comparison group before labelling a result strong or weak.
Common mistakes and limitations
- Inconsistent scope
- Changing the included business units, products, channels, or populations makes the trend look different even when underlying performance is unchanged.
- Mismatched periods
- Formula inputs from different cut-off dates or time windows do not describe one coherent result.
- Mixing accounting treatments
- Gross and net amounts, recognition dates, allocations, refunds, taxes, and capitalisation rules must be applied consistently.
- Assuming one universal target
- A useful comparison depends on project type, delivery method, scope, complexity, team capacity, and reporting date; use like-for-like internal trends and clearly documented peer groups.