Annual safeguarding refresher training: why repeats fail

The first clear evidence I had that annual safeguarding refresher training had stopped working came from watching staff complete it. The module was a commercial course written for another jurisdiction, and it arrived every September in the same form, with the same questions in the same order. By the second year the staff had a routine. They opened last year's answers, matched the questions, and finished a forty-minute course in about ten minutes. The completion report went green and the school could evidence that every member of staff had been trained that year.

I was coordinating CIS accreditation at the time, so part of my job was holding the evidence that this training existed. It existed. What it did not do was change what a teacher would do on a Wednesday afternoon when a Year 8 student said something odd about a weekend at home. Annual safeguarding refresher training is meant to close the distance between a completed record and a changed decision, and repetition on its own does not close it.

Nobody in that building was cynical about safeguarding. The staff were responding sensibly to a task that rewarded recall of definitions written for a country most of them had never worked in. The design of the module produced the shortcut, and the completion report produced the reassurance.

Four things happen when a school repeats a generic module every year. The content carries no new information after the first pass, so an experienced member of staff has nothing to learn from it. The procedures it teaches belong to another system, so a teacher following it exactly would be following the wrong route. The assessment tests recognition of definitions, which is the one thing a person can do from memory of last year. And the whole requirement sits in a single sitting in the week when everything else also lands.

The fifth problem is the one schools notice last. A school's safeguarding arrangements change over a year. The DSL changes, the concern form changes, a new messaging app appears in students' hands, and the local ministry issues something new. A module bought from a library cannot reflect any of that, so staff are refreshed on a version of the school that no longer exists. Generic safeguarding e-learning against school-specific training sets out that trade-off in more detail.

Five changes fix most of it, and none of them require a bigger budget than the licence the school is already paying for. Write the scenarios from your own building, version the content against the policy it teaches, split the hour across the year, write different versions for different roles, and assess the decision rather than the definition.

A scenario is school-specific when a member of staff can name the room it happens in. A student discloses to a teacher is a category. A Year 9 student stays behind after the last lesson in the science block, says her older brother has been hitting her, and asks the teacher not to tell anyone: that is a scenario, and it forces the decisions a teacher actually faces. What to say in the next thirty seconds, what promise not to make, what to write down, and who to walk to.

Every school already holds a stock of these, in the anonymised concerns the DSL has handled and the near misses nobody recorded. Building a year of refresher content around six of them, changed enough that no individual is identifiable, gives staff practice in the school's own route. Scenario-based safeguarding training written from your own policy covers how to source them and how to anonymise them properly.

A DSL will often resist this at first, for a sound reason. Anonymising a real concern well takes care: change the year group, the sex of the child, the subject and the time of year, and check that the member of staff who handled the original would not recognise it either. Once three or four scenarios exist in that form, they can carry a school for two or three years, because the same situation put to a nurse, a form tutor and a bus driver produces three different sets of decisions.

A refresher earns its hour when it carries something the member of staff did not know last year. The most reliable source of that something is the school's own policy. If the safeguarding and child protection policy was revised in June, the September refresher should open with what changed and why, in five minutes, before anything else.

That requires the training to be versioned the way the policy is versioned. Each module should record which version of which policy it was built from, who approved it, and on what date, so the school can answer the question an evaluator asks about a named member of staff: which version of the material did this person complete, and did it match the policy in force that term. When the policy changes mid-year, the school reissues the affected section instead of the whole course.

Most schools deliver the annual requirement as one sitting in the first weeks of term, because that is when it can be scheduled. The cost is that staff meet the material once, in the busiest fortnight of the year, and then not again for twelve months. Four fifteen-minute sessions spread across the year cover the same ground and put staff in contact with the reporting route four times instead of once.

Spacing also lets a school respond to its own year. A short session in November can take up whatever the DSL has actually been seeing since September. A session in February can follow a policy revision or a change of reporting form. Schools that already run a weekly staff briefing can carry a single scenario inside one of them without adding a meeting to anyone's calendar.

The one cost of spacing is administrative tidiness. Four short records across a year are harder to summarise than one annual completion figure, so the school needs a record that rolls the four together into a single annual position for each member of staff, with the dates and the module versions still visible underneath. Schools that skip that step tend to drift back to the single sitting within a year, because the reporting is easier to produce.

A secondary teacher, a primary teaching assistant, a school nurse, a bus driver and a member of the security team meet children in different places and need different first moves. One module written for all of them is written for none of them. The core stays constant, which is the DSL, the reporting route and the code of conduct, and the scenarios change with the role.

Writing five variants sounds like five times the work and rarely is. The policy content and the reporting route are shared across all of them, so what changes is the scenario set and the examples in the code of conduct section. A school that has already written six good scenarios can allocate two to each role group and reuse the frame around them.

The group that suffers most from a single version is the non-teaching staff, who usually receive the teachers' module in a language they read with difficulty, if they receive it at all. Safeguarding training for non-teaching staff sets out what drivers, security, catering and clinic staff need.

The assessment is where a refresher either holds or collapses. A question asking a member of staff to select the correct definition of neglect can be answered from last year's screenshot. A question that describes a situation in their own school and asks what they would do in the next ten minutes cannot, because the answer depends on this year's policy, this year's DSL and this year's concern form.

Application questions are harder to write and harder to mark automatically, which is why content libraries avoid them. A school writing its own can afford a smaller number of them. Six scenarios with a required written response, reviewed by the DSL on a sample basis, tell a Head more about staff readiness than forty multiple-choice questions with a pass mark of eighty per cent.

What the school does with the answers matters as much as the questions. When six teachers all say they would speak to the child's parents first, the DSL has learned something about the policy or about the way it was communicated, and that finding belongs in the report to the governing body next to the completion figures. If a year of refresher training generates no findings of that kind, the questions were probably too easy to tell anyone anything.

SafeguardIS builds training from the school's own safeguarding and child protection policies, so the scenarios, the reporting route and the named roles in a refresher come from that school rather than from a library. 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 a school can show which version of which module a member of staff completed and which policy version it was drawn from.

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, which is usually where a refresher rewrite starts, because the gaps in the policy become the topics for the year. I also run live workshops in English and Russian and whole-school safeguarding audits. Miras International School in Astana is the pilot school.

If the module your staff complete this September is the one they completed last September, book a 20-minute walkthrough and bring it with you.