Test safeguarding chronology training by asking staff to record and review the same short synthetic concern. Compare whether they preserve source, fact, uncertainty, decision, owner and review point.
The DSL should lead the exercise. Leaders and governors need aggregated assurance about strengths, gaps and improvement actions. Case narratives remain restricted.
A rehearsal must not decide a threshold or delay a live response. Any current concern follows the school or college policy and the appropriate local or emergency route at once.
Use the guidance that applies on 15 August 2026
This guide is for schools and colleges in England. It supports training and assurance; it does not replace safeguarding training, professional consultation or local procedure.
Keeping children safe in education 2025 is current statutory guidance through 31 August 2026.
KCSIE 2025 says all staff should receive induction training, regular updates and at least annual safeguarding updates. Training should follow advice from local safeguarding partners.
It gives governing bodies and proprietors strategic responsibility for ensuring that policies, procedures and training are effective, understood and lawful.
Working together to safeguard children 2026 is current statutory guidance, published on 18 March 2026.
It expects local arrangements to explain how multi-agency training is delivered and monitored for impact. A school rehearsal should also test how staff apply the procedure.
KCSIE 2026 is published for preparation and starts on 1 September 2026. Until then it is forthcoming guidance. KCSIE 2025 remains the applicable standard.
From 1 September, all staff follow the same Part one expectations. The new text also says safeguarding records should distinguish observed concerns, professional opinion and history.
The regulated-activity supervision exemption also ends on 1 September 2026 for roles within the change's scope. Check role-specific arrangements against the official guidance.
Run one synthetic recording rehearsal
Use invented details that cannot be mistaken for a pupil or customer case. Keep the exercise brief enough to discuss how the record changes as information arrives.
- Give one factual signal. State what a staff member directly observed or received, with a source and time. Ask participants to record only what is known.
- Add a second account. Introduce information that does not fully agree. Check that staff keep both sources visible and mark uncertainty.
- Ask for the immediate route.Participants should follow the school's reporting process. The exercise must not invent a referral threshold.
- Add the DSL's reviewed decision. Record who reviewed it, the action and the reasons known at that point. Do not rewrite the original entries.
- Close with ownership. Name the role responsible for the next action, the review point and what evidence will be checked then.
Review the record, not the writer
Compare the outputs against six questions. The purpose is to improve the shared process while avoiding staff rankings or a safeguarding score.
- Can a reader identify the source, author, date and time?
- Are direct observations, reported accounts and professional opinion distinct?
- Are uncertainty, contradiction and missing context still visible?
- Does the record show the DSL review, decision and reasons actually known?
- Does each open action have an accountable owner and due point?
- Is the next review linked to evidence that could change professional judgement?
Give staff a correction route. A later clarification should be dated and attributed. It should preserve the incomplete historic entry instead of silently smoothing the story.
If the exercise reveals confusion about reporting, pause the assurance work and correct the procedure with the DSL. Do not wait for the next scheduled training cycle.
Turn observed practice into governance assurance
A training register shows who attended. It cannot show that staff can apply the procedure or that chronology records support accountable decisions.
The DSL and headteacher can give the governing body or proprietor a concise assurance note that protects case confidentiality. It should cover four elements:
- the training and local procedure tested, with version and date;
- the recurring recording strengths and gaps seen across the synthetic exercise;
- the improvement action, owner and completion date; and
- the date and method for checking whether practice changed.
Governors should ask how leaders know the procedure is understood and applied. Proportionate routine assurance excludes identifiable case material.
The current Ofsted state-funded school inspection toolkit is inspection guidance. It has no statutory force and considers whether leaders know procedures work in practice.
A separate toolkit is published for September 2026. On 15 August, schools should distinguish preparation for that future version from the toolkit currently in use.
Keep connected records subordinate to the source file
The following example is invented and combines no real case details. A training prompt says that a staff observation has been recorded, but its source and time are missing.
Attendance metadata shows a recent change. A communication log shows contact attempts. SEND metadata records an established communication support, but none explains the change.
The DSL reviews the authorised source records. The professional question is what is known, what is missing, what action local procedure requires now and who will review it.
The decision and next action stay in the safeguarding record. Other systems retain their own facts and metadata; the detailed narrative stays out of general dashboards.
Attendance, communication and SEND records cannot prove abuse or neglect, motive, parental capacity, urgency or a statutory threshold. They prompt professional enquiry.
Where Student Radar fits
Student Radar Safeguard supports controlled concern recording and DSL-led casework for authorised staff.
Chronology presents attributed entries in sequence. The DSL Action Board supports assignment and review points.
These features can help authorised reviewers open the underlying record and see ownership. They do not diagnose harm, score risk, decide a threshold or make an autonomous referral.
Keep staff-safeguarding records on their separate authorised route. Do not use pupil chronology training to rehearse allegations or low-level-concern classification.
Finish with one checked improvement
Choose the most consequential recurring gap. Confirm the owner, correction, staff update and review date, then test the same skill again with a different synthetic prompt.
Use the separate safeguarding chronology audit when the DSL is ready to sample authorised live records under the school's assurance plan.
For voice recording, read the child and family voice guide. For unresolved partner responses, use the professional challenge record.
Sources and further reading
- Department for Education, Keeping children safe in education, page updated 7 July 2026. KCSIE 2025 applies through 31 August; KCSIE 2026 starts on 1 September.
- Department for Education, Working together to safeguard children 2026, statutory guidance published 18 March 2026.
- Department for Education, Information sharing advice for safeguarding practitioners, non-statutory advice updated 1 May 2024.
- Information Commissioner's Office, A 10 step guide to sharing information to safeguard children, published 14 September 2023 and checked 15 August 2026.
- Ofsted, School inspection: toolkit, operating guides and information, updated 12 June 2026. The page labels the versions currently in use and those for September.
- Department for Education, Working or volunteering in regulated activity with children, updated 29 June 2026. The supervision exemption change starts on 1 September 2026.
Student Radar can help authorised DSL teams keep chronology, ownership and review evidence connected. Book a demonstration to test the workflow against your policy and access model.