Service Level Policy
Response windows, priorities and escalation
What happens when you log a fault, how it is prioritised, how quickly we attend, and what to do if the window is at risk.
Version 1.0 · Last reviewed September 2026
Applicability
Who this policy applies to
Prioritisation
Priority levels and response windows
Every request is assigned a priority when it is logged, and the response window follows from that priority. Priority is set with you on the call — not decided afterwards.
Scroll sideways to compare tiers
Priority is agreed with you when the call is logged, so the window follows the incident rather than being decided afterwards.
Escalation
If the window is at risk
Escalation is not a second ticket. Each level owns the incident until it is resolved or handed up with a named owner.
P1
Field engineer to duty supervisor immediately
P2
Duty supervisor to service manager
P3
Service manager to operations head
Commitments
What we commit to on every contracted call
- A logged call reference on every request, whether it arrives by phone, email or helpdesk.
- Consumables and standby replacement hardware for corporate desktops, workstations and servers.
- Scheduled preventive maintenance, so faults are found before they become breakdowns.
- An engineer who arrives knowing the estate, because the asset register travels with the contract.
- Escalation to a named supervisor if the response window is at risk — not a second ticket.
- Monthly or quarterly service reviews, depending on the estate size.
Exclusions
What sits outside the response commitment
Raising a request
How to log a fault
Review
Service reviews
Next step
Need your contracted windows confirmed in writing?
Send us the site name and we will issue the response windows, covered asset list and exclusions that apply to your contract.
This page describes Scantech's standard service levels. Your signed contract is the governing document.
