Choosing safeguarding training software for international schools

Safeguarding training software for international schools is usually bought in a hurry, in the term before an accreditation visit, by a business manager comparing three quotes with a Head who wants the problem to go away. That is a reasonable way to buy a payroll system. It works badly here, because the thing being bought is not really a course library. It is the evidence that every adult on the campus knows what this school expects of them.

The test an evaluator applies is simple and it does not involve the software at all. They read the school's child protection policy, then ask three members of staff what they would do. If the answers match the policy, the school is in good shape. If the answers come from a module written for another country, the school has bought completion and not practice. So the buying question is narrow: does this system teach what the school's policy says, in the languages the staff read, and can it prove afterwards who learned it and who approved it? I have set out that distinction in generic safeguarding e-learning against school-specific training.

Everything below is vendor-neutral until the last section, where I describe what I have built, so you can discount it accordingly.

Start here, because content decides whether anything else matters. Ask the supplier to open the demo by uploading your own child protection policy rather than by showing a catalogue. What comes out tells you most of what you need.

• Does the training come from the school's policies, or from a library written for another jurisdiction?
• When the policy changes in November, what happens to the module, and who is told?
• Who approves content before staff see it, and is that approval recorded with a name and a date?
• Can the designated safeguarding lead edit a module, or only accept or reject it?
• Does the system keep the version a member of staff actually completed, or only the current version?
• Where does the scenario content come from, and can the DSL replace a scenario that does not fit this campus?

In an international school the teaching body works in English and a large part of the adult community does not. Drivers, security officers, kitchen and cleaning teams, nurses, coaches and administrative staff are often the adults a child meets first in the morning, and they are the group most likely to be handed an English module and a completion tick. Ask which languages the platform ships, and then ask the harder question: who checked the translation against the school's procedure, and what is their name?

Machine translation of a safeguarding module produces fluent text and unreliable meaning, because the vocabulary does not transfer cleanly. The word safeguarding has no settled single equivalent in Russian or Kazakh, and the nearest legal phrase is narrower than the practice the standards describe. A supplier who says the platform supports forty languages is describing an interface. Ask instead whether a bilingual person who understands the reporting route reviewed the training itself, and whether the school can appoint that reviewer.

On the morning of a visit, someone will ask for the training record of a named member of staff. The good version of that moment takes ninety seconds and produces a single page. Work out during the demo whether the system can produce it, and export the result so you can read it outside the platform.

• Who completed which module, on what date, in which language, and against which version of the policy.
• Who approved that module, when, and what declaration they signed.
• Which staff are outstanding, grouped by role rather than by an alphabetical list.
• A certificate that names the school, the module, the date and the version, and that a third party can verify.
• An export in a format the school can keep after the contract ends.

A certificate is worth exactly as much as the signature on it. Ask who countersigns: a platform logo proves that a supplier ran a quiz, while the head of school and the designated safeguarding lead countersigning proves the school stands behind the content. Ask whether anyone outside the school can check that a certificate is genuine without emailing the office. I have written about what belongs on one in what a safeguarding training certificate should prove, and about the wider record set in the training records inspectors and evaluators ask to see.

Data comes next, and it is the question schools skip because it feels like the lawyer's job. Ask in which country the database sits, which subprocessors touch the data, what is deleted at the end of the contract, within what period, and what evidence of deletion the school receives. Schools in Kazakhstan have a specific answer to check against, because national law requires personal data to be stored in a database located in the country. Get the position in writing before signing, not after.

If the platform has AI features, ask seven things: whether anyone trains models on school content, which model provider processes the text, in which country, what identifying detail is removed before text reaches a model, whether every generation is logged with the person who ran it, whether content can publish without a named human approving it, and what the tool does when a member of staff types a child's name. The last one is a live test you can run in the demo. I have set out the full rule set in what to allow and refuse when AI touches safeguarding training.

Per-seat pricing quietly changes safeguarding decisions. A Head with a seat budget starts choosing which adults get trained, and the adults dropped are the cleaners, the drivers, the coaches and the seasonal staff, which is to say the people with the least supervision and the most unstructured contact with children. Pricing for the whole school removes that conversation. Ask whether volunteers, contractors, board members and new starters mid-year cost extra, and get the answer as a number.

On pilot terms, three clauses matter. The pilot should run without a multi-year commitment attached, the school should own and be able to export everything it creates during the pilot, and the supplier should delete the pilot data on request with written confirmation. A supplier who cannot agree to those three has told you how the relationship will feel in year two.

Some signals are reliable enough to end a conversation early.

• The demo opens a course catalogue and never opens the school's own policy.
• Nobody can name who approves content before staff see it.
• The supplier answers data questions with a compliance badge or names a certification without producing a scope or a certificate.
• There is no answer on where the database is hosted.
• Certificates carry no countersignature and no way for an outsider to verify them.
• The pilot requires a twelve-month contract before it starts.
• AI features have no logging and no named approver.
• The pricing rises with every driver, cleaner or volunteer the school trains.

A month is enough to answer the real question, provided the pilot is narrow. Week one: give the supplier one document, the child protection policy currently in force, and one staff group, ideally the non-teaching team. Ask for a draft module and note how long it took and how much of the school's own wording survived. Week two: the designated safeguarding lead reviews and edits, and the school counts the edits. A draft that needs rewriting from scratch is a content library in a new interface.

Week three: assign the approved module to between fifteen and twenty-five people, including at least five who do not teach and at least three who work mainly in another language. Watch who can sign in unaided, because that is where platforms fail in practice. Week four: run the evidence test described above, export everything, and open the export outside the platform. On day thirty ask the supplier to delete the pilot data and send confirmation, then put one question to the designated safeguarding lead: would you defend this module in front of an evaluator? A yes with reservations is a good outcome, and the reservations are the negotiation.

SafeguardIS builds training from the school's own safeguarding and child protection policies, so what staff learn is what that school actually does. The designated safeguarding lead reviews and approves every module before staff see it, publishing requires a named reviewer's declaration, and the content is hashed and logged so the school can later show which version a member of staff completed and who approved it. Certificates are countersigned by the head of school and the designated safeguarding lead and carry a code anyone can check on a public verification page. Training ships in English, Russian and Kazakh today. If your staff work in a language the platform does not ship yet, I build that language in for your school as part of the pilot.

Staff can ask an AI policy assistant questions that are answered from the school's own policies. The designated safeguarding lead keeps every safeguarding decision, and no child's details belong in a chat window. A policy audit feature checks the school's documents against ITFCP-aligned expectations and produces an action plan, and I run live workshops in English and Russian as well as whole-school safeguarding audits. Miras International School in Astana is the pilot school. Run the thirty-day plan above against it, or book a 20-minute walkthrough and put the questions to me directly.