6th & 7th October 2026
Radisson Hotel & Conference Centre London Heathrow
17th May 2027
Hilton London Canary Wharf
Education Technology Forum

Safeguarding software for schools: A buyer’s guide to recording and oversight

When a designated safeguarding lead (DSL) reviews a child’s history, that history should be in one place, not spread across paper forms, spreadsheets and email. Safeguarding software for schools can make that possible by helping staff record concerns promptly and track the decisions that follow, so information reaches the right people when a case escalates or a pupil moves school.

The right system gives staff a clear way to report concerns, lets DSLs review and escalate them, and limits sensitive information to the people who need it.

What types of safeguarding software do schools need?

Before comparing products, separate the technologies involved. Safeguarding recording software, sometimes called child protection software, stores concerns, chronologies, referrals and child protection files.

Filtering software restricts access to harmful online material, while monitoring tools identify potentially concerning activity on school devices and networks. Visitor management systems record who is on site. This guide focuses on recording software, including how concerns raised through monitoring are followed up.

What should safeguarding recording software include?

Keeping children safe in education (KCSIE) 2026, the statutory guidance in force in England since 1 September 2026, says concerns, discussions and decisions, and the reasons for those decisions, should be recorded in writing. Records should summarise the concern, how it was followed up and the outcome, distinguishing observed concerns from professional opinion and historic information.

Initial records often need updating, so authorised users should be able to add actions, decisions and outcomes without losing earlier entries. The system should build a chronology for each child, alert the DSL and deputies, and securely store body maps, documents and referrals.

Recording a concern must never delay action to protect a child. Staff should follow the school’s procedures and speak to the DSL or a deputy, seeking emergency help where a child is in immediate danger. The software should support that response, not slow it down.

A reliable history matters most when a pupil moves school. KCSIE expects the child protection file to be transferred as soon as possible, and within five days for an in-year move or within the first five days of a new term. The file should be sent separately from the main pupil file, securely and with receipt confirmed. It should also come with a structured summary of current concerns, context and ongoing support needs, kept distinct from historic information. Ask whether a system can produce that summary for a school on a different platform.

How filtering and monitoring support school safeguarding

Some concerns surface through monitoring. Not every alert needs to become a safeguarding record, but those needing action should reach the safeguarding team and be recorded. KCSIE makes the DSL the lead for online safety, including filtering and monitoring.

The DfE’s filtering and monitoring standards apply to that provision, not to the recording platform. They expect a named senior leader and a named governor to be responsible, a review at least once every academic year, and filtering that blocks harmful content without unreasonably affecting teaching and learning.

As a minimum, monitoring should include weekly incident reports and immediate reports of high-risk incidents. Installing a product doesn’t meet these expectations, because someone still has to review alerts and act on them. Security tools don’t fill that role either, so map where cybersecurity and safeguarding responsibilities meet before buying in either area.

Safeguarding reporting, Ofsted and trust-wide oversight

Records should also help leaders spot recurring issues and confirm that actions are complete. Look for reporting by category, year group or vulnerability, open cases and response times, and anonymised summaries for governors and trust boards. Reports depend on staff categorising concerns in the same way, so check how the system keeps categories consistent.

The same evidence matters at inspection. Under Ofsted’s renewed inspection toolkit for state-funded schools, safeguarding is judged “met” or “not met”. Leaders must fulfil statutory requirements, including reporting, referrals and record-keeping. Inspectors also consider whether staff follow the school’s systems consistently and whether leaders learn from cases and incidents. Reports can reveal gaps, but inspectors will look at how procedures work in practice.

Multi-academy trusts should look for trust-wide dashboards, consistent categories and role-based access for the trust safeguarding lead, so oversight doesn’t expose case detail unnecessarily.

Protecting safeguarding records and managing access

Role-based access matters within each school too. Staff should be able to log a concern without seeing a child’s full history, and an audit trail should show who viewed or changed each record. Syncing with the management information system (MIS) reduces the risk of recording a concern against the wrong child.

Concerns about adults need separate handling. KCSIE distinguishes allegations that may meet the harm threshold from low-level concerns about staff. For low-level concerns, the headteacher or principal is the ultimate decision-maker, and records must be kept confidential and secure and reviewed to identify patterns. Check that any staff-concern records are restricted, with separate workflows that match your policies.

These records also need careful data protection checks. The DfE’s guidance on buying education technology says schools must complete a data protection impact assessment (DPIA) when processing is likely to result in a high risk to individuals’ rights and freedoms. Work through it with your data protection officer, check hosting and the processor contract, and set retention periods to match your own retention schedule. KCSIE is also clear that data protection law doesn’t prevent sharing information to keep children safe.

Safeguarding software implementation and costs

Moving from paper needs a clear migration plan. Agree when electronic recording starts, how active cases will move across and whether historic files will be scanned or retained securely. Existing information must stay accessible to authorised staff throughout.

Those decisions also shape the cost. Suppliers may charge per pupil, per school or across a trust, but licence fees are only part of the comparison. Ask what migration, training and support are included, and whether complete records, including audit trails, could be exported if you changed provider.

Safeguarding software demo checklist

Demonstrations are most useful when suppliers show how their system handles realistic situations:

  • A teacher records a concern. How is the DSL notified, how are actions added later, and does the process stay clear when a concern needs immediate escalation?
  • A pupil leaves mid-year. Can the system produce the structured transfer summary, send the file securely to a school on another system and confirm receipt?

Then ask:

AreaWhat to ask
AccessCan we restrict staff-concern records and see who viewed or changed a record?
IntegrationDoes it sync with our MIS and receive alerts from our monitoring tool?
Resilience and costWhat happens during an outage, and what do migration and training add to the cost?

Discuss your requirements at the Ed.Tech Summit

If safeguarding software is on your procurement list, include it among the products or services you want to discuss when applying for the Ed.Tech Summit. Held on 17 May 2027 at Hilton London Canary Wharf, the event brings eligible senior education decision-makers and technology suppliers together for pre-arranged one-to-one meetings, with scheduling informed by applicants’ projects and preferences. 

Apply for a buyer place at the Ed.Tech Summit

Frequently asked questions

How should schools compare safeguarding software providers?

Start with your own policy and workflows, not a feature list. Agree requirements with your DSL, data protection officer and IT lead, test each shortlisted system against the same scenarios and compare total cost.

Do schools have to use electronic safeguarding records?

No. KCSIE sets out what records should contain and how files should be transferred, not whether they are kept on paper or electronically.

Can a trust see safeguarding data across its schools?

It can, within limits. Access should reflect safeguarding responsibilities, lawful information-sharing arrangements and clearly defined permissions. A trust safeguarding lead may need oversight of emerging patterns, but that doesn’t automatically justify unrestricted access to every school’s records.

Image credit: https://unsplash.com/photos/man-using-smartphone-in-front-of-computer-monitors-xtu0RUzmjjs

YOU MIGHT ALSO LIKE

Leave a Reply

Your email address will not be published. Required fields are marked *