Why Construction Delays Propagate Through Schedules

This is delay propagation: the mechanism by which localized disruptions travel through a schedule's dependency network and compound into project-wide risk events. Understanding propagation is more valuable than understanding the delays themselves, because propagation is where the real exposure lives.

How Propagation Works

Propagation follows paths through the schedule network. Every delay to an activity creates pressure on its immediate successors — those activities can no longer start on time. If those successors have float, some of the pressure is absorbed. If they don't, the delay passes through intact, or amplifies.

Amplification happens when the delayed activity sits at a convergence point — a place in the network where multiple paths merge. A single delayed predecessor that constrains five successors simultaneously creates five concurrent delay events, each of which begins propagating into its own downstream chain. This is how localized disruptions become systemic ones.

Float Consumption and the Brittle Middle Phase

Float is the buffer between a delay and its consequence. But float gets consumed over the course of a project — through early-phase uncertainty, scope changes, weather events, and the accumulated effect of small slips that never get formally recorded.

Projects in their middle phase — typically 30% to 70% complete — are often structurally more fragile than they were at the outset, even though they look more advanced. The float that existed in the baseline schedule has been partially consumed by earlier disruptions, leaving the network with less capacity to absorb new shocks. Propagation paths that would have been contained in month two pass through intact in month six.

This is why construction delays so often seem to accelerate near project completion. It's not that more things go wrong — it's that there's less structural capacity to contain them.

Trade Resource Propagation

The dependency network in a CPM schedule captures finish-to-start relationships. It does not capture resource dependencies — the implicit constraint that a single trade crew can only be in one place at a time.

When a delay forces a trade crew to work longer on one activity, every subsequent activity in their sequence is compressed. If any of those activities are on the critical path, or if their float is already thin, the impact passes directly into the project schedule. This propagation mechanism is invisible in standard CPM analysis, because it doesn't involve a logical dependency — it involves a resource constraint that the schedule logic doesn't model.

Inspection Clusters and Regulatory Exposure

Inspection hold points create a third propagation mechanism: regulatory gating. Activities that require inspection before the next phase can begin create hard stops in the schedule — stops that are vulnerable to external timing factors beyond the project team's control.

When multiple inspection hold points cluster in the same phase, a delay at any one of them can cascade into others. If a framing inspection is delayed, the MEP rough-in can't start. If the MEP rough-in is delayed, the insulation inspection can't be scheduled. The inspection sequence creates a series of gates that amplify upstream delays into downstream compound impacts.

What Propagation Analysis Requires

Identifying propagation risk requires analyzing the schedule as a dynamic system — not just asking where the critical path is today, but modeling how disruption would travel through the network if it occurred at different points, at different magnitudes, at different phases of project execution.

This is a fundamentally different question than traditional schedule risk analysis asks. It's not about confidence intervals around the completion date. It's about the structural pathways through which failure spreads — and which of those pathways pose the greatest threat to project outcomes.

Answering it requires a model of the schedule's topology, a model of its resource structure, and a model of how disruption events interact with both. Vantage's PERR framework was built to operationalize exactly this kind of analysis.