Escalation Matrix Not Followed? The 5-Part Fix We Built

The usual advice for an escalation matrix not followed by your team is to write a better SOP and email it to your managers. Our client had already done exactly that. They’re a D2C hospitality group: a restaurant chain of 268 people across 20-plus outlets, running three different formats. The SOP was clear and the managers had been made responsible. Even so, stewards, commis and cashiers from every outlet kept calling the founder directly, and the founder kept picking up.

Why is the escalation matrix not followed even after you send the SOP?

An SOP email assumes the problem is information. It rarely is. When we sat down separately with the founder, the managers and the frontline teams, we found four overlapping reasons staff skipped their managers:

1. They didn’t know. The SOP went to managers. Most people below them had never seen it, and new joiners had no way to find it.
2. They didn’t remember. A PDF sitting in an inbox is not available at the moment of a dispute, which in a restaurant is usually in the middle of dinner service.
3. They bypassed on purpose. Long-tenured staff knew the founder personally. Calling him got faster results than going through the official channel.
4. They expected no support. Some believed the manager would not back them, and some did not want to be seen as the manager’s person.

All four were true at once, which is why a single fix like re-sending the SOP or running a reminder session could never have worked. The SOP was answering the first reason only.

Why don’t managers own escalations, even when they’re told to?

The founder’s first read was that the managers were weak. The manager interviews told a different story:

That last row matters most. When some employees can reach the founder and others can’t, the people with access can make their manager look ineffective whenever they want. According to Gallup’s research, managers account for at least 70% of the variance in team engagement. A manager who is undermined in front of their own team can’t hold that engagement, however capable they are.

Why did the founder keep the back door open?

This part is easy to judge and hard to see. The founder opened the direct channel because the middle layer could not yet be trusted with ownership. He was afraid that one missed escalation would mean a resignation, a walkout at one outlet, or a guest complaint nobody told him about. Mera darwaza hamesha khula hai (my door is always open) was a sincere promise, not an ego trip.

The trouble is what that open door costs. Here’s an illustrative calculation, not this client’s data. Say a founder handles 15 bypass calls a week, each taking 20 minutes once you include context-gathering and the follow-up call. That’s 5 hours a week. At a founder’s time valued at ₹3,000 an hour, it comes to about ₹60,000 a month spent on issues an L1 manager should have closed. The bigger cost is that he decides with half the picture, because he only hears one side, live, on the phone. Our founder hourly-rate test works through this same calculation.

So the goal was never to cut the founder off. It was to make sure that when an issue reached him, it came with the full picture: what happened, what the manager tried, and what the manager recommends.

What we built: a phone-first escalation matrix and four supporting pieces

We kept the build deliberately simple. The test was ease of use first and scale later. Three formats meant three different floor hierarchies, so whatever we built had to show each person their own chain, not one chart for the whole company.

1. A phone-first escalation matrix with levels that unlock in order

We built the Escalation Matrix micro-application, a single page that every staff member opens from one link on their phone. They type their name and see only their Level 1, their HOD, with a WhatsApp button and a call button. The higher levels stay hidden on purpose. To see Level 2, the employee has to confirm that Level 1 already knows about the issue. Level 2 then opens with a WhatsApp button only, so the message arrives with full details instead of as a rushed call. Level 3 sits behind the same check.

The separate ladders are intentional. A matrix that makes someone report harassment or a pay dispute up their own reporting line will be bypassed, and it should be. Building those routes in up front is what makes the rest of the matrix credible. The guide on the page is written for the floor in Hinglish and English: don’t bypass, give full details, be patient. You can try the live demo with a fictional restaurant group on your phone.

2. A joining manual that teaches the route on day one

Escalation now gets covered in onboarding, alongside leave policy and attendance, so new joiners stop learning the shortcut from senior colleagues. We used the same WhatsApp-first logic we described in how to create SOPs for a small business.

3. A formal step when the verbal route fails

Daily issues still start with a conversation. If that doesn’t resolve it, the employee raises a short written escalation and the manager records it in a one-on-one log. The managers’ complaint that people issues were never documented got a 3-line answer, not a form:

Issue: [what happened, one line]
Raised by / date: [name, date]
What I’ve done / next step: [action, by when]

4. A handling guide for managers

The guide covers how to listen and what managers may decide on their own. It also lists which clauses of the company’s existing code of conduct apply to each issue type, so managers point to a rule instead of inventing a ruling. We paired it with a session that walked managers through their authority and responsibility side by side. That helped because the Industrial Relations Code, in force since November 2025, already expects a formal grievance mechanism in establishments of this size. A working matrix covers that expectation as well. Our checklist system for training staff without a trainer carried most of this.

5. The founder’s rule, which mattered most

No escalation gets taken up without a formal note from the manager. The founder doesn’t ignore the call or turn the person away. He redirects them:

“Thank you for telling me. Please take this to [manager name] first. If it isn’t sorted by [day], ask them to send me a note and I’ll look at it personally, with both sides.”

Every call redirected this way strengthens the manager. Every call the founder resolves himself weakens them. This is the founder-dependency trap we cover in making a business less dependent on its founder.

Why a simple HTML page instead of an HRMS?

An HRMS with a ticketing module would have been the default recommendation. It also would have meant per-user licences, logins, vendor hosting, training and a long adoption curve, for a problem that was really about behaviour. The escalation matrix we built is one encrypted file sitting on the website the client already pays for. Software cost is ₹0. Staff data is encrypted inside the file, and sensitive fields like salary and gender never go into it. Once opened, it works offline on a phone. HR keeps it current by uploading the same Excel they already maintain, so a new joiner can be live in minutes without a developer. We built the first version for this 268-person group in a day.

There is one trade-off, made on purpose. The page keeps no history, because there’s no server behind it. The manager’s one-on-one log covers the record for now. When the habit holds and the founder needs audit trails, the server-based version takes the same data.

What should you measure in the first 90 days?

Track the habit, not the document. Four signals tell you whether the matrix is working:

• Direct calls to the founder per week, which should fall steadily
• The share of escalations that reach the founder with a manager’s note, which should approach 100%
• Entries in the one-on-one logs, which should rise at first. That rise means issues are now being recorded rather than going unreported.
• Founder reversals of manager decisions, which should be rare and always explained to the manager privately

Quick answers

An escalation matrix not followed by your team is rarely an SOP gap. The gap is in the shortcut everyone already knows about, and the person who has to close it is usually the founder.