How to Write an Escalation Policy for Managers
An escalation policy tells managers when a problem should move up, to whom, how fast, and what to include in the message. Write it around triggers and time limits, not seniority, so that small issues get solved where they arise and serious ones reach decision makers quickly.
Below is a structure you can adapt: triggers, levels, response times, a message format and a worked example, plus how to stop both over-escalation and silence.
When should an issue be escalated?
Give managers specific triggers so they don't have to guess. A common set:
- Impact: a customer, revenue or safety issue above a defined size.
- Time: the problem has stayed unresolved past its agreed response window.
- Authority: the fix needs a decision or spend outside the manager's limits.
- Risk: a legal, security, privacy or reputation issue, regardless of size.
- Uncertainty: the manager doesn't know how to resolve it and the cost of waiting is rising.
Add an explicit rule that matters for fairness and law: reports of harassment, discrimination, safety or legal violations follow your HR and legal process, not the normal chain. Have counsel or an HR professional review that part.
How to design the levels and time limits
Keep it to three or four levels so it's easy to remember:
- Level one: the person closest to the issue resolves it within their authority.
- Level two: their manager steps in when a trigger is hit or the response window ends.
- Level three: the department or function leader decides when cross-team impact or spend above limits is involved.
- Level four: the CEO or leadership team, reserved for company-level risk or major decisions.
Attach a time limit to each level, such as one business day to resolve before moving up, and shorter for urgent categories. Match limits to your decision rights so authority and escalation agree.
What must an escalation message contain?
A weak escalation forces the receiver to interview the sender. Ask for five things every time: what happened in two sentences, who's affected and how much, what's been tried, what decision or help is needed, and by when. A short template in your chat tool makes this a habit.
Compare two messages. The weak one says a customer is unhappy and needs help. The strong one says the customer's order was delayed twice, they've asked for a refund and a credit, the account owner offered a partial credit that was refused, and a decision is needed by end of day on whether to approve the larger credit. The second can be answered in a minute.
Worked example: a delayed customer delivery
Say a project lead learns that a customer's delivery will slip by a week. At level one, they try to rebalance work and tell the customer. If it can't be fixed within their authority or the customer threatens to cancel, it moves to level two: their manager approves overtime or a contractor and calls the customer. If the fix needs spend beyond the manager's limit or affects other accounts, level three decides on trade-offs. Each step has a time limit and a named owner.
What matters is that nobody sits on the problem hoping it disappears. The leader sees it early, when options are still open.
How do you stop over-escalation and silence?
Both are failures. Over-escalation swamps leaders with issues people could solve, while silence hides problems until they're crises.
For over-escalation, coach managers to bring a recommendation with every issue and praise the ones who solve problems at their level. For silence, thank people who raise bad news and never punish the messenger. Review a sample of escalations each quarter, ask which could have been solved lower, and which should have come up sooner. Fold the findings back into the policy, and bring the leadership team meeting a short list of recurring issues.
Rollout matters as much as writing. Introduce the policy in a manager meeting, walk through two real past incidents and show how each would have moved through the levels. Post the one-page version where managers will find it, and repeat it when new managers join. After a quarter, ask managers what was unclear. A policy that people can recite from memory is worth more than a thorough one that nobody reads.
What Good Looks Like
Managers know the triggers, levels and time limits for escalating a problem, and every escalation arrives with the same five facts.
Building The Capability (5-Stage Skill Ladder)
How to Get Started
Frequently Asked Questions
What is an escalation policy?
It's a written set of rules that says when a problem moves to a higher level, who receives it, how quickly it must be handled and what information to include. It keeps small issues local and gets serious ones to decision makers fast.
How many escalation levels does a small company need?
Three or four is usually enough. More levels slow things down and are hard to remember. Each level should have clear authority and a time limit so issues don't sit.
Should HR issues follow the normal escalation path?
Not always. Reports of harassment, discrimination, safety problems or legal violations should follow your HR and legal process. Have an attorney or HR professional review that part of the policy for your state.
How do I get managers to escalate earlier?
Set clear triggers, thank people who raise problems early and avoid blaming the messenger. Include time limits so waiting isn't the default, and review past cases together to show what early escalation would have changed.
About the numbers
This guide doesn't quote a sourced benchmark. Figures in it are estimates or general guidance, so check them against your own numbers.
Related Guides
How to Write a Decision Rights Document for Your Company
Build a decision rights document: inventory your decisions, assign who recommends, decides and gets informed, and set limits and escalation.
Leadership Team Meeting Agenda: A 90-Minute Weekly Format
Run a leadership team meeting that produces decisions: a timed weekly agenda, an issues list method, and how monthly and quarterly sessions differ.
Strategy on a Page: How to Fill Out Each Box
Fill in a one-page strategy: where you compete, how you win, what you'll do this year, and how you'll measure it, with a worked example.
What to Put in a Co-Founder Agreement
Draft a co-founder agreement covering roles, equity, vesting, decisions, IP, departure terms and disputes, with an outline you can adapt.
Annual Planning for a Small Business: A Six-Week Worksheet
Plan your small business year in six weeks: review last year, pick three goals, build the budget, set quarterly milestones and a review rhythm.
A CEO Weekly Schedule for Founders, Block by Block
Build a founder's weekly schedule with protected focus time, a leadership meeting, customer time and a Friday review, then audit it after two weeks.