Earn value management
Definition
Earn value management
Earn value management is a project control method that measures cost and schedule performance against the same baseline at the same time. It compares the value of work actually completed with what that work was budgeted to cost and when it was due.
The industry standard spelling is earned value management, usually shortened to EVM. Both names describe the same technique, and project documents use them interchangeably.
General budgeting asks whether you are spending to plan. EVM asks the harder question — did the money already spent buy the progress it was supposed to buy?
Budget variance analysis answers the first question well. Earn value management answers cost and schedule at a single cut-off, which is why programme offices prefer it on long builds.
Key takeaways
- Earn value management reads cost health and schedule health from one baseline.
- Three numbers drive it: planned value, earned value and actual cost.
- Progress must have a completion rule set in advance, or earned value becomes opinion.
- United States federal development programmes run the method as a reportable system.
How it works
The method works from three numbers taken at one cut-off date: planned value, earned value and actual cost. Two subtractions fall out of them, and those two tell you cost health and schedule health separately.
| Measure | What it is | How to read it |
|---|---|---|
| Planned value | Budget for the work scheduled by today | The plan |
| Earned value | Budget for the work actually finished | The progress |
| Actual cost | What that finished work really cost | The spend |
| Cost variance | Earned value minus actual cost | Below zero means over budget |
| Schedule variance | Earned value minus planned value | Below zero means behind plan |
| Cost performance index | Earned value divided by actual cost | Below 1.0 means poor value |
The subtraction only works if progress can be measured. Every work package needs a completion rule agreed before the work starts, otherwise earned value turns into an opinion and reporting drifts optimistic.
Earned value is claimed rather than observed, which is the method’s one real weak point. A rule such as half the budget on start and half on written acceptance removes most of the argument, because neither half depends on judgement.
The baseline has to be frozen to mean anything. Every approved change order resets planned value — so uncontrolled scope change quietly destroys the comparison the whole method rests on.
Forecasting is where it earns its keep. Divide the budget at completion by the cost performance index and you get an estimate at completion, which is a far harder number to argue with than a manager’s confidence.
Public buyers treat it as a system rather than a spreadsheet. Under the Federal Acquisition Regulation (FAR), a compliant system is required for major development acquisitions in line with Office of Management and Budget Circular A-11.
Contractors on those programmes file reports every month. The same requirements pass down to their subcontractors under the same rules, rather than stopping at the prime contractor.
The same policy text protects newcomers. As the Legal Information Institute publishes it, offerors are not eliminated from award for lacking a compliant system; they submit a plan to comply with Electronic Industries Alliance Standard 748 instead.
Before the baseline is trusted, buyer and contractor sit down together. That joint review tests whether the schedule, the budget and the scope actually agree with each other, and it surfaces the risks hiding between them.
The method pairs naturally with milestone based pricing, because payment and progress then share one definition and nobody argues about what “half finished” means.
Examples
Earn value management shows up wherever work is long, discrete and funded in stages: software builds, construction, defence programmes and large transformation work. The reporting shape barely changes; only the unit of completed work does.
An offshore software build run as project outsourcing reports earned value by modules that pass test, not by hours billed. Two sprints of effort with nothing shippable earn exactly nothing.
Cost-benefit analysis decides whether a programme should start at all. EVM tells you in month four whether the case that justified it still holds, while there is still time to change course.
Construction and defence programmes usually set the baseline from activity based budgeting, so each work package carries its own cost driver and the earned value figure traces back to a real activity.
Shared service transitions use it too. Moving forty processes offshore in waves gives you natural work packages — and earned value shows whether wave three is paying for the delay in wave two.
Vendors dislike it for a reason — the reporting exposes slippage months before a cheerful status meeting would, which is exactly the point of running it.
A programme can be under budget and still failing. Spend less than planned while finishing less than planned and the cost variance looks healthy, which is precisely why the schedule variance is read beside it.
Related terms
- Budget variance analysis: compares spend against plan, without the schedule half of the picture.
- Milestone based pricing: pays on completed deliverables, giving earned value a contractual definition.
- Project outsourcing: the delivery model where an external team owns a scoped build end to end.
- IT project manager: the role that owns the baseline and reports the variances each month.
- Project coordinator: the role that collects completion evidence feeding the earned value figure.
FAQ
What are the three core numbers?
Planned value, earned value and actual cost, all measured at the same cut-off date. Every variance and index in the method is built from those three figures.
What does a negative cost variance mean?
It means the work finished so far cost more than it was budgeted to cost. The gap tends to widen rather than close, so treat an early negative reading as a forecast instead of a blip.
Is earn value management only for government contracts?
No. Federal programmes made it mandatory, but commercial builders, software teams and shared service programmes use the same arithmetic without the reporting formality. The maths does not care who is paying.
How is it different from tracking spend against budget?
Spend tracking compares money out against money planned. Earn value management adds completed work to the comparison, so you can tell an underspend apart from a delay instead of guessing between them.
What does it need to work?
A baseline with discrete work packages, an agreed completion rule for each one and honest progress reporting. Without the completion rule the figures lose meaning.
Compare delivery models and vetted partners on Outsource Accelerator before you set a project baseline.
Independent
