What Earned Value Management Actually Measures
Earned value management answers one integrated question that separate schedule and budget reports cannot: for the money actually spent, how much planned work did we really get? A Gantt chart shows dates slipping and a ledger shows money leaving, but neither connects the two. EVM prices all completed work at its original budgeted rate, which makes schedule and cost directly comparable in the same units — dollars.
The naive alternative — comparing percent of budget spent against percent of work done — breaks quickly. If a project has spent 45% of its budget but finished only 30% of the work, those two percentages hint at trouble, but they cannot tell you the size of the gap in dollars, the required future efficiency, or a defensible forecast of the final bill. EVM can, from the same raw inputs.
The method dates to the US Department of Defense's cost/schedule control systems of the 1960s and is now codified in ANSI/EIA-748, with mandatory use on major federal contracts above defined thresholds. Software teams often reach for a burndown chart calculator for sprint-level progress instead; earned value covers the same ground for budgeted, dollars-based work at any scale.
The Three Base Metrics: PV, EV, and AC
Planned value (PV) is the budgeted cost of work scheduled through the status date. On the default $100,000 project that is supposed to be 40% complete today, PV = $100,000 × 0.40 = $40,000. PV comes straight from the baseline — it moves only with the calendar, never with performance, which is exactly what makes it a stable reference point.
Earned value (EV) is the budgeted worth of work actually performed: the actual percent complete times BAC. The team has finished 30% of the scope, so EV = $100,000 × 0.30 = $30,000. Notice EV is priced at budget rates, not what the work really cost — actual cost enters separately, and that separation is what lets the ratio diagnostics work.
Actual cost (AC) is the money genuinely booked against the project: $45,000 so far in the default scenario, including labor, materials, and committed subcontracts. The denominator anchoring all three metrics is BAC itself, the total approved budget — if that baseline is soft, every derived number inherits the softness. A business budget calculator helps set a defensible BAC before the project starts.
Schedule Variance and the Schedule Performance Index
Schedule variance is SV = EV − PV. The default project shows SV = $30,000 − $40,000 = −$10,000: ten thousand budget-dollars of work that should exist by now does not. Negative SV means behind schedule, positive means ahead, and unlike a slipped milestone date, SV quantifies the shortfall in the same currency as the budget.
The schedule performance index converts that variance into a rate: SPI = EV ÷ PV = 30,000 ÷ 40,000 = 0.75. The team is completing planned work at 75% of the baseline pace, so if nothing changes, calendar-driven deliverables will land roughly a third later than the work-content behind them suggests. An SPI of 1.00 is the boundary; 0.95–1.05 is ordinary noise on well-run projects.
SPI has a known blind spot: it counts all earned work equally, including work far from the critical path. A team can post a healthy SPI by finishing easy off-path tasks while the one task that gates the finish date sits untouched. Cross-check the slack time calculator to see which tasks carry float and which ones actually move the end date, and a deadline calculator to translate the pace gap into revised delivery dates.
Cost Variance and the Cost Performance Index
Cost variance is CV = EV − AC. The default project shows CV = $30,000 − $45,000 = −$15,000: the project has paid $45,000 for what the baseline prices at $30,000. Because both figures use budget rates for the work side, the variance is a clean measure of money over- or under-spent relative to progress, undistorted by rate games.
The cost performance index normalizes it: CPI = EV ÷ AC = 30,000 ÷ 45,000 = 0.67. Each dollar spent is buying 67 cents of planned work. Rules of thumb used across government and construction programs treat 0.90–1.10 as normal operating range, 0.80–0.90 as a formal concern requiring documented recovery plans, and below 0.80 as structurally broken estimates or execution.
CPI also stabilizes fast — research on large federal programs found CPI is largely locked in by the 20%-complete mark, which makes early readings disproportionately valuable. Startups and funded teams watch the same idea through a burn rate calculator expressed as runway months; CPI is burn-rate thinking applied per unit of delivered work rather than per month.
Forecasting the Finish: EAC, ETC, and VAC
Estimate at completion (EAC) projects the final bill. The three standard methods disagree usefully on the same data. Default BAC ÷ CPI gives $100,000 ÷ 0.67 = $150,000, assuming the 0.67 efficiency persists. The one-time-overrun method (AC + remaining work at budget) gives $45,000 + $70,000 = $115,000. The schedule-pressure method, dividing remaining work by SPI × CPI, gives $185,000 because being late is itself costing money here.
Estimate to complete (ETC = EAC − AC) is what still needs funding: $105,000 under the default method, $70,000 under the one-time method, $140,000 under the pessimistic one. Variance at completion (VAC = BAC − EAC) summarizes the damage for sponsors: −$50,000 at default, −$15,000 to −$85,000 across the method range. Presenting that range honestly beats a single fake-precise number in every steering committee.
EAC becomes real the moment it hits funding conversations — remaining budget, change requests, draw schedules. Laying the forecast against scheduled receipts with a cash flow calculator shows when the project runs its account dry, which is often weeks before the finish-date problem arrives. Teams that reforecast EAC every cycle catch the inflection while corrective options still exist.
TCPI: The Efficiency Bar for Finishing on Budget
To-complete performance index, TCPI = (BAC − EV) ÷ (BAC − AC), is the cost efficiency required on every remaining dollar to land exactly on the original budget. The default project needs (100,000 − 30,000) ÷ (100,000 − 45,000) = 70,000 ÷ 55,000 = 1.27. From today forward, each dollar must buy $1.27 of planned work — against a demonstrated CPI of 0.67.
That gap is the whole diagnostic. A $500,000 project at 50% complete with $300,000 spent shows CPI 0.83 but TCPI 1.25 — the team must instantly jump from 83 cents of work per dollar to $1.25 and hold it for half the project. Program-management literature puts the practical ceiling near 1.10; beyond that, history says the recovery does not happen and a re-baseline with honest new targets costs less credibility than a promised miracle.
TCPI also gives clean language for escalations. Instead of arguing about effort, report the two numbers: current efficiency CPI versus required efficiency TCPI. Management can then choose — fund the EAC, cut scope, or re-baseline — knowing exactly what each path assumes. TCPI below 1.00, for comparison, means the project can coast and still beat budget, which is the quiet signal to pull money forward or raise the stretch goals.
Reading the Numbers Together
Single metrics mislead; pairs of them diagnose. An $800,000 project at 25% planned and 25% complete with $220,000 spent posts SPI 1.00 — perfectly on schedule by earned value — while CPI 0.91 and EAC $880,000 show the cost engine bleeding. Anyone reporting only 'on schedule' from SPI has missed an $80,000 forecast overrun hiding one column over.
The reverse quadrant is just as instructive: a $300,000 project at 45% complete against 30% planned, having spent $150,000, shows SPI 1.50 with CPI 0.90 and EAC $333,333. The team is racing ahead and paying a premium to do it — overtime, expediting, extra hands. Half the budget is gone at 45% of the work, so the finish line costs $33,333 more than planned despite the glowing schedule index. Production-paced teams can cross-check delivery velocity with a cycle time calculator to see if the pace premium is even buying throughput.
Because SPI and CPI are ratios normalized to 1.00, they compare across projects of any size — a portfolio review can rank a $2 million build against a $40,000 website rebuild on identical axes. Agencies doing client work get the same leverage by feeding utilization data through a billable hours calculator, then treating revenue per earned dollar as the CPI analogue. The pattern to institutionalize: variances say what happened, indices say how bad relative to plan, and forecasts say what happens next if nothing changes.
Reporting Cadence and Common Pitfalls
Run the numbers on a fixed cadence — monthly on large programs, biweekly on shorter ones — with a frozen status date, one percent-complete rule, and a matching cost cutoff. The value compounds in the trend lines: CPI sliding 0.98 → 0.94 → 0.91 over three cycles tells a story no single snapshot can, and the slope lets you act while the TCPI is still recoverable rather than after it passes 1.3.
Three pitfalls corrupt the data more often than math errors do. Percent-complete bias inflates EV when teams report optimistic progress. BAC creep — quietly raising the budget to absorb overruns — resets every index toward 1.00 and erases history. Cost lag from invoices arriving months after the work books a fake CPI above 1.0 early in a project, which then reverses violently; committed-cost accruals fix most of it.
Finally, close the loop with portfolio decisions: an EAC that keeps climbing while TCPI sits above 1.10 is the documented signal to kill or re-scope a project before it consumes its whole VAC and more. Comparing recovered EACs against capital alternatives through an ROI calculator turns earned value from a reporting ritual into the input for kill/fix/fund calls — which is what the DoD analysts who invented the method were actually after.