Tell a client about a delay without making unverified promises
Explain a delay promptly, separate facts from estimates, and commit to the next update. Includes messages for known and unresolved delivery dates.
Open the solution →A problem in a small team’s work
The client plans around a deadline we can no longer meet.
The team knows about a delay but waits for a firm replacement date. Meanwhile, the client schedules people or dependent work around the original agreement. They need an accurate update while the new date is still being checked.
Why address it
Late information leaves the client less time to adjust dependent work. An unverified promise creates another commitment and another explanation. Separate the delivery delay from how long the client remained uninformed.
How big is the problem in your team?
For the last five deadline changes, record when the team established the impact, when the client was told, and whether the promised next update was sent on time. Record documented change costs separately; do not count the entire project value as a loss.
This is a recommended measurement approach, not an estimate of an average business loss. We have no verified market benchmark for this specific problem. Your baseline lets you compare the change later.
Choose what needs to change
Internal reminders that stop when the task is done
Use current task state and suppress same-day repeats. The included script starts in dry-run mode.
Open the solution →Start with a verifiable process
First establish the change and who will contact the client. An internal automated reminder can track the next update; the responsible person checks the current state and commitment before sending. The supplied templates are sufficient for individual messages.