School Policy Review Checklist UK: What to Review and When

For the full list of statutory policies for schools, use the governor guide. This page focuses on organising review dates, owners, decisions and follow-up.

Build the policy review calendar from current requirements

Use the linked governor guide to establish the applicable inventory. For each policy or live record, identify the current official source, school-type applicability, drafting owner, authorised approver, review basis and publication requirement. The calendar then turns those requirements into workable actions.

There is no single annual, two-year or three-year rule for every school policy. Keeping Children Safe in Education addresses annual child protection policy review; other topics have their own legal, guidance or local requirements. Do not apply a fixed two-year health-and-safety or SEND-policy cycle without an identified source. Live records need updating when information changes.

Record whether a review date follows a requirement, recommendation or local planning choice. Check current guidance and changes sooner when they affect the policy. An annual planning review of the register can identify work due during the year without falsely describing every policy as legally annual.

For sourced intervals, school-type applicability and examples of local schedules, see how often school policies should be reviewed.

Governor Approval: What the Record Must Show

Approval depends on the specific requirement and authorised delegation arrangements; not every policy needs full-board approval. The governing body's role is to set the strategic framework within which the school operates — policies are a core part of that framework.

What a valid approval record includes

  1. The date the policy was considered by the governing body (or relevant committee if properly delegated).
  2. The version of the policy that was approved (preferably a version number or date-stamped document).
  3. A brief minute entry confirming the policy was approved, amended, or deferred — with any conditions noted.
  4. The name of the governor or committee chair who confirms the record.

Common gaps in approval records include:

  • Policy approved by the headteacher alone, with no governing body record.
  • Minute entry that says "policies were approved" without naming which policies.
  • Approval of a different version to the one currently published on the school website.
  • No record at all — approval assumed to have happened at some point but undocumented.

Key principle: For inspection purposes, an undocumented approval is equivalent to no approval. The governing body's records are the evidence. If the evidence is not there, the oversight did not happen in any way that can be demonstrated.

Public Accessibility Obligations

Many statutory policies must be published on the school's website. The DfE publishes guidance on which policies must be publicly available — the list includes the SEND policy, accessibility plan, RSE policy, and several others.

Checklist for website compliance

  1. All required policies are published and accessible without requiring a login.
  2. The published versions are current — the dates on the website match the internally approved versions.
  3. The safeguarding policy is clearly accessible from the homepage or a clearly labelled policies section.
  4. Policies are not published as broken links or password-protected files.
  5. The school's complaints procedure is published and current.

Website accessibility also matters in a practical sense. Governors, parents, and inspectors can check the school website before — and during — an inspection. A policy that is three years out of date on the website is a visible gap.

Building a Sustainable Policy Review Process

A policy review calendar managed by memory or informal reminders will produce gaps. A sustainable process has four components:

1. A policy register

A single, maintained record listing every policy the school holds, with:

  • The statutory basis for the policy.
  • The current version and its approval date.
  • The next review due date.
  • The governor or committee responsible for approval.

2. Scheduled review reminders

Review dates should be built into the governing body's annual calendar, not flagged reactively when a review is already overdue. Annual policies — particularly safeguarding — should appear on the autumn term agenda without fail.

3. A clear workflow for each review

Each review should have a defined process:

  1. Headteacher or nominated lead prepares a draft (or confirms no substantive changes are required).
  2. Draft is circulated to relevant stakeholders for comment where appropriate.
  3. Updated policy is presented to the governing body with a change summary.
  4. Governor approval is recorded in the minutes.
  5. Published version on the school website is updated.

4. An audit check before inspection preparation

At least annually — and specifically before any period of likely inspection — a named person should audit the policy register against the published website versions and the governor approval records to identify any gaps requiring action.

Common Gaps and How to Address Them

Gap Typical cause Remedy
Safeguarding policy not reviewed within 12 months Review not built into annual calendar Add as fixed autumn term agenda item
No governor approval record Policy reviewed by SLT, not brought to governing body Update delegation scheme; add to board pack template
Outdated version on school website Website not updated after approval Make website update the final step of each review workflow
Missing policy from register No central policy register maintained Conduct a full policy audit against DfE statutory guidance

Manage Your Policy Review Cycle with Edvance

Edvance helps UK schools maintain a structured policy review workflow — tracking review dates, recording governor approvals, and supporting the end-to-end lifecycle from draft to published policy. The policy publication readiness workflow for England shows how to keep the approved version, public copy and follow-up evidence connected.

For broader inspection preparation context, see Inspection Readiness for UK Schools: A Practical Governance Checklist.

Start your free trial at app.edvance.co.uk/register

Frequently asked questions

How often should school policies be reviewed?

Each policy should follow the cycle set by current legislation, DfE guidance, the trust or local authority where relevant, and the governing board's approved schedule. The policy register should show the last approval date, next review date, owner, and publication status.

Who is responsible for approving school policies?

Responsibility depends on the policy and scheme of delegation, but many policies require governing board or trust approval after preparation by the headteacher or designated owner. The approval decision, version, and date should be recorded in the minutes.

What should a school do when a policy is out of date?

The school should assess the possible gap, confirm the current official requirement, assign an owner, and schedule review and approval according to risk and urgency. Any interim control or communication should also be recorded.

What policy evidence should a school keep for inspection readiness?

The school should keep the current approved version, approval date, relevant minute, next review date, owner, version history, and publication record where applicable. These records show the full policy lifecycle rather than just the existence of a document.

How often should a school uniform policy be reviewed?

DfE guidance does not set one fixed review frequency. Governing boards should place the uniform policy on their policy schedule, as they do other statutory and non-statutory policies, and review it at appropriate intervals so it remains fit for purpose. They should review it sooner when supplier arrangements, costs, branded-item requirements or the needs of the school community change. Each review should consider current DfE guidance on cost and affordability and the school's Equality Act 2010 duties where relevant.