Escalation policy
Escalations follow a fixed, domain-driven path — from executor to tactical to strategic level, at both supplier and internally.
What is this process?
Escalations follow a fixed, domain-driven path — from executor to tactical to strategic level, at both the supplier and internally. Organisation-wide signalling recognises conflicting agreements between suppliers before they become a problem.
How does it work in ServiceCockpit?
- 1
Vendor Manager marks a backlog or missed deadline as escalatable. ServiceCockpit opens the escalation path belonging to the RCF domain and shows the current level plus the next holder.
- 2
Supplier's external SDM receives the escalation at his level — the tactical line runs in parallel internally. ServiceCockpit records receipt and starts the time tracking per level.
- 3
Service Manager guides the resolution within the agreed term. ServiceCockpit flags a missing response and automatically escalates to strategic level.
- 4
Vendor Manager receives the signal on conflicting agreements between suppliers. ServiceCockpit scans organisation-wide for contradictory obligations — an early signal, before it becomes a problem.
- 5
Service Manager closes the escalation with the findings. ServiceCockpit records the entire escalation process in the supplier file and the reporting.
Roles
RCF domains
Evidence & automation
- Escalation procedures per RCF domain are configured in advance — not improvised per incident.
- Level transitions happen based on thresholds, not on individual initiative.
- Every escalation leaves a traceable trail in the supplier file.
How we do it
Escalate on time margin, not on tone
- Set fixed terms per RCF domain on which an open action automatically moves up a level.
- Make the path visible to the supplier: both work with the same escalation matrix.
- Then escalation is no longer a negotiation, but a feature of the system.
Modules that support this process
Tasks & Escalations
/en/modules/taken-en-escalaties
Control Centre & KPI dashboards
/en/modules/regiecentrum
See this process live in a demo
The fastest answer to “does this really work?” is half an hour looking together at your own scenario.