The safeguarding policy has been updated. The board approved version 3.2 at the May meeting.
The Staff Handbook still references version 2. The Parent Handbook references version 3, updated last term. The board policy manual references version 2 — the one from the year before. An email arrives this morning: which version should we follow?
Nobody has a list of everywhere the policy is cited. Nobody knows how many copies exist.
This is a predictable consequence of how most schools manage policies. A policy is approved, filed, and then distributed — copied into handbooks, linked in induction packs, uploaded to the school website, embedded in guidance documents. When it is updated, the folder changes. Everything else changes when someone notices. Or when someone asks.
Policy distribution is the discipline of controlling how a policy reaches the people who need it — in a form appropriate for each audience, without duplicating the document — so that when the board approves a new version, all downstream references update in step, automatically. Without that discipline, the question is not whether a mismatch exists. It is how many mismatches, and when the next one will surface.
The gap between updating a policy and distributing the right version.
The reference problem
Most schools do not have a complete list of where each policy is cited. The safeguarding policy appears in the staff handbook, the induction pack, the governor training materials, the school website, and possibly a Google Doc created three years ago that nobody has updated since. Each is a copy made at a specific point in time.
When the board approves version 3.2, the approved document is filed. Updating everything downstream — each handbook, each portal, each embedded reference — depends on someone knowing where to look and remembering to do it. Neither is reliably true across multiple review cycles and several changes of leadership.
The result is a policy environment where the board's approval record says one thing and the documents staff and parents are actually reading say something slightly different. Not wrong enough to cause immediate problems. Wrong enough to matter the moment anyone asks.
The audience problem
Different audiences legitimately need different access. Staff need the full operational detail. Parents need a readable summary or specific sections. Governors need the complete record including version history and approval chain. Managing three separate copies is not the same as managing three views of the same document. Only one of those keeps them in step.
Two approaches
The difference is not about adding steps — it is about what happens when the board approves a new version. With manual distribution, each downstream reference requires a separate update. With controlled publication, the approval is the update: the source changes, and everything linked to it changes with it.
Manual distribution
Controlled single-source publication
The shift
A policy portal is not a duplicate of the governance record — it is the live face of it. When the board approves a new version, the portal updates. When a section of the safeguarding policy is embedded in the staff handbook or a Google Doc via transclusion, that reference updates too — automatically, without anyone copying from a shared drive or notifying a team to check the link.
The audience access level is set once, not every time. Staff see the full operational policy. Parents see the sections appropriate to them. Governors see the complete record. Nobody downloads a copy that will be out of date in six months.
Change it once. It holds everywhere.
What controlled distribution requires
These are not features in the conventional sense — they are the mechanisms that prevent version drift. A school that cannot satisfy all four is not distributing policies. It is copying them and hoping the copies stay in step.
One place where the board-approved version of each policy lives. Not a shared drive folder with multiple copies named slightly differently. A single record that carries the approval chain, version history, and review schedule — and from which all downstream references draw.
What it answers: which document is the approved version
Staff, parents, governors, and the public all need different access to school policies. Audience-controlled views let each group see the relevant content from the same source — without creating separate copies. The access level is set once; the source is always the board-approved version.
What it answers: who sees what, from which source
A single destination — for staff, for governors, for parents — where the current approved version of every policy is always available. Not a folder. Not the school website with an upload from eighteen months ago. The actual approved document, updated automatically when the board approves a new version.
What it answers: where do people go to find the current policy
Embedding a policy — or a specific section of it — in another document as a live reference, not a copy. When the board approves a new version, any document using transclusion updates automatically. Individual sections can be embedded by subheading, so only the relevant part appears in each context. The embed carries no access control of its own — it should be placed in a document appropriate to its audience.
What it answers: how downstream references stay in step
What this enables
With controlled distribution, these questions have immediate answers — not because someone has been diligent about manual updates, but because the architecture prevents the drift from occurring in the first place.
If the board approved a new version of the anti-bullying policy today, which documents would still carry the old version tomorrow?
Do staff, parents, and the board all have access to the safeguarding policy in a form appropriate to them — from the same source?
Can you identify every place a specific policy is currently referenced — and confirm each one reflects the version the board approved?
When a section of the safeguarding policy was embedded in the staff handbook, was it a copy made at a point in time — or a live reference that updates when the board approves a new version?
The honest limitation
The failure rarely announces itself. Policies are broadly current. Audits pass. The version drift accumulates in the background — in handbooks updated last year, in Google Docs nobody has touched since the review cycle before last, in website pages nobody has permission to change without contacting the IT team.
The question is not whether policies are broadly up to date. It is whether the board can demonstrate — at any point, to any reviewer — that the version available to staff and parents is the one the board approved. Manual distribution cannot guarantee that. Controlled single-source publication can.
In Loom, the approved version of a policy is not filed — it is published. The approval at the board meeting triggers the update. The policy portal reflects the current version immediately. Embedded references update in step. No manual distribution step is required, and no copy is made.
Update once. The right version reaches the right audience — automatically.
Board Deck Standard 4.1: Transparent Communication and Advocacy ↗The test
Without contacting the IT team, searching the shared drive, or calling anyone — can the board answer these right now?
If the safeguarding policy was updated at the last meeting, you can confirm that the version on the school website, in the staff handbook, and in the parent-facing area all reflect that update — without checking each one manually.
Staff, parents, and governors all have access to the current approved policy in a form appropriate to them — from one source, not three separate documents maintained independently.
If a section of the safeguarding policy was embedded in the staff induction pack, that reference reflects the board-approved version — not a copy made when the handbook was last updated.
