Project Delay Letter to Contractor: A Sample You Can Adapt

The updated programme lands on the Resident Engineer's desk on a Tuesday morning, and the float on the critical path has gone from three weeks to nothing. Mentioning it at Friday's site meeting is not enough — it needs to be in writing, today, and it needs to cite the contract, not just the schedule. This guide gives you a project delay letter to the Contractor built around the clause that actually governs it, plus a worked example you can adapt.

Who Sends This Letter, and What It's For

This is not a Contractor's notice. It runs the other way — from the party administering the contract to the Contractor whose progress has fallen behind. On a FIDIC Red Book or Yellow Book project, that is the Engineer. On a Silver Book (EPC/Turnkey) project, there is no independent Engineer, so the Employer's Representative issues it instead.

The contractual basis is Sub-Clause 8.6 of the FIDIC 1999 Conditions of Contract, headed "Rate of Progress." If, at any time, actual progress is too slow to complete within the Time for Completion, or has fallen behind the current programme accepted under Sub-Clause 8.3, the Engineer may instruct the Contractor to submit a revised programme, together with a description of the revised methods it proposes to adopt to expedite progress. In the FIDIC 2017 Second Edition, the same mechanism sits at Sub-Clause 8.7, alongside the new Sub-Clause 8.4 Advance Warning obligation.

It is a progress-management tool, not a punishment. Used early, it puts a shortfall on record, forces a considered response from the Contractor, and gives both sides a documented starting point if the delay later needs to be argued over — whether that argument concerns delay damages, an extension of time, or something else entirely.

What the Letter Must Contain

A Sub-Clause 8.6 letter is only as strong as the comparison behind it. These are the building blocks that make it hold up:

• The clause it is issued under — Sub-Clause 8.6 (or 8.7 under the 2017 Second Edition), named explicitly so it is not read as an ordinary progress meeting comment.
• The baseline it is measured against — the current programme accepted under Sub-Clause 8.3, and the date it was accepted or last updated.
• The specific shortfall — which section or activity is behind, by how much, and why it threatens the Time for Completion.
• The instruction itself — a requirement to submit a revised programme and a description of the revised methods proposed to expedite progress.
• A response period — a specific, reasonable number of days for the Contractor to submit the revised programme and methods.
• A without-prejudice reservation — confirmation that the letter does not waive any other right or remedy available to the Employer under the Contract.

Keep the tone factual. This letter can end up as an exhibit if the delay later escalates into a dispute, and a letter that reads as an accusation rather than a documented comparison is easier for the Contractor to push back on.

Project Delay Letter to Contractor — Template

Replace everything in square brackets with your own facts, then delete the brackets.

Two notes on the placeholders. First, "[X] days" has no fixed default the way the 28-day claims notice does — FIDIC requires only that the period be reasonable, so state a specific number rather than leaving it open-ended. Second, this letter is deliberately not a claim for delay damages; it says so directly, because conflating the two can blur the record if the Employer later needs to bring a separate claim under Sub-Clause 8.7 (8.8 under 2017) and Sub-Clause 2.5.

Worked Example: A Filled-In Letter

The template filled in for a highway contract where the structures package has slipped against the accepted programme:

Notice what the letter does not do — it does not accuse, calculate damages, or thread a legal argument. It compares a baseline to an actual, names the section affected, instructs a documented response within a stated period, and reserves everything else for later.

How This Differs From a Notice to Correct

These two letters get confused because both land on a Contractor's desk as bad news, but they are not the same instrument and do not carry the same weight.

• A Sub-Clause 8.6 letter addresses the pace of work against the accepted programme. The remedy it asks for is a revised programme and expedition methods — nothing more.
• A Notice to Correct under Sub-Clause 15.1 addresses a specific failure to perform a contractual obligation. Failing to comply with it is a ground for termination under Sub-Clause 15.2 — a materially higher-stakes document.

In practice, a Sub-Clause 8.6 letter often comes first. If the Contractor recovers, the matter usually ends there. If the shortfall continues despite the instruction, the persistent failure to expedite can itself become grounds for the Engineer to move to a formal Notice to Correct — which is why the template above reserves that right explicitly rather than raising it as a threat in the body of the letter.

On the Contractor's side, the correct response depends on the cause. If the shortfall is genuinely the Contractor's own, the honest answer is a recovery plan under Sub-Clause 8.6. But if some or all of it traces back to a Variation, weather, unforeseen ground conditions, late access, or delayed drawings, the Contractor's response should itself take the form of a notice under the relevant clause and Sub-Clause 20.1 — the kind of notice ChatNotice drafts in minutes, with the 28-day clock running from the date of awareness and particulars due within 42 days (84 days under the 2017 Second Edition).

Common Mistakes

Most project delay letters to a Contractor run into one of the same handful of problems:

• Using it to claim delay damages. Delay damages are assessed under Sub-Clause 8.7 (8.8 under 2017) once the Time for Completion is actually missed, and notified under Sub-Clause 2.5 — a different mechanism entirely.
• No baseline comparison. Asserting that progress is "slow" without referencing the accepted programme leaves nothing objective for the Contractor to respond to.
• No stated response period. Leaving the deadline vague or unstated makes it harder to test whether the Contractor's response was timely.
• Dressing it up as a Notice to Correct. The two instruments have different legal consequences; using 15.1 language for an 8.6 letter overstates what is actually being issued.
• Ignoring a genuine counter-notice. If the Contractor's response cites a real Employer-side cause with its own clause reference, failing to engage with it on the record creates its own risk.
• Sending it outside the contractual notices channel. Sub-Clause 1.3 sets the valid method and address; a letter sent the wrong way can be challenged on process alone.

Most of these come down to the same discipline as any FIDIC correspondence: cite the clause, anchor the facts to a document, and say exactly what is being asked for.

Sending and Documenting

Check the contract's notices clause — usually Sub-Clause 1.3 — before sending. Many FIDIC contracts specify a particular address or method for valid notices, and a Sub-Clause 8.6 instruction should follow the same channel as any other formal correspondence, even though it carries no fixed statutory deadline of its own.

Keep proof of delivery and log the letter in the project's correspondence register — date sent, the programme comparison it relied on, the response period given, and where the Contractor's reply is filed. If the shortfall continues and the file needs to support a later Notice to Correct or a delay damages claim, this letter is often the first document a reviewer looks for.

Frequently Asked Questions

Authoritative Sources

This guide reflects the FIDIC Conditions of Contract and established construction-law authority:

• FIDIC Conditions of Contract — the official contract suite published by the International Federation of Consulting Engineers, which sets out the Sub-Clause 8.6 Rate of Progress mechanism and the Sub-Clause 20.1 claims procedure referenced above.
• SCL Delay and Disruption Protocol — the Society of Construction Law's widely used protocol on programme management, delay notification, and acceleration in construction contracts.

About the Author

Muhammad M. Jiwani is a Project Director with 15 years' experience on major infrastructure and energy projects administered under FIDIC contracts. He writes from first-hand experience serving notices and managing contractual claims on live projects.