Five Versions of the Same Policy

A parent emails with a question. A specific clause in the safeguarding policy. Something they have seen on the school website.

The policy on the website says one thing. The version shared with the board last term says something slightly different. Both look authoritative. Both carry the school's name. The differences are subtle — a paragraph here, a revised sentence there.

But subtle does not matter when someone is asking which version holds.

So the search begins. The approval meeting is found. The minutes are scanned. The motion is there — "the safeguarding policy was reviewed and approved." But which version was approved?

The document in the folder is dated two weeks after the meeting. The one shared with staff is earlier. The website version was uploaded by someone in the office who thought it was the latest.

None of this was dishonest. Each decision made sense at the time. A cleaner version for parents. A more operational one for staff. A formal copy for governance. But over time, they drifted. Small edits. Informal updates. Good intentions, carefully executed, accumulating into uncertainty.

And if an inspector arrives — or a parent presses — the question will not be about intention. It will be: which version was formally approved, by whom, and when? Right now, the honest answer is: it is complicated.

This is not a failure of process. It is a structural problem. When governance and publication are not connected — when the approved document and the published document are separate objects, maintained separately — drift is inevitable. Not because anyone is careless. Because the system makes it easy.

The problem scales with the size of the policy library. A school with forty policies on a three-year review cycle has, at any given moment, perhaps a dozen in some stage of revision. Multiply that by the number of places each policy might live — the governance folder, the staff intranet, the parent portal, the school website — and the potential for divergence is not a risk. It is an arithmetic certainty.

Some schools have started treating approval and publication as parts of the same record. The version that was formally approved is the version that is published. Not copied. Not reuploaded. The same document — with visibility shaped for each audience.

Parents see what they need. Staff see the operational context. The board sees the governance trail. Not three documents. One, presented differently.

Tools like Loom are built on this principle. The approved policy is linked directly to the decision that adopted it. Publication does not create a new document — it opens a window to the authoritative one.

So when the question comes — which version is correct? — there is only one answer. Because there is only one version.