Safeguarding induction for new staff at an international school

Every August an international school takes in a group of teachers who have never worked together and, in many cases, have never worked in the same education system. In the international schools I have worked in and evaluated since 2008, an incoming cohort routinely holds passports from six or more countries, and each of those countries taught them a different version of what safeguarding means. Safeguarding induction for new staff has to close that gap in the first week, before a child says something in a corridor and the adult who hears it decides what to do on instinct. A teacher who trained in England will look for a designated lead and a written record. A teacher who trained in a system with a direct duty to notify the police may go straight to the police. A teacher who trained in a system with no reporting duty at all may treat the conversation as private.

The differences run past law into habit. Some staff have written a concern record before and some have never seen one. Some have worked in schools where raising a doubt about a colleague was read as disloyalty, and they carry that caution into the new building. While I was coordinating CIS accreditation at Miras International School in Astana, staff joined the school from Kazakh state schools, from British and American systems, and from schools across the region, and each group arrived with its own answer to the question of who a concern belongs to. Induction is the one moment in the year when a school can set a single answer that every adult hears at the same time.

That single answer has to be the school's own. A generic module can explain what abuse looks like, and it cannot tell a new teacher which named person to walk to at three in the afternoon on their second day. The distance between general awareness and local procedure is where induction does its work.

A first week is short and every department wants a piece of it. Safeguarding induction usually has two hours at most, competing with timetables, payroll forms, a fire drill and a campus tour. The test I apply to the agenda is whether a new teacher leaving the room can name the Designated Safeguarding Lead, describe the reporting route without looking it up, and say what they would do if a student spoke to them at the end of a lesson. Content that does not serve one of those three answers belongs later in the year.

• Who the Designated Safeguarding Lead is, what they look like, and where their office is. A name on a poster carries less than a face in the room, so the DSL should deliver part of the session in person.
• The reporting route, walked once from end to end: what a member of staff does in the first ten minutes, what they write down, where that record goes, and who confirms receipt.
• The staff code of conduct, with attention to the clauses that differ from the country the new teacher came from: physical contact, transport, one-to-one tuition, photographs, and messaging students on personal accounts.
• Low-level concerns about adults: what counts as one, who receives them, and the school's undertaking that a member of staff who raises one in good faith is protected.
• Online safety as it touches staff conduct and the platforms this school actually runs, named rather than described in general terms.
• The local reporting context: which local agency the school notifies, in which circumstances, and who decides. Staff need the boundary of their own role, and the DSL needs to own the decision.
• Where the safeguarding and child protection policy lives, in which languages, and how to search it at eight in the morning on a Monday.

Seven items look like a lot for a session that also has to cover fire assembly points. They fit because most of them ask for recognition rather than mastery. A new teacher does not need to run a multi-agency meeting in September. They need to recognise the moment when the policy applies, take the first step correctly, and hand the decision to the person who is trained to make it.

Schools lose induction by trying to teach everything inside it. The material that can wait is the material a member of staff will apply through the DSL rather than alone: detailed indicators of specific forms of harm, the thresholds a local agency applies, records management, and any specialist content tied to a role the new teacher has not taken on yet. Trip leaders need trip safeguarding before the first trip and residential staff need boarding content before the first night on duty, and neither of those belongs in a general week-one session.

Deferring content honestly beats compressing it dishonestly. A school that lists nine topics on an induction agenda and gives each one four minutes will produce a record showing nine topics covered and staff who remember two. I would rather see a short, specific first week followed by a second session in October, with the October date already in the calendar before the first session ends. Scenario-based safeguarding training written from your own policy belongs in that second session, once staff know the route they are practising.

The October session also solves a problem August cannot. In August a new teacher has no students yet, so every scenario stays hypothetical. By half term they have a class, a tutor group and one or two children they are already slightly worried about, and the same material lands somewhere. A school that runs everything in the first week is training people at the moment they have the least to attach it to.

In most international schools outside the English-speaking world, the teaching staff work in English and a substantial part of the adult community does not. Teaching assistants, nurses, drivers, security staff, catering staff and administrators often hold the school together in the local language. An induction delivered only in English trains part of the building and leaves the rest with a translated handout and a signature.

A translated slide deck is a start and rarely enough on its own. The reporting route contains terms that carry weight in the local legal system, and several of them have no clean English equivalent, so a literal translation can shift the meaning of a duty. The practical fix is a short glossary agreed between the DSL and a senior colleague who works in the local language, fixed before the session and then used consistently in the policy, the training and the concern form. The same pair should deliver the session together, so that questions asked in either language reach the person who can answer them. Safeguarding training in the languages your staff speak covers the difference between translating a module and localising it.

Timing carries a message of its own. Running the local-language session two weeks after the English one tells staff where they sit in the order of importance, and they read that accurately. Where a school cannot run both on the same day, it should run the local-language session first, in the week the site teams come back, since drivers, cleaners and catering staff are usually on campus before the teaching staff arrive.

CIS and COBIS evaluators, and BSO inspectors working to the Department for Education standards for British schools overseas, tend to ask the same question about induction in different words: show me that this member of staff, who started on this date, was trained on the policy that was in force at the time. An attendance sheet with a date on it answers half of that question. The other half is the version of the content behind the session.

A defensible induction record holds the name of the member of staff, their start date, the date of the session, the topics covered, the language it was delivered in, the version of the safeguarding policy the content was drawn from, and the acknowledgement the member of staff signed. Safeguarding training records that inspectors and evaluators ask to see goes through the rest of the file in more detail.

The hardest case is the teacher who starts in January. August induction runs once, the cohort is large enough to justify a room and a session, and mid-year joiners then arrive alone into a school that has moved on. A school that has planned for this keeps a standing induction package that one person can complete with the DSL in an hour, in any week of the year, and it keeps the same record for that person as for the August cohort. When an evaluator samples staff files, the January starter is the file they open.

I built SafeguardIS because the induction problem at my own school had no tool behind it. The training is generated from the school's own safeguarding and child protection policies, so what a new teacher learns in week one is what that school actually does, down to the name of the person they report to. 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 content is hashed and logged, so the record shows which version of the material a January starter completed.

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 is what a new teacher in week two usually needs. The DSL keeps every safeguarding decision, and no child's details belong in a chat window. Certificates are countersigned by the Head of School and the DSL and carry a code anyone can check on a public verification page. Miras International School in Astana is the pilot school.

If you want to see what a first week looks like when the induction is built from your own policy, book a 20-minute walkthrough and bring your current induction agenda.