Why project delay emails matter more than you think
Most freelancers dread sending a delay notice. They wait too long, hoping the delay will resolve itself. By the time they finally send it, the client is already frustrated — not because the project is late, but because they weren't informed.
The research on client retention is clear: clients forgive delays when they're communicated early and professionally. What they don't forgive is silence. The delay email, done right, is not an admission of failure — it's a demonstration of professionalism.
What a good project delay email does
- Leads with the information. State the delay clearly in the first sentence. Don't bury it after pleasantries.
- Explains the reason briefly. One sentence. The client doesn't need your full internal postmortem.
- Gives a new, specific date. "A few more days" is worse than "May 3rd." Give them something concrete.
- Takes responsibility. No blaming external factors at length. Take ownership of the communication.
- Shows what you're doing about it. Brief plan for recovery builds confidence.
- Keeps the tone steady. Apologetic but not groveling. Professional but not cold.
Example: project delay notice
Hi Marcus,
I wanted to reach out proactively about the Brand Identity Redesign project. The design phase has taken somewhat longer than I originally scoped — the iterative feedback on the logo concepts was valuable but extended my timeline.
The new estimated delivery for the complete brand package is May 3rd. I'll send you a progress preview on April 28th so you can see where things stand.
I apologize for any inconvenience this causes with your planning. Please let me know if the new date creates any issues I should be aware of — I want to make sure we stay aligned.
Thank you for your understanding,
Jamie
Timing: when to send the delay notice
The rule is simple: as soon as you know. The moment you have reasonable confidence you'll miss a deadline, send the email. Waiting to be sure you'll be late means the client finds out at the last moment — the worst possible outcome.
Early communication gives the client time to adjust their plans. It also gives you time to potentially recover. A delay notice sent 10 days before the deadline lands very differently than one sent 10 hours before.
Common mistakes in project delay emails
- Burying the lead. Three paragraphs in, the client still doesn't know there's a delay. State it in the opening sentence.
- Over-explaining. One clear reason is better than a list of circumstances. You're communicating, not defending.
- Vague new timelines. "Soon" and "a few more days" erode trust. Give a specific date.
- Excessive apology. One genuine apology. Not seven. Excessive apology makes the client more anxious, not less.
- Waiting too long. The earlier you send, the better the outcome. Every day of delay costs you goodwill.
Frequently asked questions
What if I don't know the new delivery date yet?
Send a preliminary notice anyway. "I'll have a confirmed new timeline for you by Thursday" is better than silence. Then follow up Thursday with the confirmed date.
Should I offer a discount?
Generally no — not proactively. Offering a discount unprompted signals that the delay is worse than it is. If the client asks, address it then. Focus the email on communication and recovery.
How does Briefly know what to write?
You provide the context — project name, client, reason for delay, new timeline. Briefly uses those details to generate an email in your chosen tone. The more specific your notes, the more personalized the result.