Earned Value Management: Read Your Project Schedule and Cost Health

A weekly status report says two things: how much has been spent, and how much time has passed. Neither answers the question that matters. You have spent 60% of the budget — is that an overrun or excellent progress? The answer depends on how much work that spending bought — a figure in neither number. Earned value analysis closes exactly this gap. It adds a third dimension measuring completed work in the language of the budget authorized for it, so spending becomes comparable to something other than itself, and lateness and overrun become two separate numbers instead of one vague impression.

Definition and Foundation

Earned value analysis compares the performance measurement baseline to actual schedule and cost performance. Earned value management (EVM) integrates the scope baseline with the cost baseline and the schedule baseline to form the performance measurement baseline (PMB). That integration is the whole idea: not spending alone nor time alone, but all three in one picture.

Three key dimensions are developed and monitored for each work package and control account:

• Planned value (PV) — the authorized budget assigned to scheduled work. It defines the physical work that should have been accomplished by a given point. The total PV for the project is also known as budget at completion (BAC).
• Earned value (EV) — the measure of work performed, expressed in terms of the budget authorized for that work. It is not a fresh valuation of what was produced; it is the budget set aside for it in the first place. The EV measured for a component cannot exceed the authorized PV budget for that component.
• Actual cost (AC) — the realized cost incurred for the work performed during a specific time period. It alone has no upper limit: whatever is spent to achieve the earned value is measured.

Earned value is therefore the bridge between spending and accomplishment. Without it, a status report is a story about two numbers that never meet.

How It Works in Practice

The variances: schedule and cost

Schedule variance is SV = EV − PV. Positive means ahead of schedule, neutral means on schedule, negative means behind. Cost variance is CV = EV − AC. Positive means under planned cost, neutral means on planned cost, negative means over. A variance gives you the size of the deviation in the project's own currency.

The indices: SPI and CPI

The schedule performance index is SPI = EV / PV. An SPI of 1.0 means the project is exactly on schedule — the work actually done so far is exactly the work planned so far. Above 1.0 is ahead of schedule; below 1.0 is behind.

The cost performance index is CPI = EV / AC. A CPI of 1.0 means the project is exactly on budget: the work actually done so far is exactly the same as the cost so far. Above 1.0 is under planned cost; below 1.0 is over. An index beats a variance in one respect: it is a ratio with no unit, comparable across projects of very different sizes.

Note that the reference point differs: variances are read against zero, indices against 1.0. Mixing the two inverts the reading of the number, particularly when a stem offers a value such as 0.9 without naming which measure it belongs to.

Forecasting: BAC, EAC, ETC, VAC

Budget at completion (BAC) is the sum of all budgets established for the work to be performed — the value of the total planned work. Estimate at completion (EAC) is the expected total cost of completing all work, and its formula changes with the assumption behind it:

Estimate to complete (ETC) is the expected cost to finish all remaining project work. Assuming work proceeds as planned, ETC = EAC − AC; otherwise the remaining work is reestimated from the bottom up. Variance at completion is VAC = BAC − EAC, the estimated difference in cost at project completion: positive is under planned cost, negative is over.

Choosing the formula is the skill, not memorizing them. Each encodes an assumption about the future, and an exam stem normally states which applies.

To-complete performance index (TCPI)

TCPI measures the cost performance that must be achieved on the remaining work to meet a specified management goal. Based on budget at completion, TCPI = (BAC − EV) / (BAC − AC). If it becomes obvious that the BAC is no longer viable, it is calculated against the estimate at completion instead: TCPI = (BAC − EV) / (EAC − AC). It reads intuitively: the higher the required efficiency, the harder the goal with what remains.

On the Exam

The 2026 ECO places performance measurement in Domain II, Process, under Task 9 — evaluate project status — whose stated enablers include developing project metrics and analysis, assessing current progress, measuring and updating project metrics, and communicating project status. The financial side sits in Task 6, plan and manage finance, including monitoring financial variations and working with the governance process. Analyzing schedule variation is a stated enabler under Task 8.

The dominant pattern is interpretation rather than calculation: you are given values or indices and asked for the project's state or the next action. Three keys settle most of these items:

• The two indices are independent. Behind schedule but on cost is an ordinary, common condition, and so is the reverse. Collapsing them into a single judgment is precisely the trap the distractors are built around.
• Below 1 is a warning in both, but the warnings differ. SPI below 1 means less work completed than planned to date. CPI below 1 means less value received per unit spent.
• A "what do you do" question has no arithmetic answer. Reading the index is followed by analysis and then communicating status to stakeholders through the governance process — not by jumping to a corrective action without a diagnosis.

It also pays to notice which value the stem is asking for. "What will the project cost in the end" means EAC. "What is left to spend" means ETC. "How far over or under budget will we finish" means VAC. "What efficiency is required from here on" means TCPI.

Detailed Mistakes

Reading SPI as a measure of the delivery date

The schedule performance index is designed to gauge how far from the schedule baseline the project may be, not to protect the due date. The guide draws that distinction explicitly against the buffer protection index (BPI) used in critical chain project management, which is the measure designed to protect the project due date. Reading SPI = 0.95 as "we will deliver 5% late" asks more of the number than it can carry.

Using money spent as a proxy for work done

Earned value is the value of completed work measured by the budget authorized for it; actual cost is what was spent on that work. Their being equal is a coincidence, not a rule. The common version sounds reasonable — "we have spent half the budget, so we are halfway" — and it is exactly what earned value exists to eliminate. Spending is not progress.

Always reaching for the same EAC formula

BAC / CPI is not "the EAC formula." It is one of four, and its condition is that the current cost efficiency is expected to continue for the remainder of the project. If the overrun came from a one-off event that will not repeat, AC + BAC − EV is the appropriate form. If the initial plan is no longer valid at all, there is no substitute for reestimating the remaining work from the bottom up. Selecting the formula is an analytical decision, not a memory lookup.

Where It Does Not Apply

EVM assumes a performance measurement baseline exists — an approved and integrated scope, cost, and schedule. Without that baseline there is nothing for the numbers to be measured against, and they lose their reference. This does not confine EVM to predictive work: the guide notes that tools and techniques exist for applying EVM on projects carried out with an adaptive approach, where effort can be expressed through story points. Planned value becomes the story points estimated for the user stories planned up to a certain date, usually the end of the iteration; earned value represents the story points for the user stories considered done at the end of that same iteration; and actual cost relates to the costs of the team working on those stories during the iteration, usually derived from working hours. The prerequisite, then, is not a particular development approach — it is an agreed reference against which completion can be measured.