SPI in Project Management: Formula, Example, and CPI
What is SPI in project management?
SPI in project management stands for Schedule Performance Index. It is an earned value management metric that compares earned value (EV) with planned value (PV) to show whether the project team is completing work faster or slower than planned.
The schedule performance index formula is:
SPI = EV / PV
An SPI of 1.0 means the project is progressing at the planned rate. An SPI below 1.0 means the project is behind the baseline schedule. An SPI above 1.0 means the project is ahead of the planned schedule in earned-value terms.
PMI describes SPI as a measure of actual progress, measured by earned value, compared with planned progress, measured by planned value. See PMI's explanation of schedule variance and earned value metrics here: The practical calculation of schedule variance.
Key Takeaways
- SPI in project management is calculated as
EV / PV, where EV is earned value and PV is planned value. - SPI below
1.0means the project is behind the baseline schedule in earned-value terms, while SPI above1.0means it is ahead of plan. - SPI and CPI should be reviewed together when cost data is available because schedule efficiency and cost efficiency can point in different directions.
SPI formula and terms
| Term | Meaning | Why it matters |
|---|---|---|
| Earned Value (EV) | The budgeted value of the work completed by the measurement date. | EV shows how much planned work the team has actually earned. |
| Planned Value (PV) | The budgeted value of the work that should have been completed by the measurement date. | PV shows the baseline plan at the same point in time. |
| Schedule Performance Index (SPI) | The ratio of earned value to planned value. | SPI shows schedule efficiency against the baseline. |
| Schedule Variance (SV) | EV - PV | SV shows the schedule gap as a value instead of a ratio. |
| Cost Performance Index (CPI) | EV / AC | CPI adds cost context so teams do not read schedule health in isolation. |
SPI is useful because it gives project managers one compact schedule signal, but it should not replace milestone reviews, dependency checks, or team-level delivery conversations.
How to calculate SPI
To calculate SPI, use the same status date for earned value and planned value.
- Choose the measurement date: For example, the end of week 4 or the close of a sprint.
- Calculate planned value: Determine the budgeted value of work that should have been complete by that date.
- Calculate earned value: Determine the budgeted value of work actually completed by that date.
- Divide EV by PV: Use
SPI = EV / PV. - Interpret the result: Compare the value with
1.0, then review the underlying schedule drivers.
Example:
| Metric | Value |
|---|---|
| Planned Value (PV) | $100,000 |
| Earned Value (EV) | $90,000 |
| SPI calculation | $90,000 / $100,000 |
| SPI result | 0.90 |
An SPI of 0.90 means the project has earned 90 cents of scheduled work for every planned dollar of work by the measurement date. The project is behind schedule unless the baseline, scope, or measurement data is wrong.
How to interpret schedule performance index
| SPI result | Interpretation | Project management response |
|---|---|---|
SPI < 1.0 | The project is behind schedule. | Review blocked work, dependencies, scope changes, and whether the baseline is still realistic. |
SPI = 1.0 | The project is on schedule. | Keep monitoring EV, PV, milestones, and upcoming risks. |
SPI > 1.0 | The project is ahead of schedule in earned-value terms. | Check whether the team is truly ahead, the baseline was too conservative, or quality work is being counted too early. |
SPI is a warning signal, not a full diagnosis. A low SPI tells you the schedule is inefficient against the plan. It does not tell you by itself whether the cause is under-staffing, unclear scope, delayed approvals, weak estimation, quality rework, or dependency risk.
SPI and CPI in project management
SPI, CPI, and schedule variance are often reviewed together because they answer different questions.
| Metric | Formula | Main question |
|---|---|---|
| SPI | EV / PV | Is the project earning scheduled work at the planned pace? |
| Schedule Variance (SV) | EV - PV | How large is the schedule gap in value terms? |
| CPI | EV / AC | Is the project earning value efficiently compared with actual cost? |
| EAC | Forecast formulas vary by scenario | What is the likely final project cost? |
For example, a project can have a low SPI and a strong CPI. That means the team may be spending efficiently but completing less scheduled work than planned. The response is different from a project with both low SPI and low CPI, where schedule and cost performance are both under pressure.
If you are reviewing schedule and cost together, connect this article with the related guides on EAC in project management and CPI project management reporting.
SPI and CPI project management example
| Metric | Formula | Example value | What it says |
|---|---|---|---|
| SPI | EV / PV | 0.90 | The project has earned less scheduled work than planned. |
| CPI | EV / AC | 1.05 | The project is earning value efficiently compared with actual cost. |
| Combined reading | Review SPI and CPI together | SPI low, CPI high | The team may be cost-efficient but schedule-constrained, so the next action should focus on blockers, dependencies, sequencing, or baseline realism. |
This is why SPI and CPI project management reporting should include a short explanation, not just the ratios. Stakeholders need to know whether the project is late, over budget, both, or affected by a measurement issue.
| SPI and CPI pattern | What it usually means | What to investigate |
|---|---|---|
| SPI low, CPI low | The project is behind schedule and cost-inefficient. | Scope growth, rework, estimation quality, staffing, vendor delays, and baseline realism. |
| SPI low, CPI healthy | The project is spending efficiently but earning scheduled work slowly. | Blockers, sequencing, approvals, dependencies, or delayed starts. |
| SPI healthy, CPI low | The schedule may look fine, but the project is costing more than expected. | Overtime, expensive resources, procurement changes, or quality rework. |
| SPI high, CPI high | The project is ahead of schedule and cost-efficient in earned-value terms. | Confirm completion rules, quality, and whether the baseline was too conservative. |
When SPI is useful
Schedule performance index is most useful when a project has a baseline plan, measurable work packages, and a regular reporting cadence. It works especially well for complex projects where simple percent complete updates are too vague for decision making.
Use SPI when you need to:
- explain schedule performance to stakeholders with a repeatable metric
- compare actual work completed with the baseline schedule
- spot schedule risk before the final deadline is missed
- support earned value management reporting
- connect schedule performance with cost performance and forecast updates
SPI is less useful when the project has no reliable baseline, work is not measured consistently, or the team changes scope without updating the plan.
Common SPI mistakes
Reversing EV and PV
The correct schedule performance index formula is SPI = EV / PV. Reversing the formula changes the meaning of the result and can lead to the wrong management response.
Counting partial work too generously
If teams count unfinished work as earned value, SPI can look healthier than the schedule really is. Use clear completion rules for each work package.
Reading SPI without context
SPI does not explain why the schedule moved. Review it with milestone status, dependencies, blockers, workload, quality issues, and scope changes.
Ignoring CPI
A project that is ahead of schedule may still be over budget. A project that is behind schedule may still be financially efficient. SPI and CPI should be reviewed together when cost data is available.
Treating SPI as a team-performance score
SPI measures schedule efficiency against the baseline. It should not be used as a blunt scorecard for individual performance. A poor baseline, blocked dependency, or late stakeholder decision can hurt SPI even when the project team is working effectively.
How to improve SPI
Improving SPI means improving schedule reliability, not just pushing the team to work faster.
- Review the baseline: Confirm that the planned value curve still reflects approved scope and sequencing.
- Find the blocked work: Identify which work packages are behind the plan and why.
- Check dependencies: Look for approvals, inputs, external vendors, or technical constraints that slow earned value.
- Rebalance workload: Move people or work only when the change improves flow without creating new coordination cost.
- Tighten milestone reviews: Review schedule risk before milestone dates, not after.
- Use one shared project view: Keep schedule, ownership, comments, files, and risk signals in a place the team actually uses.
A stronger project timeline and a practical project tracking board make SPI easier to explain because stakeholders can see the work behind the number.
SPI reporting example
Here is a simple SPI update a project manager could share:
As of July 1, the project has planned value of $100,000 and earned value of $90,000, which gives an SPI of 0.90. The main schedule gap is in integration testing, where vendor access arrived later than planned. The team is moving two lower-priority configuration tasks out of the current milestone and adding a daily dependency check until testing is back on track.
This kind of update is stronger than reporting the number alone. It gives the result, the cause, and the corrective action in one short paragraph.
FAQ
Frequently
asked
questions
Related features
Explore the Scrumbuiss features mentioned in this article.
- KPIs
Track project KPIs, dashboard health, delivery analytics, risks, workload, blocker visibility, and stakeholder reporting.
Unlock Success &
Power Up Your Projects
Next to explore
Explore more pages to understand the product suite, common workflows, and evaluation guides.