Schedule Performance Index: Formula, Examples, & Tips
SPI Overview: The schedule performance index measures project progress against a planned schedule and indicates overall project health.
Importance: SPI provides early warning of schedule issues, which helps with financial visibility and objective reporting.
Recovery Steps: When SPI drops below one, some recovery steps you can take include root cause analysis, resource reallocation, and re-baselining.
The schedule performance index (SPI) tells you whether your project is keeping pace with the project plan or drifting off track. When deadlines tighten and stakeholders want progress, SPI gives you a way to measure schedule health, explain delays, and decide what to fix (and it’s easily calculated with project management software).
I’m breaking down the formula, examples, interpretation, and practical recovery steps so you can calculate this metric quickly, create clearer forecasts, and make better project decisions.
What Is the Schedule Performance Index?
Schedule performance index is a ratio that measures whether a project's actual progress matches its planned schedule. It’s an indicator of project health, and it’s part of the earned value management (EVM) framework, which integrates scope, schedule, and cost data into a unified set of metrics and KPIs.
Unlock for Free
Create a free account to finish this piece and join a community of forward-thinking leaders unlocking tools, playbooks, and insights for thriving in the age of AI.
Have an account? Log In
Why Schedule Performance Index Is Important
SPI is important because it acts as an early warning system and lets you spot a downward trend before it becomes a bigger problem.
Here’s how else SPI delivers value:
- Financial visibility: Schedule delays often increase costs through additional labor, extended vendor contracts, and potential penalties. SPI helps you identify schedule-related budget risks before they become expensive problems.
- Objective reporting: SPI replaces subjective progress updates with a measurable project performance indicator. A concrete number communicates schedule health far more clearly than vague status reports.
- More accurate forecasting: By tracking efficiency over time, SPI helps you project realistic completion dates instead of relying on project timelines that don’t reflect reality.
- Better decision-making: Consistent SPI trends provide data-driven insight into whether recovery actions, resource changes, or schedule adjustments are necessary.
SPI Formula and How to Calculate It
The SPI formula is: SPI = Earned Value (EV) ÷ Planned Value (PV)
Earned value is the budgeted cost of the work you've actually completed. It tells you how much budget you should have spent based on the work that’s been completed so far.
Planned value is the budgeted cost of the work you were supposed to have completed so far. It shows the portion of the total budget that should have been earned according to your baseline schedule.
How to Calculate SPI
Here are the steps to follow to calculate SPI:
Imagine you're managing a software project with a total budget of $200,000 over six months. You're now at the three-month mark.
- Determine PV: According to your baseline, you planned to complete 50% of the work by month three. That means PV = $200,000 × 0.50 = $100,000.
- Determine EV: After reviewing actual deliverables, your project team has completed 45% of the total scope. That means EV = $200,000 × 0.45 = $90,000.
- Calculate SPI: Divide EV by PV. SPI = $90,000 ÷ $100,000 = 0.90.
How to Interpret SPI
Your SPI will either be below 1, above 1, or exactly 1. Here’s what each result means:
- SPI < 1: The project is behind schedule (i.e. you’ve completed less work than you expected)
- SPI > 1: The project is ahead of schedule (i.e. you’ve completed more work than you expected)
- SPI = 1: The project is right on track (i.e. you’ve completed exactly as much work as you expected)
| SPI Range | Status | What It Signals | Recommended Action |
|---|---|---|---|
| Above 1.15 | Significantly ahead | Possible scope overestimation or premature task completion | Audit completion criteria; verify quality standards are being met |
| 1.01 – 1.15 | Ahead of schedule | Genuine schedule efficiency gains or favorable conditions | Review scope; consider reallocating resources to struggling projects |
| 0.95 – 1.00 | Slightly behind | Minor drift, often recoverable | Monitor closely; identify specific lagging tasks |
| 0.85 – 0.94 | Behind schedule | Systemic issue likely present | Conduct root cause analysis; implement corrective action |
| Below 0.85 | Significantly behind | Major schedule risk; recovery requires intervention | Escalate to leadership; evaluate re-baselining or scope reduction |
SPI Examples
Here are three scenarios showing how SPI plays out in real project situations.
Example 1: Behind Schedule (SPI < 1)
A construction team is building a new office space. The total construction project budget is $250,000 over five months. At the two-month mark, the plan called for $100,000 worth of work to be completed. Due to permit delays, only $80,000 worth of work has been finished.
SPI = $80,000 ÷ $100,000 = 0.80
The team is working at 80% of the planned pace. If this rate holds, the project will take longer than five months unless corrective action is taken. The project manager should investigate the root cause and consider options like adding crew members or adjusting the sequence of work.
Example 2: Ahead of Schedule (SPI > 1)
An IT team is migrating servers to a cloud platform. The project budget is $150,000 over four months. At month two, the plan anticipated $75,000 in completed work. Because the team automated several migration tasks, they've completed $90,000 worth of work.
SPI = $90,000 ÷ $75,000 = 1.20
The project SPI is 120% of the planned rate. The project manager should verify that the pace isn't compromising quality or skipping steps, whether the original scope estimates were too generous, or whether work is being marked complete before it's truly done.
Example 3: On Schedule (SPI = 1)
A marketing agency is running a six-month campaign launch with a total budget of $120,000. Three months in, the plan called for $60,000 in completed deliverables, and the team has produced exactly that amount.
SPI = $60,000 ÷ $60,000 = 1.00
The project is on schedule. The team should maintain their current approach and continue monitoring SPI at each reporting period to catch any emerging drift.
How to Use SPI in Practice
SPI is most valuable when you track it over time. A single data point tells you where you stand, but a trend line tells you whether things are getting better, getting worse, or holding steady. Plot SPI at each reporting period on a simple line chart. If you see a consistent downward slope, you know something systemic is happening.
Here’s how to get back on track when SPI drops below 1.0:
- Run a Root Cause Analysis: Identify which tasks are behind and why. Is it a resource issue, a dependency problem, or an unrealistic baseline? Dig into your work breakdown structure and look at task-level deviations rather than the aggregate SPI number.
- Fast-Track or Crash the Schedule: Fast-tracking means running tasks in parallel (which increases rework risk), and crashing means adding resources to shorten task durations (which increases cost).
- Re-Baseline When Justified: If the schedule was flawed or if major scope changes have occurred, the baseline can create misleading SPI values. Re-baselining resets the measurement, but re-baselining too often erodes accountability and makes analysis tough. If the team is simply underperforming, re-baselining just hides the problem.
- Reallocate Resources or Negotiate Scope: Sometimes the fastest path to get back on track is to shift people from lower-priority tasks or reduce scope. This requires stakeholder alignment, but it's often most practical when schedule recovery through overtime or parallel execution isn't feasible.
Schedule Performance Index vs Related EVM Metrics
SPI can be used alongside several other earned value metrics.
Schedule Variance (SV)
Schedule variance is similar to SPI, but uses dollar terms instead of a ratio. SV gives you an absolute value in financial terms, while SPI gives you a ratio that's easier to compare across projects. I find SPI more useful for portfolio-level reporting because a $10,000 variance means very different things on a $50,000 project versus a $5,000,000 project.
Formula: SV = EV − PV
If your EV is $90,000 and your PV is $100,000, your SV is −$10,000. That negative number means you're $10,000 worth of work behind schedule.
Cost Performance Index (CPI)
The cost performance index measures whether project progress matches planned costs. While SPI tells you how well you're keeping to the schedule, CPI tells you how well you're keeping to the budget. Using them together gives you a complete health check, because a project can be on schedule but over budget, or under budget but behind schedule.
Formula: CPI = EV ÷ Actual Cost (AC)
What’s Next?
Knowing your schedule performance index is only useful if you can act on what it reveals. Join The Digital Project Manager community to access practical templates, expert resources, and real-world guidance that help you keep projects on track and make better delivery decisions.
