Earned Value Management (EVM) Explained: Formulas, Worked Example and How to Read the Numbers

Imagine a project with a budget of ₹60 lakh. Halfway through the schedule, you have spent ₹30 lakh. Are you on track? You cannot tell: spending half the money means nothing unless you know how much work you got for it. Earned Value Management (EVM) solves this by comparing three numbers (what you planned to do, what you actually did and what it cost) in common monetary terms. It is a staple of PMP exam preparation and a practical tool on large IT projects.

The Three Core Measures

TermNameMeaning
PVPlanned ValueThe budgeted cost of the work scheduled to be done by now
EVEarned ValueThe budgeted cost of the work actually completed by now
ACActual CostThe money actually spent for the work completed by now

A fourth figure, BAC (Budget at Completion), is the total approved budget for the project.

The Variances and Indices

MetricFormulaInterpretation
Cost Variance (CV)EV − ACNegative = over budget; positive = under budget
Schedule Variance (SV)EV − PVNegative = behind schedule; positive = ahead
Cost Performance Index (CPI)EV ÷ ACBelow 1 = poor cost efficiency; above 1 = good
Schedule Performance Index (SPI)EV ÷ PVBelow 1 = slow; above 1 = fast

Indices are ratios, so they let you compare projects of different sizes. A CPI of 0.8 means you are getting 80 paise of value for every rupee spent.

Forecasting Formulas

MetricFormulaWhen to use
EAC (Estimate at Completion)BAC ÷ CPICurrent cost performance will continue (typical)
EACAC + (BAC − EV)The cause of the variance was a one-off; future work goes to plan
EACAC + ((BAC − EV) ÷ (CPI × SPI))Both cost and schedule performance will affect the rest of the work
EACAC + new bottom-up estimate (ETC)Original estimates are no longer valid
ETC (Estimate to Complete)EAC − ACMoney still needed
VAC (Variance at Completion)BAC − EACExpected final over or underspend
TCPI (To-Complete Performance Index)(BAC − EV) ÷ (BAC − AC)Efficiency needed on the remaining work to meet BAC

Worked Example

An ERP integration project has a BAC of ₹60 lakh. At the end of month six, according to the schedule, 50 per cent of the work should be complete. The team has actually completed 40 per cent of the work and has spent ₹30 lakh.

  • PV = 50% × 60 = ₹30 lakh
  • EV = 40% × 60 = ₹24 lakh
  • AC = ₹30 lakh

Now the calculations:

  • CV = 24 − 30 = −₹6 lakh (over budget)
  • SV = 24 − 30 = −₹6 lakh (behind schedule)
  • CPI = 24 ÷ 30 = 0.80
  • SPI = 24 ÷ 30 = 0.80
  • EAC (typical) = 60 ÷ 0.80 = ₹75 lakh
  • ETC = 75 − 30 = ₹45 lakh
  • VAC = 60 − 75 = −₹15 lakh
  • TCPI = (60 − 24) ÷ (60 − 30) = 36 ÷ 30 = 1.20

Reading the Result

The project is both over budget and behind schedule. At the current efficiency, it will finish ₹15 lakh over budget. To finish on budget, the team would need to deliver ₹1.20 of value for every rupee spent from now on, a 20 per cent improvement over the 0.80 achieved so far. A TCPI that far above the current CPI is a warning that the original budget is probably unachievable without a change in scope, funding or approach. The honest conversation with the sponsor happens now, not at month ten.

Also, a schedule variance in money terms does not by itself tell you which tasks are late. A project can show a favourable SV because non-critical work is ahead while critical-path work lags. Always check the critical path (see Project Scheduling); earned schedule techniques exist to refine this.

How to Measure Earned Value

The hardest part of EVM is deciding how much value has been earned. Common rules:

  • 0/100: value is earned only when the work package is complete. Good for short tasks.
  • 50/50: half is earned at start, half at completion.
  • Weighted milestones: value is earned as defined milestones are met, for example design 20 per cent, build 50 per cent, test 80 per cent, done 100 per cent.
  • Percent complete: subjective, so use with care. People tend to report a task as 90 per cent complete for a long time.

Prefer objective completion rules agreed in advance.

EVM and Agile Projects

EVM assumes a stable baseline, which sits uncomfortably with evolving scope. Agile projects often use burnup charts, velocity and throughput instead, but EVM can still be adapted by treating the release plan as the baseline and story points delivered as earned value. See Scrum Metrics Explained.

Common Mistakes

  • Confusing EV with AC. EV is value of work done at budgeted rates; AC is actual money spent.
  • Using subjective percent-complete figures, which inflate EV.
  • Reading SV in isolation from the critical path.
  • Ignoring the trend: a CPI that is falling month by month is worse news than a steady 0.9.
  • Calculating EVM numbers but never acting on them.
Key takeaways
  • EVM compares planned value, earned value and actual cost in money terms.
  • CV = EV − AC; SV = EV − PV; CPI = EV ÷ AC; SPI = EV ÷ PV.
  • The usual forecast is EAC = BAC ÷ CPI; TCPI shows the efficiency needed to hit the budget.
  • Use objective completion rules and watch trends, not single readings.

Related Lessons