Example 1 (simple): PV 50,000, EV 40,000, 20 weeks planned
- SPI = 40,000 ÷ 50,000 = 0.8 (behind: 80% of planned progress)
- SV = 40,000 − 50,000 = −10,000
- Forecast = 20 ÷ 0.8 = 25 weeks; delay = 5 weeks late
These are the calculator's default inputs.
Enter planned value and earned value to get the schedule performance index, the schedule variance and a forecast of how long the project will take.
Schedule performance index (SPI) = earned value ÷ planned value. Schedule variance = EV − PV. With EV 40,000 and PV 50,000, SPI is 0.8 and the schedule variance is −10,000. At that pace a 20-week plan takes 20 ÷ 0.8 = 25 weeks, so the delay is 5 weeks.
Enter planned value (PV): the value of the work you planned to have finished by now. Enter earned value (EV): the value of the work actually finished. Add the planned total duration to get a forecast. Actual cost (AC) and budget at completion (BAC) are optional and unlock the cost side.
The tool also names the band your SPI falls in. The SPI meaning guide explains every band from 0.5 to 1.5 with the delay each implies.
SV = EV − PV SPI = EV ÷ PV
forecast duration = planned duration ÷ SPI delay = forecast − planned
CV = EV − AC CPI = EV ÷ AC EAC = BAC ÷ CPI percent complete = EV ÷ BAC
These are the standard earned value management formulas. The duration forecast is a simple extrapolation: it assumes the rest of the project runs at the same schedule efficiency as the work so far. PV, EV and AC must use the same currency or unit, and PV and EV must refer to the same date.
Each example uses numbers you can load into the calculator above; the results match the tool exactly.
These are the calculator's default inputs.
An SPI above 1 is good news only if the plan was realistic; check that quality has not slipped.
PV 60,000, EV 54,000, AC 63,000, BAC 200,000 and a 40-week plan.
The forecast duration is the planned duration divided by SPI. It answers "if the rest of the project keeps going at the rate the work so far has gone, how long does the whole thing take?" Subtract the time already elapsed to get the time remaining. For a 20-week plan with an SPI of 0.8, the whole project takes 25 weeks; if 10 weeks are already gone, 15 remain.
Two cautions apply. SPI measured by value is not the same as being late on the critical path: a project can have a healthy SPI while the critical path slips, so check the critical path as well. And SPI converges to 1 as a project finishes, because EV catches up with PV, so late-project SPI says little about delay. For a simple estimate from progress and elapsed time, use the estimated time remaining calculator.
The schedule performance index is earned value divided by planned value. Below 1 means behind schedule, 1 on schedule and above 1 ahead.
Subtract planned value from earned value: SV = EV − PV. A negative number means you are behind. With EV 40,000 and PV 50,000 the variance is −10,000.
Divide the planned duration by SPI. A 20-week plan with an SPI of 0.8 forecasts 25 weeks, a delay of 5 weeks. Subtract the time already elapsed for the time remaining.
1.0 or above means on or ahead of plan. Between 0.9 and 1.0 is a small slip many teams treat as normal; below 0.8 usually needs action. See the SPI bands.
SPI compares earned value with planned value (schedule). CPI compares earned value with actual cost (cost). Both use EV as the numerator.
Yes. SPI uses value, so completing easy, low-value work first can lift it while critical-path tasks slip. Check the critical path as well.
PV comes from your baseline schedule and budget; EV is the baseline value of the tasks completed. Many project tools report both. Use the same status date for both.
Last updated 19 October 2026. Last reviewed 19 October 2026. Reviewed by Umesh Manral. Formulas and tests: methodology.