Anonymised, illustrative composite. A steel erection subcontractor on an Alberta industrial project hit an excusable delay through no fault of its own, and was told verbally to keep the crews moving. The first time this happened, that cost it the claim. The second time, it didn’t.
At a glance
On the first project, the structural steel delivery from the mill ran weeks late — a supply chain problem entirely outside the erector’s control and, on the facts, an excusable delay under the contract. Rather than formally adjusting the schedule, the site superintendent told the erector’s foreman verbally to keep the crews on the original completion date regardless. The erector added overtime shifts and a second crew to make it happen, and treated the instruction as informal permission to bill the extra cost later.
On the second project, a similar mill delay hit a different erection package. This time the erector did not rely on a verbal conversation. It issued a written delay notice and a formal extension-of-time request the same day the mill confirmed the lateness, and got a written response back: proceed on the original schedule, EOT under review. It then compressed the schedule with overtime and added crews exactly as it had on the first job — but this time with a paper trail behind every decision.
An acceleration claim is not the same thing as “the job cost more because we worked faster.” It requires proof that the extra cost was directed — that the contract administrator or GC required the original schedule to be held despite a genuine entitlement to more time, rather than the contractor simply choosing, on its own, to spend money compressing a schedule nobody asked it to hold. The CCDC Guide to Construction Contract Administration is built around exactly that kind of documented exchange: a delay notice, a request, and a recorded response, each captured as the project moves rather than reconstructed afterward from memory.
On the first job, none of that existed on paper. The site super’s verbal instruction was disputed after the fact — he recalled a general conversation about staying on track, not a directive to accelerate in the face of a known, excusable delay. Without a written EOT request the erector could point to, and without a written response maintaining the original date, there was nothing to distinguish a directed acceleration from the erector simply having made its own scheduling choice.
First claim: roughly $54,000 of overtime and added-crew cost, disallowed in full. Second claim: $71,000 of documented acceleration cost on a comparable delay, recovered in full because the written EOT request and the written instruction to hold the original date both existed and lined up with the dates on the overtime and crew records.
This is the bind: the same delay type — a late structural steel delivery, entirely outside the erector’s control — produced the same underlying commercial harm on both jobs, and the erector responded to both the same operational way, with overtime and added crews. The only thing that changed between a $54,000 loss and a $71,000 recovery was whether a written delay notice and EOT request existed before the schedule was compressed, and whether the response maintaining the original date was in writing rather than remembered.
That is not a technicality layered on top of a legitimate claim — it is the substance of the claim. Without the documented request-and-response, there is no way to distinguish a GC directing acceleration from a contractor simply deciding, on its own initiative, to spend money it was never asked to spend. The paper trail is what proves which of those two things actually happened.
The erector now issues a written delay notice and EOT request on day one of any excusable delay, regardless of what a site super says verbally in the moment, so the record exists whether or not a claim ever turns out to be needed. For the escalation side of a similar cost-risk problem on a different contract type, see a roofer's escalation clause survived a price spike, and for the vocabulary this case turns on, see the elements a delay claim actually needs.
For how AI now helps flag a schedule slipping before it becomes a claim, see AI and tracking the critical path.
A 30-minute call is enough to tell you whether AI pays for itself here.
