How to Deliver Bad News at Work: A Script for the Actual Conversation

Bad news and negative feedback get lumped together because both are uncomfortable to say out loud, but they're not the same problem. Negative feedback tells someone their work or behavior fell short, a missed deadline, an error in a deck, a tone in meetings, and it's aimed at changing what that person does next. Bad news is different: it's a fact that's already decided, a delay, a budget cut, a canceled contract, a denied request, and the other person can't change the outcome. They can only absorb it and figure out what happens now.

That distinction matters because it changes what the conversation needs to do. Negative feedback conversations end with a next step the other person commits to. Bad news conversations end with the other person understanding what happened, why, and what comes next for them, even when the answer to that last part is "less than they hoped." Trying to run a bad news conversation like a feedback conversation, asking "what do you think we should do differently" about a decision that's already final, reads as dishonest, because it implies a say in something that isn't up for a vote.

The scripts in this guide cover the range of bad news that comes up at work: telling a client a timeline slipped, telling a team a budget or a role got cut, telling a stakeholder a deal fell through, declining a request or a proposal, and reporting a mistake or a miss upward to your own manager. If what you're facing is instead a conversation about someone's performance or conduct, the structure is close but the goal is different, and it's worth reading the difference in the last section before you use the wrong tool for the job.

Most guides on how to deliver bad news treat all of this as one skill, which is part of why so much of the advice out there stays vague. A script built for telling a client their launch slipped doesn't automatically work for telling an employee their role was cut, even though both start from the same first sentence.

The few minutes before the conversation decide more of the outcome than anything you say once you're in it. Rushing into a bad news conversation half-prepared is where most of the damage happens, not in the words themselves but in the hedging, the over-explaining, and the vague timeline that follows.

This is the part most guides skip past. Below is a structure you can use for nearly any piece of workplace bad news, a delay, a cut, a rejection, a canceled deal, adapted to your specific situation. It works whether you're telling a client, a team, or your own manager, because the shape of the problem is the same in every version: say the news, give the reason briefly, and be specific about what happens next.

Not every piece of bad news needs a meeting, and forcing one for a minor delay can read as more dramatic than the situation calls for. But writing bad news well is a different skill from saying it out loud, because there's no tone of voice to soften it and no way to read the other person's reaction and adjust.

The script gets you through the first thirty seconds. What happens after, the questions, the pushback, the silence, is where most people feel the least prepared, because there's no way to fully script someone else's reaction.

A handful of habits show up again and again in bad news that damages trust more than the news itself did.

Burying the news in the middle of a long message. If someone has to read three paragraphs of context to find out the launch slipped, they'll remember the burying more than the delay itself. Research on loss aversion, going back to Daniel Kahneman and Amos Tversky's work on how people weigh losses more heavily than equivalent gains, is part of why bad news already feels bigger to the recipient than the sender intends. Making them dig for it only compounds that.

Over-explaining instead of stating the decision. A long chain of justification can start to sound like you're arguing yourself into the decision rather than reporting one that's already made, which invites exactly the negotiation you were trying to avoid.

Softening the news until it's unclear. "There might be some changes to the timeline" when the launch has, in fact, already moved six weeks leaves the other person under-informed and more upset when they learn the real scope later.

Delivering it through the wrong channel. A layoff or a canceled contract delivered by email because the conversation felt too uncomfortable to have out loud tells the other person exactly how much you wanted to avoid facing them, and they notice.

Practicing the reason but not the opening line. Most people who prepare for bad news rehearse how they'll justify the decision and skip rehearsing the sentence that actually delivers it, which is backward, since the opening line is the part that determines whether the rest of the conversation starts on solid footing.

Skipping the follow-up. Bad news delivered once and never revisited leaves people guessing whether anything changed. A short update at the next agreed touchpoint, even a small one, is what turns a hard conversation into a relationship that survived it.

The scripts in this guide are built for bad news where the outcome is already decided and the other person isn't being evaluated, a delay, a budget cut, a lost deal, a declined request. A layoff conversation with a specific employee carries legal and emotional weight that goes beyond what's covered here, and a performance review is a different exercise entirely, one built around evaluating someone's work over a period of time rather than reporting a single decided outcome. If either of those is what you're actually facing, a guide built specifically for having difficult conversations with employees or for giving negative feedback will fit the situation better than the general script for how to deliver bad news covered here.

What all of these share is the same underlying discipline: say the hard part first, keep the explanation short, and be specific about what happens next instead of leaving the other person to guess. Knowing how to deliver bad news well doesn't make the news easier to hear, but it does mean the person on the other side of the table walks away with clarity instead of confusion on top of disappointment.

The part that's hardest to get right isn't the structure, it's saying the opening line out loud for the first time without it coming out softer or vaguer than you meant. SayNow AI lets you rehearse that exact moment, the flat statement of the news, the short reason, the specific next step, before the real conversation happens, so what you deliver is the version you practiced and not the one you improvised under pressure.