SPI Calculator
The Schedule Performance Index answers one question in earned value management: is the work getting done at the pace the plan promised? This calculator divides earned value (EV) by planned value (PV) and prints the SPI to two decimals, with a verdict badge that reads the result as behind, on or ahead of schedule.
SPI prints to two decimal places, exactly as the division produces it. The badge reads the same value: below 1.00 behind schedule, exactly 1.00 on schedule, above 1.00 ahead of schedule. The badge reads the exact, unrounded SPI, while the number is rounded to two decimals: a true SPI of 0.999 displays as 1.00 but still reads Behind schedule, and 1.001 displays as 1.00 but reads Ahead of schedule.
Quick Answer
SPI = EV ÷ PV. With earned value of $46,000 against planned value of $50,000, SPI = 46,000 ÷ 50,000 = 0.92, and the project is behind schedule: it has earned 92 cents of planned work for every planned dollar, a schedule variance of SV = EV − PV = −$4,000. Enter your own EV and PV above for your project’s index.
Key takeaways
- SPI compares work earned to work planned at the same status date. Both inputs are in budget dollars, not days, which is the index’s biggest limitation.
- Below 1.00 is behind, exactly 1.00 is on plan, above 1.00 is ahead. There is no separate “good” threshold in the standard itself.
- This tool takes EV and PV directly. If you only have percent complete and a total budget, the worked example below shows how to get both inputs in two multiplications.
- Late in a project, SPI drifts back toward 1.00 even when the finish date slips, because EV eventually catches PV. Read the limitations section before trusting a late-project SPI.
- Quick Answer
- How to use the SPI calculator
- The SPI formula and where EV and PV come from
- Worked example: SPI of 0.92 on a mid-project status check
- Reading your SPI: the three bands
- SPI vs CPI: schedule pace against cost efficiency
- The late-project trap: why SPI drifts back to 1.00
- What competing calculators miss
- Frequently asked questions
- Add This Calculator to Your Website
- References
How to use the SPI calculator
Enter the earned value and planned value from your latest status report, both measured at the same date, and click Calculate.
- Enter Earned Value (EV). The budgeted cost of the work actually performed (BCWP in the older terminology). Use the value your EVM system reports for the status date, not the amount spent.
- Enter Planned Value (PV). The budgeted cost of the work scheduled (BCWS): what the baseline plan said should be complete by that same date.
- Click Calculate. The index prints to two decimal places and the badge reads it as Behind schedule, On schedule or Ahead of schedule.
Both inputs must be in the same units and cover the same scope. Mixing one team’s EV with a whole programme’s PV produces a confident, meaningless number. The units cancel in the division, so dollars, pounds, euros or labour hours all work, as long as EV and PV match.
The SPI formula and where EV and PV come from
SPI = EV ÷ PV, the ratio of work accomplished to work planned, as defined in the Project Management Institute’s earned value standards and summarised in PMI’s guide to reading earned value numbers.
Most status reports do not hand you EV and PV directly. You build them from the budget at completion (BAC), the total approved budget for the work:
- EV = actual % complete × BAC. A $200,000 project that is genuinely 25% complete has EV = 0.25 × 200,000 = $50,000.
- PV = planned % complete × BAC. If the plan said 30% should be complete by now, PV = 0.30 × 200,000 = $60,000.
- SPI = 50,000 ÷ 60,000 = 0.83. The project is earning work at 83% of the planned pace.
The honest % complete is the hard part. Percent-complete claims based on effort spent, rather than on measurable finished work, inflate EV and flatter the SPI. The U.S. Government Accountability Office’s Cost Estimating and Assessment Guide makes the same point at programme scale: earned value only means something when the baseline underneath it is disciplined. If you need EV, PV, both indices and the forecasting figures computed together from BAC and percent complete, the earned value analysis calculator runs the full suite; this page is the direct index for teams that already track EV and PV.
Worked example: SPI of 0.92 on a mid-project status check
A project team reports earned value of $46,000 against planned value of $50,000 at the end of the current period. The calculator returns 0.92, and the supporting figures check out by hand:
- Divide: SPI = 46,000 ÷ 50,000 = 0.92 exactly, so the two-decimal display loses nothing.
- Schedule variance: SV = EV − PV = 46,000 − 50,000 = −$4,000. The team is $4,000 of planned work short of where the baseline said it would be.
- Pace reading: 0.92 means the work is being earned at 92% of the planned rate. Recovering the plan needs roughly an 8.7% pace increase on the remaining schedule work (1 ÷ 0.92 = 1.087), not an 8% one, a distinction status meetings routinely get wrong.
Earned value vs planned value, worked example
The $4,000 gap is value, not time. SPI cannot tell you the project will finish four days or four weeks late; it tells you the earned pace is 8% under plan, in budget terms. Converting that into a date needs the schedule itself, which is the subject of the limitations section below.
Reading your SPI: the three bands
The reading is a comparison against 1.00, nothing more exotic. The badge on the calculator applies exactly this table:
The badge reads the exact, unrounded SPI, while the number is rounded to two decimals: a true SPI of 0.999 displays as 1.00 but still reads Behind schedule, and 1.001 displays as 1.00 but reads Ahead of schedule.
| SPI | Verdict | What it means |
|---|---|---|
| Below 1.00 | Behind schedule | Less work earned than planned by the status date. The further below 1.00, the larger the recovery problem. |
| Exactly 1.00 | On schedule | Work earned matches the plan at this date. Rare in practice, and worth checking that EV was measured honestly before celebrating. |
| Above 1.00 | Ahead of schedule | More work earned than planned. Check whether easy work was pulled forward before treating it as pure good news. |
Many organisations add their own tolerance bands on top, treating anything from 0.95 to 1.05 as within noise and escalating only outside it. That is a management convention, not part of the SPI definition, and this calculator deliberately reports the plain reading instead of baking one company’s tolerances into the verdict. A single period’s SPI also says less than its trend: three consecutive readings of 0.97, 0.94 and 0.92 describe a project drifting away from its plan, whatever any one reading suggests.
SPI vs CPI: schedule pace against cost efficiency
SPI has a sibling that uses the same EV against a different denominator, and the pair together describe a project’s health far better than either does alone. The cost performance index calculator covers the cost side in the same direct style as this page.
SPI = EV ÷ PV (this page)
- Compares work earned to work planned
- Reads schedule pace
- Ignores what the work cost
- A project can beat its schedule by throwing money at it, and SPI will not show the damage
CPI = EV ÷ AC
- Compares work earned to actual cost (AC)
- Reads cost efficiency
- Ignores whether the work was on time
- A project can look cost-efficient by quietly slipping its schedule, and CPI will not show it
The four combinations are the classic status picture: SPI and CPI both above 1 is genuinely healthy; SPI below 1 with CPI above 1 suggests the plan, not the spending, is the problem; SPI above 1 with CPI below 1 usually means the schedule was bought with overtime or extra hands; both below 1 is the project that needs intervention first.
The late-project trap: why SPI drifts back to 1.00
SPI has a built-in flaw that every project manager should know before quoting it late in a project. As the work finishes, EV catches up with the total planned value by definition, so SPI converges to exactly 1.00 at completion, even if the project delivers months late.
The failure mode is mechanical. PV stops growing once the planned finish date passes, because the baseline never planned any more value. EV keeps growing as the remaining work is done. A project that finishes three months late therefore reports a steadily “recovering” SPI through those three months and lands on a perfect 1.00 on delivery day. The index is not lying about value earned; it is answering a question that stops being the right one near the end of the job.
The earned schedule method exists to fix exactly this: it converts EV into the point in time when that value was supposed to have been earned, producing schedule measures in time units instead of budget units. PMI’s earned value literature, including its early-warning treatment of EVM on troubled projects, discusses why the raw indices need this kind of care. Practical rule: trust SPI most in the first two thirds of a project, pair it with milestone dates after that, and never report a late-project SPI without the forecast finish date beside it.
What competing calculators miss
Most SPI pages run the same one-line division. The differences are in what surrounds it:
- Index-only tools (Calculator City style): SPI plus schedule variance, with tidy ahead and behind examples. Useful, but they stop at the division: no route from percent complete and BAC to the EV and PV inputs, which is where most users are actually stuck.
- PMP study guides (PM Exams, 4PMTI, PM Study Circle): strong on definitions and exam examples, and they correctly pair SPI with CPI and the variance formulas. They are written for candidates memorising formulas, not for a manager with a status report open, and none of them warns about the late-project convergence flaw.
- Project management blogs (ProjectManager, DeeProjectManager): good worked scenarios and honest interpretation, but the calculator, where one exists at all, sits inside marketing software content and the reading bands are presented as settled fact rather than convention.
- Suite tools: full EVM suites compute SPI as a by-product of BAC, percent complete and actual cost. That is the right tool when you do not yet have EV; it is overkill, and a source of input errors, when your status system already reports EV and PV directly.
- The gap this page fills: direct EV and PV entry with the exact two-decimal output, the percent-complete route to both inputs, the recovery-pace arithmetic (1 ÷ SPI) done openly, and the convergence limitation stated on the page instead of discovered in a steering meeting.
Frequently asked questions
The Schedule Performance Index is an earned value management ratio that compares the work a project has actually earned against the work the plan said should be complete by the same date. It condenses schedule performance into one number: below 1.00 behind schedule, exactly 1.00 on schedule, above 1.00 ahead of schedule.
SPI = Earned Value (EV) ÷ Planned Value (PV). With EV of $46,000 and PV of $50,000, SPI = 46,000 ÷ 50,000 = 0.92, which is the worked example above. The calculator prints the result to two decimal places.
Multiply the budget at completion (BAC) by the percentages: EV = actual % complete × BAC, and PV = planned % complete × BAC. On a $200,000 budget that is 25% complete against a planned 30%, EV is $50,000, PV is $60,000, and SPI is 0.83.
It means the project has earned 92% of the work it planned to have complete by now, so it is behind schedule. In the worked example the shortfall is $4,000 of planned work (SV = EV − PV = −$4,000), and catching up needs about an 8.7% increase in pace, because 1 ÷ 0.92 = 1.087.
Many organisations treat 0.95 to 1.05 as a tolerance band and only escalate outside it, but that band is a management convention, not part of the SPI definition. Strictly, anything below 1.00 is behind schedule and anything above it is ahead. This calculator reports the plain reading and lets you apply your own organisation’s thresholds.
SPI is zero when no work has been earned yet (EV = 0), which this calculator returns as 0.00. A negative SPI can only come from a negative EV or PV, which are not valid earned value figures. The calculator will still divide negative entries if you type them, so treat a negative result as a data error to fix, not a schedule reading.
SPI divides EV by planned value and reads schedule pace. CPI divides EV by actual cost (AC) and reads cost efficiency. A project can be ahead of schedule and over budget at the same time (SPI above 1, CPI below 1), which usually means the schedule was recovered by spending more.
No. SPI is measured in budget value, not in days or weeks, so it cannot be converted directly into a finish date. It also drifts back to 1.00 as a late project completes its remaining work, because earned value eventually catches planned value. Use it alongside milestone dates, and look at earned schedule methods for time-based forecasts.
At every status period your project already reports, typically weekly on short projects and monthly on long ones. The trend across periods matters more than any single reading: a slide from 0.97 to 0.94 to 0.92 over three periods is a project drifting away from its plan, even though each individual number looks mild.
Add This Calculator to Your Website
Embed this calculator on your own site with the code below. Pick a size to preview it live, then copy the code.
Powered by Calculator Zilo
References
- Project Management Institute. Earned Value Management: Reading the Numbers, PMI Blog (the EVM formula table at a glance: PV, EV, AC, BAC, SV = EV − PV, SPI = EV ÷ PV, CPI = EV ÷ AC). Accessed October 24, 2026.
- Project Management Institute. Earned Value Management: An Early Warning System, PMI Learning Library (using EVM indices as an early warning on troubled projects, and the care needed when reading them). Accessed October 24, 2026.
- U.S. Government Accountability Office. Cost Estimating and Assessment Guide: Best Practices for Developing and Managing Program Costs (GAO-20-195G) (earned value management best practice, baseline discipline, and programme status reporting). Accessed October 24, 2026.
- U.S. Government Accountability Office. GAO-20-195G, full guide PDF, Chapter 17: Earned Value Management (how EVM combines cost, schedule and technical performance, and why planned and earned value must be measured consistently). Accessed October 24, 2026.
- Humphreys & Associates. EVMS Workshop Reference Materials (the ANSI/EIA-748 Standard for Earned Value Management Systems and the GAO guides that frame EV and PV measurement). Accessed October 24, 2026.
- Project Professionals. Managing Risk of Delay: Earned Value and Schedule Performance Indicators (the PMBOK definitions of schedule variance and SPI quoted in full, plus earned schedule as the time-based alternative). Accessed October 24, 2026.
