How to Write Difficult Emails: Bad News, Rejections, Complaints, and Apologies

A difficult email should make the decision or problem clear, acknowledge its effect on the reader, and state what happens next. Hiding the main point behind a long introduction creates uncertainty; being blunt without context can feel dismissive. The practical balance is directness plus empathy.

This guide provides structures and templates for five common situations: delivering bad news, declining a request, responding to a complaint, giving corrective feedback, and apologizing for a mistake. Replace every bracketed placeholder with verified details before sending.

Decide whether email is the right channel

Email works well when the message needs a clear record, the facts are settled, and the recipient can process the information without an immediate discussion. A conversation is often better for a sensitive performance issue, a complex conflict, a safety concern, or news likely to generate urgent questions. You can follow that conversation with a short written summary.

Also check organizational rules. Legal, human-resources, privacy, security, and regulated customer matters may require an approved process or reviewer rather than an improvised response.

The core structure: directness plus empathy

1. State the purpose. Put the topic in the subject line and opening sentence.
2. Give the decision or acknowledge the problem. Use plain, unambiguous language.
3. Add only necessary context. Explain the reason without creating a wall of excuses.
4. Recognize the impact. Show that you understand what the news means for the reader.
5. Give the next step. Include an owner, action, and date when known.
6. Offer an appropriate path for questions. Make clear whether the decision is final or open to discussion.

Adapt the vocabulary and amount of detail to the recipient. These broader tips on adjusting your communication style to the situation can help when the same news must go to customers, colleagues, and leaders.

How to deliver bad news

Readers should not have to decode phrases such as “we are realigning the timeline” to discover that a launch is delayed. Put the outcome near the top, then explain the consequence and the revised plan.

Template: a project delay

Subject: [Project] launch moving to [new date]

Hi [name/team],

We need to move the [project] launch from [old date] to [new date].

[One or two sentences explaining the verified reason.] I know this affects [specific dependency, customer, or commitment], and I am sorry for the disruption.

The revised plan is:

• [Action] — [owner] — [date]
• [Action] — [owner] — [date]

We will review progress on [date]. Please send urgent dependency concerns to [contact or channel] by [time].

Thanks,
[name]

Do not invent a new date to make the email feel complete. If timing is not known, say when the next update will arrive and who is assessing the schedule.

Template: an application rejection

Subject: Update on your application for [role]

Hi [name],

Thank you for the time you spent speaking with us about the [role]. We have decided not to move forward with your application.

[Optional: a brief, accurate explanation that follows company policy.]

We appreciate [specific, truthful strength or contribution from the process]. [Optional next step, only if genuine.]

Thank you again, and I wish you well in your search.

[name]

Avoid false encouragement such as inviting a future application when the organization does not intend to consider one. Do not share confidential comparisons with other candidates.

How to say no clearly

A vague response shifts the burden back to the requester. If the answer is no, say so. A brief reason can help, but it does not need to become a defense of your workload or priorities.

Template: declining a meeting

Subject: Re: Meeting about [topic]

Hi [name],

Thank you for reaching out. I cannot take this meeting [during the requested period / because the topic is outside my role].

[If useful: I can answer one or two specific questions by email / [colleague or team] handles this topic / the following resource may help.]

Thanks for understanding,
[name]

Template: declining extra work

Hi [name],

I cannot take ownership of [task] by [date] alongside my current commitments.

I can [smaller action] by [date], or we can discuss which existing priority should move. If neither option works, [appropriate alternative person or process] may be able to help.

Please let me know which option you prefer.

Offer an alternative only when it is realistic. Do not volunteer a colleague without first confirming that the referral is appropriate.

How to respond to a complaint

Begin by showing that you understood the reported experience. Investigate before accepting responsibility for facts you have not confirmed, but do not use uncertainty as an excuse to dismiss the customer.

Complaint-response structure

1. Identify the specific issue.
2. Acknowledge the customer's impact.
3. State what you verified and what remains under review.
4. Take responsibility where appropriate.
5. Give the remedy or investigation plan.
6. Set a date for the next update.
7. Provide a named support path or case number.

Template: confirmed service problem

Subject: Resolution for case [number]

Hi [name],

I am sorry that [specific problem] happened. You expected [agreed service or outcome], and instead [brief description of the impact].

We reviewed [records or process] and confirmed that [verified cause or finding]. [If responsible: This was our error.]

We have now [completed remedy]. You can expect [result] by [date or time window]. We are also [specific prevention step].

If the issue is not resolved by [date], reply to this message or contact [channel] with case [number].

Sincerely,
[name and role]

Avoid “I am sorry you feel that way,” which apologizes for the person's reaction rather than addressing the problem. Do not promise a refund, credit, replacement, or deadline unless you are authorized to provide it.

How to give constructive feedback by email

Email is suitable for concise, factual revision notes. A live conversation is usually better for serious performance concerns, emotionally charged feedback, or an issue that requires dialogue.

Describe what you observed, explain the impact, and request a specific change. Focus on the work or behavior rather than assigning a motive or personality trait.

Template: revision request

Subject: Revisions needed for [document or deliverable] by [date]

Hi [name],

Thank you for sending [deliverable]. Before it is ready for [audience or next step], please revise the following:

• [Observable issue] — [why it matters] — [requested correction]
• [Observable issue] — [why it matters] — [requested correction]

Please send the revised version by [date and time]. If any item is unclear or the deadline is at risk, let me know by [earlier time] so we can review it together.

Thanks,
[name]

“Try harder” is not actionable. Cite the page, figure, requirement, or example that needs work. For more general communication habits, see how to develop good communication skills.

How to apologize professionally

A useful apology names the mistake, accepts the appropriate responsibility, explains the remedy, and shows how recurrence will be reduced. The explanation should clarify, not transfer blame.

Template: missed deadline

Subject: [Deliverable] missed deadline and revised delivery

Hi [name],

I missed the [date] deadline for [deliverable]. I should have warned you as soon as I knew the work was at risk, and I apologize.

I will send [complete deliverable or defined portion] by [realistic date and time]. [Describe any immediate mitigation.]

To prevent a repeat, I am [specific process change]. If the revised timing creates a problem for [dependency], please tell me today so we can agree on an alternative.

[name]

Do not weaken the apology with “if anyone was offended” or a long account of how busy you were. If you do not yet know the remedy, give the next investigation update rather than an unsupported promise.

Subject lines for difficult messages

A neutral, specific subject line helps the recipient understand the topic without creating alarm or embarrassment. Examples include:

• Schedule update: [project] launch
• Decision on [proposal name]
• Update on your [role] application
• Action needed: revisions to [document]
• Resolution for case [number]
• Correction to [invoice/report/date]

Avoid vague subjects such as “Bad news,” “Problem,” or “Urgent” unless the situation is genuinely urgent. Do not put confidential medical, disciplinary, financial, or personal details in the subject line.

Common mistakes to remove before sending

• A long buffer: Move the decision or problem into the opening paragraph.
• Passive language: Name the responsible team or process when appropriate instead of writing “mistakes were made.”
• Excessive apology: One sincere apology plus corrective action is stronger than repeated self-criticism.
• Unsupported certainty: Distinguish confirmed facts from what is still being investigated.
• False options: Do not invite discussion if the decision cannot change; offer clarification instead.
• Unnecessary recipients: Remove people who do not need sensitive information.
• Emotional drafting: Pause, check the facts, and revise accusatory language before sending.
• Hidden action: Make the requested response, owner, and deadline easy to find.

Final review checklist

1. Does the subject line identify the topic without exposing sensitive information?
2. Can the reader find the decision or problem in the first few sentences?
3. Are every date, amount, name, promise, and policy reference accurate?
4. Does the message acknowledge the practical impact without exaggerating it?
5. Is the explanation brief and free of blame-shifting?
6. Are the next action, owner, and timing clear?
7. Is the recipient list appropriate, and are attachments correct?
8. Would a call or meeting be safer or kinder for any part of this message?
9. Does the tone remain professional if the email is forwarded?

Difficult emails become easier to write when their job is clear: inform the reader, treat them with respect, and reduce uncertainty about the next step. Concise does not mean cold, and empathetic does not mean vague.