A 3-level escalation ladder

An earlier lesson made work visible by tracking request status and turnaround time, and the last one kept work moving when someone is away. One question still hurts every week: the request was not blocked and nobody was absent, it was simply late, and nobody noticed until the customer called to ask.

Lateness does not need an emergency plan. It needs an escalation ladder: a written deadline per step, and three levels a case rises through automatically once the deadline passes. The point is simple, the system notices the delay instead of the customer.

Why manual escalation fails

• Noticing depends on memory: staff are busy with today's requests, and the late one is exactly the one that slips their mind.
• No stated deadline: if you never wrote that a purchase approval takes one working day, there is no definition of late at all.
• Escalation feels personal: when raising it to a manager is an individual choice, staff hesitate in case it reads as a complaint about a colleague.
• Everything reaches the owner: dozens of alerts a day, and within a week they are all ignored.

The three levels

1. Remind the owner of the step

The first level is not escalation, it is a reminder. When the deadline passes, only the person responsible for that step gets a notice: request such and such is past its deadline. Most delays end here, because the cause is forgetfulness rather than a real blocker. Keep this level silent to the rest of the team so nobody feels watched.

2. Raise it to the direct supervisor

If a second deadline passes with no movement, the case moves to the supervisor with a visible reason: waiting on a supplier reply, a missing document, or no reason recorded. The supervisor does not approve on the employee's behalf, they remove the blocker or reassign the work. This level is what stops a delay from becoming a complaint.

3. Notify the business owner

The third level is reserved for cases that touch a customer or money: a customer order past the promised date, a supplier payment near its due date, or a critical item near stock-out. If more than five of these reach you in a day, the deadlines are wrong, not the team.

Escalation deadline table

Step	Deadline	Level 1	Level 2	Level 3
Purchase request approval	1 working day	Purchasing officer	After 1 more day: supervisor	After 3 days or large amount
Invoice after delivery	24 hours	Accountant	After 48 hours: supervisor	After 3 days
Warehouse issue	4 working hours	Storekeeper	End of day: branch supervisor	If a delivery is held up
Customer enquiry reply	2 hours	Sales staff	After 4 hours: supervisor	After a full day

Start with realistic deadlines based on your current average turnaround, not on ambition. A deadline that half your requests miss produces noise the team learns to ignore within days.

A WhatsApp example

The owner sets the rule with one message to a system run from WhatsApp:

Purchase requests pending more than one working day, alert the purchasing officer; after two days raise it to the supervisor; above 10,000 SAR tell me directly.

The system confirms the rule and who receives each level. The next day the purchasing officer gets a notice about two overdue requests, clears one, and records a reason on the other: waiting for a third quote. When the second day passes, the supervisor gets a notice about the one remaining request with that recorded reason, and decides two quotes are enough. Nothing reaches the owner, because the amount is under the threshold.

When a warehouse issue is late enough to hold up a delivery, the alert goes straight to the owner with the order number, customer name and how long it has been waiting, and one reply settles it. The same rule drives reorder-point alerts when an item nears stock-out.

Checklist before switching escalation on

1. Does every critical step have a written deadline the team knows?
2. Is that deadline based on your actual current turnaround?
3. Does level one reach only the responsible person?
4. Can staff record a waiting reason instead of ignoring the alert?
5. Have you defined what genuinely deserves to reach the owner?
6. Do you review escalation counts monthly and adjust the deadlines?

A common mistake

Using escalation as a scorecard on people. If the escalation report becomes a list of who was late, the team learns to close requests on paper before the deadline without finishing the work. Ask about the step, not the person: which step keeps escalating, and why.