Pointspoken

How to escalate a blocker to your manager

Reviewed 19 Sept 2026

Escalating feels uncomfortable because it can sound like complaining about another team or admitting you cannot cope. So people soften it until the manager does not realise they are being asked to do something.

A good escalation is a request, not a report. It makes it easy for the manager to help, because it says exactly what is stuck, what it costs, and what action would fix it.

The structure: blocked, impact, tried, ask

  1. Blocked

    What you cannot do, and who or what you are waiting for. One sentence.

  2. Impact

    What it costs in days or in risk to a date the manager cares about.

  3. Tried

    What you have already done to solve it yourself, briefly. This shows the escalation is justified.

  4. Ask

    One specific action or decision, from a specific person, by a specific time.

Before and after

A one-to-one with your manager. You have waited six days for another team to grant database access.
Before

“I also wanted to mention, it's not a big thing, but the platform team still hasn't done the access thing, I asked them a few times, they're probably busy, so I'm kind of waiting on that. Just so you know.”

  • “Not a big thing” and “just so you know” tell the manager that no action is needed.
  • There is no cost, so the manager cannot judge the priority.
  • There is no request. The manager has to guess what would help.
Clearer

“I'm blocked on the migration, and I need your help. I've been waiting six days for the platform team to grant database access. Every extra day moves the migration date by a day, so the 30th is now at risk. I've raised a ticket and messaged Ken twice. Could you ask their lead today to approve it this week? If that's not possible, I need to know so that I can re-plan.”

Scripted example, not a real user's recording.

Phrases you can use

Open
  • “I'm blocked on…, and I need your help.”
  • “I need a decision from you on…”
  • “There is one thing I can't solve at my level.”
Impact
  • “Every day this waits moves the launch by a day.”
  • “If this is not resolved by Friday, we miss the 30th.”
  • “It doesn't affect the date yet, but it will from next week.”
What you tried
  • “I've raised a ticket and followed up twice.”
  • “I looked for a workaround, and there isn't a safe one.”
Ask
  • “Could you speak to their lead today?”
  • “Can you decide between A and B by Thursday?”
  • “Who is the right person for me to ask?”

Common mistakes

Minimising

Remove “just”, “a small thing” and “when you have time” if the matter is urgent. Your words should match the priority.

Blaming

Describe the situation, not the people: “access has not been granted”, rather than “they keep ignoring me”.

No ask

End with a question your manager can answer with yes, no, or a name.

Escalating too late

Raise it when it first threatens a date, not after the date has gone.

A ten-minute drill

  • Pick something you are waiting for at work right now.
  • Record a 45-second escalation. It must include a number (days or a date) and end with a question.
  • Read the transcript and delete every softener that does not match the real urgency.
  • Record again, slower, with a pause before the ask.

Questions people ask

How do I escalate without damaging the relationship with the other team?

Tell them first: “I'm going to raise this with my manager because it now affects our date.” Then describe facts, not behaviour. Most people accept an escalation that does not surprise them.

Is it better to escalate in writing or out loud?

Out loud gets a faster decision, and a short written follow-up keeps a record. Practising the spoken version also makes the written one shorter.

What if my manager cannot help?

Ask who can, and what you should do in the meantime. A clear “no” lets you re-plan, which is better than waiting.

Related situations