Policy Governance Best Practice for School Boards

Most governing boards approve policies. Far fewer have a structured way of doing it.

This article is for chairs of governors, headteachers, clerks to governors and school business managers who want a more deliberate approach to policy oversight - one that holds up in a busy term and holds up under inspection scrutiny. It sets out what good policy governance looks like in practice: who does what, what needs recording, and where the most common gaps appear.

None of this replaces your board's own constitution, your trust's scheme of delegation, or current DfE guidance. It's a practical framework for structuring the parts of policy governance that boards often leave informal.

What policy governance means for a school board

Policy governance is not the same as policy writing. It's the structure a governing board puts around policy - who proposes it, who checks it, who approves it, and how that decision is recorded and reviewed over time.

For many boards, "policy governance" has meant little more than a line on a meeting agenda: a policy is tabled, discussed briefly, and approved by nod. The document itself might be good. The governance around it - the audit trail showing how and when it was properly considered - is often thin or missing entirely.

This matters beyond paperwork. A governing board's core legal function is oversight, not delivery. Policy is one of the clearest, most visible ways governors demonstrate that oversight is real. When a policy is challenged - by a parent, a staff grievance, an incident, or an inspector - the first question is usually not "is this a good policy?" but "how do we know the board actually approved this, and when?" Without structured governance, that question can be surprisingly hard to answer.

The three core responsibilities of a governing board on policy

Governing boards sometimes drift into managing policy detail that should sit with the headteacher. Getting the boundary right starts with three responsibilities that belong to the board, and nothing more:

1. Set direction and approve. The board agrees the school's overall approach and formally approves the policies that give it effect. This is a governance decision, not a drafting exercise.

2. Hold to account. The board checks that approved policies are actually being followed, reviewed on schedule, and having the intended effect - largely through reports from the headteacher and relevant staff, not through direct involvement in delivery.

3. Ensure compliance readiness. The board satisfies itself that statutory and safeguarding-critical policies are current, properly approved, and supported by evidence that would stand up to scrutiny.

What doesn't belong on this list is day-to-day management - drafting policy text, handling individual cases, or managing implementation. That's the headteacher's role, covered in more detail below. Boards that blur this line tend to spend meeting time on wording rather than oversight.

For a fuller view of which policies fall under this oversight duty, see our statutory school policies checklist for governors.

Structuring the approval route

A clear approval route is the backbone of policy governance. At minimum, it should define four steps, each with a named responsible party:

Who drafts. Usually a member of staff with relevant expertise: headteacher, deputy, designated safeguarding lead, SENCO, or business manager.
Who consults. Staff, unions, parents or pupils where relevant - proportionate to the policy's significance.
Who presents. Typically the headteacher, or a nominated staff lead, bringing the policy to committee or full board with a short rationale and summary of changes.
Who approves. The full governing board or a committee acting under delegated authority, per the scheme of delegation.

Every one of these steps needs to be recorded, not just completed. A policy that was properly drafted and consulted on, but only shows "approved" in the minutes with no trail behind it, still leaves a gap. If a question is ever raised about how a policy was developed, the paper trail - not memory - is what answers it.

This is also where many boards lose time unnecessarily late in the term. If you recognise the pattern of policies arriving for approval in a rush before a deadline, our article on how schools can reduce last-minute policy reviews sets out how a structured approval route prevents that.

Policy ownership: assigning and recording owners at board level

Every policy should have a named owner - the individual responsible for keeping it current, initiating review, and answering questions about it. In practice this is usually a senior staff member, such as the headteacher, deputy, DSL or SENCO, rather than a governor, but the board should formally record who that owner is for each policy, not just assume it's understood informally.

Ownership should be minuted at the point of approval and kept in a central log, alongside the policy's version history. Without a recorded owner, review dates get missed by default - nobody flags that a policy is due, because nobody was told it was theirs to flag.

This becomes especially important where staff change roles or leave. A policy owned by "whoever's doing safeguarding" is a governance risk. A policy owned by a named role, reviewed at handover, is not.

Version control: why it matters and what a minimum standard looks like

Version control is one of the simplest things to get right and one of the most commonly neglected. When policies exist in multiple copies - a website PDF, a staff shared drive version, a printed copy in the office - small differences creep in, and nobody is sure which one is current.

At minimum, every policy document should carry:

Version number - even a simple v1, v2, v3 is sufficient
Approval date - the date the board or committee formally approved it
Next review date - set at the point of approval, not left open-ended
Approving body - full governing board, or the specific committee under delegation

These four fields should appear on the policy document itself, not just in a separate spreadsheet. That way, whoever is holding the policy - a staff member, a parent, an inspector - can see at a glance whether it's current.

For guidance on setting sensible review cycles in the first place, see how often should school policies be reviewed.

Building an evidence record that governors can stand behind

Governance only counts if it can be evidenced. An evidence record is the collection of documents that together prove a policy was properly considered, approved, and kept current. For each policy, that typically includes:

The minute recording approval, with date and approving body named
The version of the policy actually approved, not a later edit
A note of any consultation carried out beforehand
A record of when and where the policy was published, such as website, staff handbook or parent communication

The minute itself matters more than boards often realise. "Policy approved" is not sufficient. A stronger minute reads something like: "The governing board reviewed the [policy name], version 3, following consultation with staff in the fifth week of the autumn term, and approved it for publication, with next review due in the summer term." That single sentence does most of the work of an evidence record on its own.

Our article on policy readiness before inspection goes into more detail on how to prepare this evidence in advance rather than reconstructing it under pressure.

The clerk's role in policy governance

The clerk to governors is often the person best placed to hold the governance structure together, even though the decisions themselves belong to the board. A clerk's practical responsibilities in policy governance typically include:

Agenda management - making sure policies due for review are scheduled with enough notice, not added at the last minute
Minute-taking - capturing approval decisions with the detail described above, not just a summary
Version filing - keeping the master copy of each approved policy, with version history, in one place
Publication tracking - confirming when an approved policy actually went live on the website or was communicated to staff and parents

None of this requires the clerk to have subject expertise in the policies themselves. It requires a consistent process, applied every time, regardless of which policy is on the agenda.

Headteacher vs governor responsibilities - where the line sits

This is where governance structures most often break down in practice. The general principle is straightforward: governors approve, headteachers implement. The difficulty is applying it consistently.

Worked example 1 - Behaviour policy. The headteacher drafts the policy, reflecting day-to-day practice and any legal changes. The board's role is to satisfy itself the policy is fair, workable and aligned with the school's values, then approve it. Day-to-day decisions about individual pupil behaviour remain entirely with staff - the board should not be drawn into individual cases.

Worked example 2 - Safeguarding policy update. The DSL identifies a required change following updated guidance. The headteacher presents the proposed change with a clear summary of what's different and why. The board approves the updated version and the clerk records the approval with version detail. Implementation - briefing staff, updating training - is the headteacher's responsibility, reported back to the board rather than decided by it.

Worked example 3 - Complaints policy. The board approves the policy and periodically receives anonymised data on complaints handled under it, to check the policy is working as intended. It does not get involved in the detail of individual complaints unless its own procedures specifically require escalation to governors.

In each case, the board's job ends at approval and accountability - not delivery.

Common governance failures and how to avoid them

These are the gaps that show up most often when boards look closely at their own policy records:

No review date set at approval - leaving policies to drift indefinitely
Unsigned or undated minutes - making it hard to prove when a decision was actually taken
No published version, or an unclear publication record - so the school can't show when a policy went live
Wrong version approved - where the minuted approval doesn't clearly match the document later published
No named owner - so nobody is accountable for the next review

Each of these is a possible gap rather than a certainty of failure - but each is also entirely avoidable with a consistent process, and each is exactly the kind of detail that surfaces quickly under scrutiny.

What good policy governance looks like at inspection

This isn't a script to memorise - it's a readiness benchmark. Under questioning, governors involved in policy oversight should be able to describe, in their own words:

How a policy gets from draft to board approval, and who is involved at each stage
How they would find out when a specific policy was last reviewed and by whom
Who owns a named policy and what happens if that person leaves
Where the evidence of approval is kept, and how quickly it could be produced
How the board satisfies itself that safeguarding-critical policies are current

Governors who can answer these confidently - without needing to check first - are demonstrating governance readiness, not just policy readiness. Our inspection readiness checklist for school leaders covers this alongside other board evidence areas.

FAQ

Does every policy need full governing board approval, or can committees approve on the board's behalf? This depends on your scheme of delegation. Many boards delegate approval of lower-risk policies to committees, while reserving safeguarding-critical and statutory policies for full board approval. Whatever the arrangement, it should be written down and consistently followed.

How often should policy governance itself be reviewed, separate from individual policies? Many boards review their overall approach to policy governance annually, often alongside a governance self-evaluation, rather than only reviewing individual policy documents on their own cycles.

Who should hold the master version of an approved policy? Typically the clerk to governors, working with the school office or business manager, so there is one agreed source of truth rather than multiple copies in different places.

What happens if a policy is found to be out of date at inspection? An overdue review is a possible gap to flag and act on, not automatically a serious failure. What tends to matter more to inspectors is whether the board has a functioning process for catching this itself, rather than relying on inspection to find it.

Can academies and maintained schools use the same governance structure for policy approval? The broad principles - clear approval routes, named ownership, version control and evidence records - apply to both. Specific delegation arrangements will differ between maintained schools and academies, so check your own governance documents and current DfE guidance.

See how Edvance supports board-ready policy governance

Edvance helps school boards structure policy oversight with clear approval routes, owner assignment, version control and evidence records that governors can stand behind - reducing reliance on memory, email threads and last-minute searches before a meeting or inspection.

Book a governance readiness demo to see how Edvance helps school boards structure policy oversight, approval records and evidence trails.

For schools in Ireland, see the related article: Policy Governance Best Practice for Boards of Management.

This article reflects general best practice for school policy governance in England and is not legal advice. Governing boards should review their approach against current DfE statutory guidance and their own legal or HR advice before making governance decisions.

Frequently Asked Questions

Does every policy need full governing board approval, or can committees approve on the board's behalf?

This depends on the scheme of delegation. Many boards delegate lower-risk policy approval to committees while reserving safeguarding-critical and statutory policies for the full board.

How often should policy governance itself be reviewed?

Many boards review their overall approach to policy governance annually, often alongside a governance self-evaluation.

Who should hold the master version of an approved policy?

Typically the clerk to governors, working with the school office or business manager, so there is one agreed source of truth.

What happens if a policy is found to be out of date at inspection?

An overdue review is a possible gap to flag and act on. Inspectors are likely to look for whether the board has a functioning process for catching and addressing it.

Can academies and maintained schools use the same governance structure for policy approval?

The broad principles apply to both, but specific delegation arrangements differ, so schools should check their governance documents and current DfE guidance.