What is the best structure for delivering bad news in writing?
The most effective structure for bad news in professional contexts is the indirect approach: begin with a brief buffer that acknowledges the context or relationship, then provide the rationale for the decision, deliver the bad news clearly and directly, and close with forward-looking information or alternative options. This structure prepares the reader emotionally before the negative information.
Delivering bad news is one of the most challenging tasks in professional communication. Whether you are informing a client that a project will miss its deadline, telling an employee that their position has been eliminated, rejecting a vendor's proposal, or announcing a policy change that will be unpopular, the way you communicate negative information has lasting consequences for trust, morale, and professional relationships.
In writing, the challenge is magnified because you cannot read the recipient's reaction in real time, adjust your delivery, or answer immediate questions. The message must stand on its own, and it must accomplish a delicate balance: being clear enough that the reader understands the news, empathetic enough that they feel respected, and constructive enough that they see a path forward.
Research by the Harvard Business Review found that how bad news is communicated matters more to recipients than the news itself -- people who feel treated with honesty and respect are significantly more likely to maintain trust in the communicator and the organization, even when the news is deeply unwelcome [1].
The Two Approaches: Direct and Indirect
Business communication theory identifies two primary structures for bad news messages. The right choice depends on the severity of the news, your relationship with the reader, and the cultural context.
The Indirect Approach (Buffer-Reason-News-Close)
Best for news that is personally significant, potentially emotional, or where preserving the relationship matters:
- Buffer: Open with a neutral or positive statement that establishes common ground.
- Reasons: Explain the rationale behind the decision before delivering the news.
- Bad news: State the negative information clearly but concisely.
- Close: Offer alternatives, next steps, or forward-looking information.
Why it works: By providing context before the news, you help the reader understand and process the decision. The buffer prevents the shock of an opening-line blow, and the reasons frame the news as a considered decision rather than an arbitrary one.
The Direct Approach (News-Reasons-Close)
Best for news that is time-sensitive, not deeply personal, or where the reader expects directness:
- Bad news: State the key information immediately.
- Reasons: Provide the rationale.
- Close: Next steps, timeline, and resources.
Why it works: In urgent situations, burying the news behind a buffer wastes time and frustrates readers who just want to know what happened. The direct approach respects the reader's need for information and their ability to handle it.
"The indirect approach is not about softening or hiding the news -- it is about preparing the reader to receive it constructively. The direct approach is not about being blunt -- it is about respecting urgency." -- Kitty O. Locker, Business and Administrative Communication, 12th edition [2]
When to Use Each Approach
| Situation | Recommended Approach | Reason |
|---|---|---|
| Rejection of a job candidate | Indirect | Highly personal, relationship matters |
| Layoff or position elimination | Indirect (after in-person notice) | Deeply personal, high emotional impact |
| Project delay notification | Direct | Business-critical, reader needs facts fast |
| Proposal rejection | Indirect | Preserves relationship for future business |
| Service outage notification | Direct | Urgent, operational impact |
| Policy change that reduces benefits | Indirect | Affects morale, needs context |
| Budget cut announcement | Direct or indirect | Depends on severity and audience |
| Product recall | Direct | Safety-related, time-sensitive |
The Indirect Approach in Detail
Step 1: The Buffer
The buffer is a brief, genuine opening that establishes a connection before the bad news. It should be relevant to the topic (not just generic pleasantries) and honest (not misleadingly positive).
Effective buffers:
- "Thank you for the time and effort you invested in your proposal for the Henderson account."
- "We appreciate your interest in the Senior Analyst position and the impressive qualifications you shared."
- "Over the past three years, your team has consistently delivered exceptional results on this account."
Ineffective buffers:
- "I hope you are having a great week!" (Too generic, feels false before bad news.)
- "We are so impressed by your amazing work." (Over-the-top praise before bad news feels manipulative.)
- "This is a difficult email to write." (Centers your discomfort instead of the reader's needs.)
Step 2: The Reasons
Explain the factors behind the decision clearly and honestly. The reader should understand why before learning what.
- Present objective reasons (data, circumstances, requirements).
- Avoid blame ("the market conditions," not "your failure to deliver").
- Be specific enough to be credible but not so detailed that you overwhelm.
Step 3: The Bad News
State the news clearly and concisely. Do not hide it in vague language or bury it in a paragraph.
Clear: "We have decided not to move forward with your proposal at this time." Vague: "After much consideration, we are exploring alternative directions that may or may not include the possibility of engaging with your firm in a different capacity at some point in the future."
The vague version is longer, harder to understand, and ultimately more frustrating for the reader.
"Clarity is kindness. The reader deserves to understand exactly what the decision is, even if the decision is unwelcome. Vague language prolongs uncertainty and breeds distrust." -- Brene Brown, Dare to Lead [3]
Step 4: The Close
End with something constructive: an alternative, a timeline, resources, or an expression of continued respect:
- "We encourage you to apply for future openings that match your qualifications."
- "We would welcome a revised proposal that addresses the scope concerns outlined above."
- "Your final paycheck and benefits information are outlined in the attached document."
Examples by Scenario
Example 1: Rejecting a Vendor Proposal (Indirect)
Subject: Decision on the CloudSync Proposal
Dear Mr. Patel,
Thank you for the comprehensive proposal your team submitted for the CloudSync migration project. The level of detail and the creative approach to the data migration phase were impressive.
After evaluating all proposals against our budget constraints and timeline requirements, we have selected a vendor whose pricing structure more closely aligned with our current fiscal parameters. This was a competitive process, and the decision was not easy.
We have decided not to proceed with CloudSync Solutions for this project. However, we valued the quality of your proposal and would welcome the opportunity to work together on future initiatives.
Please do not hesitate to reach out if you have questions about our decision.
Best regards, Jennifer Moss Director of IT Operations
Example 2: Announcing a Project Delay (Direct)
Subject: Project Apex -- Timeline Extended to June 30
Hi team,
The Project Apex delivery date has been moved from May 15 to June 30. Here is why and what it means for each of your workstreams.
Reason: The third-party API integration revealed compatibility issues that require a redesign of the data layer. Engineering estimates six additional weeks for development and testing.
Impact:
- QA testing shifts from April 20 to May 20.
- Client UAT shifts from May 1 to June 1.
- Marketing launch collateral deadline extends to June 15.
Next steps: Updated timeline is in the shared project tracker. Workstream leads -- please confirm your revised milestones by Friday.
I will schedule a 30-minute team sync for Monday to discuss any concerns.
Thank you for your flexibility, David
Example 3: Rejecting a Job Candidate (Indirect)
Subject: Your Application for the Senior Analyst Position
Dear Ms. Chen,
Thank you for interviewing for the Senior Analyst position at Meridian Group. Your background in quantitative analysis and your thoughtful responses during the panel interview made a strong impression.
After careful deliberation, we have selected a candidate whose experience in our specific industry vertical more closely matched the immediate needs of the team. This was an exceptionally competitive search.
We will not be moving forward with your candidacy for this role. However, we were genuinely impressed by your qualifications and would encourage you to apply for future positions that align with your expertise.
We wish you the very best in your career.
Sincerely, Michael Torres Senior Recruiter
Common Mistakes in Bad News Communication
Mistake 1: Burying the News So Deep It Gets Missed
Being indirect does not mean being invisible. Some writers bury bad news so deeply in qualifiers and context that the reader finishes the message without realizing they have received negative news.
Too buried: "While we continue to evaluate a range of options and consider various factors in our ongoing strategic review process, we are adjusting certain aspects of our approach in ways that may impact some elements of the current proposal framework."
What does this mean? The reader has no idea.
Mistake 2: False Positivity
Opening with excessive praise before delivering bad news feels manipulative:
False: "You are one of the most talented people we have ever worked with, and your contributions have been absolutely extraordinary. That said, we are eliminating your position."
Honest: "Your contributions to the marketing team over the past two years have been significant, particularly the rebrand campaign. Due to the restructuring of the department, your position has been eliminated effective April 30."
Mistake 3: No Forward Path
Ending a bad-news message without any constructive information leaves the reader in a state of frustration or helplessness:
No path: "The project has been cancelled. Thank you." With path: "The project has been cancelled due to the shift in Q4 priorities. The work your team completed on the requirements phase will be preserved and applied to Project Echo, which begins in January. I would like to discuss your role in that initiative."
Mistake 4: Blame and Defensiveness
Blaming: "Because your team failed to deliver on time, we had no choice but to cancel the project." Neutral: "Due to timeline constraints that exceeded our project parameters, we have made the decision to cancel the project."
Tone Guidelines for Bad News
| Do | Do Not |
|---|---|
| Be honest and direct | Be brutally blunt |
| Acknowledge the impact | Minimize the reader's feelings |
| Provide context and reasons | Over-explain or justify excessively |
| Offer alternatives or next steps | Leave the reader without options |
| Use respectful, neutral language | Use blame or emotional language |
| Express genuine appreciation (when warranted) | Use false or excessive praise |
"Empathy in professional writing does not mean being soft. It means demonstrating that you have considered the reader's perspective before, during, and after delivering the message." -- Harvard Business Review, "The Art of Communicating Bad News" [1]
Bad News in Different Formats
The medium you choose affects how the message is received. While this guide focuses on written communication, understanding how the format shapes the delivery helps you make better choices.
| Format | Best For | Advantages | Limitations |
|---|---|---|---|
| Formal email | Vendor rejections, policy changes, project updates | Documented, professional, allows recipient to process privately | No real-time feedback; tone can be misread |
| Letter (printed) | Layoffs, legal matters, formal rejections | Formal, creates strong documentation, conveys gravity | Slow; feels impersonal for some audiences |
| In-person + written follow-up | Position eliminations, serious performance issues | Allows real-time empathy; written follow-up provides documentation | Requires scheduling; stressful for both parties |
| Video call + written follow-up | Remote team bad news, major client communications | Allows tone and facial cues; written follow-up documents the conversation | Technology issues can disrupt; recording concerns |
| Group announcement (email or memo) | Policy changes, budget cuts, organizational restructuring | Consistent message to all recipients simultaneously | Cannot personalize; high risk of leaks before delivery |
Choosing the Right Format
The general rule: the more personally significant the news, the more personal the delivery should be. A vendor rejection is appropriate by email. A layoff should be delivered in person (or by video call for remote employees), followed by a written summary that documents the conversation, the terms, and the next steps.
"Never deliver life-altering bad news solely in writing if you have the option to deliver it face-to-face first. The written document should confirm what was discussed, not serve as the first notification. People deserve the dignity of a human conversation for news that affects their livelihood." -- Kim Scott, Radical Candor, revised edition [4]
Timing and Sequencing Bad News
When you deliver bad news matters almost as much as how you deliver it.
Timing Guidelines
| Principle | Explanation |
|---|---|
| Do not send bad news late on Friday | The recipient has the entire weekend to stew without the ability to ask questions or take action |
| Deliver promptly once the decision is final | Delays allow rumors to spread and erode trust |
| Consider time zones | Ensure the recipient receives the news during their business hours |
| Avoid holidays and major observances | Respect cultural and personal calendars |
| Sequence the communication | Inform directly affected individuals before making broader announcements |
Sequencing for Organizational Bad News
When bad news affects multiple levels of an organization, the order of communication matters:
- First: Inform the directly affected individuals (privately, one-on-one if possible).
- Second: Brief their immediate managers and HR (if not already involved in the decision).
- Third: Communicate to the broader team with context and forward-looking information.
- Fourth: Issue any external communications (press releases, client notifications) only after internal stakeholders are informed.
Breaking this sequence -- for example, announcing a restructuring to the press before telling the affected employees -- is one of the most damaging communication failures an organization can make.
Related Communication Guides
- How to Handle Difficult Conversations -- verbal strategies for tough talks
- How to Give Feedback -- constructive criticism techniques
- Tone in Professional Writing -- controlling how your message lands
- How to Say No Professionally -- declining with respect
- How to Write Clear Emails -- clarity in all email contexts
Summary
Delivering bad news in writing requires a deliberate balance of clarity, empathy, and forward-looking constructiveness. The indirect approach (buffer-reasons-news-close) works best for personally significant news where relationships matter. The direct approach (news-reasons-close) is appropriate for urgent, operational, or less personal communications. In both cases, the news itself must be stated clearly -- vague language and buried messages cause more harm than directness ever does. End every bad-news message with a path forward, and your reader will leave the conversation with their trust and respect intact, even if the news itself was unwelcome.
How to End an Email Delivering Bad News?
End a bad-news email with empathy, next steps, and availability. Template: 'I know this is not the outcome we hoped for. If it would help to talk through the decision or what comes next, I am available on [Day] or [Day] -- please pick any time that works. I am sorry for the impact, and I appreciate your understanding. Sincerely, [Name].' This is the final beat of the bad-news framework the guide outlines: acknowledge the human impact, offer a concrete path forward, and sign off with dignity. Never close a bad-news email with 'Have a great day' or any line that feels out of sync with the news.
How to End an Email Giving Bad News?
End a bad-news email by acknowledging the impact, pointing to support or next steps, and signing off warmly. Template: 'I recognize this is disappointing news, and I am sorry for the impact on your team. I am available to talk through it Wednesday or Thursday -- pick any time on my calendar. Thank you for your understanding. Sincerely, [Name].' The guide's bad-news framework treats the closing as essential, not decorative: it is the moment that signals whether you see the recipient as a person or a task. Avoid cheerful sign-offs ('Have a great day!') and corporate evasions ('We hope you understand'). Direct, humane, concrete.
How to End an Email Professionally Looking Forward?
End a professional email with a forward-looking sentence that names a specific next step, then a formal sign-off. Examples: 'I look forward to your response by Friday. Kind regards, [Name].' 'I look forward to discussing this on Tuesday. Best regards, [Name].' 'I look forward to sharing the final report next week. Sincerely, [Name].' The bad-news guide shows how 'looking forward' closes need particular care -- they sound hollow after hard news, so substitute 'I am available to discuss when you are ready. Sincerely, [Name].' Always use the full verb form ('I look forward to') rather than the fragment ('Looking forward!') in formal correspondence.
References
[1] Harvard Business Review. "The Art of Communicating Bad News." HBR Communication Series, 2019.
[2] Locker, Kitty O. Business and Administrative Communication. 12th ed., McGraw-Hill, 2019.
[3] Brown, Brene. Dare to Lead: Brave Work. Tough Conversations. Whole Hearts. Random House, 2018.
[4] Scott, Kim. Radical Candor: Be a Kick-Ass Boss Without Losing Your Humanity. Revised ed., St. Martin's Press, 2019.
Frequently Asked Questions
What is the best structure for delivering bad news in writing?
The most effective structure for bad news in professional contexts is the indirect approach: begin with a brief buffer that acknowledges the context or relationship, then provide the rationale for the decision, deliver the bad news clearly and directly, and close with forward-looking information or alternative options. This structure prepares the reader emotionally before the negative information. However, for urgent or safety-related bad news, use the direct approach: state the news immediately, then provide context and next steps.
How do I maintain empathy while being direct?
Empathy and directness are not opposites -- they complement each other. Acknowledge the impact of the news on the reader ('We understand this is disappointing'), use clear language without euphemisms or excessive hedging ('The position has been eliminated' is clearer than 'We are exploring workforce optimization'), and focus on what comes next rather than dwelling on the negative. Avoid phrases like 'I know how you feel' (you may not) and instead use 'We recognize that this creates uncertainty.' The reader should feel respected and informed, not patronized or confused.
Should bad news be delivered in writing or in person?
The general principle is that the more significant the news, the more it warrants a personal conversation first, followed by a written summary. Layoffs, terminations, and major organizational changes should ideally be communicated face-to-face or via video call, with written documentation provided afterward. Less personally impactful news -- a rejected proposal, a denied request, a policy change -- can be delivered effectively in writing. When in-person delivery is not possible (remote teams, large-scale announcements), a well-written message becomes the primary channel and must be crafted with extra care.