A simple project delay email structure
Use five parts: the dependency that changed, the date it was expected, the date it became available, the original delivery date and the revised delivery date. Add one sentence explaining that existing scheduled commitments mean elapsed delay does not necessarily translate one-for-one into calendar days.
Subject: Project schedule update — revised delivery date
Hi [Client],
The [feedback / files / approval / access] required for the next production stage was due on [date] and became available on [date]. I have recalculated the remaining work against the next available production capacity.
Original delivery: [original date]
Revised delivery: [new date]
Because production capacity is reserved around existing commitments, the elapsed client delay does not necessarily translate directly into the same number of calendar days at the end of the project.
I’ll continue against the revised schedule and let you know promptly if anything else changes.
What to avoid
- Do not invent a date just to make the email easier to send.
- Do not silently move another client’s work to preserve the old deadline.
- Do not bury the revised date inside a long explanation.
- Do not write an emotional blame summary when a factual dependency timeline is enough.
Calculate first, write second
The wording is only useful if the date behind it is feasible. SlotReset calculates the normal-capacity date first and can also test whether extra capacity genuinely changes the outcome.
Need the exact revised date for the email?
Run the free calculation, then use the result in your update. The optional Delay Report generates neutral client-ready wording automatically.
Calculate the date for your email