Project Cost Control Is Not a Report. It Is a Discipline.

Earned Value Management (EVM) & Cost Value Reconciliation (CVR)

Most cost overruns are not discovered. They are revealed, usually months after the point where anything could have been done about them. By the time a project reports a variance at final account stage, the money is already spent, and the only conversation left is who is responsible.

This is preventable. The tools to know exactly where a project stands, on cost and on schedule, at any given week, are not complicated. What follows is the discipline behind them, and how it applies to a project from mobilisation through to handover.

1.0 The framework: Earned Value Management (EVM)

Every EVM calculation starts from one reference point:

• Budget at Completion (BAC): the original total approved budget for the entire project.

From there, EVM compares three figures at the same point in time: what was planned, what has actually been delivered, and what it has actually cost to deliver it.

• Planned Value (PV): the budgeted cost of the work that should be complete by this point in the schedule.

PV = Planned % Physical Progress × BAC

• Earned Value (EV): the budgeted cost of the work actually completed at this point in time.

EV = Actual % Physical Progress × BAC

• Actual Cost (AC): what has genuinely been spent to reach that point.

Together, these four figures, tracked consistently, are the foundation for everything a management team actually needs to know about a project’s financial health.

2.0 Variances: What Is Actually Happening

A variance is the first signal that a project has moved off course, the raw gap between what was planned and what has actually happened, before that gap is expressed as a ratio.

• Cost Variance (CV):

CV = EV − AC

A negative result means the project is spending more than the value it has delivered.

• Schedule Variance (SV):

SV = EV − PV

A negative result means the project’s progress is behind where it should be.

Variance confirms that a gap exists. The indices that follow measure its magnitude, and reveal whether that magnitude is widening or holding steady.

3.0 The Indices That Matter to Management

• Cost Performance Index (CPI)

CPI = EV ÷ AC

A CPI of 1.0 means the project is spending exactly what the completed work is worth. Below 1.0, every unit of currency spent is buying less than it should. A CPI of 0.85 does not simply mean a project is over budget, it means that for every unit spent, only 85 percent of that value has actually been delivered. Across a large contract, that gap compounds quickly, and it compounds silently if nobody is watching for it.

• Schedule Performance Index (SPI)

SPI = EV ÷ PV

The same logic, applied to time. An SPI of 0.80 means the project has achieved only 80 percent of the progress it should have reached by this point, a shortfall that tends to compound further as remaining activities queue up behind an already delayed programme. Because SPI is calculated in cost terms rather than calendar terms, it frequently flags a schedule problem before the programme itself makes it visible, giving management an earlier signal than a Gantt chart update alone would provide.

4.0 Cost Value Reconciliation (CVR)

Where Cost Variance measures earned value against actual cost on a physical-progress basis, Cost Value Reconciliation operates one level up, the periodic commercial exercise of comparing actual value certified or invoiced against actual cost incurred, to confirm real margin, not assumed margin. Run monthly rather than only at milestone or final account stage, CVR is what catches a margin quietly eroding long before it shows up as a loss on a closing statement, giving management the chance to respond while the contract is still live, not once it is closed.

5.0 Forecasting: Where This Becomes Genuinely Useful to Decision-Makers

Knowing where a project stands today is necessary. Knowing where it will end up is what actually protects budget and reputation.

• Estimate at Completion (EAC): the revised total cost forecast, based on performance to date.

EAC = AC + ((BAC − EV) ÷ (CPI × SPI))

This formula assumes that both current cost efficiency and current schedule performance will continue to affect the remaining work, a more honest forecast than assuming the rest of the project will simply perform better than the part already measured. This is the statistical approach to forecasting, projecting forward from performance to date.

An alternative, bottom-up approach has the project team re-estimate the remaining scope directly, producing ETC first, with EAC then derived as AC + ETC. The statistical method is faster and suited to regular reporting cycles; the bottom-up method is more accurate when conditions have changed enough that historical performance is no longer a reliable guide to what remains.

• Estimate to Complete (ETC): what it will cost to finish the remaining scope.

ETC = EAC −  AC

• Variance at Completion (VAC): the gap between the original budget and the current forecast.

VAC = BAC − EAC

VAC is the number that should reach management in a scheduled review, not the number they discover on their own at the end of a project.

6.0 Applying This Across the Project Lifecycle

At tender and baseline stage, cost control begins before mobilisation. BAC must be built on rates that reflect genuine cost, not aspirational pricing. A cost control system built on an unrealistic baseline will only ever measure how wrong the baseline was.

During execution, PV, EV, and AC are tracked on a consistent cycle, weekly or monthly, never less frequently than that. CPI and SPI are reviewed at every cycle, not only when something already feels wrong, and CVR is run on the same rhythm to confirm that certified value continues to hold up against actual cost. Variance is addressed while it is still a five percent drift, not once it has become a structural problem.

At close-out, final account preparation reconciles actual cost against actual value delivered, and captures what the CPI and SPI trend actually revealed, insight that feeds directly into the baseline of the next project, not only the closing file of this one.

7.0 The Bottom Line

Cost control is not about producing a number for a report. It is about knowing, at any given week, exactly where a project stands against its budget, having enough lead time on any variance to act before it becomes irreversible, and trusting the forecast enough to bring bad news to management early rather than late. The projects that stay on budget are not the ones that got lucky. They are the ones where someone was tracking earned value against actual cost, reconciling it against certified value, and forecasting where it would all land, every week, not only when management asked for an update.