Policy Approval Records: What Governors Should Keep

Governing boards are accountable for the policies they approve - not just for having them, but for being able to show how and when they were approved. When an inspector, a parent, or a solicitor asks "can you show me how this policy was reviewed?", the only credible answer is a documented evidence trail. A policy that exists only as a PDF on the school website, with no supporting record of governor scrutiny, tells its own story.

This article sets out exactly what governing boards, clerks to governors and headteachers should be capturing every time a policy is approved, reviewed or amended - from the minute itself through to publication confirmation.

Why the evidence trail matters

Good record-keeping is not paperwork for its own sake. It is what allows a governing board to demonstrate active oversight rather than passive sign-off. Three situations make this especially clear.

Inspection questioning. An Ofsted inspector may ask a chair of governors or clerk to explain how a particular policy was scrutinised and approved. A confident, specific answer - "the safeguarding policy was reviewed and approved at the March meeting, version 4.2, minuted with the next review date recorded" - reads very differently to "I believe it was looked at at some point."

A parental complaint about a policy. If a parent challenges how a behaviour or exclusions policy was applied, the school may need to show the version of the policy in force at the relevant date, when it was approved, and that it was properly published. Without a version history, it can be genuinely difficult to establish which policy applied when.

A safeguarding incident that references school policy. Where a serious incident triggers a review, investigators and the local authority may ask to see the approval history of the relevant safeguarding-related policy, not just the current document. A clear record shows the board was actively governing the policy, not simply storing it.

In each case, the underlying document matters less than the record of what the board did with it.

What the minutes should capture when a policy is approved

Many governing boards under-record policy decisions in minutes, often reducing a substantive discussion to "the policy was approved." At minimum, minutes should capture:

Policy name - the exact title as it appears on the document
Version number - so there is no ambiguity about which draft was approved
Date of approval
Who proposed the approval
Who seconded it, or how consensus was reached if the board does not use formal proposing and seconding
Outcome of the vote or consensus - approved, approved with amendments, deferred, or rejected
Next review date
Policy owner - the named role responsible for the next review
Any conditions or amendments noted at approval, for example, "approved subject to updated contact details being added before publication"

A minute along these lines gives a governing board a defensible, specific record: "Child Protection and Safeguarding Policy, version 5.1, approved 14 March 2026, proposed by [governor], seconded by [governor], approved unanimously, next review March 2027, owner: Designated Safeguarding Lead."

Version history - what it is and why it matters

Version history is the record of how a policy has changed over time. Without it, a school cannot answer a simple but important question: which version was in force on a given date?

Minimum version control should include:

A consistent version number format - for example, major.minor (v1.0, v1.1, v2.0), incremented each time the document changes
The approval date printed on the document itself, not just held in the minutes
A short summary of what changed from the prior version, even if only a line or two - this matters far more than it seems when a policy is challenged later

A policy document without a version number or approval date on its face is a governance gap, even if the underlying minutes are sound. The two records need to match.

Delegated authority

Not every policy change requires a full governing board vote. Many boards delegate limited authority to the headteacher, often for minor, non-statutory amendments or for policies falling under a specific committee's remit.

Where delegation exists, the record should show:

The scope of the delegation - ideally set out in the board's scheme of delegation or terms of reference, not assumed informally
That the headteacher's approval under delegated authority is itself minuted - for example, reported to the next full board meeting as "approved under delegated authority, [date], for board's information"
The limits of delegation - statutory policies, safeguarding-related policies and anything with significant financial or legal implications typically fall outside what can reasonably be delegated

A policy approved under delegated authority still needs a version number, an approval date and a named owner. Delegation changes who approves; it does not remove the need for a record.

Next review date - why it belongs in the minutes

Most policy documents state a next review date on the document itself. That is necessary, but not sufficient. If the review date lives only in the document and not in the minutes, there is no independent board-level record that the review cycle was actually agreed and tracked.

Recording the next review date in the minutes:

Creates a board-level commitment, not just a document-level note
Makes it possible to check governance records against policy records to confirm they agree
Supports how the board tracks policy review dates across the whole policy set, rather than relying on memory or a single document owner

Policy owner - recording who owns the next cycle

Every policy should have a named owner recorded at the point of approval, not just "the headteacher" generically, but the specific role or individual accountable for initiating the next review. In practice, this means:

The owner is named in the minutes, not only in the document footer
The owner is understood to be responsible for bringing the policy back for review ahead of its next review date
If ownership changes, for example following a staff change, the change itself should be minuted

This closes a common gap: a policy with no clear owner tends to drift past its review date because no single person is accountable for raising it.

Publication and display status

Approval is not the end of the process. Once a policy is approved, the board should confirm and record:

That the school website has been updated with the current version, and the date this happened
Any statutory display obligations have been met - some policies must be displayed or made available in specific ways, separate from general publication
The date of publication, which may differ from the date of approval

A policy approved in March but not published until June creates a window where the "current" published version does not match what the board approved. Recording the publication date closes that gap and gives the board a clean answer if ever asked when a policy became publicly available.

How long to keep policy approval records

As general practice, and not as legal advice, most schools find it useful to retain policy approval records, including minutes, version histories and superseded policy documents, for several years beyond the life of the policy itself, particularly for safeguarding-related and statutory policies. Retention periods can vary depending on the type of policy and the school's own retention schedule, so governing boards should agree and document their own retention approach rather than relying on informal practice.

Common record-keeping failures

A short checklist of the gaps that show up most often:

No version number recorded in the minutes
Minutes refer to "the policy" without specifying which version was approved
No next review date recorded in the minutes, even though one appears in the document
Publication not confirmed or dated anywhere in the record
The version published on the website does not match the version actually approved
No named owner recorded for the next review cycle
Delegated approvals not reported back to the full board

Any one of these is a manageable gap. Several at once suggest the board's record-keeping process itself needs attention, not just a single policy.

What governors should be able to produce when asked

For any given policy, at any given time, the governing board should be able to produce:

The minute recording approval, including version number, date, proposer or seconder, and outcome
The current version of the policy document, with version number and approval date shown on the document itself
A brief record of what changed from the previous version
The next review date, matching in both the minutes and the document
The named policy owner
Confirmation and date of publication, whether website, statutory display, or both
A record of any delegated approval, reported back to the full board

If any of these cannot be produced quickly, that is a possible gap worth a manual review - not evidence of wrongdoing, but a prompt to tighten the process before it is tested by an inspection or a complaint.

This kind of structured record is exactly where many boards struggle, particularly where policies, minutes and version history sit in different folders, inboxes or shared drives. It is worth reviewing alongside the board's wider approach to policy governance best practice and policy readiness before inspection.

FAQ

Do minutes need to record the exact version number of every policy approved? It is good practice to do so. Recording the version number removes any ambiguity later about which draft the board actually approved, particularly if the policy is challenged or reviewed again quickly.

Can the headteacher approve a policy without a full governor vote? In many schools, yes, for certain policies under a scheme of delegation, but the scope of that delegation should be clearly set out, and any approval under delegated authority should still be recorded and reported back to the full board.

What happens if the published policy doesn't match the version the board approved? This is one of the most common record-keeping gaps. It usually means publication happened before final wording was locked down, or an old version was left live after a new one was approved. Checking the published version against the approval minute is a useful periodic exercise.

How long should we keep old versions of a policy? As general practice, many schools retain superseded versions and their approval records for several years, particularly for safeguarding-related and statutory policies. This should be set out in the school's own retention schedule rather than decided informally, and schools should seek their own advice on retention periods where needed.

Who should be responsible for checking that approval records are complete? This typically falls to the clerk to governors, working with the headteacher or school business manager, to confirm that each approved policy has a matching minute, version history entry, next review date and publication record.

See how Edvance supports this

Edvance helps governing boards maintain structured policy approval records - version history, owner assignment, approval dates, next review dates and publication status, all tracked in one place and accessible when they are needed. Book a governance readiness demo to see how it works.

Jurisdiction disclaimer

This article reflects general practice for governing boards of maintained schools and academies in England and is intended as practical guidance, not legal advice. Requirements and expectations can vary by school type, local authority and individual circumstances. Governing boards should confirm their own retention, delegation and publication obligations with their appropriate advisers, and refer to current DfE and Ofsted guidance directly. For the equivalent guidance for boards of management in Ireland, see Policy Approval Records: What Boards of Management Should Keep on edvance.ie.

Frequently Asked Questions

Do minutes need to record the exact version number of every policy approved?

It is good practice to do so. Recording the version number removes any ambiguity later about which draft the board actually approved.

Can the headteacher approve a policy without a full governor vote?

In many schools, yes, for certain policies under a scheme of delegation, but the scope of that delegation should be clearly set out and reported back to the full board.

What happens if the published policy doesn't match the version the board approved?

This is a common record-keeping gap. Checking the published version against the approval minute is a useful periodic exercise.

How long should we keep old versions of a policy?

Many schools retain superseded versions and approval records for several years, particularly for safeguarding-related and statutory policies, but this should be set out in the school's own retention schedule.

Who should be responsible for checking that approval records are complete?

This typically falls to the clerk to governors, working with the headteacher or school business manager.