What Is SPI?
Schedule Performance Index (SPI) is an Earned Value Management metric that measures how efficiently a project is progressing against its planned schedule. It tells you whether you are completing work faster or slower than the baseline plan.
The formula is: SPI = Earned Value (EV) / Planned Value (PV)
Earned Value is the budgeted cost of work actually completed. Planned Value is the budgeted cost of work that should have been completed by this point according to the schedule. If your project has an EV of $180,000 and a PV of $200,000, your SPI is 0.90. That means you have completed 90% of the work you planned to have done by now.
An SPI of 1.0 means perfectly on schedule. Above 1.0 means ahead of schedule. Below 1.0 means behind schedule. The metric is defined by the Project Management Institute (PMI) in the PMBOK Guide as one of the two primary Earned Value performance indicators, alongside CPI.
SPI Benchmarks
Like CPI, the benchmark for SPI centers on 1.0. The distance from 1.0 tells you the severity of the schedule variance. Use the tables below to interpret your SPI result and compare against industry norms.
SPI Range Interpretation
| SPI Range | Interpretation | Action Required |
|---|---|---|
| Above 1.2 | Significantly ahead of schedule | Verify estimates. Schedule may have been too conservative. |
| 1.0 - 1.2 | On schedule or slightly ahead | Project is healthy. Continue monitoring. |
| 0.9 - 1.0 | Slightly behind schedule | Minor corrective action. Review task dependencies and resource allocation. |
| 0.8 - 0.9 | Behind schedule | Corrective action required. Consider fast-tracking or crashing critical path. |
| Below 0.8 | Significantly behind schedule | Major intervention needed. Scope reduction or deadline extension likely required. |
Typical SPI by Project Type
| Project Type | Median SPI | Top Quartile SPI | Notes |
|---|---|---|---|
| IT / Software Development | 0.87 | 1.00 | Requirement changes and integration delays are common drivers. |
| Construction | 0.93 | 1.04 | Weather and permitting cause predictable delays. Buffers help. |
| Government / Defense | 0.90 | 0.98 | Approval cycles and compliance reviews slow progress. |
| Manufacturing | 0.95 | 1.06 | Supply chain visibility allows better schedule adherence. |
| Healthcare / Pharma | 0.82 | 0.93 | Regulatory timelines and trial enrollment drive schedule risk. |
Source: PMI Learning Library. Benchmarks are based on aggregated project data from PMI Pulse of the Profession reports and EVM research. Results vary by project complexity and organizational maturity.
How to Calculate SPI
SPI requires two inputs: Earned Value (EV) and Planned Value (PV). Both must be measured at the same reporting date.
SPI = Earned Value / Planned Value
Worked example: An IT department is implementing a new ERP system with a total budget (BAC) of $1,200,000 over 18 months. At the end of month 6, the baseline schedule shows that 40% of work should be complete, but the team has only finished 32%.
- Planned Value (PV) = 40% x $1,200,000 = $480,000
- Earned Value (EV) = 32% x $1,200,000 = $384,000
- SPI = $384,000 / $480,000 = 0.80
- Schedule Variance (SV) = EV - PV = $384,000 - $480,000 = -$96,000
- Estimated Duration = 18 months / 0.80 = 22.5 months
The SPI of 0.80 means the team is completing work at 80% of the planned rate. At this pace, an 18-month project will take about 22.5 months, a delay of 4.5 months. The negative schedule variance of $96,000 represents the dollar value of work that should have been done but has not been completed yet.
SPI vs CPI
SPI and CPI are two sides of the same Earned Value coin. SPI tells you whether you are on time. CPI tells you whether you are on budget. Both use Earned Value as the numerator but divide by different denominators.
| Metric | Formula | Measures | Above 1.0 | Below 1.0 |
|---|---|---|---|---|
| SPI | EV / PV | Schedule efficiency | Ahead of schedule | Behind schedule |
| CPI | EV / AC | Cost efficiency | Under budget | Over budget |
The most common pattern in troubled projects is low SPI combined with low CPI, meaning the project is both late and over budget. But the opposite pattern also occurs. A project can have a high SPI (ahead of schedule) with a low CPI (over budget) when the team is spending extra money to accelerate delivery, a strategy called "crashing" the schedule.
Example: A software development project has an EV of $320,000, PV of $300,000, and AC of $370,000. SPI = $320,000 / $300,000 = 1.07. CPI = $320,000 / $370,000 = 0.86. The project is 7% ahead of schedule but 14% over budget. The team is delivering fast but spending too much to do it. This pattern often appears when overtime or additional contractors are used to hit deadlines.
Why SPI Matters
Schedule delays cascade across organizations. A late project does not just affect the project team. It impacts product launches, revenue targets, customer commitments, and downstream projects. SPI provides an objective, early-warning metric that prevents schedule problems from becoming surprises.
It catches delays before they become crises. A project manager reviewing monthly SPI values can spot a declining trend three to four months before the delay becomes obvious on a Gantt chart. An SPI that drops from 0.98 to 0.95 to 0.91 over three months is a clear signal, even if no single milestone has officially been missed yet. Early detection means earlier corrective action and smaller overall impact.
It provides a common language for schedule discussions. Telling a sponsor "we might be running a bit late" invites debate. Reporting "our SPI is 0.85, which means we are completing work at 85% of the planned rate and will likely need an additional 3 months" provides specificity. The number removes ambiguity and makes resource allocation conversations more productive.
It connects schedule to cost. Because SPI uses Earned Value, it links schedule performance directly to the budget. A schedule variance of -$96,000 means that $96,000 worth of planned work has not been completed. This dollar-denominated schedule metric is more meaningful to financial stakeholders than a simple "two weeks behind" status update.
It supports contract compliance. On government and large commercial contracts, SPI reporting is often a contractual obligation. Missing SPI thresholds (typically an SPI below 0.9) can trigger mandatory corrective action plans, additional oversight, or contract penalties. Consistent SPI tracking keeps projects compliant and avoids these consequences.
How to Improve SPI
An SPI below 1.0 means the project is completing work slower than planned. Here are the most effective strategies to get back on schedule.
1. Analyze the critical path. Not all delays affect the project end date. Focus on activities on the critical path, the longest sequence of dependent tasks that determines the project duration. A one-week delay on a critical path task delays the entire project by one week. A one-week delay on a non-critical task with float may have no schedule impact at all. Prioritize recovery efforts on critical path activities.
2. Fast-track parallel activities. Fast-tracking means performing tasks in parallel that were originally planned sequentially. For example, beginning user acceptance testing on completed modules while development continues on remaining modules. This compresses the schedule without adding cost, but it increases risk because rework may be needed if earlier tasks change.
3. Crash the critical path selectively. Crashing means adding resources to critical path activities to shorten their duration. This always increases cost, so use it selectively. A construction project behind schedule might add a second shift for concrete pouring (the bottleneck activity) rather than adding workers to every task. Focus crashing on activities where additional resources actually reduce duration.
4. Remove blockers and dependencies. Low SPI often comes from tasks sitting idle while waiting for approvals, deliverables from other teams, or external dependencies. Track blocked tasks separately and escalate them aggressively. A software project found that 40% of its schedule delay came from a single API dependency on another team. Resolving that one blocker improved SPI from 0.82 to 0.93 in a single reporting period.
5. Reduce scope on non-critical deliverables. If the schedule cannot be recovered through resource adjustments, negotiate scope reduction with stakeholders. Cut or defer low-priority features that are not on the critical path. A pharmaceutical company behind on a clinical trial timeline deferred two secondary endpoints from Phase 2, reducing the data collection timeline by six weeks and bringing SPI back above 0.95.
6. Re-baseline when the plan no longer reflects reality. If SPI has been consistently below 0.8 for several reporting periods and the original schedule is no longer achievable, consider a formal re-baseline. This resets PV to a new, realistic schedule. Re-baselining should be a last resort and requires stakeholder approval, but it is better than reporting meaningless SPI values against an impossible plan. Document the reasons for the re-baseline and the lessons learned.
This calculator provides estimates for informational purposes only. It does not constitute financial or project management advice. Actual project performance depends on scope, resources, methodology, and organizational factors. Consult your project management office or PMI-certified professionals for precise Earned Value analysis.