For DSLs and operations managers
What a good out-of-hours escalation policy looks like
A practical framework for deciding who responds, when to escalate and what happens if a contact is unavailable.
Start with a usable decision route
A policy needs to work when someone is tired, worried and looking at a phone. Put the immediate response, the escalation route and the fallback contact together in a short operational guide. Keep the fuller procedures available behind it. A duty responder should be able to find the next action without interpreting several documents.
Define the limits of the first response
Describe what the responder can arrange independently and what requires a school decision. Useful examples include a delayed arrival, an accommodation access problem and a concern about a student’s welfare. For each example, identify the information to establish, the person to contact and the decisions the responder cannot make. Safeguarding concerns should follow the school’s agreed safeguarding procedures.
Make the fallback explicit
List roles as well as names, with current contact details and the periods each person covers. Agree what to do if the first contact does not answer, how attempts are recorded and which alternative route applies. Avoid a contact tree that eventually loops back to the same unavailable person. Set response expectations with the people who must meet them.
Close the loop at handover
The incident record should show the concern, actions, contact attempts, decisions and outstanding work. Assign a named owner to the next action and specify how they acknowledge receipt. A message sent at the end of a shift is not the same as a follow-up accepted.
Test it before you need it
Walk through a late arrival, an unavailable duty manager and a concern that needs the safeguarding lead. Ask a colleague unfamiliar with the document to find the next step. Update any unclear instruction, confirm the contact details and record who owns the next review.