Explain a missed deadline with a recovery plan

When a deadline is going to slip, silence makes the recipient plan around a date that no longer holds. Send the update as soon as you have enough information to explain the risk. You do not need a perfect recovery plan before acknowledging that the original commitment is in doubt.

Name the missed or threatened deliverable in the opening. Avoid ‘a slight delay’ if you do not yet know its length. A clear statement such as ‘The draft will not be ready for tomorrow's review’ is uncomfortable but gives the reader something definite to act on. Follow it with the relevant reason, not a chronology of everything that went wrong.

Explain the impact before offering reassurance

The recipient needs to know what the change affects. Does a review need to move? Can another part of the project continue? Will the delay reduce their own approval time? If you do not know the downstream effect, ask rather than assuming the change is harmless.

A hypothetical message could read: ‘The draft will not be ready for Thursday's review because the revised specifications are still being checked. I can send the unchanged sections today. I will confirm the remaining delivery date by 11:00 tomorrow after the technical review.’ This does not pretend that a partial draft is the original deliverable. It offers a useful interim step and a specific next update.

Only give a replacement deadline after checking the work required and the people needed. An optimistic date used to soften the news can create a second breach of trust. Where uncertainty remains, distinguish an estimate from a commitment and explain what will resolve it.

Offer choices that preserve the purpose

There may be a real choice between reducing scope, moving the date or changing the sequence. Describe the trade-off plainly. Do not quietly remove a required check to make the original date appear achievable. If the recipient must approve a change, ask for that approval through the agreed process.

Take responsibility for your part without speculating about motives or blaming colleagues. A short acknowledgement is usually enough. Repeated apologies can crowd out the information needed to recover the work; no apology at all can make the impact seem unrecognised.

After the revised delivery, review the cause separately. Was the estimate wrong, a dependency unconfirmed or the approval window too short? The recovery message should focus on what happens now. The later review should change the process so the same uncertainty is visible earlier next time.