The Schedule Failure Pattern
After managing rail corridor projects, highway rehabilitation programs, and billion-dollar transit delivery at Metrolinx, I have observed a consistent pattern in schedule failures on large infrastructure programs: the delay is visible in the data long before it is acknowledged in the report.
The projects that finish late almost always showed warning signs six to twelve months before the delay became undeniable. Those warning signs were present in the schedule data, in the procurement lead time tracking, in the RFI log, and in the change order trend analysis. But the systems that would have aggregated those signals into an early warning were absent, or the culture that would have surfaced the warning to decision-makers was not in place.
The problem on most delayed mega-programs was not that the delay could not have been seen coming. It was that no one was looking for it systematically and honestly.
The Difference Between Leading and Lagging Indicators
A lagging indicator tells you what has already happened. Schedule performance index, actual progress against planned progress, percentage complete — these are lagging indicators. They tell you, with accuracy, that you are behind. They do not tell you why, or how far behind you will be at completion, or what to do about it.
A leading indicator tells you what is likely to happen if current conditions persist. A leading indicator for schedule risk might be the trend in RFI response time — if the designer is taking three weeks to respond to RFIs that should be turned around in three days, that is a leading indicator of design coordination problems that will create field disruption in 4-8 weeks. Or the trend in planned versus actual drawing release dates — if drawings are consistently releasing two weeks later than the schedule requires, the construction activities dependent on those drawings are carrying two weeks of unplanned float that will eventually become a delay.
Effective schedule risk management requires both, with an emphasis on leading indicators proportional to the time horizon of the program. A mega-program with 48 months of construction remaining needs a robust leading indicator system. A program with 6 months remaining needs lagging indicators — there is no longer enough time for leading indicators to produce actionable early warning.
Critical Path Monitoring
The critical path is the sequence of activities that determines the project’s completion date. Monitoring the critical path means monitoring the activities on that sequence — their progress, their resource loading, their dependencies, and the float that separates them from near-critical activities that could become critical if conditions change.
On complex mega-programs, the critical path is not static. It migrates as work advances, as sequence changes are approved, as acceleration or de-acceleration of different work packages changes the relative timing of activities. A project control system that identifies the critical path at baseline and monitors it without reassessing which path is actually critical at any given point in the project lifecycle is providing false assurance.
I built Project Management dashboards at Metrolinx that integrated critical path monitoring with a four-week lookahead schedule, current EAC variance reporting, and change order trend analysis. That integration — seeing critical path progress, near-term lookahead, cost trajectory, and commercial trend in a single view — is what enables proactive management rather than reactive reporting.
Recovery Planning: When to Invoke It and How
Recovery planning — the development and analysis of schedule recovery strategies — should be triggered by leading indicator signals, not by the point at which delay has become undeniable. When the leading indicators are trending negative and the critical path analysis shows a completion exposure, that is the time to develop recovery options — before the delay has materialized in the schedule record.
Recovery options fall into several categories: acceleration of critical activities through additional resources or extended work hours; sequence changes that allow work to proceed in parallel rather than in series; scope adjustments that defer non-critical scope elements to reduce the critical path duration; and commercial mechanisms that realign incentives toward delivery performance.
Each recovery option has a cost, a feasibility constraint, and a time horizon for effectiveness. Recovery planning is the analysis of which options are available, what they cost, and which combination produces the best balance of schedule recovery and cost exposure. It is a professional planning discipline, not a crisis response exercise. Treating it as the latter produces worse outcomes than treating it as the former.
Building a PMO Control System That Catches Problems Early
The organizational capability that makes leading indicator monitoring possible is the program management office — specifically, a PMO with the analytical capability to synthesize data from multiple systems into early warning signals, and the organizational authority to surface those signals to decision-makers without them being filtered by project teams protective of their schedule.
The PMO design choices that matter most for schedule risk management are: independent reporting authority (the PMO should report to program leadership, not to the project team whose schedule it is monitoring), analytical depth (schedule analysts who can interrogate the programme rather than just read it), integration with procurement tracking (schedule risk almost always has a procurement component), and a cadence of honest schedule assessment that is separate from the project team’s status reporting.