When staff are reluctant to report safeguarding concerns

Most missing safeguarding reports do not begin with someone deciding to stay silent. They begin with a pause. A teaching assistant notices that a colleague keeps a particular student behind after the last lesson, thinks about it for two days, decides it is probably nothing, and does not write it down. A driver hears a comment on the bus, is not sure it means anything, and mentions it to no one because he does not know whether a driver is supposed to. A newly appointed teacher sees a senior colleague send a message to a student outside school hours and calculates, quite rationally, what raising it would cost her in a school where she has worked for three weeks.

Each of those people made a judgement about the route rather than about the child. That is the useful thing to understand about staff who are reluctant to report safeguarding concerns: the hesitation is usually a reasonable response to how the route is built, and a school can rebuild the route. Blaming the culture in the abstract produces a poster. Changing the number of entry points, the written protections and what senior staff visibly do produces reports.

The NSPCC published a briefing in March 2024 drawing on contacts to its helpline and whistleblowing advice line, and the barriers professionals described there are recognisable in any school in any country. Staff said they felt they had insufficient evidence or detail to justify a report. Some believed they needed permission before reporting. Others feared for their own safety or their job. Several described organisations without clear procedures, and some described dismissive responses when they did raise something. None of those barriers is exotic and none is cultural in origin.

Deference to seniority adds a second layer on top of that, and it operates through mechanisms rather than through national character. Where a school's route runs through one senior person, a concern about that person has nowhere to go. Where the only channel is a face-to-face conversation, a member of staff has to perform certainty they do not feel, in front of someone who outranks them, often in a second language. Where employment is tied to a visa or a fixed-term contract, the cost of being wrong is not evenly distributed across the staff body. And where the ordinary word for reporting carries the sense of informing on a colleague, the training is asking staff to do something their own vocabulary already frames as disloyal.

The result is predictable and consistent. High-certainty concerns about children still get through, because nobody hesitates about a bruise and a clear account. Everything below that threshold thins out, and it thins out most sharply for concerns about adults.

Keeping children safe in education, the Department for Education's statutory guidance for schools in England, sets out a separate process for low-level concerns about adults precisely because those concerns are the ones a normal reporting culture suppresses. A low-level concern is behaviour by an adult that is inconsistent with the staff code of conduct without meeting the harm threshold, and the point of recording it is that a pattern only becomes visible once several small entries sit next to each other. One member of staff giving one student a lift home is a note. The same note four times, from four different reporters, is a case.

A school that receives no low-level concerns in a year has not achieved a staff body with perfect conduct. It has a route that only carries certainty. The NSPCC guidance on managing allegations about staff and volunteers puts the requirement plainly: staff and volunteers should feel confident about challenging the behaviour of others and voicing concerns, and organisations need clear procedures for handling what comes back. Confidence is the operative word, and confidence is built by design rather than by exhortation. The mechanics of writing and running that process are covered in a low-level concerns policy for international schools.

A route that works under hierarchy has redundancy built into it. The design below is not expensive; most of it is a page in the policy, a form, and a decision by the senior team about how they will behave.

• More than one named person. The DSL, at least one deputy DSL, and a named route to the Head and to the board chair for concerns about the DSL or the Head. Every school should be able to answer where a concern about the most senior person goes.
• More than one channel. A conversation, a written form, and an email address that at least two people monitor. Written reporting removes the requirement to perform certainty out loud.
• A confidential option that is honestly described. If anonymous reports are accepted, say what the school can and cannot do with one. If they are not, say that instead, and say who will know the reporter's name and who will not.
• Retaliation protection in writing, with a named enforcer. A sentence in the policy stating that no member of staff will be disadvantaged for raising a concern in good faith, signed by the Head, and a named person to complain to if that sentence is broken.
• An explicit permission clause. State in the policy and in the training that no member of staff needs approval from a line manager before reporting to the DSL, and that reporting to the DSL is never a breach of the line-management relationship.
• A defined response time. Twenty-four hours to acknowledge, and a stated point at which the reporter is told what happened in general terms. Silence after a report is the single most effective way to stop the next one.
• One sentence any adult can say. If a driver, a cleaner and a head of department describe the route in three different ways, the route is not yet a route.

The strongest signal available to a school costs nothing and cannot be delegated. When a member of the senior leadership team logs a minor concern about their own conduct or about a colleague of equal rank, and the school handles it visibly and proportionately, every member of staff learns more about the route than a module can teach them. I have seen a single instance of this change a staff room's behaviour for a year. The reverse is also true: one dismissive response to a small report, delivered in front of other people, sets the threshold for the whole department.

The Designated Safeguarding Lead carries most of this weight, which is why the role needs protected time and authority rather than an additional line on a deputy head's job description. The demands of the post in an international context are set out in the Designated Safeguarding Lead role at an international school.

Staff do not need to be told that reporting matters. They need to have done it once in a setting where nothing was at stake. Induction is the place to rehearse it, and the rehearsal should be concrete: give a new member of staff a written scenario drawn from the school's own policy, ask them to complete the actual reporting form with the actual names on it, and have the DSL respond as they would to a real report. Ten minutes of that produces more usable memory than an hour of definitions. The wider design of that first week is covered in safeguarding induction for new staff at an international school.

Refresher training should rehearse the harder cases, because the easy ones were never the problem. Use scenarios in which the person of concern outranks the reporter, in which the evidence is a feeling rather than a fact, and in which the reporter is uncertain whether the behaviour is a cultural difference or a boundary breach. Ask staff to write what they would do rather than to select an option. Then have the DSL read a sample of the answers, because a set of free-text responses from a department is the cheapest culture survey a school will ever run.

Two conditions make the rehearsal work. Every member of staff has to do it in a language they use comfortably, otherwise the exercise measures English rather than judgement. And the school has to run it for non-teaching staff on their own terms, with scenarios set in the bus, the gate, the kitchen and the medical room. A school that skips either condition will keep a reporting route that only its confident English-speaking teachers can use, which is the coverage problem described in how to tell a safeguarding culture from a compliance record.

Reporting volume on its own tells a Head very little, because the right number is unknown. The useful measures are about distribution and response, and a DSL can produce all of them from an ordinary log once a term. Count distinct reporters rather than reports, and watch whether that number grows. Count the proportion of entries that came from staff who do not teach. Count the entries closed with no further action, since a route that only carries confirmed cases is a route that is filtering upstream. Track the time between report and acknowledgement, and track how many reporters were told an outcome.

Two further signals are worth watching over a longer period. The first is whether concerns about adults appear at all, and whether any of them concern senior staff; a log full of concerns about students and empty of concerns about adults is describing the route rather than the school. The second is repeat reporting: a member of staff who reports twice has concluded that the first report was worth making. Present those figures to the board once a term as a pattern rather than a total, and ask the board to question the shape rather than to congratulate the number.

Working together to safeguard children, the statutory multi-agency guidance for England, and the resources of the International Task Force on Child Protection both assume that concerns will travel between people and agencies rather than stopping at the first desk. A school measuring its own route is checking the same assumption locally.

SafeguardIS builds a school's training from that school's own safeguarding and child protection policies, so the route staff rehearse in a module is the route printed in the policy, with the same names and the same channels. 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. Certificates are countersigned by the Head of School and the DSL and carry a code anyone can check on a public verification page. The platform ships training in English, Russian and Kazakh today.

The feature most relevant to hesitation is the AI policy assistant. Staff can ask it questions that are answered from the school's own policies, which gives a member of staff who is unsure whether something counts a way to check the policy without first approaching a senior colleague. The DSL keeps every safeguarding decision, and no child's details belong in a chat window; the assistant answers questions about procedure and points the adult to the person who acts. A policy audit feature checks a school's documents against ITFCP-aligned expectations and produces an action plan, which is where most schools discover that their route has one entry point and no retaliation clause. I also run live workshops in English and Russian and whole-school safeguarding audits, and 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 test your own reporting route against the design above, book a 20-minute walkthrough and bring the page of your policy that describes it.