Schedule Performance Index (SPI)

How SPI Works

The Schedule Performance Index is an earned value management metric that measures schedule efficiency by comparing the budgeted cost of work completed to the budgeted cost of work scheduled. The formula is SPI = EV / PV, where EV (Earned Value) is the budget for work actually completed and PV (Planned Value) is the budget for work that should have been completed by now according to the schedule baseline.

An SPI of 1.0 means the project is exactly on schedule. Greater than 1.0 means ahead of schedule: the team has completed more work than planned. Less than 1.0 means behind schedule: less work is done than the plan called for at this point.

SPI is a companion metric to CPI. Together, they provide a complete picture of project health: CPI tells you if you are spending efficiently, SPI tells you if you are progressing on time. A project can be on budget but behind schedule (CPI = 1.0, SPI = 0.85), or ahead of schedule but over budget (SPI = 1.1, CPI = 0.80).

SPI Limitations Near Completion

SPI has a known mathematical limitation: it always converges to 1.0 as the project approaches completion. This happens because both EV and PV approach the Budget at Completion (BAC) as work finishes, regardless of how late the project is. A project that finishes 3 months late will still have an SPI of 1.0 at completion because all the planned work was eventually done.

To address this limitation, some organizations use the Time based SPI (SPI(t)), which compares actual time elapsed to planned time elapsed. SPI(t) does not converge to 1.0 and provides a more accurate schedule efficiency measure in the second half of the project.

How to Calculate SPI

SPI = Earned Value / Planned Value. Example: A project has a total budget of $400,000 over 8 months. At Month 4, the baseline says $200,000 of work should be complete (PV = $200,000). The team has actually completed work budgeted at $170,000 (EV = $170,000). SPI = $170,000 / $200,000 = 0.85. The project is 15% behind schedule in terms of work accomplished versus work planned.

Pair SPI with CPI to understand the full picture. If the same project has AC = $180,000, then CPI = $170,000 / $180,000 = 0.94. The project is both behind schedule (SPI = 0.85) and slightly over budget (CPI = 0.94).

When to Track SPI

Track SPI alongside CPI on any project using earned value management. SPI is most useful in the first half of the project for early schedule variance detection. In the second half, complement SPI with critical path analysis and SPI(t) for more accurate schedule assessment.

SPI is especially valuable on projects with hard deadlines (regulatory submissions, event launches, contract milestones) where schedule performance directly affects project success or triggers penalties.

When SPI Is Less Useful

Beyond the convergence issue, SPI does not distinguish between critical and non critical path delays. An SPI of 0.90 could mean 10% less work is done on non critical tasks (low risk) or 10% less work is done on the critical path (high risk). Always pair SPI with critical path analysis to understand whether the schedule variance threatens the project end date.