Construction Earned Schedule: The Time-Based Performance Measurement Extending Earned Value Management

Earned Value Management (EVM) is standard project controls methodology measuring cost and schedule performance through metrics like Cost Performance Index (CPI) and Schedule Performance Index (SPI). But EVM's SPI has a known weakness — it uses dollar values for schedule, which produces misleading results as projects near completion. SPI tends toward 1.0 as projects finish regardless of actual schedule performance. Earned Schedule (ES) addresses this by using time-based schedule metrics.

Developed by Walter Lipke in 2003, Earned Schedule has gained adoption in sophisticated project controls. For construction projects using rigorous project controls, understanding ES enables more accurate schedule analysis and forecasting. This post covers Earned Schedule fundamentals.

EVM Schedule Limitations

EVM SPI has known issues:

EVM's SPI uses EV (earned value) divided by PV (planned value) in dollar terms. As project completes, EV approaches BAC regardless of timing — SPI approaches 1.0. Looks like schedule is recovering when actually late. Late-project schedule analysis unreliable. Forecasting degraded.

Earned Schedule Concept

ES uses time instead of dollars:

Earned Schedule calculates ES as time when current EV was originally planned to be achieved. AT is actual time elapsed. SPI(t) = ES/AT gives time-based performance. Unlike dollar-based SPI, time-based SPI(t) remains meaningful throughout project. Complements EVM cost metrics.

SPI(t) Calculation

SPI(t) interpretation:

SPI(t) interpretation similar to SPI but based on time. 1.0 is on schedule. Below 1.0 behind. Above ahead. 0.85 SPI(t) means 15% behind time. Critical insight is time-based measurement remains valid throughout project unlike dollar-based SPI.

Schedule Forecasting

ES enables better forecasting:

Independent Estimate at Completion (time) = PD/SPI(t). If project planned for 24 months and SPI(t) is 0.8, forecast completion is 30 months (24/0.8). Extrapolation more reliable than EVM schedule forecasting. Gives schedule insight throughout project life.

When ES Helps Most

ES particularly valuable:

ES especially valuable where EVM schedule metrics fail. Late-project schedule analysis. Schedule forecasting requirements. Rigorous controls environments. Long projects where degradation of SPI accumulates. Projects with schedule penalty provisions or contractor incentives.

Implementation

Implementation straightforward:

ES builds on EVM data. Time-based calculations from PV, EV, and dates. Reporting supplements EVM reports. Software support varies — some EVM software includes ES; others require custom calculations. Custom Excel common. Training for project controls team to understand and apply.

Industry Application

Adoption growing:

ES adoption growing but not yet mainstream construction. Federal contractors and DoD projects lead adoption. Large construction projects with EVM apply ES. Engineering firms use. Mainstream construction (mid-size GCs) less common. For projects using EVM, ES adds value with minimal additional effort.

Bottom Line

Earned Schedule extends Earned Value Management with time-based schedule metrics overcoming EVM's SPI limitations. SPI(t) based on time remains meaningful throughout project unlike dollar-based SPI. Schedule forecasting through IEAC(t) = PD/SPI(t) provides reliable estimates. ES particularly valuable late in projects, for schedule forecasting, and in rigorous controls environments. Implementation builds on EVM data with minimal additional effort. Software support growing but often requires custom calculations. Industry adoption growing from federal contractors outward. For projects using Earned Value Management, adding Earned Schedule produces substantially better schedule insights at minimal additional cost. ES is complementary to EVM — not replacement — and deserves consideration in sophisticated project controls programs.