Why Earned Value matters
Movement in Earned Value should prompt a check of the underlying volume, mix, timing, and data coverage before the team attributes the change to performance.
- Business question
- How is Earned Value changing, and which operating segments explain that movement?
- Teams that use it
- Project managers, delivery leads, finance, operations, and project sponsors.
- Decisions it supports
- Schedule recovery, budget control, scope choices, staffing, and delivery-risk management.
Earned Value formula
(Actual Progress × Planned Budget)
Formula components
- Actual Progress
- The consistently defined rate or score for the selected population and period.
- Planned Budget
- The monetary amount assigned to planned budget for the same scope and reporting period used by Earned Value.
- Reporting period
- The consistent day, week, month, quarter, or year covered by every input.
How to calculate Earned Value
- Define the business scope, reporting period, and the event or status that qualifies for Earned Value.
- Collect each input in the workbook formula from systems that use the same cut-off and unit.
- Remove duplicates and exclusions according to the documented rule, while retaining a reconciliation count.
- Apply (Actual Progress × Planned Budget) and label the result with its period, unit, and relevant segment.
Earned Value example
A fictional team applies the documented Earned Value factors to the same reporting scope.
- Actual Progress = 16.
- Planned Budget = 8.
- Earned Value = 16 × 8 = 128.
Earned Value is 128.
The result is meaningful only when both factors use compatible units and refer to the same population and period.
How to interpret the result
Compare Earned Value over a consistent cadence and break it down only by segments large enough to support a decision. Review the formula inputs beside the result so teams can distinguish a real operating shift from a denominator or mix effect.
There is no single target that fits every organisation. Interpretation depends on project type, delivery method, scope, complexity, team capacity, and reporting date. Document the comparison group before labelling a result strong or weak.
Common mistakes and limitations
- Inconsistent scope
- Changing the included business units, products, channels, or populations makes the trend look different even when underlying performance is unchanged.
- Mismatched periods
- Formula inputs from different cut-off dates or time windows do not describe one coherent result.
- Reading the headline alone
- A single value can hide offsetting movement across segments, volumes, or contributing formula components.
- Assuming one universal target
- A useful comparison depends on project type, delivery method, scope, complexity, team capacity, and reporting date; use like-for-like internal trends and clearly documented peer groups.