Mandatory reporting laws for international schools: local duties

An international school sits inside one country's legal system while employing staff trained in twenty others. Mandatory reporting laws for international schools are set by the host country, and they apply to the adults on that campus whatever framework the school has adopted for its own governance. A teacher recruited in Manchester arrives with a mental model built on English statutory guidance. A counsellor recruited in Ontario arrives with a different one. Neither model tells that adult who to telephone in the city where they now work, or how many hours they have to do it in.

The gap shows up in the same place every time. The policy describes reporting in general terms, the staff can name the DSL, and nobody can say what the law of the host country requires of them personally. The school has a framework, the host country has a duty, and bringing the two into one document that staff actually read is the work.

I have worked in international education since 2008, most recently as CIS accreditation coordinator at a school in Astana. Reading safeguarding policies from schools in several countries, the section that most often reads as though it were lifted from somewhere else is the reporting section, which is the one section that has to be local to be any use at all.

Mapping is a research task with a fixed set of questions, and it produces a single page. Ask a local lawyer or the host country child protection agency to answer them in writing, and put a date on the answers. Statutes are amended, agencies are reorganised, and a dated mapping document can be reviewed in an hour rather than rebuilt from nothing.

The ICMEC Education Portal publishes child protection legislation overviews for more than eighty countries, alongside guidance on background checks, incident response and reporting protocols. It answers the first pass for most host countries and gives the DSL the vocabulary to hold a useful conversation with a local lawyer. The portal grew out of the International Task Force on Child Protection, formed in 2014 and hosted by ICMEC, with the Executive Director of the Council of International Schools in the chair.

Treat that summary as a start. A document written for an international audience will not always carry an amendment passed last year, and it cannot tell a school which district office answers the telephone on a Saturday. Local confirmation closes the gap and costs one meeting. The wider expectations the task force sets for a school safeguarding programme are covered in the ITFCP child protection standards, which assume a school knows its local duty rather than replacing it. The mapping itself has to answer six questions.

• Who carries the duty: every adult, or a defined group such as teachers, doctors and social workers, and whether the school as an institution carries a duty separate from the individual.
• What triggers it: suspicion, reasonable belief, a disclosure by a child, or an observed injury, and whether the threshold is written in the statute or left to professional judgement.
• Who receives the report: which agency, which office, which telephone number, and what happens outside working hours and during school holidays.
• In what form and within what time: a call, a written form, an email, and whether the deadline is counted in hours or in days.
• What protection exists for the person reporting: immunity from civil or criminal liability, protection from dismissal, and whether a report can be made anonymously.
• What follows: who investigates, what the school may and may not do while an investigation runs, and what the school is told at the end of it.

Most conflicts are procedural rather than moral. A school framework may say the DSL decides whether a concern goes to an external agency, while the local statute places the duty on the individual who formed the suspicion, with a clock that starts at that moment. Both can be satisfied. Staff tell the DSL immediately, the DSL acts, and the policy states plainly that the individual duty under local law stays with the individual and is not discharged by telling somebody senior.

Harder cases exist. A local requirement may direct reports to an agency the school has reason to doubt, or a family may face consequences the school did not intend. A school does not resolve that by ignoring the law. It resolves it by taking local legal advice before a case arrives, by recording what advice it received and from whom, and by deciding in advance which board member is told when a case moves into that territory. The distance between an adopted framework such as KCSIE and what actually applies to a school outside England is worth working through in writing once, calmly, rather than at four in the afternoon during a live case.

One rule holds across every version of this. The international standard a school has adopted sets the floor for its own conduct, and it never lowers the duty the host country places on the adult. Where the two differ, the school follows both and writes down why. Almost every host country has ratified the UN Convention on the Rights of the Child, which gives a board a shared reference point when it has to explain a decision to a community that spans several legal traditions.

A reporting section that works fits on one page and answers five things in the order a worried adult asks them. What to do in the next ten minutes. Who to tell, by name and by mobile number. What to write down, and where that note goes. Who contacts the external agency, and by when. What to say to the child, and what never to promise them.

Names and numbers date quickly, which is an argument for putting them in the policy rather than keeping them out. A policy with a wrong number gets corrected by the first person who dials it. A policy that says contact the relevant authority gets ignored. The DSL owns that page and reviews it each term, and the review takes five minutes when the mapping document sits behind it.

The policy also has to cover the case where the person who should be told is the person the concern is about. Schools write the ordinary route and about half of them stop there. The deputy route, the board route, and the route to an external agency when the head of school is the subject need the same names, numbers and deadlines as the ordinary one, written with the same precision.

Reporting is a language problem before it is a legal one. A security guard who speaks Kazakh and Russian, a driver who speaks Russian, a cleaner who speaks Uzbek and a maths teacher who speaks English can each be the adult who notices something on a Wednesday afternoon. If the reporting route exists only in English, the school has trained part of its staff and left the rest to guess.

Translating the policy is the minimum. Training in the local language, on the actual route, with the actual agency name and the actual deadline, is what changes what people do. Staff need to rehearse the sentence they will say on the telephone, in the language they will say it in. The distance between translating a module and localising it is the distance between a colleague who recognises the words and a colleague who can use them while their hands are shaking.

Hierarchy makes this harder in some school cultures than in others. Where raising a concern about a senior colleague carries a social cost, the written route needs an alternative that does not require a junior member of staff to confront anyone, and the training has to name that alternative out loud rather than bury it in a paragraph. The reasons staff hesitate to report are rarely about knowledge.

The record is what allows a school to explain itself a year later to an accreditation team, to a parent, or to a court. It has to hold the reasoning as well as the facts, and it has to hold the cases where the school considered an external referral and decided against one, since those are the decisions that look worst when they survive only in somebody's memory.

• Date and time the concern was raised, and by whom, in their own words where possible.
• What the child said or what was observed, recorded factually and separately from any interpretation.
• Who was told inside the school, at what time, and by what means.
• The decision taken, the person who took it, and the reasoning, including the threshold applied.
• Whether an external report was made: to which agency, at what time, by whom, and any reference number given.
• Where no external report was made, the reason, the person who authorised that, and the date the decision will be reviewed.
• What the school did next: support offered, monitoring arranged, and the person responsible for each.

A mapped duty and a written policy still fail if the first person to use them is doing so during a real disclosure. Once a year the DSL should run the route as an exercise: a scenario handed to a mixed group of teaching and support staff, a clock, and the requirement to produce the actual telephone number and the actual form. Twenty minutes of that surfaces more defects than an hour of reading the policy.

The findings are usually dull and usually important. The number in the policy has changed. Nobody knows who covers the DSL role during half term. The written form exists in English only, and the two people most likely to fill it in read Russian. The board has never seen the escalation route that names the board. Each of those is a ten-minute fix when it is found in an exercise, and NSPCC Learning's guidance on managing allegations of abuse is a reasonable check on the internal steps that sit alongside the external duty.

Mandatory reporting is where generic training does the most damage, because a module written for another jurisdiction teaches a route that does not exist here, and staff pass it. SafeguardIS builds training from the school's own safeguarding and child protection policies, so the route staff practise is the route in the school's own document, with the school's own names and deadlines attached. 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.

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. When a member of staff is unsure which authority a report should go to, the AI policy assistant answers from the school's own policies rather than a general search engine, though the DSL still owns every safeguarding decision and no child's details go into the chat.

A policy audit feature checks a school's documents against ITFCP-aligned expectations and produces an action plan, which is one way to find out whether the reporting section of your policy survives contact with the host country's law. I also run live workshops in English and Russian and whole-school safeguarding audits. The pilot school is Miras International School in Astana. To go through your own reporting section with me, book a 20-minute walkthrough.