Refusing, Escalating and Delivering Bad News: practical B2+ English

Your goal for Refusing, Escalating and Delivering Bad News

Refusing, Escalating and Delivering Bad News: The release will be one working day late. By the end, you should be able to refuse a senior's request, escalate an issue and deliver bad news, each with the appropriate register.

Try the release-delay scenario first

Your team promised a client a Friday release. Testing has found a defect that can corrupt imported records. The earliest responsible delivery is Tuesday afternoon. Write the first three sentences of your client update before reading the models below.

Keep your first attempt. Later, check whether it gives the news, the effect and the next step early enough.

Three conversations, three structures: Refusing, Escalating and Delivering Bad News

A client update that respects their time

The release will be one working day late. Testing found a defect that can corrupt imported records, so we have paused deployment. The fix is in progress and the revised delivery time is Tuesday at 3 p.m.

I will send the test result by noon on Tuesday. If your team needs a temporary export before then, we can provide one today.

The message does not begin with a cheerful cushion. It states the result, explains the verified reason and offers a useful option. It also avoids promising that the fix is complete before testing proves it.

Listen to the client update

Refusing a senior without becoming passive

I understand why Friday matters. I cannot approve a release without the required security check. I can ask the security lead for an expedited review this afternoon, or we can move the release to Monday.

The speaker does not ask permission to follow a required control. The boundary is direct because the risk requires it. The acknowledgement and alternatives protect the working relationship without weakening the decision.

Escalate the decision, not the emotion

An escalation should make it easier for the next person to act. Use this order:

1. Risk: What may happen, and by when?
2. Evidence: What is confirmed? What is still an assumption?
3. Work already done: What did you try, and what happened?
4. Decision required: Who has the authority, and what exactly must they decide?
5. Timing: When does the decision become too late to be useful?

Compare “The vendor is impossible, please deal with them” with “The vendor has declined both approved payment terms. Procurement approval is required for a third option by 4 p.m. if we want to keep Monday’s start date.” The second version can be acted on.

Choose directness by risk and relationship

Politeness does not always mean softness. A safety instruction, legal deadline or exposed credential may require direct language. A preference, suggestion or early concern usually allows more room.

Language that makes difficult news worse

• “There is a small issue.” Do not minimise an impact the recipient needs to assess.
• “It was not my fault.” Start with the situation and the recovery action, not self-defence.
• “We take full responsibility.” Do not make contractual or legal admissions before the facts and authority are clear.
• “As soon as possible.” Give a date, time or next checkpoint.
• “You misunderstood.” Use repair language such as “I may not have made the distinction clear.”

Make three decisions under pressure: Refusing, Escalating and Delivering Bad News

1. A manager asks you to remove testing so a launch can happen today. Write a firm refusal and one alternative.
2. A supplier has missed two milestones and your team cannot resolve the dependency. Write a five-line escalation asking for one named decision.
3. A client report contains an error. Write the opening, the corrected fact, the impact and the next update.
4. Rewrite one message for a peer and then for a senior executive. Note what changed and what remained direct.
5. Read each response aloud. Remove any long background sentence that delays the actionable point.

Check your professional judgment

Record a ninety-second difficult update: Refusing, Escalating and Delivering Bad News

Choose one of the three situations above. Give the headline in the first fifteen seconds. Separate verified facts from what is still being investigated. End with the action, owner and time.

1. Record the first attempt without reading a full script.
2. Listen once as the recipient. Write down the decision you think you were being asked to make.
3. If that decision is unclear, repair the message.
4. Record the second attempt and compare the first thirty seconds.

Reuse one earlier workplace decision: Refusing, Escalating and Delivering Bad News

Start with Recognise the goal, state the boundary, give a brief reason, offer an alternative. Add one relevant move from the previous lesson, such as a clear owner, deadline, condition or reason. Remove it if it does not help the recipient act.

What a responsible difficult message contains: Refusing, Escalating and Delivering Bad News

Refuse with a clear boundary and a possible route forward. Escalate a risk with evidence and a named decision. Deliver bad news early, distinguish facts from assumptions and give the recipient a useful next step.