How to write an escalation email

An escalation email has one job: get a decision maker to act on something that is stuck. Most people write these in the heat of frustration, which is exactly what makes them backfire. The version that actually works reads calmly, shows the ground already covered, and asks for one clear thing.

Facts and impact, never blame

The instinct when escalating is to explain who dropped the ball. Resist it. A senior reader does not need to know whose fault something is; they need to know what is happening and what it is costing. Instead of “Sam has not responded to my last three emails”, write “the request has been open for two weeks without a response, and it is now blocking the release”. The first sounds like a complaint about a person. The second is a fact the reader can act on, and it protects your relationship with Sam once this is resolved.

Show your working first

An escalation that skips straight to “please sort this out” can look like you went over someone’s head at the first sign of friction. Before the ask, add one or two lines on what you have already tried: who you raised it with, when, and through what channel. This does two things: it proves you tried to resolve it at the right level, and it saves the reader from asking “have you spoken to Sam about this?” as their first reply.

Make the cost of waiting concrete

Senior people triage by impact, not by how stuck something feels to you. “This is frustrating” will not move an email to the top of an inbox. “This is blocking the launch due in two weeks” will. Name the specific consequence of the delay: a deadline at risk, a cost that is growing, a client who is waiting. If you genuinely do not know the downstream impact, it is better to say so than to guess at one, since an invented consequence is easy to spot and undermines the rest of the email.

Example escalation email

Subject: Vendor integration delay now risking the March 14 launch Hi Priya, Flagging an issue that is now at risk of affecting the March 14 launch date. The vendor integration has been open for three weeks without a fixed delivery date. I have followed up twice with their account manager by email and once on a call, and raised it in our last two weekly syncs, but there is still no committed timeline. If it is not resolved in the next few days, we will not have enough runway left to test before launch. Could you help either get a firm date from the vendor at your level, or make the call on whether we push the launch by a week? Happy to jump on a call if useful. Thanks, Dave

Common mistakes

Naming who is at fault instead of what is at risk. It reads as a complaint, not a request for a decision.
Leaving out what you already tried, which makes the escalation look premature or like a shortcut.
Ending on the problem instead of the ask. Always close with the specific decision or action you need.
Padding the email with backstory. A senior reader wants the facts, the impact, and the ask, not the full history.