It’s a sinking feeling.

You’ve checked the project plan, you’ve seen the team’s velocity, and you’ve done the math. There’s no way around it. You are going to miss your deadline.

Your first instinct might be to panic. Your second might be to hide, work harder, and hope for a miracle. “Maybe we can make up the time? Maybe I just won’t say anything yet…”

This is the single biggest mistake a project manager can make.

Hiding bad news doesn’t make it go away. It just makes it worse. The real failure isn’t being late; the real failure is the surprise. A “guru” PM knows this: Trust is not built by being perfect. Trust is built by being honest when things aren’t perfect.

Delivering bad news is one of the most important parts of your job. Here is your 4-step plan to do it professionally, confidently, and without losing your client’s trust.

Before You Say Anything: The “Don’t” List

DON’T wait until the last minute. Bad news early is a problem to be solved. Bad news late is a catastrophe and a breach of trust.
DON’T deliver it in a casual email or Slack message. This is a “face-to-face” conversation (a video call is the next best thing).
DON’T blame your team. (“The developers are just too slow.”) You are the leader. You are one team. You take ownership.
DON’T just present the problem. (“So, we’re late… what do you want to do?”) This is the weakest thing a PM can do. You must present solutions.

Your 4-Step Plan for Delivering Bad News

Step 1: Get Your Data (Don’t Panic, Prepare)

You cannot go to a client with a “feeling.” You must go with facts. Before you even think about scheduling the meeting, you must have the answers to these three questions:

What is the exact status?
- Wrong: “We’re just… behind.”
- Right: “Our original deadline was October 30. Our new, data-based projection is November 15.”
What is the root cause?
- Wrong: “A bunch of stuff just went wrong.”
- Right: “The delay is due to a 3-day unexpected server outage and a new feature request that added 10 days of unplanned work.”
What is the full impact?
- Wrong: “This is gonna be expensive.”
- Right: “This 15-day delay will impact the budget by $X and will require us to move the marketing launch.”

Step 2: Bring Solutions, Not Just Problems

You are now ready to build your “Go-Forward” plan. You must present options. This gives the client a sense of control and shows that you are already on top of the solution.

Your options will almost always involve the “Iron Triangle”: Scope, Time, and Cost. You can’t change one without affecting the others.

Option A: (Cut Scope) “We can still hit our original October 30 deadline, but it means we must cut features X and Y. We can add them back in Phase 2.”
Option B: (Add Time & Cost) “We can deliver 100% of the original scope, but it will move our deadline to November 15 and require a budget increase of $X.”
Option C: (The Hybrid) “We can cut feature X, which will get us most of the way. We will still have a small, 5-day delay and a minor budget impact, landing us on November 5.”

Crucially, you must also have a professional recommendation. “Based on our goals, I recommend Option A…”

Step 3: Deliver the Message (The Hard Conversation)

You have your data. You have your options. It’s time to schedule the call. Do not label the meeting “BAD NEWS.” Call it “Project Timeline & Strategy Review.”

Follow this script to guide the conversation.

The Opener (Be Direct): Get straight to the point. Don’t start with 10 minutes of small talk.
- Script: “Thanks for your time today. I’m calling because I’ve identified a delay in our project schedule that I need to make you aware of.”
The News (Facts, Not Emotion): State the problem clearly, using your data from Step 1.
- Script: “Our original go-live date was October 30. My latest forecast, based on [Root Cause], shows a new projected date of November 15.”
The Ownership (Take Responsibility):
- Script: “This is a miss in our original plan. I own that, and my team and I have spent the last two days creating a set of go-forward options for us.”
The Plan (Present Your Solutions):
- Script: “We have three ways we can handle this. I’d like to walk you through the trade-offs for each…” (This is where you present your Options A, B, and C).
The Recommendation & Next Steps:
- Script: “Based on our shared goal of [Project Goal], I recommend we go with Option A. It delivers the core value on time. If you agree, I can have a revised project plan to you by EOD.”

Step 4: Follow Up and Over-Communicate

The meeting is over. The client has (hopefully) chosen a new path. Your work is not done.

Send a Recap Email: Immediately after the call, send an email that summarizes the problem, the options discussed, and the decision that was made. This is your new “source of truth.”
Increase Communication: Trust is fragile. You must now “over-communicate” to rebuild it. Move from a bi-weekly to a weekly status report. Be extra transparent about progress against the new plan.

This is How You Build Real Trust

Delivering bad news is the moment you earn your title as Project Manager.

Clients know that problems happen. What they don’t know is if you’re the kind of person who will hide from a problem or face it head-on. By being direct, data-driven, and solutions-oriented, you prove you are a leader they can trust—especially when things get tough.

Dreading a tough conversation?

Sometimes you need a PM who isn’t afraid to manage the hard parts of a project, from complex timelines to challenging conversations. If you need a leader to get your project on track and keep you informed every step of the way, I’m here to help.

[Contact me] for a consultation.

How to Deliver Bad News to Your Client