Scenario-based safeguarding training written from your own policy

Scenario-based safeguarding training places a member of staff inside a situation that could happen on their campus this term, and asks them to decide what to do next. Most of the design work sits in the answer key rather than in the story. If the correct response comes from a course written for another country, staff rehearse a procedure their school does not use, and the rehearsal teaches them a reflex they will have to unlearn. If the correct response comes from the school's own child protection policy, they rehearse the route they will actually take when a child speaks to them in a corridor.

I have worked in international education since 2008, as an IB and MYP teacher and later as CIS accreditation coordinator at Miras International School in Astana. Over those years I watched safeguarding modules repeat almost unchanged from one year to the next. Staff recognised the questions from the previous cycle and finished them in a few minutes. Recognition is a weak form of learning. A scenario written from the school's own policy is harder to complete from memory, because the decision points ask for that school's named people, its forms and its deadlines.

Building scenarios takes longer than buying them. A school needs a current policy, someone who can read that policy as a procedure rather than as a statement of values, and a Designated Safeguarding Lead willing to say what the correct answer is where the wording leaves room. That last conversation is often the most useful part of the work. Ambiguity found while writing a scenario is ambiguity removed before a real disclosure.

A first set of scenarios should not begin with the categories of abuse. It should begin with the parts of the school's own procedure that people misapply. When I ask a Designated Safeguarding Lead which steps go wrong, the same answers come back: staff tell a colleague instead of the DSL, staff promise a child that the conversation will stay between them, staff write the record two days later from memory, and staff ask a few questions of their own because they want to be sure before they report.

Read the policy looking for verbs and deadlines rather than principles. Who receives a concern. In what form. By when. What happens if that person is on a flight. What a member of staff must not do, stated plainly. Those sentences are the raw material, and a school usually has fewer of them than it thinks. A policy of thirty pages may contain a dozen sentences that decide a real case.

Keep a scenario when the policy contains a sentence that settles it. When the honest answer is that it depends on who you ask, send that one back to the leadership team as a policy question instead of writing it into training. A school that publishes a scenario with a contested answer teaches its staff that the procedure is negotiable, which is the opposite of what the training is for.

The four situations below come up in almost every international school I have worked with, and each one lands on a member of staff who is unlikely to be in the room for a standard teacher training session. Write them for the people they actually happen to, in the language those people speak at work.

• A disclosure on the bus home. A Year 5 student tells the driver, in Russian, that her older brother hits her when their parents travel. The driver has little English and no school email account. The decision point asks who he tells, how quickly, and what happens if the DSL is already off site.
• A parent at the gate. A father asks the receptionist to confirm which club his daughter attends and what time she finishes. The student file records a court order about contact. The decision point asks what the receptionist may say at the desk, who she calls first, and what she writes down afterwards.
• A message at ten in the evening. A Year 9 student sends a teacher a photograph and a message on a personal social account, apologising and asking her to keep it private. The decision point asks what the teacher does with the message, what she replies, and which staff conduct rule applies to the channel itself.
• A colleague at the pool. A swimming coach keeps one student behind after every session and drives her home. Another coach notices the pattern. The decision point asks whether this belongs in the low-level concerns process or is an allegation against an adult, who receives it, and why it does not go to the coach's line manager first.

A decision point is a question with one defensible answer in that school and at least two plausible wrong ones. Plausibility carries the weight here. If the wrong options are obviously wrong, staff select the right one without reading the scenario, and the module records a pass that proves nothing. The distractors should be the things people really do: tell the class teacher because she knows the family, reassure the child that nobody else will hear about it, ring the mother to check, or wait until Monday because it is late on a Friday.

Write the correct answer with the policy open beside you, and make the feedback quote the school's own sentence. Feedback that says a concern should be reported promptly teaches nothing. Feedback that says the concern goes to the named DSL before the end of the same school day, on the concern form in the staff portal, and that the member of staff does not contact the family, gives the reader something to repeat under pressure.

Two constraints keep the set honest. Each scenario stops at the point where the member of staff hands the case on, because the decisions after that belong to the DSL and to the local authorities. And each scenario names a real object in the school: the form, the portal, the office, the person. Generic wording is how a school-specific scenario slowly turns back into a generic one across successive edits.

Where a school runs in more than one language, write the decision point in the language the reader works in rather than translating an English original at the end. A bus driver deciding what to do in Russian needs the Russian wording of the procedure, and translation after the fact often loses the part that carries the obligation. Staff who read the module in their working language also read the policy in it, which is where training in the languages your staff speak stops being a courtesy and becomes part of the control.

Multiple choice can test recall of a name or a deadline, and that is worth testing. It handles judgement poorly, because the options carry the thinking. Two other formats do more work for the same amount of staff time. The first asks each member of staff to write three or four sentences saying what they would put in the record and who they would send it to. The second gives five steps out of order and asks the reader to sequence them, which exposes people who would report but would speak to the family first.

Written answers need a reader, and that reader should be the DSL or a deputy. Sampling is enough. A DSL who reads twenty answers out of a hundred learns more about the school's safeguarding culture than any completion percentage will tell them, and the weak answers usually cluster in one team, one campus or one shift. That pattern is the finding, and it is more useful than the score.

Set the pass condition on the step that matters. A member of staff who names the right person but the wrong deadline needs a correction. A member of staff who does not report at all needs to retake the module, and the retake should use a different scenario, because repeating the same one teaches the answer rather than the procedure. Keep the attempts, the date and the version of the material, because what inspectors and evaluators ask to see is the record behind the completion, not the completion itself.

Scenario sets rot quietly. The reporting form moves to a new portal, a deputy DSL leaves in December, the school changes bus contractor, a boarding house opens, and the module keeps teaching last year's route. Stamping every module with the policy version and date it was written from makes the drift visible. When the policy is republished, the school can see which modules were built on the superseded text.

Not every change requires the whole staff to retrain. A new deputy DSL changes a name in three scenarios and needs a short notice rather than a course. A change to the reporting route changes the correct answer, so the affected groups repeat the affected scenarios. Statutory revisions matter too: the Department for Education publishes a new edition of Keeping children safe in education each September, and schools that align with it should check which of their scenarios still match the current wording. What that means outside England is a separate question, covered in KCSIE for international schools.

Keep the superseded versions rather than overwriting them. When an evaluator asks what a member of staff was trained on in March, the school needs the March material, not the current one. This is also what makes an annual refresher worth running: the refresher can carry the scenarios that changed, and staff notice that the content moved because their school moved.

SafeguardIS builds training from the school's own safeguarding and child protection policies, so the correct answer inside a scenario is the school's actual procedure rather than a generic one. 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 a school can show later which version of the material a member of staff worked through.

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. Staff can also ask the AI policy assistant questions that are answered from the school's own policies, which helps a driver or a receptionist check a step without waiting for a meeting. The DSL keeps every safeguarding decision, and no child's details belong in a chat window. Miras International School in Astana is the pilot school.

A policy audit feature checks a school's documents against ITFCP-aligned expectations and produces an action plan, which is usually where a scenario set starts, because the gaps in the policy are the scenarios nobody can answer yet. I also run live workshops in English and Russian and whole-school safeguarding audits. If you want to see how a scenario is written from a real policy clause, book a 20-minute walkthrough.