Earned Schedule: A Better Way to Track Schedule Performance
Earned Value Management (EVM) is the most widely used quantitative framework for tracking project cost and schedule performance. Its core metrics -- Planned Value, Earned Value, and Actual Cost -- underpin project controls in infrastructure, defence, IT, and capital construction programmes worldwide. But EVM has a well-documented flaw in the way it measures schedule performance, and understanding that flaw is important for anyone relying on EVM data to make schedule decisions.
The flaw is this: EVM's Schedule Performance Index (SPI), calculated as Earned Value divided by Planned Value, converges toward 1.0 as the project approaches completion -- regardless of whether the project is on schedule or not. A project that is significantly behind schedule will show SPI improving in the final months of the project simply because the denominator (Planned Value) stops growing while the numerator (Earned Value) continues to accumulate as remaining work is completed. By the time the project closes, SPI = 1.0 always, whether the project finished on time or two years late. This makes SPI unreliable as a schedule indicator in the latter stages of a project -- precisely when schedule performance is most consequential.
What Earned Schedule Is
Earned Schedule (ES) is a time-based extension of EVM, developed by Walt Lipke in 2003, that measures schedule performance in time units rather than cost units. The key insight is straightforward: instead of asking "how much value have we earned compared to what we planned?" ES asks "at what point in time should we have earned the value we have actually earned?"
In other words, ES locates the project's current Earned Value on the Planned Value curve and reads off the corresponding time. If the project has earned value equal to what the plan said it would have earned at month six, then Earned Schedule equals six months -- regardless of what month it actually is. If it is currently month eight and ES is six months, the project is two months behind schedule.
Calculating Earned Schedule and SPI(t)
The calculation requires the project's Planned Value curve (also called the Performance Measurement Baseline) and the current Earned Value. The steps are:
Locate current EV on the PV curve. Find the point on the planned value (S-curve) that corresponds to the project's current Earned Value. This may fall between two reporting periods.
Interpolate to find the corresponding time. If current EV falls between the PV at time n and the PV at time n+1, interpolate to find the fractional time period. This gives Earned Schedule in time units (months, weeks, etc.).
Calculate SPI(t). SPI(t) = Earned Schedule / Actual Time. An SPI(t) below 1.0 means the project is behind schedule; above 1.0, it is ahead. Unlike the traditional SPI, SPI(t) does not converge to 1.0 at project completion -- it converges to the ratio of the actual duration to the planned duration, which is exactly the information you want.
Why ES Gives a Better Picture Late in the Project
The mathematical behaviour of SPI(t) is fundamentally different from that of SPI. Because SPI(t) is computed in time rather than cost, it does not share the convergence property that makes traditional SPI misleading. A project that is running six weeks late at the 80 percent complete mark will show an SPI(t) that reflects that six-week slippage. It will not show a recovering SPI that creates a false impression of schedule recovery.
This matters most on large projects with significant schedule risk, where the cost of failing to identify schedule problems early is measured in millions of dollars of liquidated damages, extended overhead, and supply chain disruption. On these projects, a schedule indicator that flatters the situation in the final third of the project is worse than useless -- it actively misleads decision-makers at the moment when intervention is most valuable.
Forecasting Completion Date with ES
ES also enables a time-based independent estimate at completion (IEACt), which forecasts the project's likely completion date. The most common formula is:
IEACt = Planned Duration / SPI(t)
If the planned duration is 24 months and SPI(t) is 0.85, the forecast completion is 24 / 0.85 = 28.2 months. This forecast can be compared to the project's approved schedule to quantify the expected delay. As with all EVM forecasts, IEACt should be triangulated against schedule network analysis and the project team's own assessment -- no single metric tells the whole story.
When to Use Earned Schedule
Earned Schedule is most valuable on:
Large infrastructure and capital projects with planned durations of 18 months or more, where schedule slippage carries significant financial consequences.
Projects where the traditional SPI has been observed to recover in the final stages despite the schedule remaining behind -- a common pattern that ES corrects for.
Programmes where multiple projects are being compared on schedule performance, and a consistent, time-unit metric is needed to make comparisons meaningful.
Contracts with liquidated damages clauses, where an early and accurate picture of forecast completion date informs mitigation decisions.
Implementing ES Alongside Traditional EVM
Earned Schedule is an extension of EVM, not a replacement. The data inputs are identical -- all you need is the Planned Value curve and Earned Value at each reporting period. The additional calculation is straightforward in a spreadsheet. Many project management information systems can be configured to calculate and display ES metrics alongside traditional EVM metrics.
The implementation challenge is not technical -- it is interpretive. Project teams and sponsors who are accustomed to reading SPI need to understand why a different metric is being introduced and what it tells them that SPI does not. That communication investment pays off quickly when ES provides an early warning that SPI is masking.
XNM Consulting provides project controls, EVM implementation, and schedule performance analysis for major infrastructure and capital programmes.