Escalating an issue means handing it to someone with more authority to fix it, because the level it is stuck at cannot move it. You do that without throwing anyone under the bus by writing the state of the work and what it costs, and leaving out every guess about why a person did what they did.
Escalations fail in two directions. They arrive far too late, wrapped in loyalty, or they arrive as a case file with a timeline attached.
I also think the fear of bus-throwing gets used a little too freely. It keeps careful people quiet for weeks, and the only person it reliably protects is whoever is late.
Escalation is a routing decision
Escalating is routing, not judging. The problem has outgrown the level it sits at, and you are moving it to a level that can act on it.
That framing changes your wording more than any script will. A routing message says where the work is stuck and who can unstick it. A judging message explains why the people near the work are the way they are.
Work gets stuck for boring reasons. A dependency slipped. Someone got pulled onto a fire. The requirement was wrong before anybody wrote a line of it down.
None of that needs a villain. The bus shows up when you skip the routing and go straight to the character sketch.
Tell the person first, in one line
The single move that prevents most bus-throwing is telling the person before you write to anyone above them.
This is a warning, not a permission request. Use the channel you were already talking in, and keep it to two sentences.
Something like: "I'm raising the integration delay with the leads tomorrow so we can get a call on the launch date. Wanted you to hear it from me first, and tell me if I have any of it wrong."
Short on purpose. If that message turns into a negotiation, you have accidentally asked for permission, which was never the point.
Two things can follow, and both are fine for you. Sometimes the problem gets fixed that afternoon, which was the actual goal. Sometimes nothing moves, and the escalation goes out without being an ambush.
You give up surprise, and you should want to. Surprise is the ingredient that turns an ordinary management message into something the other person has to defend themselves against.
Stick to what happened and when
An escalation reads as blame when it explains motives. Report what happened and when it happened, then stop.
Motive is the tell. "The API keys are still not provisioned" is a fact anyone can check. "Ops does not think this matters" is a theory about someone's inner life, and you are not qualified to publish it.
These are the moves that turn a report into an accusation:
- Any sentence about what someone "keeps" doing.
- The words repeatedly, still, again, and once again.
- Character words like unresponsive, disorganized, or careless.
- A timeline built to prove a pattern rather than to explain a delay.
- Screenshots pasted in where one sentence would carry the same information.
- Any version of "as I mentioned", which is a receipt rather than a fact.
Cut those and the message gets shorter and more alarming, in the way you actually want. Plain facts about stuck work are alarming on their own.
Name people when the facts need names
Vagueness feels like kindness. It is where most well-meant escalations die. If the reader cannot tell who owns the blocked step, they cannot unblock it, and your message turns into a mood.
"There have been some delays on the data side" asks a busy reader to run their own investigation. They will ask who. Then you are naming the person anyway, out loud, in a thread you no longer control.
Naming is fine. Characterizing is the part that costs you.
Write that the schema change went to the data team two weeks ago and has not come back. That sentence carries a name, a date, and no opinion, and nobody reading it learns a thing about how you feel toward the data team.
An escalation without an ask is a complaint
An escalation without an ask is a complaint with better formatting. The reader's question is always the same: what do you want me to do?
Asks that work look like these:
- Choose between two dates you can genuinely hit.
- Say which of the blocked items gets the person you can spare.
- Make the call you are not senior enough to make.
- Lend you someone for a stated number of days.
- Tell the customer, if telling the customer belongs to them.
"Let me know your thoughts" hands homework to the one reader you were trying not to burden, and it leaves the thread open, which is how escalations quietly become recurring meetings. The mechanics of the ask are their own skill, and I wrote separately about getting a real decision out of a busy reader.
Write it so a forward would not hurt
Assume the person you wrote about will read every word of it. Escalations travel. They get pasted into other threads, quoted back in meetings, and it happens at the worst possible moment every time.
The forward test is really a fact check. Sentences that survive being read by their subject are usually the ones you could defend out loud in a room, and the rest were guesses in a confident font.
I have deleted whole paragraphs on that test. The deleted parts were never load-bearing. They were the places where I was still annoyed and had let it into the verbs.
It does not come out on its own, though. It attaches itself to word choices I would defend one at a time if you asked me about any of them. That is a fair share of why Unvent exists: I send the version with the facts intact and the temperature taken out.
When the escalation lands on you
If someone escalates something you own, do not defend your character. Nobody accused it, and defending it in writing tells the room there was something worth defending.
Answer the state of the work, give a date, and thank them for the flag, even if you type that last part through your teeth.
People remember how you replied to the escalation much longer than they remember the delay behind it. Which is unfair to whoever did the actual work, and true anyway.
Facts loud, temperature low
Unvent rewrites what you are typing, in place, in the tone you pick. The message that leaves your hands is the one they will remember, so it may as well be the calm one.
Add Unvent to Chrome