Earned Schedule Calculator
This earned schedule calculator finds the baseline time at which cumulative planned value equals current earned value. It interpolates a time-phased PV curve, then calculates time variance, SPI(t) and a finish-time forecast from EV, actual time and planned duration.
By Dr. Hassan Khames EliwaLast updated
Result
- Time variance
- -1.00 time units
- SPI(t)
- 0.83
- Forecast finishPD / SPI(t), assuming current time efficiency continues.
- 9.60 time units
- Baseline PV
How it works
Supply a cumulative baseline, not period spending
Each textarea row contains time,PV with no header or thousands separators. Times must increase strictly, while cumulative planned value must never decrease. The baseline starts at 0,0 and ends at planned duration PD with a positive final budget. Enter between two and 500 rows. EV and PV share a monetary or other consistent earned-value scale; AT, PD and baseline times share one time unit. AT can exceed PD when work is late.
Interpolate the time earned
Find the two baseline points bracketing EV and interpolate linearly between their times. If EV falls exactly on a flat PV plateau, the calculator uses the rightmost equal-PV point before the next increase. That convention advances through a period with no additional planned value. EV zero is explicitly assigned ES zero rather than advancing through an initial flat baseline. EV cannot exceed the final planned budget. Coarse baseline intervals imply coarse information even though the result displays two decimals.
Express schedule efficiency in time
Time variance SV(t) equals ES − AT, so negative means behind the baseline in time terms. SPI(t) equals ES ÷ AT. A ratio below one indicates less time-equivalent progress than elapsed time. The forecast finish is PD ÷ SPI(t), assuming present time efficiency continues. When EV reaches the final budget, work is treated as complete and the actual time is reported as finish instead. With EV zero, SPI(t) is zero and no finite forecast is available. Earned Schedule terminology follows Walt Lipke’s method; the interpolation and forecast assumptions are described here.
Worked example
Scenario 1: progress within a rising interval
Use baseline rows 0,0; 2,100; 4,300; 6,600; and 8,1000. EV is 450, AT is 6 and PD is 8. EV sits halfway between PV 300 at time 4 and PV 600 at time 6, so ES is 5.00 time units. Time variance is −1.00. SPI(t) is 5 ÷ 6, displayed as 0.83. Forecast finish is 8 ÷ (5 ÷ 6) = 9.60 time units. The forecast uses the unrounded ratio, not 0.83.
Scenario 2: a flat baseline interval
Use rows 0,0; 2,100; 4,100; and 6,300, with EV 100, AT 5 and PD 6. The rightmost equal-value convention assigns ES 4.00 at the end of the plateau. Time variance is −1.00 and SPI(t) is 0.80. Forecast finish is 7.50 time units. This example matters because another plateau convention could yield a different ES despite identical EV.
From the field
From Dr. Hassan Khames Eliwa's project controls experience
I've sat in reviews where the cost-based SPI said we were nearly on plan and everybody in the room knew we were weeks late. Here's that situation with the numbers rounded so you can check them yourself. A commissioning package has earned 90% of its budget. Use weeks and enter this cumulative baseline, one row per line: 0,0; 10,700; 14,900; 18,930; 20,1000. With EV 900, AT 18 and PD 20, conventional SPI is 900 ÷ 930 = 0.97 to two decimals. Looks fine.
Earned Schedule disagrees. The baseline reached EV 900 at week 14.00, so SV(t) is −4.00 weeks and SPI(t) is 0.78 (14 ÷ 18 before rounding). Keep the same efficiency and the forecast finish is 25.71 weeks. That's time-equivalent progress, mind you, not a diagnosis of the remaining critical path.
Now let the package earn the full 1000 at week 24. Conventional SPI becomes 1.00, simply because EV caught up with final PV, even though we finished four weeks late. Enter EV 1000 and AT 24: ES is 20.00, SV(t) holds at −4.00 weeks, SPI(t) is 0.83, and the forecast finish is the actual 24.00 weeks.
Late in a job, I stopped quoting conventional SPI on its own. I report the time measures and the handover logic next to it, because a ratio drifting to one has never once recovered a lost week.
Field quick reference
| Status | ES, weeks | SV(t), weeks | SPI(t) |
|---|---|---|---|
| Progress review | 14.00 | −4.00 | 0.78 |
| Actual completion | 20.00 | −4.00 | 0.83 |
Expert tips
Common mistakes
- Period-by-period PV is not a cumulative baseline. Enter running totals that rise or stay level, rather than restarting the value at each reporting period.
- SPI(t) and EV ÷ PV answer different questions. The former compares earned time with elapsed time; the conventional index compares earned budget value with planned budget value.
- The forecast finish is total time from the baseline origin, not time remaining. Subtract AT separately when discussing how much longer the work may take.
Frequently asked questions
Why can EV not exceed the final PV?
The interpolation needs a baseline time corresponding to EV. Beyond the final budget there is no defined segment, so the calculator rejects extrapolation rather than inventing one.
What does a flat PV interval mean?
No additional value was planned during that interval. At an exact positive plateau value, the earned time is the last equal-value point before the next increase; zero EV is handled separately.
Can actual time be beyond planned duration?
Yes. AT must be positive but may exceed PD. An overdue project can still have incomplete EV and an earned schedule somewhere within the original baseline.
What happens before any work is earned?
ES and SPI(t) are zero, time variance is negative AT and forecast finish is shown as undefined. A finite division-based forecast is impossible without earned progress.
Is this the same as earned value cost forecasting?
No. The forecast is in time units, derived from the baseline curve. Use the earned value calculator for cost-oriented performance measures and keep their assumptions distinct.
Related calculators
Related guides
Construction & ProjectCPI and SPI trends: read the direction, not just the numberRead period and cumulative CPI and SPI together, test the data behind changing trends, and turn earned-value signals into practical decisions.16 November 2026 · 8 min read
Construction & ProjectEarned schedule: turn progress into timeCalculate earned schedule from a planned-value curve, interpret time-based variance, and avoid misleading finish forecasts.14 November 2026 · 8 min read
Construction & ProjectThree-point estimating: when PERT beats a single guessA practical guide to three-point duration estimates, weighted averages and the limits of turning uncertain activities into a promised date.14 November 2026 · 7 min read
Construction & ProjectEarned value management in plain English: CPI, SPI and what to do about themTurn planned value, earned value and actual cost into useful decisions without confusing budget performance with cash flow or time.14 November 2026 · 7 min readSources and standards
About the author
Dr. Hassan Khames Eliwa holds a PhD in Construction & Built Environment and has more than 20 years of international project controls experience. He is Director of Eliwa Project Controls Limited in Auckland and founder of PMMilestone.org and PMMilestone.com.
Buy me a coffee