Escalation Process: When and How to Escalate Problems at Work

By Nicole Hullihen, former SaaS Chief Operating Officer and Microsoft MVP · Updated October 13, 2026

Problems at work don't usually become emergencies all at once. They start small: a part that's running late, a customer who's getting frustrated, a task that's taking twice as long as planned. Whether that small problem gets fixed or grows into a crisis often depends on one thing: did someone raise it with the right person in time?

Many employees aren't sure when to escalate. Some raise everything and flood their manager. Others raise nothing because they don't want to look like they can't handle it. An escalation process removes the guesswork. This guide shows how to build one, with a free escalation matrix template, scripts and the mistakes to avoid.

What Does It Mean to Escalate?

To escalate a problem means to move it to someone with more authority, information or resources to solve it. It isn't complaining, and it isn't passing the blame. It's recognizing that a problem has outgrown what you can fix on your own, and getting the right person involved before it gets worse.

Why Every Team Needs an Escalation Process

• Problems get solved earlier, when they're smaller and cheaper to fix.
• Managers aren't flooded with issues employees could handle themselves.
• Employees feel safe raising problems because the rules are clear.
• Customers get faster answers when issues reach someone who can make a decision.
• Fewer missed deadlines. Blocked work gets attention before the due date. See why teams miss deadlines.
• Clear accountability. Everyone knows who owns which decisions.

When to Escalate: Common Triggers

The heart of an escalation process is a short list of triggers, situations where employees should escalate rather than keep trying on their own:

Customize the limits for your business. A dollar amount, a number of hours blocked or a type of customer can turn a vague judgment call into a clear rule.

When Not to Escalate (Yet)

Escalation works best when it's used for the right things. Before escalating, employees should ask:

• Have I tried the obvious fixes?
• Is this something I'm allowed to decide myself?
• Have I talked directly with the person involved?
• Is there a policy, SOP or checklist that answers this? See SOPs for small business.

If the answer to all four is yes and the problem is still there, it's time to escalate. Safety and legal issues are the exception: they should go up right away, without waiting.

Building an Escalation Matrix

An escalation matrix shows who handles which kind of problem at each level, and how quickly they should respond. It can be as simple as a table posted on the wall or saved in a shared folder.

Add names and contact information for each level, plus a backup for when someone is out. A matrix without backups breaks down the first time a manager goes on vacation.

Free Escalation Process Template

How to Escalate Well: The Four-Part Message

A good escalation gives the other person everything they need to act quickly. Teach your team a simple four-part format:

1. What's happening: the facts, briefly.
2. Why it matters: the impact on the customer, deadline, cost or safety.
3. What I've tried: so they don't suggest the same things.
4. What I recommend or need: a decision, approval, resources or help.

That message takes 30 seconds to read and gets a decision in minutes, compared to "we have a problem with Garcia, can we talk?"

Escalation Scripts

When You're Blocked

When a Customer Is Upset

When Something Is Over Budget

When Escalating Above Your Manager

Going above a manager should be rare and done respectfully. Most processes ask employees to tell their manager first that they're taking it higher.

How Managers Should Respond to Escalations

An escalation process only works if escalations get a good response. If people get criticized for raising problems, they'll stop raising them. Managers should:

• Thank the person for raising it, especially if it's bad news.
• Respond within the promised time, even if it's only to say when you'll decide.
• Make a decision or give clear direction. "Let me think about it" with no date isn't a response.
• Close the loop. Tell the person what happened.
• Coach when needed. If something didn't need escalating, explain privately how they could handle it next time.
• Look for patterns. The same escalation every week usually points to a process that needs fixing.

Protecting Employees Who Raise Concerns

Some concerns come with legal protections, which is another reason your process should welcome them. The Occupational Safety and Health Administration states that workers can report safety concerns without being punished, and that it's illegal to retaliate against a worker for complaining to OSHA. The National Labor Relations Board explains that employees generally have the right to act with coworkers to address work-related issues, including talking with each other about pay and working conditions.

An escalation process should never require employees to keep these concerns inside the company or discourage them from going to a government agency. If you're unsure how these rules apply to your business, check with an employment attorney. For more on handling serious concerns, see the HR investigation guide.

Common Escalation Mistakes

• Escalating too late, after the deadline or the customer is gone.
• Escalating everything, which buries the issues that really matter.
• Escalating without facts, so the manager has to start from scratch.
• Skipping levels without telling the manager in between.
• No backup contacts, so escalations stall when someone is out.
• Punishing the messenger, which guarantees the next problem stays hidden.
• Never closing the loop, so people don't know if escalating helped.

Rolling Out an Escalation Process

1. List the problems that came up in the last few months and how they were handled.
2. Pick triggers and limits that fit your business.
3. Name the contacts and backups for each level.
4. Write it on one page using the template above.
5. Walk through it at a team meeting with real examples.
6. Post it where people can find it, and include it in onboarding.
7. Review it every few months and adjust triggers that aren't working.

Escalation Examples by Department

Your own matrix will look different, but writing down the most common escalations for each department is a good starting point. It shows employees that escalating is a normal part of the job, not a sign of failure.

Setting Approval Limits

Many escalations happen because employees don't know what they're allowed to decide. Clear approval limits cut down on unnecessary escalations and speed up the ones that matter:

These are example amounts; set limits that fit your business and margins. Write them down, share them and revisit them as people grow into more responsibility. Giving trusted employees more authority is one of the best ways to reduce escalations. See learning to delegate work.

Tracking Escalations

A simple log of escalations, what happened, who handled it and how long it took, turns individual problems into useful information. Review it monthly and ask:

• Which kinds of problems get escalated most?
• Are escalations getting resolved within the expected time?
• Are some issues escalated that employees could handle with more authority or training?
• Are some issues not escalated soon enough?

Patterns in the log point to the fixes that will prevent the next round of problems, such as a new SOP, a training session or a change in approval limits.

Teaching New Employees to Escalate

New employees are often the least likely to escalate, because they don't want to look like they can't handle their job. Cover the escalation process during onboarding, walk through a few real examples and tell them directly that raising problems early is expected. Pair them with a teammate they can ask first. In their first weeks, praise good escalations out loud, so the behavior sticks.

Make Escalations Visible in Updoot

In Updoot's project management, anyone can mark a task as blocked, so managers see what needs help without waiting for a message. Every task has a clear owner, due date and priority, and the overdue and blocked views show exactly where work is stuck. In meetings, escalated issues become action items with an owner and a due date, so they get resolved instead of discussed again next week.

Sources

• OSHA: Workers' Rights
• NLRB: Concerted Activity

Frequently Asked Questions