Client Delay Email Before a Deadline: Give an Early Warning

State the risk before it becomes a surprise

Identify the deliverable and agreed date. Explain which checked dependency puts it at risk. Avoid announcing a definite delay if you only know there is uncertainty. Equally, do not hide a likely problem behind an optimistic sentence that gives the client no reason to plan differently.

Own the warning you can provide

You may not control every external step, but you control how accurately and promptly you communicate. If you should have identified the risk earlier, acknowledge that. Keep internal blame out of the message. The client needs a useful account, not an unverified description of which person or department caused everything.

Offer only viable options

A partial delivery or changed order of work may help if it is actually feasible. Explain the limitation of each option and ask which is useful where a choice belongs to the client. Do not describe a proposal as agreed. If there is no reliable completion estimate, commit to checking and updating rather than inventing one.

Continue: Client ↗

Keep the promised checkpoint

Send the next update at the stated time even if the dependency remains unresolved. Say what changed and what did not. Silence after an early warning can remove the benefit of giving it. Make the current status easy to find in the same thread or agreed project channel.