Table of Contents
What KCSIE 2026’s Part Four means for how schools handle low-level concerns about supply staff, trainees, volunteers and contractors
Most schools have spent the last decade quietly transforming how they safeguard pupils. A concern raised in a corridor now lands in a structured system within minutes, categorised, timestamped and visible to the right people. Compare that to how the same school typically handles a low-level concern about a member of staff, and the gap is stark. Too often it still lives in an email, a note in a drawer, or someone’s memory of a conversation that happened “a while back.” Keeping Children Safe in Education 2026 doesn’t just tidy up the language around staff allegations, it puts that gap directly in the spotlight.
What Part Four actually tightens
Part Four of KCSIE 2026 keeps the framework schools already know: a clear line between low-level concerns or allegations that meet the harm threshold, and those that don’t. What’s changed is who that framework explicitly covers. Trainee teachers are now named alongside supply staff, volunteers and contractors, joining a group the guidance already expected schools to treat with the same seriousness as permanent employees. The instruction that any concern, “no matter how small”, should be referred appropriately, and that headteachers or principals should consider a referral to the Local Authority Designated Officer, now appears earlier and more prominently in the document.
None of this is a dramatic rewrite. It’s a tightening. And that’s exactly what makes it worth paying attention to: the DfE isn’t describing a new kind of risk, it’s describing the same risk schools have always had to manage and insisting more clearly that the process around it has to hold up under scrutiny, for every category of adult in the building.
The widening circle
That’s harder than it sounds, because the people most likely to fall outside a school’s normal record-keeping rhythm are precisely the ones Part Four names. A supply teacher isn’t in the annual appraisal cycle. A contractor isn’t on the staff behaviour policy briefing list in the same way a permanent teacher is. A trainee is often someone else’s employee for part of the week. Each of them can be the subject of a low-level concern just as easily as anyone else, and each of them is more likely to have that concern handled informally, by whoever happens to be in the room when it’s raised.
The result is a familiar and uncomfortable question for any designated safeguarding lead: if a low-level concern about a visiting music teacher, a facilities contractor, or a trainee on placement was raised six months ago, could you produce a clear, dated, decision-by-decision record of it today? Not a recollection. A record of who raised it, how it was categorised, who decided whether it met the harm threshold and what happened next.
What good practice looks like
Part Four is, in effect, asking schools to apply the same discipline to staff safeguarding that they already apply to pupil safeguarding: one place to record a low-level concern, consistent categorisation regardless of who the concern is about, leadership visibility without needless exposure and a trail that shows a decision was made and why. That standard shouldn’t change because the person the concern relates to is agency staff rather than payroll, or three weeks into a placement rather than three years into a career.
This is where the culture question and the systems question meet. A school can have exactly the right values and still fail to evidence them, simply because the mechanism for capturing a low-level concern about a contractor looks nothing like the mechanism for capturing a concern about a child. Two safeguarding cultures operating side by side, one visible and auditable, one informal and fragile, isn’t a sustainable position under a guidance document that increasingly expects consistency across the whole adult workforce.
Closing the gap in practice
This is precisely the gap CPOMS StaffSafe was built to close. Rather than treating staff safeguarding as a separate, paper-based process bolted on beside pupil safeguarding, StaffSafe brings it into CPOMS StudentSafe, so schools and trusts have one governed system, one set of standards and one defensible audit trail – whatever the individual’s employment status. A low-level concern about a supply teacher is captured with the same rigour as a low-level concern about a permanent member of staff. Leaders get the oversight Part Four expects, role-based permissions keep access appropriately restricted and records can be reviewed, updated and closed in a way that stands up to inspection, months or years after the event.
KCSIE 2026 hasn’t reinvented staff safeguarding. It has simply made it harder to ignore the places where practice hasn’t caught up with policy. To find out more about how StaffSafe can support your school or trust, book a demo today.
