Safeguarding training records: what inspectors ask to see

Most schools can produce safeguarding training records within a minute of being asked. The file usually looks the same everywhere: a spreadsheet of names, a course title, a date, and a column of ticks. It proves that people were present or that a platform registered a completion. An inspector or an accreditation evaluator is asking a different question, which is whether the adult in front of them knows what to do, and the tick tells them nothing about that.

I saw the difference during an accreditation visit at the school in Astana where I coordinated the process. The team had the training log in advance. What they did on site was walk into the kitchen and ask a member of the catering team who they would tell if a child said something worrying, and what would happen next. That question is the audit. The log only matters to the extent that it predicts the answer, and a log built from attendance predicts nothing.

Statutory guidance sets the frame without solving the problem. Keeping children safe in education 2026, which came into force on 1 September 2026, requires that all staff receive safeguarding and child protection training including online safety at induction, that the training is regularly updated, and that all staff receive safeguarding updates as required and at least annually. It does not prescribe a record format. That gap is where schools get into trouble, because a record designed for counting cannot answer a question about understanding.

A record is defensible when a stranger can reconstruct the whole event from it, years later, without asking anyone. That means naming the person, the material, the version of the policy behind the material, the assessment, and the human being who approved it. Keeping children safe in education notes that schools are free to record information beyond the statutory minimum on the single central record, and gives as examples the dates on which safeguarding and safer recruitment training was undertaken and the name of the person who carried out each check. Both of those examples point in the same direction, which is towards attribution.

• Who: full name, role, employment type, line manager, and the language the person works in.
• What: the module or session title, its version number, and its duration.
• Which policy: the exact version and approval date of the child protection policy the module taught.
• When: the completion date, and separately the date the person started at the school, so induction timing can be checked.
• Result: the assessment outcome, with the pass threshold and the number of attempts, rather than a completion flag.
• Who approved it: the named reviewer who confirmed the content matched the policy before staff took it.
• Certificate: an issued certificate with an identifier a third party can verify.
• Follow-up: any remedial action, retake, or coaching conversation, with its date and who held it.
• Language: which language version the person took, in a school working in more than one.

The single most useful change a school can make is to stop dating training against the academic year and start dating it against the policy. A row that says a teaching assistant completed child protection training in October 2025 is weak. A row that says she completed module version 3.1, built from child protection policy version 4.0 approved by governors on 12 September 2025, is strong, because the moment the policy moves to version 4.1 the school can see exactly who was trained on the superseded text.

That linkage also solves the reporting problem in a school with several campuses or a large local-hire staff body. When the reporting route changes, the school does not retrain everyone. It retrains the people whose last training pointed at the old route, and it can name them. Without the version link, the only safe option is to run the whole staff through the module again, which is how annual refresher training turns into an exercise staff learn to click through. The reasons repeats stop working are covered in why annual refresher training fails and what replaces it.

The same principle governs what the school hands the individual. A certificate that says only that somebody completed safeguarding training is a decorative document. One that names the policy version, the module version, the assessment result and the countersigning reviewers is a piece of evidence. I have set out that in detail in what a safeguarding training certificate should prove.

Keep one authoritative log, and treat everything else as a copy. Schools commonly run three parallel versions: an HR spreadsheet, the learning platform export, and the designated safeguarding lead's own tracker. During a visit those three disagree, and the disagreement itself becomes the finding. Decide which system is the record of truth, then make the other two read from it or stop maintaining them.

Keeping children safe in education allows the single central record to be kept in paper or electronic form, and the British Schools Overseas standards say the same about the staff register, provided the information can be reproduced in legible form. Electronic is easier to sample and easier to lose control of, so set the access rules explicitly. Training completion by role is ordinary management information. Assessment results and remedial actions are personal data about an employee, and they belong with the designated safeguarding lead and HR rather than in a shared folder. Prepare an anonymised or aggregated view for the parts of the log a visiting team will see in bulk, and keep the individual detail behind a person who can be asked for it.

One further practical point. Whatever system holds the log has to survive the departure of the person who built it. Ask whoever owns it to write down, on one page, where the data lives, who can export it, and how a new designated safeguarding lead would run the ten-name sample described in the safeguarding evidence checklist for an accreditation visit.

The August induction session is the strongest part of most schools' training year and it creates the weakest part of the record. Everybody who arrives in November, February or the week after Easter falls outside it. Keeping children safe in education is specific about what induction must cover: the child protection policy, the behaviour policy, the staff behaviour policy including low-level concerns, allegations against staff and whistleblowing, the safeguarding response to children absent from education, and the role and identity of the designated safeguarding lead and deputies, with copies of the policies and Part one of the guidance provided at induction. A member of staff who joins in February needs the same content, on a date the school can show, before they are alone with children. What that session should contain is set out in safeguarding induction for new staff at an international school.

Part-time and peripatetic staff are the second gap. The piano teacher who comes on Tuesdays, the swimming coach contracted through a club, the after-school Mandarin tutor and the exam invigilator all have unsupervised contact with children and none of them attend the whole-staff INSET. Record them on the same log as everyone else, with employment type as a field rather than as a separate spreadsheet, so a team sampling the staff list finds them where it expects to.

Contractors and volunteers need a proportionate record rather than the full staff module. Log the induction briefing they received, who gave it, the date, and the supervision arrangement that applies to them on site. The British Schools Overseas standards give one explicit interval in this territory: adults providing lodgings for pupils on the school's behalf must have undergone suitable safeguarding training at least every three years, kept updated, and must understand the school's policy on pupils going missing. For everyone else who works on campus without being employed by the school, the arrangements in safeguarding with visitors, contractors and volunteers on campus are worth setting before the term starts.

There is no single international retention period, and any vendor quoting one to you is quoting a jurisdiction rather than a rule. What the school controls is its own retention schedule, which should name safeguarding training records specifically instead of leaving them inside a general HR category. Write down the period, the reason for it, and the person who authorised it, and have the data protection lead and the designated safeguarding lead sign the same document.

Two considerations pull in opposite directions and both are legitimate. Keeping children safe in education says an individual's details should be removed from the single central record once they no longer work at the school, which argues for prompt deletion of the recruitment entry. Against that, an allegation about a period of employment can be raised long after the person has left, and the school may then need to show what that person was taught and when. Most schools resolve this by removing the leaver from the live register while retaining the underlying training evidence in a separate archive with a defined period and restricted access. Decide which you are doing, write it down, and apply it consistently rather than deleting by habit.

I built SafeguardIS because the training available to my school was written for another jurisdiction and the record it produced was a list of completions. The platform builds training from a school's own safeguarding and child protection policies, so the module a staff member takes teaches that school's reporting route. 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, which is what makes the policy-version link in a training record real rather than typed in by hand.

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, so an evaluator can confirm one without asking the school to vouch for it. 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 also put questions to an AI policy assistant that answers from the school's own policies; the designated safeguarding lead keeps every safeguarding decision, and no child's details belong in a chat window. Miras International School in Astana is the pilot school.

If your training log is currently a spreadsheet and you want to see what a version-linked record looks like, you can book a 20-minute walkthrough.