Delays are normal in client work. A permit takes longer, a supplier ships late, a client sends their part a week after you asked. What turns a normal delay into an unhappy client is usually not the delay itself. It is finding out on the day, or after it.

Four rules for any delay email

  1. Before the date, not after

    Send it as soon as you know the date will slip. A day early is better than a day late, even if you have less to say.

  2. One sentence of reason

    Say what is holding it up, plainly. Clients want to know it is real, not every detail.

  3. A date, or when you will know it

    Give a new date you believe. If you cannot, give the date you will update them, and keep it.

  4. Whose turn it is

    Say clearly whether the client needs to do anything. “Nothing is needed from you” is reassuring on its own.

Four templates

A — Waiting on someone else (a permit, a supplier, an office)Copy and adapt · {{fields}} are yours to replace

Subject {{project}}: new date {{new_date}}

Hi {{first_name}},

A quick update on {{project}}: we are still waiting on {{third_party}}, so we will not be ready by {{old_date}} as planned.

Our new date is {{new_date}}. Nothing is needed from you. I will update you again by {{next_update_date}}, or sooner if it moves.

{{your_name}}

Naming the outside party shows the delay is real without sounding like an excuse. “Nothing is needed from you” stops the client wondering whether it is their fault.

B — Waiting on the clientCopy and adapt · {{fields}} are yours to replace

Subject {{project}}: we need {{item}} to keep the date

Hi {{first_name}},

To finish {{project}} by {{old_date}}, we still need {{item}} from you.

If it reaches us by {{cutoff_date}}, we keep the date. If it arrives later, the new date will be about {{new_date}}.

{{your_name}}

No blame, just cause and effect. The client can choose to keep the date, which is better than being told it already slipped.

C — Your own mistakeCopy and adapt · {{fields}} are yours to replace

Subject {{project}}: a delay on our side

Hi {{first_name}},

I want to let you know before {{old_date}}: {{project}} will be late, and it is on our side. {{one_sentence_reason}}.

The new date is {{new_date}}, and we have {{what_you_changed}} so it does not happen again. Nothing is needed from you.

I am sorry for the change of plans.

{{your_name}}

Own it once, clearly, then move to the fix. A long apology reads as worry; a short one with a new date reads as control.

D — You do not know the new date yetCopy and adapt · {{fields}} are yours to replace

Subject {{project}}: update by {{next_update_date}}

Hi {{first_name}},

{{project}} will not be ready by {{old_date}}. {{one_sentence_reason}}, and we do not have a firm new date yet.

I will send you the new date by {{next_update_date}}, even if the news is that we are still waiting.

{{your_name}}

When you cannot promise a delivery date, promise an update date and keep it. That promise is the one that rebuilds trust.

What to leave out

Blame on a colleague or another client, long technical explanations, internal names the client does not know, and any date you do not believe yourself. A second delay hurts more than a later first date.

After you send it

  • Update wherever the client checks their status, so the page and the email say the same thing.
  • Put the next update date in your calendar a couple of days early.
  • If the new date slips too, say so before it passes, with the same four rules.
  • When the work is done, a one-line “thanks for your patience” closes the loop.

Delay email checklist

  • Sent before the old date
  • The reason fits in one sentence
  • There is a new date, or the date of the next update
  • It says whether the client needs to do anything
  • Your status page or tracker shows the same date