Escalation
In operations, escalation is raising a task or request to a higher level of authority, such as a supervisor or manager, when it is overdue, at risk of missing its target, or beyond what the assignee can resolve.
Also known as: escalation rule · escalation path · escalation matrix
Escalation is how an operation makes sure nothing sits forgotten. When a task passes its deadline, nears an SLA breach, or needs a decision or skill the assignee does not have, it is raised to someone who can act: a supervisor, a department head or the duty manager.
Example
A guest asks for a baby cot at 19:10. The task goes to housekeeping with a 30-minute deadline. At 19:40 it is still open. The housekeeping supervisor is alerted, finds that the room attendant is tied up with a VIP turndown, and sends someone else. Without the escalation, the next sign of trouble would have been a second, less patient call from the guest.
Types of escalation
- Time-based (hierarchical): triggered when a task is overdue or close to its deadline, and raised up the management line.
- Functional: passed to a team with the right skills, for example from a general technician to a lift specialist.
- Manual: a staff member flags a problem they cannot solve, such as a missing spare part.
An escalation matrix writes this down: who is notified, after how long, for which category and priority.
How it relates to neighbouring terms
An SLA sets the target; escalation is the safety net when the target is at risk. A missing first response is often the first trigger, because an unacknowledged request is the one most likely to be lost. Escalation is not the same as reassignment: the original owner may keep the work order, but now a supervisor is watching it.
Where TaskLoop fits
TaskLoop escalates overdue tasks to supervisors, so late work becomes visible without anyone chasing it by phone. Supervisors also see all open requests and department workload in real time on the admin dashboard. See escalations and SLAs.