School Policy Publication Best Practice
Publishing a policy is the public-facing end of a governance process. It should reflect what was actually approved, by whom, and on what date, and tell the reader when the policy is next due for review.
In practice, this is where good governance often becomes invisible, or inaccurate. A governing board can do everything right at approval and still end up with a website showing the wrong version, no approval date, or a policy quietly superseded months ago and never taken down. For headteachers, school business managers (SBMs) and clerks to governors, publication is not paperwork. It is the part of the governance cycle that parents, staff, the local authority (LA) and Ofsted can actually see.
This guide sets out a practical approach: what to include, how to manage versions, how to close the gap between approval and publication, and how governors can keep sight of the process without checking the website themselves.
The policy lifecycle: from review to publication
Publication is the last step in a governance cycle, not the first. The cycle runs: scheduled review date reached, or an early review triggered by a guidance change or incident; policy updated or confirmed unchanged; governors formally approve it, usually at a board or committee meeting; the approved version is published; the next review date is set and recorded.
If any step is missing or undocumented, the published policy cannot be relied on as a governance record. A policy that was updated but never formally approved is not an approved policy, however current its content looks. One that was approved but never published, or published in draft form, breaks the chain between what governors decided and what the public sees.
Treating publication as an integral step in this cycle, rather than an afterthought once the meeting ends, is the single biggest shift most schools need to make.
What every published policy should include
At minimum, every published policy document should carry: the policy title; a version number; the date of governor approval; the name or role of the person responsible, for example "Headteacher" or "SBM"; and the next scheduled review date. Where a policy is a DfE statutory requirement, it should also note its statutory basis: the guidance or regulation that requires the school to have it.
A published document missing any of these does not demonstrate governance, even where the underlying content is sound. A reader with no approval date has no way of knowing whether the document reflects a board decision or a forgotten draft.
Weak example: A safeguarding policy PDF titled simply "Safeguarding Policy," with no version number, date or named owner.
Strong example: "Safeguarding Policy v2.1 - approved by the Governing Board 14 March 2026 - Policy owner: Headteacher - Next review: March 2027."
Version control for school policies
Version control solves one problem: knowing which version is current. It sounds simple, but it is one of the most common gaps schools have. Internal drafts, board-approved copies and the version live on the website often drift apart within a single academic year.
A simple numbering convention works for most schools: v1.0 for initial adoption; v1.1, v1.2 for minor updates, such as wording clarifications or contact detail changes; v2.0 for substantial revisions, such as a change in approach, a new statutory requirement or a significant restructure.
The version number, approval date, and a brief note of what changed should appear in the document footer or a document history table. This is not extra bureaucracy. It is what lets anyone reading the document later understand its provenance at a glance.
The critical rule: the version number in internal governance records and on the published document must match. If governors approved v2.0 but the website still shows v1.2, the published document is evidence of a gap, not of governance. See Policy Approval Records: What Governors Should Keep for what to hold on file at approval stage.
The approval-to-publication workflow
The gap between governor approval and publication is where most errors happen: a draft uploaded instead of the final approved copy, an approval date never added, or an old version left live alongside the new one.
A simple checklist closes most of this gap once a policy is approved: confirm the published version matches what governors actually approved; add the approval date; add the next review date; upload the new version and replace the old one; remove or clearly archive the superseded version; and record the publication date in the governance log alongside the approval date.
None of these steps is individually difficult. The problem is usually that no one owns the sequence. The clerk assumes the SBM will publish it, the SBM assumes it is already done, and the policy sits in limbo. Naming a single owner, as set out in Policy Governance Best Practice for School Boards, removes most of the ambiguity.
Keeping published policies current
The most common failure is a policy approved by governors but still shown on the website in its previous version weeks, sometimes months, later. This happens when publication is delegated informally, with no deadline and no follow-up.
The fix is to put publication on the agenda immediately after approval, not as a task picked up "when there is time." Agree three things in advance, as a standing part of the governance process: who is responsible for publishing, typically the SBM or clerk; what the target turnaround is, for example within five working days; and how completion is confirmed, such as a note in the governance log, an email to the chair, or an item at the next meeting.
Schools that track review dates systematically tend to have fewer publication gaps, because review and publication sit on the same timeline. See How to Track Policy Review Dates Across Your School.
Governor visibility of the publication process
Governors should never assume publication has happened simply because approval was minuted. The clerk or SBM should confirm, in writing, that the policy has actually been published. A short email or a note in the action log is enough; it just needs to exist as a record.
If governors are told a policy has been "approved and published," both statements should be recorded separately in the minutes, and only once publication has actually happened. Recording publication as complete before it occurs creates exactly the gap between governance and practice this guide is about closing. See Recording Board Decisions Effectively for wider guidance on accurate minuting.
Governors reviewing the website annually, as a standing agenda item or governance audit, should check published versions actually match what the board approved, rather than assuming the website is correct because it looks current.
Accessibility and findability of published policies
A policy that is technically published but buried three clicks deep in an unlabelled sub-menu is not meaningfully accessible. If a parent, staff member or inspector cannot find it without knowing exactly where to look, publication has failed its purpose.
Policies should be reachable from the website's top-level navigation, or a single, clearly labelled policies page linked from the homepage. Where DfE requires a policy to be published, it must be available without a login. Page titles and document file names should be clear and consistent. "SEN Information Report" should say exactly that, not "Document3."
A quick sense-check: ask someone unfamiliar with the website to find the safeguarding policy in under a minute. If they cannot, the structure needs attention. See the School Website Governance Checklist.
Handling policy gaps and outdated publications
If a policy is overdue for review, or the published version is out of date, the right response is to fix it, not leave it until the next meeting. Prioritise statutory policies first, then work through the rest by risk, tackling safeguarding-adjacent and high-visibility policies before lower-risk administrative ones.
Record every gap in the governance log with the remediation action and target date. This turns "we noticed a problem" into evidence the school is actively managing its policy estate. Where a gap is significant, such as a statutory policy missing entirely or several months overdue, tell governors directly rather than letting them find out during a routine review. A pattern of unreported gaps is harder to explain at inspection than a single, well-documented one that was caught and fixed.
Common policy publication failures
Quick reference - the recurring issues that most often break the link between approval and publication:
- No version number on the published document.
- Approval date missing from the published policy.
- Wrong version published after review, such as a draft instead of final or an older version left in place.
- Policy approved by governors but never actually published.
- Superseded version still live alongside or instead of the current one.
- Review date not shown on the published document.
- Policies buried in the website structure and difficult to find.
FAQ
Do all school policies need a version number? It is best practice for every policy, and essential for statutory ones. A version number is the simplest way to confirm a document matches what governors actually approved.
Who is responsible for publishing an approved policy? This varies by school, but it is usually the SBM or clerk to governors. What matters is that one person is clearly named as responsible, with an agreed turnaround, rather than the task being left unassigned.
How quickly should a policy be published after governor approval? There is no single statutory deadline, but leaving it for weeks creates a visible gap between governance and practice. Many schools set an internal target of five to ten working days and record the publication date as evidence.
What should happen to old versions of a policy once a new one is published? Superseded versions should be removed from public-facing pages or clearly archived internally, not left live alongside the current version. Two versions online is a common source of confusion for parents, staff and inspectors.
Does this apply the same way to academies as to maintained schools? The core principles - accuracy, version control and findability - apply broadly, but the statutory list of what must be published can differ between maintained schools and academies. Always check current DfE guidance for your school's category.
Close the gap between approval and publication
Most schools already have reasonably good policy approval processes. The weak point is almost always what happens next: the handoff from governor sign-off to public publication. Edvance helps schools connect that cycle, so the version governors approved, the approval date, and the published document stay aligned, with a clear audit trail from review through to publication.
Book a governance readiness demo to see how Edvance helps close the gap between policy approval and policy publication.
Jurisdiction note
This guidance is written for maintained schools in England. Academies, free schools and colleges have their own published-information requirements, which overlap with but do not exactly mirror those for maintained schools. Always verify current statutory publication requirements against the latest DfE guidance before relying on this article as a compliance reference.
This article is a process and best-practice guide, not a jurisdiction-specific list of statutory publication requirements. For schools in Ireland, the equivalent statutory obligations - what must be displayed or made available, and to whom - are covered separately in What Irish Schools Need to Display or Make Available. The two articles are related but not directly equivalent: this UK article focuses on the publication process and governance cycle, while the Ireland article sets out specific display and availability obligations under Irish requirements.
Sources: GOV.UK - What maintained schools must publish online; GOV.UK - What academies, free schools and colleges should publish online; DfE statutory guidance collection.
Frequently Asked Questions
Do all school policies need a version number?
It is best practice for every policy, and essential for statutory ones. A version number is the simplest way to confirm a document matches what governors actually approved.
Who is responsible for publishing an approved policy?
This varies by school, but it is usually the SBM or clerk to governors. What matters is that one person is clearly named as responsible, with an agreed turnaround.
How quickly should a policy be published after governor approval?
There is no single statutory deadline, but many schools set an internal target of five to ten working days and record the publication date as evidence.
What should happen to old versions of a policy once a new one is published?
Superseded versions should be removed from public-facing pages or clearly archived internally, not left live alongside the current version.
Does this apply the same way to academies as to maintained schools?
The core principles apply broadly, but the statutory list of what must be published can differ between maintained schools and academies. Always check current DfE guidance for your school's category.