Project Delay Email to a Client: Template

Every project runs late sometimes; the projects that survive it are the ones where the client heard it from you first, with a new date attached. A delay email is not an apology letter, it is a re-planning document in five sentences. This guide builds those sentences, the keepable-date discipline behind them, and the options table for clients whose deadline cannot move.

Tell Them Before They Notice

The delay email goes out the moment the new risk to the deadline is real, because a delay the client hears from you is a managed event while a delay they discover is a broken promise. Apology-letter guidance and customer-communication templates converge on the same instruction: notify early, notify first, notify yourself. Waiting for certainty converts a warning into an apology; the email you could have sent last week as a heads-up must be sent this week as a confession. Define your own notify-by trigger now, while nothing is late: the day any task on the critical path slips past half its buffer, the client email is being drafted. Clients forgive slow news they helped plan; they audit slow news they discovered.

The Five Sentences of the Notice

The delay notice runs five sentences: a subject naming the project and the change, the specific deliverable that is late, one honest line of cause, the new date with what is already done, and the next check-in.

1. Subject: Delivery update on the [project] website build, so the thread is filed as news, not as blame.
2. The deliverable: the staging site handover moves from 14 November to 21 November, naming the deliverable, never the vague project.
3. The cause in one honest line: the payment-gateway integration surfaced a compliance check we did not forecast.
4. The new date plus completed work: design and content are approved and staged; the new handover date is 21 November.
5. The next check-in: I will confirm progress this Friday, and the date holds unless you hear otherwise.

Name the deliverable, never the vague project, so scope stays fixed. Five sentences is a ceiling, not a floor; the moment the notice starts explaining itself in paragraphs, it has started excusing itself instead.

The New Date You Can Keep

The revised date carries visible buffer beyond your best case, because a second missed date costs more trust than the first delay ever did. Your internal target and the client's date should differ: if the team believes 18 November, the client hears 21 November, and the gap is not dishonesty but insurance. Under-promise the date, over-deliver the update cadence until it lands; a Friday confirmation email during the recovery week buys more goodwill than an early delivery of a shaky deliverable. When the task completes ahead of the padded date, say so plainly and deliver early; the surprise runs in your favour exactly once, and it only exists because the pad existed. The unpadded date is a gamble with your credibility as the stake.

Reason Without Excuse

The cause is one sentence, honest and blame-free, followed immediately by the fix, because clients read long explanations as invoices for sympathy. Career guidance on delay apologies and support templates agree on the shape: acknowledge, explain once, move to the plan. Never name a team member or subcontractor as the cause; the client's contract is with you, and internal blame reads as a preview of how you will describe them to others. The test of the sentence is simple: it survives being forwarded. If the cause line works as a standalone quote in the client's internal update to their boss, it is written correctly. If it needs the paragraph around it to stop sounding like an excuse, it is not finished.

When the New Date Still Hurts

When the revised date does not work, offer a three-way trade in a table: full quality on the new date, a reduced first release now, or a phased delivery, letting the client choose the pain they prefer.

Any partial release still passes acceptance criteria; never ship untested to save a date. The table converts a negotiation into a choice, and clients punish bad news far less when the bad news arrives holding three doors open.

Delay Writing as Trust Repair

Delay notices, revised quotes and recovery plans share the bad-news register where structure rebuilds trust, and marked small-group practice keeps that writing calm under real pressure. iWorld Learning's Business English small-group classes rehearse exactly this delivery-news register in classes of three to six, where a marking teacher catches the over-apologising before your client does. Log every delay cause; repeated causes are a process problem, not a writing problem, and the log is how you tell them apart.

Frequently Asked Questions

Should I offer a discount when the project is late?

Offer it when the delay is your fault and contractual penalties apply, state it as a specific amount in the notice, and avoid percentage discounts that cheapen the work.

What if the delay happens twice?

The second notice escalates: state the pattern, name the systemic fix, and offer the scope trade or an exit, because a third promise has no currency left.

Should I share internal evidence of the cause?

Share evidence only when it changes the client's decision, screenshots of a blocker or a supplier confirmation, and keep internal staffing matters internal.