Safeguarding Software for Schools: A Buyer's Guide

Choosing safeguarding software for schools is one of those decisions that looks straightforward until you start comparing options. Every system on the market will let you record a concern. The differences — the ones you will feel every day for the next five years — sit underneath the demo.

This guide is written for Designated Safeguarding Leads (DSLs), headteachers, business managers and Multi-Academy Trust (MAT) leaders who are either buying school safeguarding software for the first time or reviewing a system that no longer fits. It sets out what the category actually covers, the questions worth asking, and how to run a procurement that gets you a fair comparison rather than a polished sales pitch.

First, Be Clear What You Are Buying

"Safeguarding software" is used loosely in the education market, and it covers at least four different product types. Being precise about which you need saves a great deal of wasted time.

Category	What it does	Typical examples
Concern recording and case management	Staff record concerns; DSLs triage, act, and build a chronology per child	The core of what most schools mean by safeguarding software
Filtering and monitoring	Blocks harmful content and flags risky activity on school devices	Sits alongside, not instead of, case management
Anonymous pupil reporting	Gives pupils a confidential route to report worries	Often an add-on to a recording system
Safeguarding training	Delivers and tracks statutory staff training	Usually a separate purchase

Most schools searching for school safeguarding software want the first category — a system of record for concerns — and then decide whether to consolidate the others into it. Search results mix all four freely, so a shortlist assembled from a single search can end up comparing products that do not compete with each other.

Keeping Children Safe in Education (KCSIE) does not mandate any particular software. What it does expect is that concerns are recorded, acted on, and evidenced. Your software choice is about how reliably you can do that.

The Questions That Actually Separate Systems

1. Does it show you patterns, or just store records?

This is the single most useful question to ask in a demo.

Every system produces a chronology for an individual child. Far fewer help you see across children, across time, and across concern types — the accumulation of small, individually unremarkable entries that together indicate something is wrong. Serious case reviews return to this point repeatedly: the information was usually present, but nobody joined it up.

Ask the vendor to show you how the system surfaces a pattern without someone already suspecting it. If the answer depends on a DSL running the right report, at the right moment, with the right filters, then the system is storing information rather than helping you interpret it.

2. How consistent is the response when you are not there?

Safeguarding quality varies with who is on duty. A concern raised at 4pm on a Friday should get the same considered response as one raised on a Monday morning.

Ask how the software supports staff who are not safeguarding specialists. Does it prompt them for the right detail at the point of recording? Does it reference your own policies when suggesting next steps, or does it rely on the individual knowing what your policy says? Consistency is a design property of the system, not a training problem you can solve indefinitely with INSET.

3. What does it do to your admin burden?

DSL workload is the reason many schools change systems. Look specifically at:

• Subject access requests — can the system compile everything for one person and redact third-party information, or is that a manual afternoon?
• Transfers in and out — what happens when a child arrives with a folder of documents from a previous setting?
• Document handling — are uploaded reports, EHCPs and letters readable and searchable, or just attachments?
• Reporting to governors — is the termly safeguarding report a click, or a rebuild?

4. Does it integrate with your MIS?

Duplicate data entry is where safeguarding records go stale. Ask which management information systems are supported — Arbor, Bromcom, Wonde, SIMS and others — and specifically what syncs: roll and demographics, attendance, and whether child protection status flows through automatically.

5. Where does the data live, and who can reach it?

Safeguarding records are among the most sensitive data a school holds. Establish:

• Where data is hosted (UK regions matter to many governing bodies)
• Encryption in transit and at rest
• Granular role-based permissions — can you restrict sensitive records to DSLs only?
• Audit logging — can you see who viewed what, and when?
• Authentication — is multi-factor or passkey login supported?
• Sub-processors, retention periods and the data processing agreement

A vendor should publish this rather than assemble it on request. Be precise about certification claims, too: there is a meaningful difference between a supplier who is certified to a standard and one whose hosting provider is. Ask which applies.

6. What is the total, honest cost?

Pricing in this market is often quoted per pupil, but the headline figure is rarely the whole story. Ask directly about: per-user or per-staff-account charges, feature tiers, modules priced separately, data migration fees, training costs, and what happens to the price at renewal.

For MATs, ask how central oversight is licensed — trust-level reporting is sometimes a separate product.

7. How do you get your data out?

Ask this before you sign, not when you leave. You should be able to export your complete safeguarding record in a usable format. Migration difficulty is a real cost, and a vendor's answer tells you a good deal about their confidence in keeping you.

Running a Fair Procurement

Shortlist three, not seven. Beyond three, demos blur and you end up choosing on presentation quality.

Use your own scenarios. Send each vendor the same two or three anonymised situations from your setting — a low-level concern that escalates over a term, a transfer-in with messy paperwork, a subject access request — and ask them to demonstrate those rather than their standard script.

Get the DSL and a non-specialist in the room. The person who uses it daily and the person who uses it twice a term have different definitions of "easy".

Ask for a reference from a school like yours. Similar size, similar phase, ideally one that migrated from your current system.

Test it with real-shaped data. A demo environment with three tidy pupils tells you very little about how the interface behaves with a full roll and five years of history.

A Note on Switching

Schools often stay with a system they have outgrown because migration feels daunting. It is worth separating two things: the genuine effort of moving historical records, and the inertia of habit.

If you are switching, plan for a clean cut-over date, a read-only archive of the old system for a defined period, and a short, practical staff briefing rather than a lengthy training programme. Ask any prospective supplier what they do for you during migration — importing historical records is a reasonable thing to expect help with.

Where Signal Fits

Signal is AI-powered safeguarding software for UK schools and Multi-Academy Trusts, built recently rather than maintained from a legacy codebase. Against the questions above:

• Patterns — Signal analyses concerns across your setting to surface connections and emerging risks, rather than waiting for someone to run the right report.
• Consistency — Signal reads your safeguarding policies and references them when suggesting next steps, so responses are grounded in what your school has actually agreed.
• Admin — subject access requests compile in one click with automatic redaction; transfer documents are summarised into a structured safeguarding picture; action plans and document summaries are drafted for review rather than written from scratch.
• Integration — Arbor, Bromcom and Wonde are supported, covering 60+ MIS systems, including child protection status flowing straight onto the pupil record.
• Security — hosted in UK Azure regions, built to UK GDPR and Data Protection Act 2018 requirements, with role-based permissions, audit logging and passkey authentication. Our due diligence page sets out the detail, including where we are and are not certified.
• Pricing — a flat rate per pupil, per year: no per-user charges, no feature tiers, and unlimited staff accounts, so encouraging staff to report costs you nothing. If you are switching mid-contract, our pay-for-one promise means you never pay for two systems at once.

You can explore the full feature set, or read our comparisons with CPOMS and MyConcern if you are weighing specific alternatives.

Frequently Asked Questions

Does KCSIE require schools to use safeguarding software?

No. KCSIE does not mandate any particular system or require software at all. It expects concerns to be recorded, responded to, and evidenced. Most schools find dedicated software the most reliable way to meet that expectation, but the guidance is about the outcome, not the tool.

What is the difference between safeguarding software and filtering and monitoring?

Filtering and monitoring controls and observes what happens on school devices and networks. Safeguarding software of the kind described here is your system of record for concerns about children, wherever those concerns originate. KCSIE 2026 places clearer accountability on filtering and monitoring reviews, but the two remain separate products solving different problems. We cover this in our KCSIE 2026 guide.

How long does it take to move to a new system?

It depends mainly on how much historical data you migrate and how clean it is. Schools commonly time a change for the start of an academic year or the beginning of a term. Ask any supplier what they handle on your behalf.

Can safeguarding software make us Ofsted or KCSIE compliant?

No supplier can make that promise honestly. Compliance rests on your policies, culture, training and professional judgement. What good software does is make your practice demonstrable — capturing decisions, dates, actions and review cycles so the evidence exists when an inspector, an auditor or a serious case review asks for it.

Is AI in safeguarding software safe to use?

It depends entirely on how it is applied. Signal's approach is that AI supports professional judgement and never replaces it: it surfaces patterns, drafts documents and suggests policy-grounded next steps, all of which a human reviews before anything is actioned. Ask any vendor offering AI features what data it is trained on, whether your data is used to train models, and where a human sits in the decision.

Next Steps

If you are early in the process, the most useful thing you can do is write down the three things your current arrangement makes hardest — then ask every supplier to show you those three things specifically.

If Signal looks like it might fit, you can start a free demo with populated data and explore it without a sales call, or contact our team with the questions your school needs answered.