How to Tell Your Boss a Project Is Behind Schedule (Without Losing Their Trust)

Why delay news goes wrong

Delay news rarely damages trust on its own. What damages trust is how it arrives. Four patterns cause most of the damage:

• Waiting until it’s certain. You hope to catch up, so you say nothing. By the time the delay is certain, your boss has no time left to adjust.
• Leading with the explanation. Three paragraphs of background before the new date makes the reader hunt for the point — and look for excuses.
• Assigning blame mid-project. “The vendor dropped the ball” turns a planning conversation into an argument about fault.
• Bringing a problem with no options. Your boss now has to solve it for you, on the spot.

When should you tell your boss a project is behind?

Tell your boss as soon as you know the date is at risk — not when the delay is certain. Early bad news gives your boss options: move resources, adjust what they’ve promised upward, or accept a smaller scope. Late bad news only gives them a surprise.

A useful test: if your boss would want to know before their own next meeting with their boss, tell them today.

How to tell your boss a project is behind schedule: the 5-part update

Use the same order every time. It answers your boss’s questions in the order they’ll ask them.

1. The result: what moved, and to when

Start with the new date — one sentence, no preamble.

“The vendor integration will finish on July 15, not June 30.”

2. Where things stand

Remind your boss what’s done and what’s left. They have other projects; don’t assume they remember the plan.

“Data mapping and testing are complete. What’s left is the billing connection.”

3. Why it slipped

One or two causes, stated as facts. Not a story, and not a defense.

“The vendor’s API changed in May, and their updated documentation arrived three weeks late.”

4. What the delay affects

Say what moves because this moved: other teams, customers, costs, commitments your boss has made.

“Customer invoices will stay manual for two more weeks. No customer-facing date changes.”

5. Risks and options

If there’s a risk of slipping further, say so — and bring options, with the one you recommend.

“If the vendor misses July 1 again, we can launch without automated invoices and add them in August. I recommend we hold the July 15 date and decide on July 1.”

How I report delays

When I report a delay upward, I follow two rules.

The first is timing: as soon as possible, every time. Not when I’m sure, not after I’ve tried one more fix. If the date is at risk, my boss hears it from me before they hear it from anyone else.

The second is tone: as dry as possible. Just the facts — the new date, where we are, why it moved, what it affects, and what we can do. I keep the question of who made the mistake and who’s responsible out of it completely. That conversation has its place, but it’s after the work is done. While the project is still running, a delay report is about solving the problem, not settling the account.

The order matters more than the wording. A boss who gets the new date in the first sentence spends the rest of the conversation helping you. A boss who has to dig for it spends the conversation doubting you.

Copy-paste delay update (email or message)

Subject: [Project] — new completion date: [date]

Hi [Name],

The result: [Project/milestone] will finish on [new date], not [old date].

Where we are: [What’s done]. Remaining: [what’s left].

Why it moved: [One or two facts].

What it affects: [Teams, customers, costs, commitments — or “nothing outside the team”].

Risks and options: [If it slips further, what happens]. Options: [A], [B]. I recommend [A], and I’ll confirm by [date].

Happy to talk through it — [time] works for a 10-minute call.

How do you present bad news to executives?

Present bad news to executives with the same five parts, shorter, and never as a surprise in a big meeting. Send a short written pre-read first, so the executive hears it from you before the room does. In the meeting, spend your time on part 5 — the options and the decision you need — not on the explanation.

For the regular updates that follow, lead with the verdict, then the risk, then your recommendation. Here’s the full format with a template: how to write a status update for executives.

If the delay forces a real decision — more budget, a smaller scope, a new launch date — put it in a one-page decision memo: the decision you need, the options, and what happens if nobody decides.

What not to say

• “We’re doing our best.” It answers a question nobody asked. Give the new date.
• “It should be done soon.” Soon isn’t a date. If you’re unsure, give a range and the day you’ll confirm.
• “It’s not my fault.” Even when it’s true, it moves the conversation to blame. Save it for the review after the project.
• “There’s nothing we can do.” There’s always “do nothing” plus at least one option. Bring both.

After you’ve told them

The delay update creates new commitments: a confirmation date, a decision, maybe new action items. Follow up on them the same way you’d follow up on any meeting — one owner, one date, a check-in at the midpoint. Here’s how to follow up on action items after a meeting without nagging.

If the delay needs a decision above your boss’s level, read how to escalate an issue without going over your boss’s head.

If the deadline was unrealistic from the start, it’s better to negotiate it before it slips: see how to push back on an unrealistic deadline from your boss.

Frequently Asked Questions

The bottom line

Bad news doesn’t get better with age. Tell your boss as soon as the date is at risk, put the new date first, keep it dry, and bring options. That’s how to tell your boss a project is behind schedule — and keep their trust while you do it.

Related reading:

• How to follow up on action items after a meeting (without nagging)
• Decision memo template: one page, one decision
• Pre-mortem: how to surface the risks nobody says out loud