Earned Value Management: The Project Control Method Your PM Software Probably Doesn't Support

Earned Value Management has been written into US Department of Defense contract requirements since the 1960s. It is the standard performance measurement method in aerospace, defence, infrastructure, and large-scale construction. NASA uses it. The UK's Major Projects Authority uses it. ANSI/EIA-748, the standard governing EVM implementation, runs to 32 guidelines covering everything from work breakdown structure to change control.

And the project manager running a €2 million office fit-out or a €500k IT migration has almost certainly never calculated a CPI.

The gap is not methodological. EVM is not conceptually complex. The three core inputs — what you planned to spend, what you actually spent, and what the completed work was worth — are numbers that any project business has in principle. The barrier has been software. EVM requires tracking actual cost at the individual work-package level, and that capability has historically lived inside SAP, Oracle, or specialist tools like Primavera P6 — platforms priced for organisations with dedicated project controls functions, not businesses delivering projects as a commercial service.

That is starting to change. Which makes this a useful moment to understand what EVM actually measures and why it tells you things that standard project tracking cannot.

The Three Core Values

EVM is built on three numbers, each answering a specific question about a project at a point in time.

Planned Value (PV) — also called Budgeted Cost of Work Scheduled (BCWS) — is the budgeted cost of the work you planned to have completed by a given date. If your project has a €200k budget and you planned to complete 50% of the work by week 10, your PV at week 10 is €100k. It does not matter how much you have actually spent. PV is purely a statement of what the plan said should be done by now, expressed in budget terms.

Earned Value (EV) — Budgeted Cost of Work Performed (BCWP) — is the budgeted cost of the work you have actually completed. This is the number that most project managers do not track, and it is the one that makes EVM work. If you have completed 45% of the project scope, your EV is 45% of the total budget — regardless of what you actually spent to get there. You have "earned" that portion of the budget by completing that portion of the work.

Actual Cost (AC) — Actual Cost of Work Performed (ACWP) — is what you actually spent to complete the work that has been done. Not your total spend to date, not your committed costs. The cost of the work that is finished.

These three numbers, taken together, give you the complete picture of where a project stands. Taken individually, they tell you almost nothing useful.

CPI and SPI: What the Numbers Mean

From PV, EV, and AC, you derive the two performance indices that make EVM worth implementing.

Cost Performance Index (CPI) = EV ÷ AC. A CPI of 1.0 means you are spending exactly your budgeted amount to deliver work. Above 1.0 means you are delivering work for less than it was budgeted to cost — you are under budget. Below 1.0 means every euro you spend is returning less than a euro of completed work.

Schedule Performance Index (SPI) = EV ÷ PV. An SPI of 1.0 means the work you have completed matches the work you planned to have completed by now. Above 1.0 means you are ahead of schedule in value terms. Below 1.0 means you have delivered less value than planned.

Take a concrete example. A 20-week office fit-out with a €200k budget. By week 10 — the halfway point — the plan calls for €100k of work to be complete. The team has actually completed 45% of the scope: an Earned Value of €90k. They have spent €115k to get there.

• PV = €100k (what the plan said should be done by now)
• EV = €90k (what was actually done, in budget terms)
• AC = €115k (what was actually spent)
• CPI = 90 ÷ 115 = 0.78
• SPI = 90 ÷ 100 = 0.90

A CPI of 0.78 means that for every €1 spent, the project is only delivering €0.78 of planned work. The project is 28% over budget relative to what it has achieved. An SPI of 0.90 means the project has delivered 90% of the value it should have reached by week 10 — it is behind schedule in output terms.

This combination, identified at week 10, gives the project team six weeks to respond. A CPI of 0.78 found at week 18 leaves almost no room to recover.

Why CPI Matters More Than Schedule Variance

Schedule Variance (SV = EV − PV) measures whether you are ahead or behind the plan in value terms. It is a useful early warning. It is also a number that will always equal zero at project completion — because at the end of the project, the only work left to earn is the work you have done. SV is informative during the project; it becomes uninformative at the end.

CPI does not have this property. Research across large project datasets has consistently found that CPI stabilises relatively early in a project's lifecycle — typically once a project is 15–20% complete — and rarely improves significantly after that point. A CPI of 0.85 at 20% completion is a strong predictor of final cost overrun. A project that is 30% over budget at the halfway point almost never finishes on budget; it typically finishes at a similar or worse ratio.

This predictive stability is why EVM is used in high-stakes project environments. It is not just a report of where you are — it is a forecast of where you are going, based on the performance pattern the project has already established.

Forecasting Final Cost: Estimate at Completion

EVM produces a natural forecast of final project cost, called Estimate at Completion (EAC). There are several formulas depending on your assumptions about future performance:

The most commonly used version assumes that the efficiency you have demonstrated so far will continue for the rest of the project:

EAC = BAC ÷ CPI

Where BAC is the original Budget at Completion. Applied to the fit-out example: EAC = €200,000 ÷ 0.78 = €256,000. If the project continues at the same cost efficiency it has shown in weeks 1–10, it will finish €56,000 over budget.

A more optimistic version assumes future work will be delivered at the originally planned efficiency, and only sunk costs are over budget:

EAC = AC + (BAC − EV)

That gives €115k + (€200k − €90k) = €225,000. This formula is useful when the causes of early overruns have been identified and genuinely resolved. It is less useful when the overrun reflects a systemic efficiency problem — staffing, scope, or planning assumptions — that will persist.

A related metric, To-Complete Performance Index (TCPI), tells you the CPI you would need to achieve from now on to finish within the original budget. TCPI = (BAC − EV) ÷ (BAC − AC) = (200k − 90k) ÷ (200k − 115k) = 110k ÷ 85k = 1.29. The project would need to deliver €1.29 of work for every €1 spent, for the remaining half of the project, to break even on budget. That is almost certainly unrealistic if CPI to date is 0.78. TCPI makes explicit what recovery would actually require.

Why Most PM Software Cannot Do This

The reason EVM has not reached mid-market project businesses is structural. Calculating CPI requires three data points: planned cost by work package, earned value (percent complete times budget), and actual cost by work package. Most project management tools track only one of these, sometimes two. None of them, in combination, support EVM.

Task trackers — Asana, Monday.com, ClickUp — have no concept of budgeted cost per task versus actual cost. They track task completion, comments, and in some cases time logged. But financial cost per task is not a field in their data model. You cannot calculate EV from a task list, because EV requires each task to carry a budget weight, and you cannot calculate AC because the tool does not record actual financial cost.

Jira tracks story points, not financial value. A team that completes 40 story points out of a planned 50 has an SPI-equivalent of 0.80 — but this measures volume of work, not cost performance. Story points were designed to estimate effort for sprint planning, not to represent financial value. CPI from story points is meaningless.

The platforms that have historically supported EVM are Primavera P6, Microsoft Project with the full cost module configured, and enterprise ERP systems with project management capability. All of these carry implementation costs that are hard to justify for a project business turning over €3–10 million annually.

Implementing EVM in Your Project Business

Full EVM implementation — with work breakdown structures, earned value baselines, and monthly reporting at the work-package level — is a significant undertaking. It requires either a system built to support it or substantial manual process around whatever system you have. Neither is where most project businesses should start.

Partial EVM, applied consistently, is considerably more valuable than no EVM. The minimum viable version:

• Budget at the phase level, not just at the project total. A five-phase project with a total budget of €300k should have a budget per phase. This creates the baseline for measuring EV by phase.
• Track actual cost by phase. If you invoice internally or record timesheets against project codes, you have actual cost data — it may require extraction, but it exists.
• Assess percent complete honestly, monthly. Not "we have done half the deliverables" but "what percentage of the total scope value has been delivered?" This requires judgment. It is the hardest part of EVM to systematise without the right tools.
• Calculate CPI monthly. Even a single CPI per project, calculated monthly, gives you a trend line. A project that runs CPI 0.95, 0.91, 0.87 over three consecutive months is telling you something that no status RAG report will show.

Where software matters is in making this calculation continuous rather than monthly. The cost of a monthly EVM exercise is borne by whoever does the extraction and calculation. Systems that track actual cost at the task level and calculate earned value in real time eliminate that cost — and move the signal from a monthly review to something you can see as costs are recorded.

Platforms like Response365 PM have built native CPI and SPI tracking directly into the project management module, calculated in real time as costs are recorded — without requiring a separate ERP layer. At €14.99 per primary user per month, it brings EVM within range of project businesses that have historically been priced out of the tools that support it.

The Bottom Line

EVM is not a methodology for large organisations with dedicated project controls teams. It is a measurement framework that answers the two questions every project manager should be able to answer at any point in a project's life: are we spending efficiently, and are we delivering value on time? The fact that most mid-market project businesses cannot answer these questions is a software problem, not a methodological one.

A project that is consuming budget faster than it is delivering value will not fix itself at month-end review. The CPI tells you that at week six, week eight, week ten — early enough to intervene. That is the entire point. The tools to do this are no longer exclusively the domain of aerospace contractors and infrastructure megaprojects. The question is whether project businesses will use them.

Frequently Asked Questions

What is earned value management in simple terms?

EVM is a way of measuring how well a project is performing financially and in terms of schedule — at the same time. It compares what you planned to spend, what you actually spent, and the financial value of the work actually completed. The result is two key numbers: CPI (are you spending efficiently?) and SPI (are you progressing on time?). Both can signal problems weeks or months before a traditional status review would.

How do you calculate CPI?

CPI equals Earned Value divided by Actual Cost. Earned Value is the budgeted cost of the work you've completed — not what you spent, but what that work was worth in budget terms. Actual Cost is what you actually spent to complete that work. A CPI of 0.85 means you're spending €1.18 for every €1 of planned work delivered.

What is a good CPI for a project?

CPI of 1.0 means you are exactly on budget. Above 1.0 means under budget; below 1.0 means over budget. Research on project performance shows that CPI rarely improves significantly once a project is more than 20% complete — which is why early detection matters. A CPI of 0.9 at 30% complete is a warning; at 70% complete, recovery is extremely difficult.

Do I need special software for earned value management?

You need software that tracks actual cost at the work-package or task level — not just time, but financial cost. Traditional task trackers don't do this. Primavera P6 and Microsoft Project with cost modules do, but they are expensive and complex to implement. Platforms like Response365 PM bring EVM to project businesses at a price point that doesn't require an ERP implementation.