Keeping Published Policies Current
Most schools review their policies on schedule. Governors approve updates at the right meetings, minutes record the decisions, and the paperwork is in order. Yet when you check the school website, some documents are a year or two out of date. The reviews happened. The approvals happened. The policies just never quite made it back online in current form.
This is the gap that catches schools out - not a failure to review, but a failure to publish. Keeping published policies current is not primarily a content problem. It is a process problem: what happens, and who is responsible, in the days after a governor approves a policy. Get that right and the website looks after itself. Leave it informal and it slowly drifts out of alignment with what governors have decided.
Why publication drift happens
The policy governance cycle, as most schools run it, effectively ends at the point of governor approval. A policy is reviewed, brought to a meeting, discussed, and approved. The decision is minuted. At that point, everyone in the room considers the job done.
What happens next is usually informal. Someone - often the headteacher or the SBM - is expected to update the website "at some point." There is rarely a deadline attached, rarely a requirement to confirm back to governors, and rarely any record that it happened at all. It sits alongside dozens of other operational tasks with no particular urgency attached.
When several policies are approved at the same meeting, this gets worse. Some get uploaded promptly because someone happens to prioritise them. Others slip down the list. Six months later, the website is a patchwork: some policies reflect the latest governor decisions, others still show the previous version. No single person intended this - it is simply what happens when a process has no defined end point. For a broader look at how these gaps accumulate across a school website, see common school website compliance gaps.
The publication step - making it part of the approval workflow
The fix is structural, not attitudinal. Publication should not be an assumed follow-on from approval - it should be a defined, documented stage of the approval workflow, with the same seriousness as the review and approval stages that precede it.
A workable sequence: governors approve the policy; it is published within an agreed number of working days - five or ten is typical; the clerk or SBM confirms in writing, by email or action log, that publication has taken place; and that confirmation is noted at the following governor meeting.
That last step matters more than it looks. Without a confirmation loop back to governors, "approved" and "published" are treated as the same event when they are not. A policy can be fully approved and still be absent - or outdated - on the website for months. Building publication into the same workflow that already exists for approval, as set out in school policy publication best practice, closes that gap without much extra process.
Assigning publication ownership
A task with no named owner tends not to get done reliably, and publication is a good example. If "someone will update the website" is the working assumption, the honest answer is usually that no one has been specifically tasked with it - it competes with everything else on several people's lists.
Every policy should have a named publication owner, decided in advance. In practice, this usually splits along familiar lines: the SBM typically owns operational policies such as health and safety, attendance, or charging; the clerk to governors typically owns governance documents such as the instrument of government or terms of reference; and the SENCO is often the right owner for the SEN information report, given their day-to-day ownership of its content.
Whoever the owner is, their responsibility is specific: upload the current version, remove the superseded one, and confirm the update has been made. This is a small amount of work, but it needs to sit clearly with one person rather than being a shared, unassigned expectation. Without a named owner, publication is everyone's job in theory and no one's in practice.
Version control as a publication discipline
Every published policy should carry a version number and the date it was approved by governors, ideally in the document footer. This single habit does more to prevent drift than almost anything else, because it makes currency visible rather than assumed.
If a policy document does not show when it was approved, there is no way for a parent, governor, or inspector to verify it reflects the school's current position. A simple version table - version number, date approved, next review date - in the footer is enough. It costs nothing to produce and removes any ambiguity about whether the copy in front of the reader is current.
The website's policy list should mirror this same information. If the document footer says "Version 3, approved March 2026, next review March 2027," the website listing should say the same. Any mismatch between the two is itself a signal that the publication process has broken down.
The policy review calendar as a publication schedule
The most effective schools treat their policy review calendar as a publication schedule, not just a reminder of when reviews are due. When a policy comes up for review, the review, the governor approval, and the publication step are planned together as a single sequence, with the publication date built in from the outset.
This works best when the SBM or clerk maintains a policy register - a single document showing, for every policy, its current version, last approval date, next review date, and publication status. This register does more than track paperwork. It lets someone check, at a glance, whether the website is aligned with governor decisions without checking every document individually. Building and maintaining this register is covered in more detail in how to track policy review dates.
It is worth treating this register as a governance document in its own right, not just an administrative convenience. It should be visible to governors, not just to whoever maintains it, because it is effectively the evidence record for the whole publication process.
Dealing with mid-cycle updates
Not every policy update happens on the scheduled review date. DfE or ESFA guidance sometimes changes mid-year, and a school may need to update a policy in response - safeguarding guidance is the most common example, though the same can happen with health and safety, finance, or attendance policies. A significant incident can also prompt an out-of-cycle change.
Mid-cycle updates should go through exactly the same approval and publication workflow as scheduled reviews - there is no reason to treat them as a special case that skips governor sign-off or the publication confirmation step. The updated policy should carry a new version number and the date of the mid-cycle approval, just as a scheduled update would.
It is good practice to add a brief note in the document's history section explaining why the update happened outside the normal cycle - for example, "updated in response to DfE guidance issued January 2026." This gives anyone reviewing the policy later, including an inspector, an honest account of why the version history looks the way it does.
Governor oversight of publication compliance
Governors should not assume a policy is published simply because they approved it. Approval is a governance decision; publication is an operational task carried out afterwards, and the two should not be conflated. Governors are well placed to ask the follow-up question, and doing so is a legitimate part of their oversight role.
A practical habit is for the clerk to include a short publication confirmation in the action log after each meeting - confirming, for each policy approved, that it has since been published. Once a term, or at minimum once a year, the governing board should receive a short publication compliance summary, ideally folded into a wider website governance review as described in the school website governance checklist. This is a governance responsibility, not simply an administrative one. Good practice around retaining the underlying approval evidence is set out in policy approval records governors should keep.
Checking alignment between approved and published versions
The most useful test is also the simplest. Pick five policies at random from the school website and compare the version number and approval date shown on each to the entries in the policy register. If they match, the publication process is working. If they do not, there is drift somewhere in the chain - and it is worth tracing where the breakdown happened, rather than simply fixing the one policy in front of you.
This spot-check should not be a one-off exercise. It works best as a standing part of the annual website compliance review, carried out at a fixed point in the school year so drift is caught before it accumulates across multiple policies and terms.
Common publication drift failures
- Governor approval is not followed by an agreed publication deadline
- No named publication owner for the policy
- The old version is not removed once the new one is uploaded
- A published PDF has no version number or approval date, so currency cannot be verified
- A mid-cycle DfE guidance update is approved but never reflected on the website
- Governors are never told whether publication actually happened
FAQ
How quickly should a policy be published after governor approval? There is no single statutory deadline, but schools that manage this well set an internal target of five to ten working days, with a named owner responsible for meeting it.
Who should be responsible for publishing policies on the school website? It varies by policy type. The SBM usually owns operational policies, the clerk usually owns governance documents, and the SENCO is often the right owner for the SEN information report. Each policy should have one named owner, not a shared assumption.
What should a policy document show to prove it is current? At minimum, a version number, the date of governor approval, and the next review date, ideally in a simple footer table. The website listing should show the same details.
Do mid-cycle policy updates need full governor approval? Yes. A mid-cycle update - for example, in response to new DfE guidance - should follow the same approval and publication process as a scheduled review, with a new version number and a note explaining why it happened outside the normal cycle.
How often should governors check that published policies match what they approved? At least once a year, as part of a wider website governance review, with a random spot-check of several policies against the policy register.
Keeping the record straight
Reviewing policies on schedule is only half the job. The other half is ensuring what governors actually approved is what parents, staff, and inspectors see on the website - which requires a publication step that is planned, owned, and confirmed, not assumed. Edvance links the approval workflow to the publication record, so when a policy is governor-approved, its version, approval date, and next review date are logged and tracked rather than left to chance. Book a governance readiness demo to see how this works for your school's policy cycle.
This article addresses maintained schools in England. Statutory publication requirements can vary by school type and are updated periodically - always verify current requirements against the latest DfE guidance.
Frequently Asked Questions
How quickly should a policy be published after governor approval?
There is no single statutory deadline, but schools that manage this well set an internal target of five to ten working days, with a named owner responsible for meeting it.
Who should be responsible for publishing policies on the school website?
It varies by policy type. The SBM usually owns operational policies, the clerk usually owns governance documents, and the SENCO is often the right owner for the SEN information report.
What should a policy document show to prove it is current?
At minimum, a version number, the date of governor approval, and the next review date, ideally in a simple footer table. The website listing should show the same details.
Do mid-cycle policy updates need full governor approval?
Yes. A mid-cycle update, for example in response to new DfE guidance, should follow the same approval and publication process as a scheduled review, with a new version number.
How often should governors check that published policies match what they approved?
At least once a year, as part of a wider website governance review, with a random spot-check of several policies against the policy register.