Earned Value Management (EVM): Formulas and Examples

Earned value management is the project control method that tells you, at any point in a project, exactly how much work you planned to do, how much you actually did, and how much you spent doing it. Most project managers can report whether they are over budget or behind schedule. EVM lets you report both at once, with numbers that point to a forecasted final cost, and it does this using three simple values measured against the same baseline.

The technique is decades old, mandatory on US federal contracts above certain thresholds, and backed by the ANSI/EIA-748 standard. It sounds technical, but the core idea is straightforward: compare what you got for the money you spent against what you planned to get.

What Is Earned Value Management?

Earned value management (EVM) is a project performance measurement framework that integrates scope, schedule, and cost data into a single, consistent set of metrics. Rather than tracking cost and schedule as separate concerns, EVM expresses both in the same unit (dollars or hours) so you can compare them directly and forecast where the project will end up.

The method starts with a performance measurement baseline (PMB): a time-phased budget built from your work breakdown structure and your project schedule. Every week or reporting period, you compare three values against that baseline and compute variance and efficiency ratios from them.

Key Facts

• ANSI/EIA-748, first published in 1998 and revised in 2019, defines 32 guidelines that govern EVM systems on US government contracts.
• The US Department of Defense requires EVM on all contracts valued at $20 million or more for development programs, per DoD Instruction 5000.02.
• PMI's PMBOK Guide includes earned value as a core technique under project cost management and schedule management knowledge areas.

The Three Core EVM Values

Every EVM calculation flows from three measured values. Get these right and the rest of the math is just arithmetic.

A few things to notice. PV and EV are both expressed in budget dollars, not real dollars. EV is what the completed work was worth in your original plan, not what it cost. AC is the only value that uses real spending numbers. This is what lets you compare cost and schedule performance on the same scale.

PV comes directly from your project cost estimation and schedule. AC comes from your accounting system. EV is the one you have to calculate: it equals the percent complete of each task multiplied by that task's budget.

EVM Formulas

The eight derived metrics below cover virtually every EVM question a project manager faces. The formulas use only PV, EV, AC, and BAC (Budget at Completion, the total approved project budget).

Reading the indices. CPI and SPI below 1.0 mean you are getting less than a dollar's worth of progress per dollar spent (CPI) or per day elapsed (SPI). Above 1.0 means you are ahead. A CPI of 0.85 means for every dollar spent you are completing only $0.85 of planned work. That gap compounds as the project progresses, which is why EAC (BAC / CPI) often produces a larger overrun than people expect.

TCPI answers the question: "What efficiency do we need on the remaining work to still finish within the original budget?" A TCPI above 1.2 is generally considered unrealistic to recover.

Common Mistakes

Measuring percent complete incorrectly. EV depends entirely on how you report percent complete. Two common traps: the "20/80 rule" (tasks are 20% done the moment they start, 80% when finished) and the "0/100 rule" (nothing counts until done). Both are legitimate simplifications for short tasks. The mistake is mixing methods inconsistently across the project.

Ignoring the performance measurement baseline. EVM only works if PV comes from an approved, frozen baseline. If you re-baseline every time a problem appears, CPI and SPI will always look fine, but you lose all forecast value. Changes should go through formal change control, not silent re-baselining.

Tracking cost but not scope. Some teams know their actual costs but never calculate EV. Without EV you cannot compute CV or CPI. You just know you spent money, not whether you got anything for it.

Confusing SV with time. Schedule Variance is expressed in dollars (or hours), not days. SV = -$50,000 does not mean you are 50 days late. To translate SV into time, you need the planned burn rate for the period.

Applying EVM too late. EVM forecasts are most useful in the first half of a project. By the time you are 80% through, there is not enough remaining work to correct a bad CPI. Start tracking from the first reporting period.

How to Use Earned Value Management

Step 1: Build the performance measurement baseline

Start with your work breakdown structure and break it down to the control account level. Assign a budget (in dollars or hours) to each control account and time-phase that budget across the project schedule. The result is your PV curve, which shows cumulative planned spend across the project life cycle.

Step 2: Establish the completion method for each work package

Decide before work starts how percent complete will be measured for each work package. Short tasks can use 0/100. Longer tasks should use weighted milestones or a physical percent complete method. Document the decision. Changing the method mid-task distorts EV.

Step 3: Collect actuals each reporting period

Pull actual costs from your accounting or time-tracking system for the reporting period. Record them at the control account level, not just the project total. This is your AC.

Step 4: Calculate earned value

For each control account, multiply the approved budget by the percent complete. Sum across all control accounts to get total EV for the period. This step requires discipline: the percent complete must reflect real, verifiable progress, not gut feel.

Step 5: Compute variances and indices

With PV, EV, and AC in hand, calculate CV, SV, CPI, and SPI. Any variance beyond a defined threshold (many teams use 10%) triggers a variance analysis report explaining the cause and the corrective action.

Step 6: Forecast EAC and ETC

Use EAC = BAC / CPI for the most statistically reliable forecast. Some teams use alternative EAC formulas for specific circumstances: EAC = AC + (BAC - EV) assumes future work runs at the planned rate, which is optimistic if the current CPI is poor. For schedule recovery scenarios, also recalculate SPI and check TCPI.

Step 7: Report and take action

Present the indices with trend data, not just a point-in-time snapshot. A CPI that was 0.90 last month and is 0.88 this month is trending in the wrong direction. A CPI that moved from 0.85 to 0.92 shows recovery. The trend matters as much as the current value.

Earned Value Management Example

Suppose a software project has a total budget (BAC) of $200,000 and is scheduled to be 50% complete after three months. At the three-month mark, the team reports 40% complete, and the accounting system shows $110,000 spent.

Now compute the derived metrics:

The picture is clear: the project is both over budget and behind schedule. The EAC of $274,000 represents a 37% cost overrun if the current CPI holds. The TCPI of 1.33 means the team would need to deliver 33% more work per dollar on everything remaining, which is a very difficult recovery target.

This is the kind of early warning EVM delivers. Without it, the project manager might report "we spent $110,000 against a $100,000 plan" and miss the deeper problem: the team is only 40% done, not 50%.

Best Practices

Keep the baseline frozen. Approve re-baselining only when the original scope changes formally. A baseline that moves every quarter cannot anchor meaningful performance measurement.

Report CPI trend, not just the current value. Research by Christensen (referenced in NASA cost estimation guidance) found that a project's CPI rarely improves by more than 10% after the 20% complete mark. If CPI is below 1.0 early, plan for an overrun.

Connect EVM to the critical path. SPI tells you that schedule performance is poor, but it does not tell you which tasks are on the critical path. Always cross-reference EVM data with your schedule network to find the tasks that actually affect the end date.

Integrate with three-point estimation. ETC becomes more reliable when the remaining work packages use range-based estimates rather than single-point estimates. A pessimistic ETC scenario can be calculated by applying the pessimistic cost factor to the remaining BAC - EV.

Right-size the reporting frequency. Weekly EVM on a two-year program generates a lot of noise. Monthly is standard for most projects. Very short projects (under three months) may benefit from weekly tracking, but the overhead of calculating EV must be proportional to the project size.

Automate AC capture. The biggest EVM failure mode in practice is stale actual cost data. If the team is doing manual timesheet collection and reconciling it once a month, the actuals will always lag, and CPI will be unreliable. Connect your project management tool to your accounting or ERP system wherever possible.

Frequently Asked Questions

What is the difference between EVM and traditional budget tracking?

Traditional budget tracking compares actual spending (AC) to planned spending (PV). But it tells you nothing about how much work you completed for that spend. EVM adds earned value (EV), which lets you tell the difference between "we spent more because we did more work" and "we spent more and fell behind."

Can EVM be used on agile projects?

Yes, with adaptation. Agile teams often use story points or story count as the unit for EV instead of dollars. The formulas work the same way. Sprint velocity data maps naturally onto SPI. Some teams combine EVM with agile burn-up charts to get both schedule trending and cost performance in the same view.

What is a good CPI or SPI value?

Above 1.0 means you are ahead of the plan. Below 1.0 means you are behind. In practice, most large projects run a CPI between 0.85 and 1.05 for most of their duration. A CPI below 0.75 at the 25% complete mark is a serious warning sign. Aim for CPI between 0.95 and 1.05 as a healthy range.

When should I use the alternative EAC formulas?

The standard EAC = BAC / CPI is the most statistically validated formula for large programs. Use EAC = AC + (BAC - EV) (assumes future work at planned rate) only if you have strong evidence the past inefficiency was a one-time event, not a systemic problem. Use EAC = AC + a re-estimated ETC when the remaining work scope has changed significantly from the original plan.

Does EVM require special software?

No. The formulas work in a spreadsheet. That said, dedicated project management tools (Microsoft Project, Primavera P6, and others) have built-in EVM calculations. The real requirement is not software but discipline: you need a frozen baseline, accurate percent complete reporting, and timely actual cost data.

---

EVM rewards teams that invest in a solid baseline and honest progress reporting. The formulas are simple. The discipline is not. But once you have CPI and SPI updating each period, you replace project status meetings based on gut feel with numbers that forecast the end date and the final cost before either arrives.

Related reading

• Work Breakdown Structure
• Critical Path Method
• Triple Constraint in Project Management
• What Is a Gantt Chart?
• Project Life Cycle
• Three-Point Estimation
• Project Cost Estimation
• Fast Tracking vs Crashing