How to Tell a Client Their Project Is Delayed (Email Templates)

The delay email is the hardest one to write. Here's how to write it honestly, professionally, and in a way that keeps the relationship intact.

Why the Delay Email Feels Impossible

You know you need to send it. You've been putting it off for two days. The longer you wait, the worse it gets — but every time you open the draft, you close it again.

This happens to almost every freelancer. The delay email triggers a specific kind of anxiety: the fear that admitting a delay will make the client angry, damage your reputation, or end the contract.

In reality, the opposite is usually true. Clients handle delays far better than silence. What damages relationships isn't the delay — it's finding out about it late, or not finding out at all.

The Structure of a Good Delay Email

1. State the situation clearly in the first sentence — don't make them read three paragraphs to find out there's a delay.
2. Explain briefly what happened — one or two sentences. Don't over-explain or make excuses.
3. Give a revised timeline — be realistic. If you're not sure, give a range.
4. Reassure them the project will get done — tell them what you're doing to get back on track.
5. Invite them to discuss if needed — some clients need to talk it through.

Delay Email Template 1: Small Delay (1-3 days)

Subject: [Project Name] — Quick Update on Timeline

Hi [Client Name],

I wanted to give you a heads-up: [deliverable] is going to be a few days later than originally planned. I'm now targeting [new date] instead of [original date].

[Brief reason — one sentence.]

I'm focused on this and confident we'll be back on schedule after this. I'll send you [deliverable] by [new date].

Sorry for the shift — let me know if this causes any issues on your end.

[Your name]

Delay Email Template 2: Significant Delay

Subject: [Project Name] — Timeline Update

Hi [Client Name],

I need to update you on the timeline for [project]. We're running behind, and I want to be transparent about it rather than wait until the deadline.

Here's where things stand: [honest 2-3 sentence summary of what happened and current status].

Revised timeline:
• [Milestone 1]: [new date]
• [Milestone 2]: [new date]
• Final delivery: [new date]

I've [what you're doing to catch up]. I'm confident in these revised dates.

I know this isn't ideal. If you'd like to jump on a call to discuss, I'm available [times]. Otherwise I'll keep you updated with weekly progress reports.

[Your name]

Delay Email Template 3: Delay Caused by External Factor

Subject: [Project Name] — Timeline Impact

Hi [Client Name],

Quick update: [project/feature] will be delayed by approximately [time period] due to [external factor — third-party API, waiting on assets, technical blocker, etc.].

Specifically: [one sentence on the situation].

My revised estimate is [date]. In the meantime, I'm [what you're doing — working on other parts, researching alternatives, etc.].

[If they can help:] If you're able to [action from client — provide assets, approve spec, etc.], that would help me move faster.

I'll keep you updated as this develops.

[Your name]

What Not to Write

• Don't over-apologize — one apology is enough. Multiple apologies start to sound hollow and erode confidence.
• Don't over-explain — a long list of reasons for the delay reads as making excuses. State the situation and the plan.
• Don't be vague about the new timeline — "it might be ready next week" is not a revised timeline. Give a specific date, even if it's a range.
• Don't wait until the deadline has passed — the earlier you communicate, the better the outcome.

"The email that protects the relationship is never the one that explains away a delay. It's the one that says: here's what happened, here's the new plan, you can count on me."

Writing These Emails When You're Already Anxious

The delay email is hard precisely because you're already stressed. You're behind, you're worried, and now you have to write about it clearly and professionally — which takes energy you don't have.

This is exactly the problem UpdateBrief was built for. Paste your rough notes about the situation — even just "two days late on the API integration, told client Friday, new deadline is Wednesday" — and get a polished, ready-to-send email.

The writing part is the smallest problem. UpdateBrief handles it so you can focus on the actual work.