The designated safeguarding lead in an international school

The designated safeguarding lead in an international school holds the same post as a DSL anywhere else, because the description of the role is about responsibility rather than jurisdiction. Keeping children safe in education sets it out in Annex B of the 2026 edition, which was Annex C until the 2025 edition was replaced. The governing body or proprietor appoints an appropriate senior member of staff from the leadership team. That person takes lead responsibility for safeguarding and child protection, including online safety and an understanding of the filtering and monitoring the school runs, and the responsibility is explicit in the job description.

Two lines in that annex do most of the work, and they are the lines schools skip. The first is that the DSL should have the status and authority within the school to carry out the duties of the post. The second is that the role carries a significant level of responsibility, and the holder should be given the additional time, funding, training, resources and support needed to carry it out. A school that appoints a DSL and leaves the timetable untouched has read the first half of that sentence.

The lead responsibility itself cannot be delegated. Deputies may take on the activities of the role, and should be trained to the same standard with the role written into their job descriptions too, but the lead responsibility for child protection stays with the DSL. In practice that distinction decides who answers when a child protection file was not transferred or a concern was not escalated, and it deserves saying out loud at the moment the post is offered.

Annex B expects the DSL to refer suspected abuse and neglect to local authority children's social care, to refer radicalisation concerns to the Channel programme, to make a barring referral to the Disclosure and Barring Service where someone is dismissed or leaves because of risk to a child, and to contact the police where a crime may have been committed. It expects liaison with the safeguarding partners and with the local authority designated officer where the concern is about a member of staff. An international school outside England has access to none of those four bodies.

The work, then, is to name the local equivalent for each function and to accept that some functions have no equivalent at all. Children's social care becomes the local children's rights or guardianship authority. The police function usually survives, although the specialist unit and its willingness to engage vary a great deal by country. The barring referral has no counterpart in most jurisdictions, which is why international recruitment leans so heavily on references and why safer recruitment across borders is a separate problem in its own right. The LADO function has to be rebuilt as a named external second opinion, and it is the hardest of the four gaps to fill. That rebuilt route belongs in the low-level concerns policy, alongside the recording rules for concerns about adults.

A local mandatory reporting duty changes the sequence as well. In several countries where international schools operate, the duty to report falls on the individual who learned of the harm rather than on the institution, with a short deadline and a penalty attached. That can put a teacher under a legal obligation running ahead of the school's internal escalation. The DSL has to know which duty applies and design a route that satisfies both, and how international schools handle local reporting duties is a governance decision for the board rather than a personal judgement for the DSL to make alone.

Governance adds distance of a different kind. Many international schools report to a board or an owner in another country, sometimes seven or eight time zones away, so a DSL who needs a decision from the chair at nine in the evening local time is waiting until tomorrow. Records raise the same question in another form. Where case notes are written in Russian and the board reads English, someone has to decide in advance which language the record of decisions is kept in and who translates it. Leaving that to the moment of an incident guarantees a delay.

During term time the DSL or a deputy should always be available during school hours for staff to discuss a safeguarding concern. The guidance lets the school and the DSL define what available means, and decide whether availability by telephone or video is acceptable in exceptional circumstances. It asks for adequate cover for out-of-hours and out-of-term activity, which for an international school means residential trips in other countries, summer programmes, and the two or three weeks in December when a large share of the staff has flown home.

The 2026 edition added an expectation about cover when the DSL is unavailable through illness, leave or other circumstances. Schools keep discretion over how that works, provided the responsibilities stay covered, and the guidance suggests a clear, reliable and known arrangement so that concerns can still be raised and acted on without delay. A confidential shared mailbox is the example it gives, monitored by more than one trained person, so that nothing waits for one individual to come back. A school with a single DSL and no deputy fails that test in the first week the DSL is ill.

Deputies are optional in the guidance and close to essential in practice for an international school. Two trained deputies is a reasonable floor for a school of any size, and one of them should sit in a different part of the campus from the DSL, so that a primary school concern does not have to travel through a secondary school office to be heard. Where the school boards, at least one person with DSL-level training should be reachable at eleven at night without going through a switchboard.

Formal DSL training should be updated at least every two years, and the knowledge behind it refreshed at regular intervals and at least annually, through reading, bulletins or meeting other designated safeguarding leads. Schools in England add Prevent awareness training on top. The list of what the training has to cover is long and specific: local referral criteria and the assessment process, how a child protection conference works and how to contribute to one, the lasting impact of adversity and trauma, the needs of children with special educational needs and disabilities, information sharing, online safety, data protection law, and keeping detailed, accurate, secure written records of concerns, discussions and decisions including the reasoning behind them.

Half of that list assumes an English system. A DSL in Astana or Amman will not attend a child protection conference in the English sense and will not apply English referral criteria. What survives translation is the underlying requirement: the DSL should understand the local processes as thoroughly as an English DSL understands theirs. That usually means going and building those relationships in person, because no course covers them, and because the person who answers the phone at the local authority matters more than the organisation chart does.

The larger risk is isolation. A DSL in England has a local authority, a network of DSLs in neighbouring schools and some supervisory structure. A DSL at an international school is often the only person in the country doing that job in that language, holding cases they cannot discuss with anyone in the building. Regional safeguarding groups, the ITFCP community and accreditor networks fill part of the gap. A Head who arranges no external case supervision for the DSL is leaving a foreseeable risk unmanaged.

Beyond casework, Annex B hands the DSL a standing administrative load. Child protection files have to be kept up to date, with each record carrying a clear and comprehensive summary of the concern, details of how it was followed up and resolved, and a note of the action taken, decisions reached and the outcome. Files transfer to a new school separately from the main pupil file, securely, with receipt confirmed, and within five days for an in-year transfer under the English timeframe. The child protection policy is reviewed at least annually and published. Every member of staff, including part-time and newly arrived staff, has to have access to that policy and understand it.

International schools add turnover on top. A school replacing a fifth of its staff each August runs a full safeguarding induction every year, for a group arriving three days before the students, in a country whose laws and agencies they have never encountered. The DSL usually owns that induction and owns the record proving it happened. What inspectors and evaluators ask to see is a per-person trail with dates, policy versions and evidence of understanding, and assembling it from spreadsheets in the week before a visit is where most of the pain lands.

The evidence burden also arrives in cycles. An accreditation visit or an inspection asks for the policy set, the training record, the recruitment files, the concerns log and the minutes showing the board discussed safeguarding. Most DSLs I have worked with as an evaluator can produce all of it eventually. Very few can produce it inside a week while also teaching a timetable, and the gap between those two states is the thing a Head is actually being asked to fund.

Time comes first, and it belongs in the timetable rather than in goodwill. A DSL carrying a full teaching load reads concerns after the last lesson, which is the wrong time for most of them. Whatever release the school settles on, write it into the job description and protect it, because the safeguarding release is the first thing a cover crisis eats.

Authority comes next. The DSL should report to the Head directly, sit in the senior leadership meetings where decisions about staffing, supervision, trips and buildings are made, and hold the standing to stop a trip, decline a visitor or require a member of staff to be supervised while a concern is looked at. The guidance calls this status and authority within the school. It shows up in small things, such as whether the DSL can call a meeting and whether people come.

The record system follows. A DSL keeping concerns in one spreadsheet, training completions in another and policy versions in a shared drive spends hours each week on clerical work and sits one laptop failure away from a serious problem. After that come deputies trained to the same standard and genuinely released to do the work, external supervision so the person holding the cases has somebody to talk to, and a board relationship with a named governor holding a safeguarding remit and a standing item on the agenda. The point of all of it is that the DSL stops being the only adult in the school carrying the risk.

Most of what I have described is an evidence and records problem sitting on top of a judgement problem, and only the first half can be built into a system. I designed SafeguardIS around the parts a system can carry, so that the DSL spends their hours on the parts it cannot.

Training modules are built from the school's own safeguarding and child protection policies, so what staff learn is what that school actually does, and the August induction stops being a slide deck about another country. 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 the approval sits in the record rather than in an email thread. 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 ask the AI policy assistant questions that are answered from the school's own policies, and the DSL keeps every safeguarding decision. No child's details belong in a chat window. Training ships 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.

Miras International School in Astana is the pilot school. If you want to see what the DSL review and approval step looks like against your own policy set, book a 20-minute walkthrough.