Earned Value Management: Cost Control for Project Accountants

Accountants with financial oversight of a project or programme are frequently asked a version of the same question: "are we on track?" Earned Value Management (EVM) is the standard technique for answering that precisely, rather than with a gut-feel status update — and it's one of the more directly transferable technical skills between project management and financial control.

Why "on budget" alone doesn't tell you enough

A project that has spent 40% of its budget could be exactly on track, ahead of schedule, or seriously behind — spend alone doesn't distinguish between these. EVM solves this by combining cost and schedule performance into a single framework, so a project accountant can tell not just how much has been spent, but how much value that spend has actually produced relative to the plan.

The three core numbers

EVM starts with three figures at any point in a project: Planned Value (PV), the budgeted cost of the work that was scheduled to be completed by now; Earned Value (EV), the budgeted cost of the work that has actually been completed; and Actual Cost (AC), what has genuinely been spent to complete that work. Everything else in EVM is derived from the relationship between these three.

Variance: are we ahead, behind, over, or under?

Cost Variance (CV = EV − AC) shows whether the completed work cost more or less than planned — a negative number means the project is over budget for the work actually delivered. Schedule Variance (SV = EV − PV) shows whether the project is ahead of or behind its planned schedule in cost terms — a negative number means less work has been completed than was planned by this point.

Performance indices: ratios that forecast, not just describe

The Cost Performance Index (CPI = EV ÷ AC) and Schedule Performance Index (SPI = EV ÷ PV) turn those variances into ratios that are easier to track over time and use for forecasting. A CPI below 1.0 means the project is spending more than the value it's earning; a CPI trending steadily downward across several reporting periods is a much stronger warning sign than a single bad month, and is where EVM earns its keep as an early-warning tool rather than a retrospective scorecard.

Forecasting the final cost

Estimate at Completion (EAC) uses current performance to project the likely final cost of the project, most simply calculated as Budget at Completion (BAC) divided by CPI — in other words, assuming the project continues performing exactly as it has so far. This is a genuinely useful conversation-starter with project sponsors: a EAC materially above the original budget, surfaced early via EVM, gives far more room to act than the same overspend only becoming visible at project close.

Applying EVM without over-engineering it

Full EVM implementation with formal work breakdown structures suits large capital projects well, but the same core logic — comparing planned value, earned value, and actual cost — can be applied at a lighter weight to smaller finance-function projects without the full formal apparatus. The discipline of asking "what have we actually delivered for what we've actually spent, relative to plan" is valuable at almost any project scale.

FAQ

Is EVM only used in construction and capital projects? No — while it originated there, the same technique applies to any project with a defined budget and schedule, including finance-function transformation projects.

What CPI or SPI value should trigger concern? There's no universal threshold, but a sustained trend below 0.9 on either index across multiple reporting periods is generally treated as a serious warning sign worth escalating.

Do I need special software to run EVM? Basic EVM tracking can be built in a spreadsheet; dedicated project management software makes it easier to maintain at scale but isn't a strict requirement.

Cost control and forecasting are core skills for anyone with financial oversight of a project. Explore Learnsignal's Project Management CPD courses, and for the systems-project context these techniques are often applied in, see managing ERP implementation projects in finance.

A simple worked example

Consider a project with a Budget at Completion (BAC) of £100,000, where by the reporting date £40,000 of budgeted work was planned to be complete (PV = £40,000), £35,000 of that work has actually been completed in budgeted terms (EV = £35,000), and £42,000 has actually been spent (AC = £42,000). CPI works out to 0.83 (35,000 ÷ 42,000) and SPI to 0.88 (35,000 ÷ 40,000) — telling the project accountant plainly that the project is both behind schedule and running over budget for the work delivered so far, well before that becomes obvious from the headline spend figure alone.

That combination of a below-1.0 CPI and SPI, sustained over more than one reporting period, is exactly the pattern that should prompt a serious conversation with the project sponsor about scope, budget, or timeline, well before the project reaches its original deadline with no room left to adjust.