Work coordination
Explain a project delay without hiding the facts
An update that buries the cause or offers a vague new date makes the next conversation harder. Give the assistant the cause, what is still unknown, any revised date your team has agreed on, and who will read it.
A text to start with
Our project is delayed. The cause is [specific reason]. We do not yet know [what is uncertain]. The team has agreed the new target is [date], contingent on [condition]. The audience is [role]. Draft an update that names the cause plainly, says what we know and do not know, gives the revised date with its condition, and states the next checkpoint. Do not soften the cause or imply more certainty than we have.
Example request. Change the details to fit your situation.What to check before you send
Confirm the cause in the draft matches what happened, not a diplomatic version of it. If the revised date has a condition, that condition must appear in the update itself. Anything described as resolved should be resolved. If the audience includes stakeholders outside your team, check whether the technical detail suits them or whether they need a shorter summary.
Following up after the update
Name a checkpoint date in the update and keep it. When it arrives, send a short follow-up even if nothing has changed, so stakeholders are not left guessing. If the cause is still active, say so then instead of waiting until the next deadline is at risk.