Schedule Performance Index Calculator
Calculate the Schedule Performance Index (SPI) — the ratio of Earned Value to Planned Value — to measure whether a project is ahead of, on, or behind schedule. Use it as a core EVM metric for project status reporting and forecasting completion.
Last updated: May 2026
Compare with similar
About this calculator
Schedule Performance Index (SPI) is a key earned-value management (EVM) metric measuring schedule efficiency. The formula is: SPI = Earned Value / Planned Value. Variables: Earned Value (EV) is the budgeted cost of work actually completed to date; Planned Value (PV) is the budgeted cost of work scheduled to be completed by this date per the original baseline. Edge cases: SPI > 1.0 means the project is ahead of schedule (more work completed than planned); SPI = 1.0 means exactly on schedule; SPI < 1.0 means behind schedule. SPI of 0.85 means you've completed only 85% of the work that should be done by now; SPI of 1.10 means 110%. Interpretation: SPI 0.95–1.05 is normal noise; 0.90–0.95 deserves attention; 0.80–0.90 requires management action; below 0.80 is serious and likely requires scope cuts, schedule extension, or stakeholder escalation. SPI is the time-side companion to Cost Performance Index (CPI = EV / AC); together they provide a complete picture of project performance. Note: SPI converges toward 1.0 as the project approaches completion (because PV eventually equals EV at the end), so it loses sensitivity late in the project. For better late-project schedule diagnostics, use Earned Schedule (ES) methodology: SPI(t) = ES / AT (Actual Time), which more accurately reflects schedule status near completion. Earned Schedule was developed by Walt Lipke around 2003 and is increasingly the preferred approach for sophisticated EVM practitioners.
How to use
Example 1 — Healthy project. Earned Value $450,000 (work completed to date, valued at budget rates), Planned Value $500,000 (work that should have been done by now). Step 1: SPI = 450,000 / 500,000 = 0.90. Verify ✓. SPI of 0.90 means only 90% of planned work is done — about 1 week behind on a 10-week project, or roughly a month behind on a 10-month project. Falls in the "management attention" zone — investigate root cause, plan recovery, and inform stakeholders if the slip is material to overall timeline. Example 2 — Ahead of schedule. Earned Value $320,000, Planned Value $280,000. Step 1: SPI = 320,000 / 280,000 ≈ 1.14. Verify ✓. SPI 1.14 means 14% ahead of plan — could indicate genuine excellent performance OR scope reduction OR aggressive early-loading of easy tasks (which leaves harder work for later when budget is tight). Investigate: are the completed tasks the planned ones, or are easier-than-expected tasks being completed while harder ones lag? "Ahead" can be a leading indicator of trouble if it reflects task cherry-picking.
Frequently asked questions
What's a healthy SPI threshold?
Industry guidance varies but common thresholds: SPI 0.95–1.05 is normal performance with no action needed; 0.90–0.95 is "watch" zone (verify root cause, no immediate corrective action); 0.80–0.90 is "yellow" — needs management attention and recovery plan; below 0.80 is "red" — requires escalation, possible re-baselining, scope reduction or stakeholder communication about schedule slip. The exact thresholds should be calibrated to project criticality: mission-critical projects may have tighter tolerances (yellow at 0.95, red at 0.90); large or complex projects naturally have higher variance and may use looser thresholds (yellow at 0.85). Trends matter as much as absolute values — SPI declining from 1.00 to 0.95 to 0.90 over three reporting periods is more concerning than stable SPI of 0.92 throughout. Government and defense EVM standards (DCMA, NDIA) typically require explanation for any SPI below 0.95 and recovery plans below 0.90.
Why does SPI lose sensitivity near project end?
Mathematically, both EV and PV converge to BAC (Budget at Completion) at the end of the project — by definition, when the project is complete, both equal total budget. As the project approaches 100% complete, SPI naturally trends toward 1.0 regardless of actual schedule performance. A project that finished 3 months late and over budget can still show SPI = 1.0 at completion because EV = BAC = PV. This is the major limitation of traditional SPI. Earned Schedule (ES) methodology, developed by Walt Lipke in 2003, addresses this by measuring SPI in time units rather than dollars: SPI(t) = ES (where on the planned schedule the current EV would have been achieved) divided by AT (actual elapsed time). This time-based version stays meaningful throughout the project and accurately reflects schedule performance near completion. Modern PM tools (Primavera, MS Project Pro) implement Earned Schedule. The original dollar-based SPI is still widely used because it's simpler and the underlying issue only matters in the final 10–20% of project duration where most schedule slip has already happened.
What are the most common mistakes with SPI?
The biggest is treating SPI as if it measured schedule perfectly throughout the project — as discussed, SPI converges to 1.0 near completion regardless of actual schedule. Use Earned Schedule (SPI-t) for late-project schedule analysis. The second is interpreting high SPI (>1.0) as universally good without checking whether easy tasks are being cherry-picked at the expense of harder work scheduled later. The third is using SPI on tasks that don't have clear scheduling baselines (research, exploratory work) — meaningful SPI requires a defensible Planned Value baseline, which agile projects often lack. The fourth is computing SPI in isolation without CPI — a project with SPI 1.10 and CPI 0.75 is over budget and trading cost for schedule, which is a different story than SPI 1.10 with CPI 1.00. The fifth is not understanding what counts as 'earned value' — proper EVM requires objective work measurement (0/100, weighted milestones, equivalent units); subjective '90% done' reporting destroys SPI reliability. The sixth is using SPI for variable-scope agile projects where the baseline shifts continuously; agile uses velocity-based forecasting rather than EVM-style schedule metrics.
When should I NOT use SPI?
Skip SPI for projects without a stable Performance Measurement Baseline (PMB) — without a baseline, there's no Planned Value to compare against. Avoid SPI for agile/iterative projects where scope evolves during execution; agile uses velocity (story points per sprint), burnup/burndown charts, and release confidence rather than EVM metrics. Do not use SPI as the sole schedule metric in the final 10–20% of project duration; switch to Earned Schedule SPI(t) for accurate late-project diagnostics. Skip SPI for highly stochastic projects (research with binary outcomes, drug development, exploration) where 'schedule' is fundamentally uncertain. Do not use SPI as a replacement for active project management — it's a measurement tool that requires action when it warns of problems; tracking SPI without acting on the warnings is theater. And do not compare SPI across very different project types or organizations without normalization; a 0.95 SPI is concerning in a tightly-managed construction project but normal in an exploratory R&D effort.
How does SPI work with CPI for complete project health?
SPI and CPI together form the EVM 'quadrant view' of project health: (1) SPI > 1, CPI > 1: ahead of schedule AND under budget — green, but verify it's not because of inflated estimates; (2) SPI > 1, CPI < 1: ahead of schedule but over budget — common when teams add resources to accelerate, watch for sustainability; (3) SPI < 1, CPI > 1: behind schedule but under budget — common when teams are under-resourced or work is more complex than planned; consider adding resources; (4) SPI < 1, CPI < 1: behind schedule AND over budget — red, requires immediate action (scope cut, recovery plan, escalation). The product SPI × CPI is sometimes called Critical Ratio; values below 0.9 indicate serious trouble regardless of which dimension is failing. Forecast metrics extend this: Estimate at Completion (EAC) = BAC / CPI (cost forecast); time-based EAC(t) projects schedule completion. Mature project organizations track all of these together weekly or monthly and respond systematically when warning thresholds are hit. The discipline of measurement plus action is what makes EVM valuable — measurement without action is theater.