“I’d like a copy of your anti-bullying policy.”
It’s a request that school leaders receive more often than they would like, and is almost never sent merely out of curiosity. Usually, it either precedes or follows a debate between parent and teacher about whether the behaviour of one child towards another constitutes bullying, and by extension whether or not the school has responded appropriately to the situation.
Before hitting reply, the standard first step is to speak to the teacher and establish what actually happened. That conversation tends to surface one of three situations: the policy was applied correctly and the matter handled appropriately; the policy was read but misinterpreted, or simply didn’t fit the situation in front of the teacher; or the policy was never read at all, and the teacher did what they thought was right. Anything other than the first is a problem, more often than not rooted in the policy documentation itself rather than staff incompetence or negligence.
I have spent hundreds of hours on school policies, both at a micro level, working on individual statements, and at a macro level, managing whole-school policy libraries and their review and evaluation cycles. None of that was as challenging (or if I’m honest, as interesting) as investigating the issues that arose when they weren’t followed or weren’t fit for purpose.
Over the course of many such investigations, I’ve found a few common points of failure. Inadvertent misinterpretation is usually the result of vague statements. Deliberate bending of the rules is generally a response to overly rigid frameworks. Failing to read the policy at all is something that staff are blamed for all too often, but in practice it is typically a problem of design, training, communication or a mix of the three.
Disputes often come down to semantics, not values
It is striking how often it is the definitions, not the belief statements or principles, that are the root cause of both internal and external disputes. Take my example of the parent asking for a copy of the anti-bullying policy. Every school agrees it should have one, and the vast majority will espouse a zero-tolerance approach with a commitment to investigating every report or accusation. These things are easy, because the principles are embedded in our societal and cultural norms, and you will find few in the modern world who disagree with them.
It is much harder to achieve consensus on what bullying actually is: how it differs from an isolated conflict, what counts as repeated, what counts as an imbalance of power. Working in all-through schools, I have even found that the age of the students matters. A dynamic that would absolutely meet the bullying threshold in a secondary setting may be characterised as social development that needs a different kind of management by an early years specialist.
If these things aren’t clearly articulated from the off, two staff members enforcing the ‘same’ policy may be making two different judgement calls. A parent’s definition is often shaped less by a dispassionate reading of the principle than by their own cultural background, and the strength of their conviction is understandably dependent on which side of the incident their child is on.
Of course, none of this is specific to bullying and the same issue rears its head in every aspect of school life: you can’t assume that everyone has the same interpretation of any given term that you do. So if it’s an important one, you need to spell it out. Whether the agreed definition is crowdsourced by consulting stakeholders, borrowed from elsewhere or plucked out of thin air will depend on the school and the nature of the policy and, in many cases, is immaterial. Whichever way, clarity in the document and communication to all stakeholders after the fact are key.
Enter the policy package
So, how do you create a policy document that is clear enough to share with a parent and ensure consistent application, flexible enough to be responsive to different circumstances, and useful enough that staff feel that referring to it is worth their time? My answer: you don’t need a policy document. You need a policy package.
The fundamental purpose of a policy, at least on the educational side of things, is to describe how the school’s guiding statements should be applied in a given area, on a day-to-day basis. Put that way, it sounds like one job. But in reality it’s four, each requiring a different style and format to function well. Trying to crowbar all of them into a single structure, usually a long list of nested bullet points or numbered clauses, often creates documents that are either concise to the point of being too vague, or complex to the point of being impenetrable to the average staff member who just needs an answer. Separating them into independent elements that reference each other is the best solution I’ve found.
Shared ownership, shared understanding
The first element is the policy itself: the document you would share with parents and potentially put on your website (doing so is a legal requirement for some policies in some jurisdictions). This should include the statement of intent, the scope (noting any exclusions or exceptions), the definitions, the belief statements, and the guiding principles. It must be directly and explicitly rooted in the school’s published aims or values.
This is the layer that is least likely to change from one year to the next, because it describes what the school believes, not how it currently operationalises that belief. The exception is anything tied to external regulation or guidance: a safeguarding definition, for instance, may need to move whenever government guidance does, as UK schools do annually in line with Keeping Children Safe in Education.
Though every policy will have a notional lead for the purposes of formulation and review, this element should never belong to one person. When it comes to values and standards, the senior leadership team’s responsibility and (arguably more importantly) credibility are collective. Other relevant stakeholders such as governors, other staff members, students and parents may need a voice too, depending on what the policy covers.
Even if they don’t know the details of how they are implemented, any member of the team should be able to confidently articulate the principles that apply in all areas of the school’s educational provision. A document that’s written by the deputy head responsible for the area and rubber-stamped without consulting those who will depend on it won’t achieve that.
This is the point at which discipline needs to kick in. Once you have agreed the intent, scope, principles and definitions, you have your policy, and you need to stop. You have your ‘why’ and your ‘what’. Everything else is the ‘how’, and merging it into the above creates the complexity problem mentioned earlier.
From policy to practice
The second element in the package is the standard operating procedure (SOP), which some may call a ‘process’ or a ‘protocol’. This will usually be a staff-facing document rather than a public one, and should be written for those who are expected to implement the policy on a day-to-day basis. This purpose means it requires a very different format to the policy document. Long prose, nested bullet points and value statements should be minimised or eliminated, making way for focused step-by-step procedures, flow charts and reference tables.
Take the anti-bullying example again. The policy might state that any report will be investigated, but the SOP governs how that investigation is actually done: taking statements, reviewing CCTV, collating written or electronic evidence, and compiling a report. Any staff member asked to look into a bullying accusation should be able to pick this up and handle the matter in line with the school’s expectations, assuming they have some training or experience in dealing with sensitive matters or conversations.
Unlike the policy layer, the SOP may change relatively often, as people identify more appropriate, rigorous or efficient ways of doing things. There is also an ever-changing compliance landscape to consider: updates to an exam board’s requirements, a new group-level framework, or a regulatory shift can all prompt modifications to the established protocol.
There are two ways in which SOPs tend to cause problems, and both come down to an unwillingness to change. The first is ‘we do it that way because we have always done it that way’. Don’t be scared of testing new ideas and methods that come from your team. The second is not building paths where people walk. Sometimes, even with the best intentions, we create SOPs that seem fine on paper but are a pain in practice. Listen to the staff who are actually doing the job every day and adapt to support their work, rather than clinging to the original design and making their lives unnecessarily difficult.
Prepared now, not improvised later
The third element is documentation: the pro formas, the checklists, the infographics, the boilerplate text that has to appear somewhere. In our anti-bullying example, that might include a student statement form, an investigation report template and a script to be used at the beginning of a student interview.
Documentation may not be exclusively applicable to one policy: in this example, all three may also be referenced in a behaviour or sanctions policy. A central document library that can be referenced or linked from multiple policies and SOPs is therefore likely to be more effective than every policy having its own appendices that duplicate (or, worse, contradict) each other.
Parts of a documentation layer can sit untouched for years, and that’s not a sign of neglect. A form that still works doesn’t need changing for the sake of it. What it does need is to be complete: if you want your staff to follow the SOP in a consistent and compliant way, everything they need to do so should already exist inside this layer. If it doesn’t, you are tacitly asking your staff to improvise, which not only creates work for them, but also introduces a source of risk to the school.
Over the years I have dealt with and heard about many issues arising from staff using different versions of everything from incident forms to permission slips. Sometimes these have been their own concoctions, but more often they are borrowed from a previous school. What’s missed, of course, is that the school in question was in a different country or operating under a different regulatory regime. In extreme cases this can expose the school to financial, reputational or even legal risk, and it usually isn’t fair to blame the staff member. It is far more likely the result of either missing policy documentation or poor communication of the location and importance of that documentation.
Precedent that relies on record, not memory
The fourth element is guidance, which helps a member of staff apply the policy to a situation the SOP doesn’t explicitly mention. It usually takes the form of exemplars, case studies and plain-language notes drawn from real situations. In most schools, though, it lives in people’s heads rather than on paper, which means institutional memory is lost when the person carrying it moves on. As such, it’s worth pushing for this to exist as a live document somewhere, updated as new scenarios come up.
The important distinction is between a general rule missing from the SOP, which does warrant an SOP edit, and a specific example or application of an existing rule, which belongs in guidance instead. Think of it as introducing case law into what is otherwise a constitutional system: precedent accumulates around the edges of the rules, rather than the rules themselves being amended every time something new comes up.
Done well, guidance should never surprise anyone who understands the policy and SOP. Its role is to illustrate how they have been applied in practice, not to introduce exceptions to them or contradict them outright. It also does something leaders underrate: it stops the same judgement call being made from scratch every time it comes up. A behaviour policy’s guidance that records, over time, an ever-growing list of what counts as a Level 2 offence gives every member of staff the same precedent to work from. Without it, every leader is left making the call alone based on a short list of generic descriptors in the SOP, and often making it slightly differently each time.
Organisation, communication and accessibility
Policy, SOP and guidance may be stored within a single file for ease of access and review, or separated into different documents for sharing, as the school sees fit. Documentation is the exception, given the case already made for a central library: it’s better kept separate and referenced or linked from wherever it’s needed. Wherever the elements live, there should be no duplication between them: a definition belongs in one place, not four, and every other element should point back to it rather than restate it. In short, there should be a single source of truth for everything in your policy library.
The four-element structure also allows for a more dynamic review cycle. Most schools review policies on a fixed cycle, one or two years, regardless of what’s actually happening on the ground. That may be the right rhythm for the policy layer, which shouldn’t be moving much anyway. It’s the wrong rhythm for SOPs and guidance, which should be responding to real signal: a pattern in incidents, a question staff keep asking, a regulatory change. A school that only revisits its ways of working when the calendar says to has, in effect, decided that necessary updates and new precedent can wait up to two years before documented adoption.
Even with all of this in place, one further step is still needed. Separating the four elements makes a policy easier to understand, but that’s not the same as training staff to use it. My mantra: sent doesn’t mean read, read doesn’t mean understood, understood doesn’t mean implemented, and implemented doesn’t mean implemented correctly. In the UK system, statutory safeguarding guidance already accepts this. Schools must give staff formal annual training on the safeguarding policy and evidence that staff have read and understood it through a signed acknowledgement. Few, if any, extend the same rigour to any other key policy, which is worth questioning.
The international sector adds another dimension: policies should bear in mind the language proficiency of stakeholders who need to understand it. Sharing simplified versions or translations for different members of the school community, even if only for a subset of key policies, can make a real difference. If only the native speakers of the document’s language can truly access it, it is simply not fit for purpose.
Clear, responsive and confident
Go back to the parent who wants a copy of the anti-bullying policy. For many leaders, the difference between replying quickly and feeling the need to interrogate the paperwork and the relevant staff first is their confidence in the policy work the school did in advance. Get the package right, and the concise-or-complex dichotomy most schools think they’re stuck with disappears. There is a clear policy to send to the parent, a structured SOP with supporting precedent that should have guided the staff actions up to that point, and a library of documentation to support their work. No system is entirely foolproof, but if you ask me, that’s as good a starting point as one could hope for.