Audit an attendance-related safeguarding escalation by tracing the concern from its sources to the DSL's recorded reasoning, owned action and review point. Staff should be able to explain what prompted concern beyond the percentage, what remains uncertain and who accepted responsibility. An attendance pattern prompts human enquiry. It can't diagnose, prove harm, assign blame or predict future absence.
Urgent concerns go immediately to the DSL or deputy through the school's safeguarding procedure and relevant local safeguarding route. For immediate danger, call 999. Don't wait for this audit, a complete record or a lower attendance figure before acting. This is a suggested assurance method for attendance leaders, DSLs, school leaders, pastoral and family-support staff and SENCos in England. It isn't a statutory form.
Pass one: follow one decision back to its sources
Choose an escalation already made and identify the decision being checked. Use the school's approved record and an auditor authorised to see the necessary material. The question is whether the decision can be understood and challenged. An audit can't retrospectively certify that a safeguarding judgement was correct.
Keeping children safe in education 2026 says concerns, discussions, decisions and their reasons should be recorded. Repeated or prolonged absence can be a vital warning sign. It doesn't establish why a child was absent or prove harm. Working together to improve school attendance also expects schools to listen to families, understand barriers and work together on support.
Use the annotated template below to test the chain. A reference can point to a restricted record without copying its sensitive narrative into an attendance tracker. These are editorial prompts, not Student Radar form fields or a scoring system.
| Record to inspect | Question for the authorised reviewer |
|---|---|
| Concern and source window | What specific information prompted concern? Identify dates, sessions, source and missing or corrected marks. Separate a reported event from the date it was recorded. |
| Attributed context and gaps | Who reported each fact or account? Distinguish observation, pupil or family account and professional interpretation. What support was offered, delivered or still unconfirmed? |
| DSL rationale | Who made the decision, when, and why? Can they explain how the available information informed it, what remained unknown and why the recorded response was chosen? |
| Acknowledged action and outcome | Who accepted each action? Check contact acknowledgement and evidence of delivery. Keep an action marked complete separate from evidence about the child's safety or experience. |
| Review and challenge | Who checks next, and when? What new information or failed contact brings review forward? Record how a correction or professional disagreement reaches the responsible decision-maker. |
Don't infer agreement from silence or delivery from an assigned task. If a reason is missing, record the gap and obtain a dated clarification from the responsible professional. Preserve the original entry. Don't backfill an explanation as though it existed at the time.

Try the template on an incomplete explanation
This composite is wholly invented and contains no real pupil, family, school or customer data. An attendance note says that a falling percentage was passed to the DSL. The source window shows repeated missed morning sessions. A family account describes transport difficulties. A separate staff concern has reached the DSL through the restricted record.
The percentage alone doesn't explain the escalation. The authorised reviewer checks the source references and asks the DSL to identify their recorded rationale. The concern may depend on information the attendance team isn't entitled to read. That team needs an acknowledged handoff and its own support instructions, not access to the whole case.
The record also says transport support was arranged. No one has confirmed delivery or asked whether the pupil could use it. The attendance leader owns that check, using the pupil's established communication method and SENCo input where needed. The family account is attributed and any disagreement preserved. A barrier deserves support; it neither proves nor rules out a separate safeguarding concern.
The audit leaves two explicit gaps: the DSL rationale needs a traceable reference, and support delivery remains unconfirmed. Each has an owner and a review time agreed for this case. Those times are local decisions, not national deadlines. New concerns or failed contact can require action sooner. Nothing in this example establishes a safeguarding threshold or a referral outcome.
Pass two: read back what happens next
Ask the responsible adults to read back their own action, the information they need, the next check and the route if that action fails. Use role-appropriate summaries; don't read a restricted narrative to a wider meeting. Check the record again after the agreed review point. A named owner is useful only if responsibility was accepted.
A completed call doesn't establish that support worked or that the child is safe. Record the observed outcome, pupil and family accounts where safe and appropriate, and what remains unresolved. Working together to safeguard children supports accountable decisions and multi-agency assessment. Follow local escalation and professional challenge procedures if concern remains unresolved.
Information sharing to safeguard children and young people informs decisions about necessary, proportionate sharing through approved channels. Record the sharing decision and reasons. Don't give every participant access to every source. Keep corrections attributable and preserve the route back to the original record.

Attendance percentages can't decide safeguarding thresholds or automatically trigger referral, sanction, penalty notice, attendance contract or any legal route. Registered pupils who are persistently or severely absent aren't automatically children missing education. Children missing education guidance requires careful judgement and appropriate enquiries; don't let an administrative label delay action.
For the earlier route decision, use the attendance and safeguarding guide. The chronology source-record audit checks recording quality. This audit asks whether one escalation has an intelligible, accountable decision trail. It doesn't repeat either task or assess cumulative harm.
Where enabled and authorised, Student Radar's Attendance Analytics exposes the pattern and source window, Safeguarding Chronology keeps restricted attributed records and decisions, and the DSL Action Board supports owner, status and review workflows. These tools don't determine risk, referral or outcome. Assess those workflows alongside your school's procedures.
Sources and further reading
Official sources checked on 14 November 2026. This article concerns England.
- DfE: Keeping children safe in education 2026, statutory guidance in force from 1 September 2026; publication page updated that day.
- DfE: Working together to improve school attendance, statutory guidance; publication page updated 9 July 2026.
- DfE: Children missing education statutory guidance for local authorities and schools, updated 8 September 2025.
- DfE: Working together to safeguard children 2026, statutory guidance; page and document updated 13 November 2026 to add MAPPA paragraphs 322 to 324. That addition doesn't change this school decision-audit method.
- DfE: Information sharing to safeguard children and young people, statutory guidance updated 10 September 2026; the section 16LA duty commenced on 30 September 2026.
