How to tell your team a project is delayed
Reviewed 19 Sept 2026
Bad news gets worse when it arrives slowly. People who have to announce a delay often start with the background, hoping the listener will understand before hearing the conclusion. The listener hears a long build-up and expects something worse than the truth.
Say the size of the delay and the new date in your first sentence. Everything after that is explanation, and explanation is much easier to listen to once the uncertainty is gone.
The structure: new date, cause, plan, ask
- New date
What is late, by how much, and the date you are now committing to.
- Cause
One or two causes in a sentence. Facts, not blame and not a long apology.
- Plan
What is already being done, and what would put the new date at risk.
- Ask
Anything you need from the listeners, or what they should tell others.
Before and after
“So, um, about the project… we had some issues with the vendor and also the API changed, so basically we are a bit late, like a week maybe, but the team is working on it and, yeah, we should be fine I think.”
- The delay is the last thing the team hears, after two causes they cannot yet judge.
- “A bit late, like a week maybe” is not a date anyone can plan around.
- “We should be fine I think” asks the listener to trust a feeling rather than a plan.
“We are one week behind: the delivery moves from Friday the 17th to Friday the 24th. Two causes. The vendor delivered late, and their API changed, which broke our import. The fix is in testing now. The 24th holds as long as testing finishes by Tuesday, and I'll confirm that on Tuesday afternoon. Dana, could you let the client know today?”
Phrases you can use
- “We are going to miss Friday. The new date is the 24th.”
- “This will be two days late.”
- “I want to flag a delay before it surprises anyone.”
- “The main cause is…”
- “Two things changed:…”
- “I underestimated the testing time.”
- “The fix is already in testing.”
- “The new date holds as long as…”
- “I'll confirm by Tuesday afternoon.”
- “What I need from this group is…”
- “Could you let the client know today?”
- “If the 24th is a problem for anyone, tell me now.”
Common mistakes
Put the new date in sentence one. Then explain.
“A bit late” invites the worst guess. Give days and a date.
One “I'm sorry for the change of plan” is enough. Repeated apology takes time away from the plan.
Say what the date depends on. A conditional date you keep is worth more than a confident one you miss.
A ten-minute drill
- Think of a real or likely delay in your work. Write down only the new date and one cause.
- Record a 45-second announcement. Your first sentence must contain the new date.
- Check the transcript for “maybe”, “a bit”, “should” and “I think”. Replace each with a fact or a condition.
- Record again.
Questions people ask
Should I apologise for a delay?
Once, briefly, if the delay affects others. Then move to the plan. People remember whether you gave them a reliable new date far longer than they remember the apology.
What if I do not know the new date yet?
Give the date by which you will know: “I can't give a new date today. I'll have one by Wednesday, after the vendor call.” That is still something people can plan around.
When should I announce it?
As soon as you are reasonably sure. An early warning with a conditional date gives others time to adjust. A late, certain announcement removes their options.