Understanding Earned Value Management
Earned value management combines three critical data streams: budgeted cost (what you allocated), actual cost (what you've spent), and earned value (the monetary worth of completed work). Together, these metrics expose whether budget overruns or schedule slippage are occurring in real time.
Unlike simple percentage completion reporting, EVM accounts for the quality and timeliness of work. A task marked 80% complete but costing 20% more than budgeted tells a different story than 80% complete on budget. By tracking these relationships across all project tasks, managers can:
- Spot cost and schedule performance trends before they spiral
- Forecast the final project cost (estimate at completion) with statistical confidence
- Predict when the project will actually finish, independent of the original deadline
- Make corrective decisions backed by objective data rather than gut feeling
EVM works for any project—construction, IT implementation, product launches, or events—as long as you can define tasks, budget them, and measure progress.
Core Earned Value Formulas
EVM relies on four foundational calculations applied to each task, then summed across the entire project:
Planned Value (PV) = Scheduled Progress (%) × Budget
Earned Value (EV) = Actual Progress (%) × Budget
Cost Variance (CV) = Earned Value − Actual Cost
Schedule Variance (SV) = Earned Value − Planned Value
Cost Performance Index (CPI) = Earned Value ÷ Actual Cost
Schedule Performance Index (SPI) = Earned Value ÷ Planned Value
Scheduled Progress— The percentage of the task that should be complete by the reporting date, according to the original planActual Progress— The real percentage of work completed on the task as of the reporting dateBudget— The total budgeted cost allocated to the taskActual Cost— The real amount of money spent on the task to dateEarned Value— The budgeted cost attributed to the actual work completedPlanned Value— The budgeted cost of work scheduled to be complete by nowCost Variance— Positive = under budget; negative = over budgetSchedule Variance— Positive = ahead of schedule; negative = behind scheduleCPI— Ratio of value earned to cash spent; values above 1.0 indicate cost efficiencySPI— Ratio of work earned to work planned; values above 1.0 indicate schedule efficiency
Interpreting EVM Metrics
Once you calculate EVM indicators, patterns emerge:
Cost Variance and CPI. A negative CV or CPI below 1.0 means you're spending more than the value of work completed. If your CPI is 0.8, every dollar spent only yields $0.80 of completed work—a 20% cost efficiency loss. A positive CV or CPI above 1.0 signals cost control.
Schedule Variance and SPI. A negative SV or SPI below 1.0 indicates schedule lag. If SPI is 0.75, you're only completing 75% of planned work per time period. A positive SV or SPI above 1.0 shows you're ahead.
The combined view matters most. A project can be ahead of schedule but over budget, or behind schedule but under budget. EVM lets you see both dimensions simultaneously and make trade-offs consciously. For example, if you're behind schedule (low SPI) but cost-efficient (high CPI), accelerating work may cost less than accepting the delay.
Using EVM Data for Forecasting
The real power of EVM emerges when you use current metrics to forecast the future. Two critical predictions are:
Estimate at Completion (EAC). Assuming your current cost efficiency (CPI) continues, EAC = Total Budget ÷ CPI. If your project is budgeted at $100,000 and your CPI is 0.9, you're likely to spend $111,111 by project end—a $11,111 overrun.
Estimate to Complete (ETC). The remaining work cost, calculated as EAC − Actual Cost spent so far. This helps you decide whether to continue, reallocate resources, or adjust scope.
Revisit these forecasts at each project milestone. Early warnings give you time to intervene. Many organisations require EVM reporting at the end of every major phase or monthly, whichever is more frequent. Over time, your historical CPI and SPI data become invaluable for estimating future projects.
Common EVM Pitfalls to Avoid
Applying EVM correctly requires attention to measurement discipline and interpretation nuance.
- Misaligned progress definitions — Ensure 'actual progress' reflects only genuinely complete work, not merely effort expended or money spent. A task might cost 50% of budget but only be 30% functionally complete. Agree upfront on what 'complete' means for each task type—delivered, tested, approved, installed.
- Ignoring dependencies and quality — EVM captures cost and time, not quality or risk. A task marked 90% complete on budget might have unresolved technical debt. Always pair EVM metrics with quality checks and risk reviews. Schedule variance alone won't tell you if rework will crater the deadline.
- Treating CPI and SPI as independent — Many managers focus only on CPI and ignore SPI (or vice versa). Both trends matter. Low CPI + low SPI means the project is in serious trouble. High CPI + low SPI might signal that accelerating work will blow the budget further. Review them together and understand the cause.
- Forgetting to update estimates regularly — EVM forecasts degrade if task progress data becomes stale. Update actual progress and costs at least monthly, ideally every two weeks on fast-moving projects. Stale data feeds bad decisions. Set a cadence and enforce it across the team.