TemplateEmail
Project delay notice
Deliver a slipped deadline like a professional: the new date, the reason without excuses, what's protected, and what you're doing so it holds.
Last updated
Fill in the blanks
Assembled in your browser — nothing you type is stored or sent anywhere.
Your email
Subjectthe inventory dashboard — revised delivery date: Friday 26 September
Hi Rohit,
I need to move the delivery date for the inventory dashboard. The revised date is Friday 26 September — one week later than planned. I'm sorry for the disruption this causes.
The reason: the supplier API we integrate returned malformed data for two of your warehouses, and building the validation layer to handle it safely took priority over hitting the date with bad numbers.
What this doesn't change: the scope is unchanged, the budget is unchanged, and the reporting module is already live for your team to use.
To make the new date reliable: the risky integration work is now done and tested; what remains is UI polish we've done many times over.
If the revised date creates a problem on your side, tell me what's immovable and I'll re-plan around it.
Best regards,
Nisha
How to use it well
- →Lead with the new date, not the apology — the reader's first question is "when", and burying it under context reads as evasion.
- →One honest reason beats three small ones; a list of reasons reads as a list of excuses.
- →Send it the day you know. A delay announced early is planning; the same delay announced late is a broken promise.