Multilingual safeguarding training in the languages staff speak

Walk through an international school in Astana, Almaty, Dubai or Istanbul on a normal Tuesday and count the languages in use. The teaching staff work in English. The drivers who collect students at seven in the morning speak Russian or Kazakh. The cleaners who move through classrooms after the last lesson, the security officers at the gate, the catering team and the school nurse mostly do the same. Local teaching staff switch into English for lessons and back into their first language in the staff room, and their fastest, least filtered thinking happens in the second one.

That school will usually buy one safeguarding course in English and assign it to everybody. The completion report comes back at ninety-something per cent, and the file looks complete. Multilingual safeguarding training exists to close the gap that report hides, because a driver who ticked through an English module has not been trained; he has been recorded. I have sat with staff in Astana who completed a course in English and could not, ten minutes later, say who they would tell if a child said something worrying on the bus.

Translation moves words across a language boundary and keeps the source intact. That is exactly the wrong instinct here, because a safeguarding module is mostly procedure, and the procedure is what changes at the boundary. A faithful Russian rendering of a British module tells a Kazakhstani driver to contact a local authority designated officer, describes thresholds set by English statutory guidance, and gives him a helpline number that does not connect. He now has accurate information about a country he does not work in, expressed in a language he understands.

Localisation starts from the school's own policy and produces the module in each language as a first-class version rather than a derivative. The reporting route in the Russian version names the person who actually receives concerns at that school, the channel that person actually monitors, and the timeframe the policy actually sets. The examples happen on that campus, in the bus bay and the nurse's office rather than in a leisure centre in Manchester. The legal frame is the local one, with the school's international standards sitting alongside it rather than replacing it.

UNESCO makes the underlying point about children rather than staff: its summary of multilingual education reports that around forty per cent of learners worldwide are not taught in a language they speak at home, and that learning in a language you understand well produces better comprehension. Adults are not exempt from that finding. A safeguarding module asks staff to absorb unfamiliar concepts, hold a procedure in memory for months, and act on it under stress, which is a harder cognitive task than most of what they read at work.

In the bilingual reviews I have run, the same handful of terms cause trouble every time. None of them is a translator error in the ordinary sense. Each one is a case where the English word carries a legal and cultural history that the target language has not built.

• Safeguarding. Russian and Kazakh have no settled single word for the broad English duty that covers noticing, preventing and promoting welfare. Translators reasonably reach for the phrase used for child protection, which narrows a wide obligation into a narrow one about responding to abuse.
• Disclosure. Rendered literally, the word lands closer to confession or revelation, which suggests a formal statement rather than the fragment a nine-year-old lets slip while packing a bag. Staff then wait for a formal statement that never comes.
• Concern. In several languages the nearest word implies certainty or accusation, so staff hold back until they are sure. The English term deliberately covers unease without evidence, and the target-language version has to say so explicitly.
• Low-level concern. This one has no equivalent at all, because it names a category invented by English statutory guidance for behaviour by adults that is inappropriate without being abusive. The translated module has to define it before it can use it.
• Reporting. In hierarchical workplaces the ordinary word for reporting carries the sense of informing on a colleague. A version that uses it without qualification tells staff, accurately in their own idiom, that the school is asking them to inform on each other.
• Consent, boundary and duty of care. Each maps onto local legal vocabulary that already has a fixed meaning, and the fixed meaning is usually narrower than the safeguarding one.

The method that works is a short pipeline with two named people at the end of it, and it is worth writing down before the first module is drafted. Start from the school's current child protection and safeguarding policies rather than from an English course, so that every language version has the same parent document. Draft the module in the language of the policy, then produce each additional language from that draft with the reporting route, the names, the channels and the examples rewritten rather than converted.

The Designated Safeguarding Lead reviews every version for procedure. The DSL does not need to read Kazakh to do this; the reviewer reads the route back to them in English, and the DSL confirms that it matches what the school does. The bilingual reviewer, who should be a member of staff who works in that language daily rather than an external translator, checks three things: that the terms above carry the intended meaning, that the register is right for the audience, and that the examples are plausible on this campus. A driver reviewing the driver-facing module catches problems that no language professional will.

Two practical rules save most of the rework. Fix the glossary before the drafting, so the term chosen for concern is the same term in the module, the poster, the induction slide and the reporting form. And re-review whenever the policy changes, because a policy revision that reaches only the English version quietly puts the school in the position of having taught two different procedures. The same discipline applies to the induction pack, which is covered in more detail in safeguarding induction for new staff at an international school.

A completion record proves that a person reached the end of a module. An evaluator or inspector who is doing their job will ask a different question, which is whether that person can act. The difference matters more in a multilingual school than anywhere else, because completion in a second language is the specific record most likely to overstate what happened.

Comprehension is testable without turning training into an examination. Ask staff to write the reporting route in their own words in their own language, and compare the answers across a department; three different routes in six answers is a finding. Use free-text scenario responses rather than multiple choice, because a driver who selects the right option from four may still not produce the right action from a blank page. Record the language each member of staff completed the module in, and hold that field on the certificate, so the record states what was actually taught rather than what was assigned. Run a short spoken check during appraisal for staff who do not write comfortably in any of the school's written languages, and log the outcome.

Written scenarios drawn from the school's own policy carry most of this weight, and they are the part staff remember months later. The design of those scenarios is worth its own attention, and scenario-based safeguarding training written from your own policy sets out how to build them. For non-teaching teams the scenario set has to change as well as the language, which is the argument in safeguarding training for drivers, security, catering and nursing staff.

The first change a school usually sees is in the concerns log. Non-teaching staff start appearing as reporters, often within a term, because the route stopped being a sentence in a language they read slowly and became a sentence they could repeat. The second change is in the questions the DSL receives. Staff who train in their own language ask more questions and ask them earlier, and the questions are more specific, which is a reasonable proxy for comprehension.

The third change is slower and shows up at accreditation. A school that can produce a training record stating the language of delivery, a named reviewer for each language version, and scenario responses written by staff in their own words has answered the question an evaluator is actually asking. The Council of International Schools runs its child protection workshops on the premise that international schools have to interpret differing cultural attitudes and laws rather than import a single national model, and the ICMEC Education Portal publishes country-specific summaries of child protection law for the same reason. A school that trains only in English is skipping the interpretation step and hoping nobody notices.

For schools working under Kazakhstani law specifically, the interaction between local reporting duties and international standards deserves its own treatment, and I have set it out in safeguarding in Kazakhstan's international schools.

SafeguardIS builds training from the school's own safeguarding and child protection policies, so every language version descends from the same document and states the same route. The platform ships training in English, Russian and Kazakh today. The Designated Safeguarding Lead reviews and approves every module before staff see it; publishing requires a named reviewer's declaration, and the approved content is hashed and logged, so the school can show later exactly which version a member of staff was taught. Certificates are countersigned by the Head of School and the DSL and carry a code anyone can check on a public verification page.

Staff can also ask the AI policy assistant questions that are answered from the school's own policies, which gives a member of staff who is unsure about a term a way to check it without asking a senior colleague in a second language. The DSL keeps every safeguarding decision, and no child's details belong in a chat window. 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 as well as whole-school safeguarding audits. Miras International School in Astana is the pilot school. 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.

If you want to see how the same module reads in English, Russian and Kazakh side by side, book a 20-minute walkthrough and bring your child protection policy.