Pacing Delay: What It Looks Like in a Schedule

What Legitimate Pacing Actually Requires

Slowing down is easy to do and easy to claim. What separates genuine pacing from a post-hoc excuse for a party’s own non-excusable slow performance is three conditions, all of which generally have to hold:

1. Deliberate and documented. The decision to slow down has to actually be a decision -- made and recorded at or near the time it happened (a meeting minute, a notice to the owner, a staffing directive), not reconstructed afterward from the schedule data alone.
2. A response to an already-existing excusable delay. The other party’s excusable delay has to have already happened, or at least already be known, before the pacing decision is made. Slowing down first and pointing to someone else’s later delay afterward isn’t pacing -- it’s just a convenient sequence of events.
3. Reasonable in degree. The slowdown should roughly match the delay it’s responding to, not exceed it. Pacing an activity by 20 days in response to a 20-day excusable delay elsewhere is defensible; pacing it by 60 days is no longer proportion -- it’s using someone else’s delay as cover for a larger slip of your own.

Worked Example: A Steel Delay Triggers a Paced Finishes Schedule

Two paths on a fictional mid-rise project. Path X is structural steel erection, driving the project’s critical path with 0 float. Path Y is a separate, contractor-performed interior finishes scope on a lower level, not physically dependent on steel completion, running comfortably ahead of schedule with 40 days of float.

• Baseline (Day 0). Steel erection: 60-day duration, finishing Day 60, driving the project’s Substantial Completion to Day 150. Finishes: starts Day 30, planned 80-day duration, baseline finish Day 110 -- 40 days of float against the Day 150 completion date.
• Day 45 -- the excusable delay. The owner directs a redesign of the steel connections after a late structural review. Steel erection slips 20 days, to a Day 80 forecast finish, pushing the project completion date to Day 170. Finishes hasn’t been touched by any of this, but its float jumps from 40 days to 60 days -- the direct arithmetic result of the project’s completion date moving out from under it.
• Day 50 -- the pacing decision. Rather than run the finishes crew at full rate toward a Day 110 finish and then sit 60 days ahead of an area that can’t be turned over any earlier because of the steel delay, the contractor reduces the Level 2 finishes crew and records the reason in that week’s project meeting minutes.

The result: finishes’ forecast finish moves from Day 110 to Day 130 -- a 20-day push that matches the steel delay exactly, not a larger slip dressed up as pacing. That also means finishes’ float settles back down to 40 days once the paced schedule is reflected -- the same level it sat at before the steel delay ever happened, not the inflated 60 days the delay briefly made available.

Distinguishing Real Pacing From a Post-Hoc Excuse

Strip away the narrative and the schedule data itself either supports a pacing story or it doesn’t. The questions that matter:

• Does the timing line up? A slowdown that starts only after the other party’s delay is already known is consistent with pacing. A slowdown that starts first, with the other party’s delay surfacing later, is not -- the sequence runs backward from what pacing requires.
• Does the magnitude line up? A 20-day rate reduction responding to a 20-day excusable delay is proportionate. A 60-day reduction responding to the same 20-day delay uses the real delay as cover for a much larger slip that needs its own explanation.
• Is there anything contemporaneous at all? A meeting minute, notice, or staffing record written at the time carries far more weight than a written explanation produced after the dispute has already started, reconstructing intent the schedule alone can’t prove.
• Was the path actually non-critical when the slowdown began? Pacing only makes sense on a path that genuinely doesn’t need to finish early anymore. A slowdown on a path that was still driving the finish date when it started is just a new delay, not a response to one.

Frequently Asked Questions

Is pacing delay a formally recognized legal doctrine?

It's widely accepted as a concept in delay analysis and referenced in industry guidance such as AACE's recommended practices, and boards and courts have credited it when the facts support it. But it isn't a doctrine a party gets the benefit of automatically -- the party invoking pacing bears the burden of proving the decision was genuine, contemporaneous, and proportionate.

What's the biggest risk in claiming pacing after the fact?

Without contemporaneous documentation, a pacing claim is nearly impossible to distinguish from ordinary slow performance dressed up in hindsight. A schedule showing a slowdown, on its own, is equally consistent with a deliberate decision or with a struggling contractor -- the difference lives in the paper trail, not the float.

Does pacing require slowing an activity to a full stop?

No. A full stop is easier to justify as pacing in one sense (it's unambiguous) but is also more likely to be seen as excessive if it consumes more schedule than the other party's delay actually created. Legitimate pacing is a measured rate reduction sized to the delay being responded to, not a work stoppage.

Can an owner pace its own work, or is this only a contractor argument?

The concept applies to either party in principle -- an owner could pace its own furnished-equipment installation in response to a contractor-caused delay elsewhere, for example. In practice it's raised far more often by contractors defending against a claim that their own path ran slower than planned.