To review repeated concerns about possible neglect, read the chronology alongside the original accounts, support actually delivered and the child's experience over time. Check whether entries describe separate events, repeated reporting or unresolved questions. The DSL records their professional judgement, action owner and next review point. A pattern cannot substantiate neglect. Don't wait for a fuller chronology before acting on a concern through the school's safeguarding procedure, contacting the DSL or deputy, using the relevant local safeguarding partnership or children's social care route, or contacting emergency services where there's immediate danger.
This worked review is for DSLs and deputies in England, with sources checked on 4 November 2026. It concerns the cumulative picture across records. The separate disclosure-recording guide covers receiving and recording an individual account. This example doesn't replace training, supervision, professional consultation or local procedures.
Start with the sequence and its sources
The administrative example that follows is wholly invented. It contains no pupil, family, school or customer data. A DSL reviewing repeat concern entries sees several references to the same unmet need. A support offer also appears in the record. The first question is what those entries establish about the child's experience, and what remains unknown.
In Keeping children safe in education 2026, neglect involves persistent failure to meet basic physical or psychological needs, with likely serious impairment of health or development. That definition cannot become a count of entries. The guidance also identifies failure to reassess concerns when situations don't improve as poor practice. Repetition deserves professional attention even when each entry has previously received an administrative response.
The DSL opens the restricted source accounts. One entry is a staff observation. A later entry relays that observation in a meeting summary. A third records a separate concern. Counting all three as independent events would exaggerate what is known. Keep the second entry and its provenance, but identify its relationship to the first. Don't delete legitimate records to make the sequence tidy or erase the fact that the concern was discussed.
Preserve who observed or reported what, the event time where known, the recording time, and the source record or version. An opinion stays attributed to its author. An unknown event time stays unknown. A late entry or imported record can alter the apparent sequence; the date on a screen doesn't necessarily identify when the event occurred. Establish the review window and which records are available, restricted, missing or awaiting clarification.
DfE's practitioner advice, published in March 2015, explains that concerns can develop over time and need a coordinated response. Read its recognition advice alongside the 2026 statutory guidance. It supplies no numerical test for neglect. Neither a quiet period in the system nor an absence of new entries establishes that the child's circumstances improved.
Read the support record before interpreting repetition
The invented support entry initially says an offer was made. Its linked delivery record shows that the planned contact did not happen because the school could not provide the agreed arrangement. A later note says another contact is planned, with no outcome recorded. The concern history and support record now change the question: what help actually reached the child and family, and what still needs to happen?
Keep offered, agreed, delivered and reviewed support distinct. A completed task can mean someone sent a message; it doesn't establish receipt, participation or benefit. Ask the responsible colleague for the source account and outcome. If delivery remains unconfirmed, record that uncertainty and the enquiry owner. Don't turn a missing entry into a statement that the family refused help, or treat a school delivery gap as parental non-engagement.
In its multi-agency assessment framework, Working together to safeguard children 2026 calls for analysis that considers the child's history, cumulative harm and the impact of previous services. It also calls for challenge and reflection. The school's contribution is its factual evidence and accountable response; this review doesn't replace a statutory assessment or determine its outcome.
The DSL asks whether an earlier explanation still fits, what changed after support was delivered, and whether concerns continued across the review window. Record improvement and protective factors as carefully as unresolved needs. Improvement in one area doesn't settle every concern, and later improvement cannot by itself prove that a particular service caused it. Retain alternative explanations and seek appropriate professional challenge.
The Child Safeguarding Practice Review Panel's April 2026 thematic analysis of neglect calls attention to cumulative experience and the child's daily life. Its research supports looking beyond isolated episodes. These are findings and recommendations from a national review, distinct from statutory requirements. The example here borrows no case details or outcomes from that report.
Poverty, SEND, disability and health needs aren't proxies for neglect or parental capacity. NSPCC Learning's neglect guidance distinguishes poverty from neglect and explains that there is often no single indicator. Understand material barriers and access needs while continuing to respond to the specific concern. An explanation for difficulty doesn't remove the need to establish whether the child receives the help and protection they need.
Bring the child's and family's account into the review
In the invented record, the family's account of the agreed contact arrangement is available, but there is no attributed account of how the child experienced the support. That gap changes the review again. The DSL identifies who will seek the child's views through an appropriate, accessible conversation, consistent with local procedures and any partner involvement. Don't repeatedly question a child or ask them to resolve conflicting records.
Distinguish the child's words, a parent's report and an adult's interpretation. Record relevant wishes and feelings, what the child says would help, and how these informed the response. If an account cannot yet be obtained safely or accessibly, retain the gap and the reason. An empty field isn't agreement, reassurance or evidence that there is nothing to say. The child and family voice review explores that recording boundary in more detail.
Explain an appropriate route for the child or family to correct factual inaccuracies, where safe to do so. Preserve the original record and attribute additions or corrections with their date and reason. Disagreement belongs in the evidence, alongside the DSL's judgement and rationale. It doesn't automatically resolve the concern in either direction.
Leave an accountable decision and next review point
The DSL records the distinction between the original concern and its repeated summary, the undelivered school support, the separate later concern and the missing child's account. Their review remains open. The DSL owns the safeguarding response through local procedures; the support lead owns checking and restoring the agreed arrangement. Each action has a specific review point proportionate to the situation, with earlier action if new information changes the concern. Agree those points in the actual case; this example sets no statutory deadline.
Review question: What does the sequence establish about the child's needs over time, and what evidence could change the DSL's judgement?
Decision record: Record the DSL's interpretation and reasons separately from facts, the action taken through local procedures, who owns each outstanding enquiry, and when the DSL will review the answer or continuing uncertainty.
Challenge: Record who will provide professional supervision or challenge and how unresolved disagreement will follow the local escalation procedure.
Follow the local professional challenge route if the response remains unresolved or circumstances don't improve. The professional challenge record helps preserve that exchange. A future meeting or unanswered request mustn't delay action needed now. Closing an administrative action cannot establish that a child is safe.
For sharing, use the September 2026 statutory information-sharing guidance. The section 16LA duty commenced on 30 September 2026. Where its criteria apply, organisations must share relevant information with a relevant recipient, subject to the statutory limitation concerning greater detriment to the child. Follow the guidance and local pathways for the actual decision. Data protection still requires lawful, necessary, proportionate and secure processing, with an accountable record and any additional conditions for sensitive data. Don't wait for a statutory assessment threshold before considering necessary sharing.
Authorise access to each source separately, including sensitive metadata and the existence of a record. Keep concern narratives in the restricted safeguarding system. Don't copy them into general dashboards, SEND plans, behaviour records or routine family messages to assemble a connected picture. A shared pupil reference or a SENCo role alone doesn't grant safeguarding access.
Where enabled and authorised, Student Radar's case chronology supports reviewing recorded history, while the DSL Action Board supports ownership and review follow-up. Staff still read permitted source records and check gaps. These tools cannot substantiate neglect, diagnose, score a child's risk, decide statutory thresholds or make autonomous referrals. Review the school safeguarding workflow against your arrangements. Begin with one outstanding question, its source, an accountable adult and the point at which they will review it.
Sources and further reading
- Keeping children safe in education 2026, Department for Education: England statutory guidance, in force from 1 September 2026. Part 1 paragraphs 29, 74 and 76, and Annex B on the DSL role. Landing page updated 1 September 2026.
- Working together to safeguard children 2026, Department for Education: England statutory guidance, published 18 March 2026. Multi-agency analysis and decision-making, paragraphs 185 to 191.
- Information sharing to safeguard children and young people, Department for Education: statutory guidance updated 10 September 2026; section 16LA duty commenced 30 September 2026. Chapters 1 to 3 cover scope, limitation and data protection.
- What to do if you're worried a child is being abused, Department for Education: non-statutory practitioner advice, published 26 March 2015. Recognition and coordinated action; read alongside the 2026 statutory guidance.
- Protecting children from neglect, NSPCC Learning: professional guidance updated 28 July 2026, recognition and poverty sections.
- Child neglect: A thematic analysis, Child Safeguarding Practice Review Panel: primary review research published 27 April 2026, particularly pages 6 to 7 and 25. All six underlying sources were checked on 4 November 2026.