Skip to content
P6 Schedule Analytics
← Blog

Draft for review. Not yet published or indexed.

Earned value for planners: SPI, SPI(t) and when to trust them

What cost-based SPI stops telling you late in a job, and how Earned Schedule keeps telling the truth.

[FOUNDER NAME] ·

Earned value tends to live with the cost team. But if your programme is resource- or cost-loaded, you already have everything it needs: a budget on each activity, a percent complete, and planned dates. The planner is well placed to read it.

The three numbers#

From these come the two indices everyone quotes: SPI = EV ÷ PV, and CPI = EV ÷ AC. Below 1.0, you're behind plan or over budget.

The trouble with SPI#

Cost-based SPI has a well-known flaw. As a job nears completion, all the planned work is eventually done, so EV climbs to meet PV and SPI drifts back towards 1.0, however late the job is. A project that finishes six months late reports an SPI of 1.00 on its last day.

That makes SPI least useful exactly when people are watching it most closely.

Earned Schedule#

Earned Schedule asks a different question. Not "how much value have we earned?" but "when should we have earned it?".

Take the value earned so far and find the date on the planned value curve when that value was due. That's the earned schedule, ES. Compare it with the actual time elapsed, AT:

SPI(t) doesn't drift back to 1.0. A job running at 88% of the planned rate stays at 0.88 until the day it finishes.

Two forecasts, one question#

On a live programme you'll usually have two forecast finishes. The critical path assumes the remaining work runs at its planned durations. Earned Schedule assumes the job keeps performing as it has so far.

When they disagree, and they often do, the gap is the conversation to have: is there a reason to expect the rest of the job to run better than the first half?

What to watch#