How to Write a Delivery Delay Email: Five Things Clients Need Before an Apology

What a client needs to know first

Imagine discovering a day before delivery that the promised work cannot be handed over as planned. A solo operator may keep hoping to catch up and delay the conversation. The client instead needs to know what changed and what decision they can make now, not a long account of your workload. The design work, dates, and client in this article are hypothetical writing examples. Check the actual agreement before deciding contractual terms or compensation.

Tell the client when the delay becomes credible

Do not wait for a perfectly certain replacement date until the original deadline passes. Once you know which item cannot be delivered, you can say so and openly state that the final timeline remains uncertain. Avoid an unsupported 'It will be fixed soon.' In the opening sentence, give the original promise, the verified status, and the client impact. For example: 'The mobile screens in the design package promised for Friday have not passed review, so I cannot deliver the agreed final version on Friday.' This lets the client plan.

Separate your constraints from the client's choices

You may explain why internal work ran late, but that does not automatically justify changing the client's schedule. They may have an event, a review meeting, or a dependent order. After apologizing, say what they may need to reschedule. If part of the work is ready, ask whether a clearly marked review copy would help; do not present an incomplete file as final. Depending on the relationship, pausing until a revised date is known may also be an option to discuss.

Distinguish delivery from the next update

A revised delivery date is when you believe you can hand over the work. The next update time is merely when you promise to reassess and report. Do not let 'I will contact you tomorrow' sound like a promise to deliver tomorrow. If review is unfinished, say that no new delivery date is confirmed. Instead promise a realistic update, such as 'By Tuesday at 2 p.m. I will report what remains and the earliest feasible delivery date.' If uncertainty remains then, share verified progress and another update time rather than going silent.

Fill five fields in one email

Include 1) the promised deliverable and date, 2) the verified scope of delay, 3) the effect on the client's plans, 4) a confirmed revised date or the next update time, and 5) a choice or question the client can respond to. Say 'no issue' only about work already checked. Even with several contributors, use one official sending address and one reply owner so conflicting promises do not reach the client.

Check the client's next action before sending

Read the draft as the client: should I wait, reply, or change another appointment? If the email does not answer that, a long apology is not enough. Put the project name and schedule change in the subject so the message is easy to find. This is a hypothetical example, not a real incident.

Before sending a real message, replace the project, verified facts, dates and time zone, and client options. Check the agreement first if contractual or compensation decisions are involved.

Conclusion: do not let the explanation arrive late

A delay email is not a plea for understanding through excuses. It gives the client a verified status and a dependable next update so they can make their own plans. A regular client status-update routine also helps you avoid making the delay notice your first message about progress.

Frequently asked questions

Should I wait until I know the new date?

No. Share the verified delay, client impact, and next update time now. Do not present an uncertain date as confirmed.

Can I send partial work first?

Offer it if it helps the client review and clearly mark what remains incomplete. Never pass an unfinished file off as final.

How long should the apology be?

Acknowledge responsibility clearly and briefly, then give the information and next update the client needs to decide.

Read next

A realistic client-response schedule helps you promise a response time you can actually keep when a schedule changes.