For DSLs and operations managers
What belongs in an out-of-hours incident handover?
Give the morning team enough context to act, with a clear record of what remains unresolved.
Record the situation clearly
Start with the time of the contact, the person reporting the issue, the relevant student identifier and a concise description of the concern. Include location and contact details where needed for the response. Separate what someone reported from what the responder directly established; avoid presenting an assumption as a confirmed fact.
Show what happened next
Use a short timeline for actions and contact attempts. Record who was contacted, whether they responded, what was agreed and who authorised a decision. A useful entry explains the result of the action: “residence contact confirmed access” tells the next reader more than “called residence”.
Make outstanding work visible
State the position at handover. Identify what is resolved, what remains uncertain and what still needs a decision. Give each follow-up an owner and an agreed time or trigger. If the next team must check that a student has arrived, make that an explicit action rather than leaving it buried in the narrative.
Use the agreed information route
Keep the record relevant to the incident and use the school’s agreed systems and access arrangements. Sensitive concerns should follow the relevant reporting procedure. Avoid copying an entire record to everyone simply because they are on a general duty distribution list.
Confirm the handover has landed
Decide in advance who receives the record and how urgent outstanding actions are acknowledged. During service reviews, sample records for clarity: could a colleague understand the situation and take the next step without calling the overnight responder? Use recurring gaps to improve the template and briefing.