When the date changes, the client needs an update
The team knows Monday’s promised deliverable will not be ready. Hoping for a quick fix, it postpones the message. Meanwhile, the client plans dependent work around a date the team already considers unrealistic.
Prepare a specific update when the change affects an agreed step. You do not need every answer yet. You do need to distinguish known facts, unresolved checks, and the next update.
Use the message templates and next-action record or completed fictional example. None of these messages is sent automatically.
Check the latest valid agreement first
Find the promised deliverable, date, and original agreement. Distinguish a confirmed deadline from a working estimate. Check whether the client replied or another colleague issued a more recent update.
Establish the actual impact: is the whole result missing, only part of it, or is usability affected? Assign one owner to the next step. Separate messages from several colleagues can add uncertainty.
State four things
Explain the original step, what changes, the verified impact, and the next confirmed action. Give a brief reason when it helps the client decide. Avoid making the client participate in internal blame.
When you have a verified replacement date, connect it to the deliverable and any dependency. When you do not, promise an update time you can meet. The update date is not a new delivery deadline.
A fictional example with an unresolved delivery date:
Hi Jamie, we will not complete the final export planned for October 12. Our review found incorrect data relationships that need repair before handover. We are still checking the extent of the repairs, so we do not have a confirmed replacement date. By October 14 at 3 p.m. Eastern, I will send the review outcome and a proposed next step. If the delay blocks another part of your work, please tell me which one so we can assess an alternative together.
The dates and issue are fictional. Use only verified facts in the actual message. Sending the review outcome also means writing on time when the review has not yet produced a final answer.
Offer only a feasible alternative
You may be able to deliver a usable part earlier. State what it enables and what remains missing. A working preview must not look like a final deliverable. If the part has no independent value, sending it only to create an impression of progress is unlikely to help.
Open a separate decision when scope or price changes. A delay update should not silently alter the agreement. Handle commercial consequences under the actual project terms.
Do not invent a date because the client wants certainty. An unverified promise creates another commitment to explain later.
Record the next update as work
Keep the message, change reason, promised update time, and owner with the project. Create a task for someone who will recheck the current state before sending. Continue with follow-up with a pre-send review.
Update the client earlier if the situation changes earlier. If they reply with a different priority, retain it for a decision rather than automatically treating it as a new accepted commitment.
Try two fictional outcomes: a confirmed replacement deadline and a still-unresolved date at the promised update time. In both, the client should receive an accurate message and a specific next step. Automation can track the task; the message must follow the actual state.
If the delivery date is still unknown on October 14, send the promised update anyway. Morgan’s fictional message could be: “Hi Jamie, the export review has not yet established the extent of the repairs. We still cannot hand over the final export, and the delivery date remains unconfirmed. Tomorrow, October 15, by noon America/New_York, I will send the capacity-review status and next action.” Only promise that next update after reserving time to send it.
Use an internal task reminder to track your update. The reminder goes to a teammate; it does not send a project-status message to the client. This procedure does not require an AI agent: the essential work is verifying the impact and keeping the next contact commitment.