Safeguarding and child protection training principles for 2026

For several years I watched safeguarding and child protection training arrive in the same shape every August. A module opened, staff worked through it in a free period, the completion figure climbed towards a hundred per cent, and the school filed the report. By the third year the same people were meeting the same questions, and several of them told me plainly that they were remembering last year's answers rather than the content. The number in the report was accurate. It described attendance, and attendance is not capability.

I noticed this most clearly during accreditation work. As CIS accreditation coordinator at my school in Astana I had to assemble the safeguarding evidence, and the training file was the thinnest part of it. It could prove who had sat down in front of a course. It could not show that a swimming coach knew which of the two deputy heads to find on a Saturday, or that a bus driver had ever been told what to do about a child who would not get off the bus at the last stop. The training was real and the record was tidy. The link between them and daily practice was missing.

The five principles below come out of that gap. They are not a standard and they carry no authority of their own. They are what I would check if a Head asked me to look at a school's safeguarding training programme before an inspection or an accreditation visit.

The first principle is that the training should teach the document the school is actually held to. Most commercial modules are written to a jurisdiction. Keeping children safe in education sets the legal duties for schools and colleges in England, and Working together to safeguard children sets the multi-agency expectations behind it. Both are strong sources. Neither one names your deputy DSL, your out-of-hours number, your local referral body, or the form your staff have to complete before they go home.

When a module and a policy disagree, staff follow the module, because the module is what they were tested on. I have seen a teacher describe a reporting route confidently and accurately, and then discover it was the route from the course rather than the route in the school's own child protection policy. Nobody had done anything careless. The school had simply taught two procedures and only written one of them down.

The practical response is to write the training from the policy, sentence by sentence, and to treat any point the training makes that the policy does not support as a defect in one of the two. That comparison is uncomfortable the first time. It is also the fastest policy review a school will ever get, and it is the difference between generic safeguarding e-learning and school-specific training.

Schools tend to train teachers thoroughly and everyone else lightly, because teachers are easy to timetable and easy to count. The adults who see children in the least supervised parts of the day are usually the ones who received the shortest briefing. A nurse hears things in the medical room that no teacher hears. A security guard on the gate sees who arrives and who waits outside. A cleaner is in a corridor after everybody else has gone home.

Role-specific training does not mean five separate courses. It means one shared foundation, covering the categories of harm, the reporting route, the recording standard and the confidentiality rules, and then a short section that changes with the job. The bus driver gets the transport scenarios. The boarding staff get the eleven o'clock scenarios. Trip leaders get the ones about a hotel corridor in another country.

This also fixes a quiet compliance problem. When a school runs a single course for everyone, the content drifts towards the average member of staff, and the people furthest from that average learn least. Safeguarding training for drivers, security, catering and nursing staff is usually the weakest part of the programme and the easiest to strengthen.

Most safeguarding assessments test recognition. A question lists four categories of abuse and asks which one matches a short description, and almost everybody gets it right. The decisions that go wrong in schools are rarely definitional. They are decisions about threshold, timing and who to tell, made by one adult with incomplete information and eight minutes before the next lesson.

Training that changes practice puts staff inside that situation. A child says something ambiguous at the end of a lesson and then leaves. A colleague asks you to keep something between the two of you. A parent tells you at pick-up that a member of staff has been messaging their child. Each of these has a correct next step in the school's policy, and each one is a genuine test of whether the member of staff can find it under pressure.

Feedback matters as much as the scenario. When a member of staff chooses the wrong route, the explanation should quote the school's own wording and say what would have happened next. That is how a scenario becomes a rehearsal rather than a quiz, and it is why I favour scenarios written from the school's own policy over stock case studies from another country.

In an international school a significant part of the staff body works in a second or third language. Teaching staff usually manage English comfortably. Drivers, kitchen staff, maintenance teams, security and some administrative staff often do not, and they are precisely the group whose training was shortest to begin with.

A member of staff who half understands a reporting instruction will usually do the safe social thing, which is to tell a colleague and wait. That is a delay introduced by the training, not by the person. I treat language as an operational control rather than a courtesy, in the same category as knowing where the file is kept and who holds the on-call phone.

Translation on its own is not enough. Role titles, legal terms and referral routes have to be rendered in the words the local system actually uses, which is why training in the languages your staff speak is a localisation problem rather than a translation problem.

Evaluators and inspectors rarely ask whether staff were trained. They ask what the staff were trained on, who approved it, when, and what happened to the people who did not complete it. A completion spreadsheet answers none of those questions.

A defensible training record ties each completion to a version of the material, and each version of the material to a named person who reviewed it and to the policy documents it came from. It shows the date, the language the member of staff took it in, the questions they answered, and the follow-up for anyone who fell short. It survives a change of DSL, because it does not live in one person's memory.

• The version of the training each member of staff completed, and the date.
• The source policies that version was built from, with their own version dates.
• The named reviewer who approved it before publication, and the declaration they signed.
• The language each member of staff worked in.
• The follow-up action for anyone who did not complete or did not pass.

Take last year's safeguarding training and read it next to your current child protection policy. Mark every instruction in the training that the policy does not support, and every duty in the policy that the training never mentions. That list is your agenda. It is usually shorter than leaders expect and more specific than a general review would produce.

Then look at the record rather than the content. If you cannot say which version of the training a particular teaching assistant completed, in which language, and who approved that version, the record is not yet ready for a visit. What inspectors and evaluators ask to see in training records is a narrow list, and a school can close most of it in a term.

I built SafeguardIS because my own school needed the loop above and nothing available did it. Training is generated 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 any member of staff sees it: publishing requires a named reviewer's declaration, and the approved content is hashed and logged so the version behind each completion stays identifiable. Certificates are countersigned by the Head of School and the DSL and carry a code anyone can check on a public verification page.

The platform ships training 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. A policy audit feature checks a school's documents against ITFCP-aligned expectations and produces an action plan, and I run live workshops in English and Russian and lead whole-school safeguarding audits on request.

I have worked in international education since 2008, as an IB and MYP teacher, an IB DP economics teacher, an IB and CIS evaluator and workshop leader, and most recently as CIS accreditation coordinator. I am not a Designated Safeguarding Lead, and the platform is built so that the DSL keeps every safeguarding decision. If you want to see how the review and evidence trail works on your own policy, book a 20-minute walkthrough.