Esc

↑↓ move↵ openIndex · Pagefind
Project management

Pacing

Definition

A deliberate slowing of non-critical work in response to a delay on another path, so it isn't counted as concurrent delay.

Topic: Changes & claims · Scheduling

Updated

Pacing is slowing work on purpose to keep step with a delay elsewhere. If an owner-caused delay has already pushed completion out, a contractor may sensibly slow non-critical work rather than hurry to wait. AACE RP 29R-03 treats a properly evidenced pacing delay as a response to the parent delay, not as an independent concurrent delay in a delay claim.

The logic is economic. Once the finish has moved, finishing other work on its original dates only means crews and equipment sit idle later. Slowing that work, and saving the cost, is a reasonable use of the float the parent delay created.

How it works

  1. Parent delay. A delay on the critical path, caused by one party, pushes the forecast completion date.
  2. New float. Work on other paths gains float against the new completion date.
  3. Decision. The other party decides to slow some of that work, for example by reducing crews or deferring deliveries, and records why.
  4. Paced work stays non-critical. The slowdown uses less than the available float, so it doesn’t drive completion.
  5. Analysis. When delays are later assessed, often in a windows analysis, the paced period shows up as slower progress on a non-critical path. The analyst tests whether it was pacing or an independent delay.
  6. Result. If the pacing tests are met, the slower work isn’t treated as concurrent with the parent delay.

Worked example

Illustrative: structural steel is held for 20 working days by late owner approvals. Interior framing, on another path with 25 days of float, is slowed from two crews to one for that period. The owner argues the framing delay was concurrent. The contractor shows the steel delay came first, framing had enough relative float to absorb the slowdown, and site meeting minutes record the decision to reduce crews because of the steel hold.

The float position, in working days (assuming the framing path doesn’t feed the steel path):

Step Framing total float
Before the steel hold 25
Steel hold pushes completion out 20 days 25 + 20 = 45
Framing slowed, adding 12 days to its duration 45 − 12 = 33

Framing ends with 33 days of float, so it never drove completion. Had the slowdown added 50 days, framing would have become critical and its own delay could have been concurrent.

What to record at the time

A pacing argument is won or lost on records made while it happened. Useful evidence includes:

  • The parent delay: when it started, what caused it and how it moved the forecast finish.
  • The schedule update showing the paced work’s float before and after the parent delay.
  • The decision itself, in meeting minutes, a letter or an email, with the reason given.
  • What changed on site: crew sizes, shifts or delivery dates, from daily reports.
  • Notice to the other party that work is being paced, where the contract or good practice calls for it.
  • When normal progress resumed after the parent delay ended.
Concept Cause Drives completion? Typical effect on damages
Parent delay One party Yes Delay damages or LDs, depending on who caused it
Pacing Response to the parent delay No Not treated as concurrent if proven
Concurrent delay Both parties, independently Both do Often time but no money
Acceleration Owner instruction or constructive Shortens it Contractor may recover acceleration cost
Non-critical slow progress Contractor No Usually none, if float absorbs it

Why it matters

Concurrency can cut off delay damages. A pacing argument, where it holds, keeps the paced delay from being counted against the party that paced. It fails without evidence of the decision made at the time.

It also matters for liquidated damages. An owner that delays the job and then points to the contractor’s slower non-critical work to argue concurrency may still be liable for the delay it caused, if the contractor can show it was pacing.

Common mistakes

  • Claiming pacing after the fact with no contemporaneous record of the decision.
  • Pacing work that had too little float, so it became critical in its own right.
  • Treating a pacing assessment as a verdict on responsibility.
  • Not telling the other party about the decision to pace, which makes it look like an independent delay.
  • Failing to resume normal progress once the parent delay is resolved.
  • Ignoring productivity records in the daily log that contradict the stated reason for slowing down.

How os.construction handles it

A concurrency analysis on the Forensics page accepts pacing claims. Test 1 is computed from the chronology and, when both activities are named, their relative total float in an optional context version. The other tests are the analyst’s evidence, and no verdict is produced. See Pacing.

FAQ

How is pacing different from concurrent delay?

Concurrent delay is two independent delays affecting completion at the same time. Pacing is one party choosing to slow its work because another delay has already pushed the completion date, so its slower progress is a response, not an independent cause.

What evidence supports a pacing argument?

That the parent delay came first and was critical, that the paced work had enough float to slow down without becoming critical, that a decision to pace was made, and contemporaneous records of that intent.

Who usually raises pacing?

Often the contractor, to answer an owner's argument that the contractor's own slow progress was concurrent with an owner-caused delay.

Can an owner pace too?

Yes. If a contractor's delay has already pushed completion, an owner might reasonably slow its own activities, such as reviews or owner-furnished deliveries, to match. The same tests apply: the contractor's delay came first, the owner's work had float, and the decision was recorded.

Why does pacing matter for damages?

When delays are concurrent, many contracts and courts deny one or both parties delay damages for the overlapping period. If the slower work was pacing, not an independent delay, the party that caused the parent delay can't use it to argue concurrency and avoid paying for the delay it caused.

Sources

Keep exploring

Related across os.construction

Open file