Professional Communication
How to Deliver Bad News in a Professional Email
Something went wrong. A delay, a miss, a budget overrun. Now you need to tell the person who needed it to go right. Here's how to deliver bad news in a way that preserves trust — and a tool that writes the email for you.
Write your bad news email with AI
Tell us what happened and what your plan is. Get a clear, professional email that preserves the relationship.
Write my bad news email →Free. No account. Ready to send in 60 seconds.
What to include in your bad news email
- The news, upfront: Don't bury the lede. State the bad news in the first paragraph. Recipients who sense something is wrong but can't find it will trust you less, not more.
- Brief explanation: One or two sentences on why it happened. Don't over-explain or make excuses — take ownership and move quickly to what you're doing about it.
- Your plan: This is the most important part. What are you doing to fix it, mitigate it, or prevent it from happening again? Be specific.
- Revised timeline or expectation: Give them a new date or outcome to plan around. Uncertainty is harder to work with than bad news.
Example bad news email
Here's what a well-written bad news email looks like in practice. Notice how it's direct, warm, and preserves the professional relationship.
Subject
Project Update — Revised Timeline
Hi Marcus,
I need to share some news about the project timeline that I wanted you to hear from me directly.
We're going to need an additional three weeks beyond our original delivery date. We hit an unexpected dependency with the third-party API integration that we couldn't fully scope until we were deep in the build. Our original estimate didn't account for the complexity we found.
Here's what we're doing about it: I've brought in a second engineer to focus entirely on the integration problem. We're also running parallel work on everything that doesn't depend on the API, so we lose as little time as possible. Our new delivery target is May 15th, and I'm confident in that date.
I understand this affects your planning, and I'm sorry for the impact. I'm available to talk through the details this week if it would help.
[Your name]
Want a version personalized to your situation?
Answer a few quick questions — AI does the rest.
Write mine →
Do's and don'ts
✓ Do this
- Lead with the bad news — don't make them wade through preamble
- Take ownership — don't blame others or external factors primarily
- Have a plan before you send — 'I don't know yet' is the worst thing to pair with bad news
- Give a specific new date or expectation
- Offer to talk — some news is better processed in conversation
✗ Avoid this
- Bury the bad news at the end of a long email
- Over-explain or justify excessively
- Send without a plan for addressing it
- Be vague about what the 'fix' is
- Minimize the impact with phrases like 'it's really not that bad'
Common mistakes that backfire
- Softening the news so much it doesn't land — recipients need to understand the actual situation
- Focusing on explanation rather than plan — 'why it happened' matters less than 'what we're doing about it'
- Sending without checking: do you have a realistic new timeline to offer?
- Waiting too long to send — bad news doesn't improve with age, and late disclosure is its own problem
- Not offering a conversation — some people need to talk through bad news, not just read it
The right structure
A professional bad news email typically follows this structure:
- Lead with the news: State clearly what happened or what's changing. First paragraph.
- Brief explanation: Why it happened — honest and concise, without being defensive.
- Your plan: What you're doing about it. Specific steps and owners.
- Revised expectation: New timeline, date, or outcome they can plan around.
- Offer to talk: Some news needs a conversation. Make yourself available.
Frequently asked questions
Should I deliver bad news by email or in person?
Significant bad news (major delays, budget overruns, serious problems) is often better as a call or meeting first, followed by a confirming email. Minor bad news can go by email alone.
What if I don't have a plan yet?
Get one before you send. 'I don't know what we're going to do' paired with bad news is the worst combination. Even a preliminary plan ('we're assessing options and will have an answer by Thursday') is better than nothing.
Should I apologize in the bad news email?
If the situation is genuinely your fault or your team's fault, yes — a sincere, brief apology is appropriate. If it's external circumstances, acknowledge the impact without an apology: 'I understand this affects your timeline.'
How do I avoid sounding defensive?
Minimize the explanation and maximize the plan. The more space you give to 'why it happened,' the more defensive you sound. Lead with what you're doing about it.
What if this is the third time this has happened?
Acknowledge the pattern. 'I know this is the second time we've had to extend the timeline' shows you understand the impact. Then focus extra hard on what's different about the plan this time.
Write your bad news email now
Answer a few questions about your situation. AI drafts a professional, ready-to-send email in under a minute.
Write my bad news email →Free. No account. Your details stay private.