How do I tell someone a project will be late before the deadline passes?
Quick answer
Tell the person as soon as you have a credible reason to expect a delay. State what will miss the deadline and what that affects, give a revised date or a time for your next update, and briefly explain the steps you are taking. If a decision or trade-off could reduce the impact, ask for it directly. Be candid, specific, and avoid promising a date you cannot support.
The question, the details, the next step.
I can see that our project is likely to miss its deadline, but it hasn’t passed yet. What should I say, and how much detail should I give about the reason?
Tell the affected person now, rather than waiting until the deadline is missed. Keep the message factual and focused on four things: what is delayed, the likely impact, the revised timing, and what you are doing next. If you do not yet have a dependable new completion date, say when you will provide a firmer update instead of guessing. Early notice gives the other person a chance to adjust plans or help resolve a blocker.
Give enough context to explain the change, but keep ownership of the update. Name the specific issue and its consequence in plain language; skip a long timeline of who did what. For example, “The final review needs another round, so I can’t send the approved draft Friday.” That is more useful than “Things got complicated,” and less defensive than a lengthy account of every obstacle. Don’t blame a person or team unless identifying their role is necessary to resolve the issue.
What if I’m not certain of the new date yet? How can I ask for help without making it sound like the other person caused the delay?
Separate what you know from what you still need to confirm. You can say that Friday is at risk, explain what is being checked, and commit to a specific time for your next update. If you can offer a reasonable date range, label it as an estimate and say what it depends on. Avoid presenting a hopeful guess as a firm commitment. Set a next-update time you can meet, even if the final schedule is still being worked out.
Connect any request to the choice in front of them. Ask for one specific decision, resource, or scope trade-off, and explain what it could change. For example: “If we send the core section first and the remaining section Tuesday, would that help your review?” Make clear who owns the next step and by when. If there is no useful decision for them to make, don’t invent one; share the revised plan and invite them to flag conflicting needs.
Can you give me a message I can adapt, including an example?
Use this template and replace the brackets with confirmed details. Keep the impact concrete, and include only recovery steps you can actually take.
Subject: Project timing update: [project or deliverable]
Hi [name],
I’m writing before the [original deadline] because [deliverable or milestone] is at risk of being late. [Brief, factual reason]. This means [specific impact on their work, review, or next step].
I’m [recovery action one] and [recovery action two]. Based on what I know now, I expect to deliver [revised date or clearly labeled estimate]. [If not yet known: I’ll send a timing update by date and time] once [specific uncertainty] is confirmed.
[Decision or help needed, if any]: Could you [specific action] by [date]? That would allow us to [practical effect]. If that timing doesn’t work, please tell me what needs to take priority.
I’m sorry for the disruption. I’ll keep you updated if the plan changes.
[Your name]
Worked example, with hypothetical details: “The review of the draft is taking longer than planned, so I can’t send the approved version Friday. That leaves your team less time for its Monday review. I’m narrowing the open comments today and checking the remaining changes with the reviewers. I expect to send the draft Tuesday by noon. Would a short outline Friday help you start planning?” Change or remove any detail that isn’t true. Send the message through the normal project channel, and follow through on the date you promise for the next update.
A practical checklist
Send the update before the current deadline, once a delay is credible.
Name the affected deliverable and explain the practical impact.
Give a supportable revised date, or a specific time for your next update.
List only recovery steps you can take and own.
Ask for a specific decision or trade-off only if it could change the plan.
Check that the message is factual, respectful, and free of blame or unsupported promises.
A few more useful answers
Should I apologize for the delay?
A brief apology for the disruption is appropriate when it fits the situation. Pair it with clear timing and next steps rather than relying on an apology alone.
What if the revised deadline is also uncertain?
Label any date as an estimate and explain what it depends on. If you cannot give a useful estimate, commit to a specific next update instead.
Should I tell them in a meeting or in writing?
Use the channel that lets the affected person respond in time. If you discuss it live, send a short written recap of the impact, timing, decisions, and owners.