School Policy & Compliance Tracker: 18 Fields

A school policy tracker is only useful if it records more than a list of document names. Governors, headteachers and school business managers need to know which policies exist, who owns them, when they were last reviewed, where the approved version is stored, and whether the public website matches the current file.

For maintained schools in England, policy tracking is part of everyday governance discipline. It helps the governing body see whether required policies, statutory publication items and review cycles are being managed deliberately rather than by memory.

This guide sets out the core information a school policy tracker should record and how to make it useful for governor oversight.

This article covers the full record structure. For the companion scheduling view, see Policy Review-Date Tracker: Setting Owners and Early-Warning Dates, which focuses on dates, named owners and reminders before reviews become overdue.

Why a basic spreadsheet often fails

Many schools start with a simple spreadsheet. That can work for a small list, but it often becomes unreliable when the tracker needs to manage:

Policies across several hubs, such as safeguarding, admissions, behaviour, finance and SEND.
Different approval routes, such as headteacher, governing body, committee or local authority.
Website publication requirements.
Review dates and event-triggered updates.
Evidence files, meeting minutes and version history.
Multiple owners across school leadership, office, governance and business management.

The issue is not the spreadsheet itself. It is that the tracker has to represent a live governance process, not just a static inventory.

The core fields every policy tracker should include

A practical tracker should capture the following fields for every policy or statutory document.

Policy title

Use the exact title of the approved document. Avoid vague labels such as "safeguarding" if the actual document is "Child Protection and Safeguarding Policy". Consistent naming makes it easier to match the tracker, document library and website.

Policy category

Group policies into clear categories such as safeguarding, admissions, behaviour, attendance, SEND, curriculum, health and safety, governance, finance, HR, data protection and website publication. This helps governors review high-risk areas without reading a long flat list.

Requirement status

Record whether the item is statutory, DfE recommended, locally required, trust or local authority required, or operational good practice. Where the answer is not clear, use "check required" and assign an owner.

Jurisdiction and school type

If your organisation works across different school types or jurisdictions, record whether the policy is for maintained schools in England, academies, independent schools, Ireland or another context. This prevents guidance from one setting being copied into another.

Policy owner

Every policy needs an internal owner. That may be the headteacher, deputy headteacher, DSL, SENCO, school business manager, governance professional, clerk, premises lead or office manager.

Approval route

Record whether the policy is approved by the full governing body, a committee, the headteacher, the local authority, a trust or another responsible body. This avoids sending operational policies through the wrong route and helps governors see where their formal approval is required.

Last approved or adopted date

Record the date the current version was approved or adopted. This should match the policy front page and the meeting record where relevant.

Last reviewed date

The review date may be different from the approval date. Some reviews confirm that no change is needed. The tracker should still show that the review happened.

Next review date

Record the next planned review date and make it visible. For high-risk policies, use a shorter cycle or an annual Board or governor check where required.

Review frequency

Use simple values such as annual, two-yearly, three-yearly, termly check, or event-triggered. This makes it easier to sort the tracker by upcoming work.

Evidence location

Record where the evidence sits: governor minutes, committee minutes, approval paper, consultation record, signed policy file, website page, shared drive folder or local authority confirmation.

Publication status

Show whether the document is published on the school website, available on request, internal only, or not applicable. Do not assume that an approved policy has been published.

Live website URL

Where a policy or statutory statement is published, include the live URL. This makes broken links and old versions easier to spot.

Current status

Use a clear status such as current, due soon, overdue, awaiting approval, awaiting publication, archived or check required. Avoid ambiguous labels that do not trigger action.

Free tracker template: 18 fields to copy

Use the table below as the column structure for a spreadsheet or shared register. It combines the core record, publication controls and governor-oversight fields into one school compliance tracker. If you are starting with the review process rather than the full register, use the free policy review checklist alongside it.

Field	What to record
Policy title	Exact title of the current document
Policy category	Safeguarding, admissions, finance, SEND or another useful group
Requirement status	Statutory, DfE recommended, local, trust, operational or check required
Jurisdiction and school type	The setting to which the record applies
Policy owner	One named role or person accountable for the next step
Approval route	Governing body, committee, headteacher, trust or another route
Last approved or adopted date	Date of the formal approval or adoption decision
Last reviewed date	Date the content was last checked, even if no change followed
Next review date	The next planned review point
Review frequency	Annual, two-yearly, three-yearly, termly or event-triggered
Evidence location	Link to minutes, approval paper, consultation or signed file
Publication status	Published, available on request, internal, not applicable or outstanding
Live website URL	Direct link to the public version where relevant
Current status	Current, due soon, overdue, awaiting approval or another action state
Risk rating	High, medium or low using the school's agreed approach
Governor or committee oversight	The link governor, committee or board receiving assurance
Meeting due date	Meeting where review, approval or assurance is scheduled
Action required	Plain-English next step, owner and target date

Governor oversight fields

A school leadership tracker can be detailed, but governors usually need a sharper oversight view. Add these fields for governing body reporting.

Risk rating

Use high, medium or low. High-risk policies usually include safeguarding, child protection, behaviour, admissions, health and safety, SEND, complaints, data protection and finance controls.

Governor or committee oversight

Record the relevant committee or link governor where applicable. This helps avoid duplication and makes it easier to schedule committee work.

Meeting due date

Record the meeting where the policy is expected to be reviewed, approved or noted. This turns the tracker into a forward planner for agendas.

Action required

Write the next action in plain English: update website, send for consultation, check DfE guidance, approve at next FGB, remove old version, or confirm local authority link.

What to track for website publication

Publication needs its own controls because the website can drift away from the approved policy file. For each public-facing item, record:

Whether publication is required, recommended or optional.
The live URL.
Date last checked on the website.
Whether the live version matches the approved version.
Who is responsible for uploading changes.
Whether a paper-copy route is offered where required.
Whether the page has duplicate or old downloads.

This is especially important for maintained schools because DfE guidance sets out information that must or should be published online.

Review-cycle rules to build into the tracker

The tracker should support both scheduled and event-triggered reviews.

Scheduled reviews might include:

Annual checks for safeguarding, website publication, governance membership, financial publication and other high-risk items.
Two-year reviews for behaviour, attendance, SEND, data protection and digital-use policies where no specific shorter cycle applies.
Three-year reviews for lower-risk operational policies.

Event-triggered reviews should happen after:

New DfE guidance or statutory updates.
Keeping Children Safe in Education updates.
A safeguarding, behaviour, health and safety or data incident.
An Ofsted inspection, complaint or governance review finding.
A change in admissions, staffing, premises, systems or school structure.
Governor concern that evidence or publication is incomplete.

A strong tracker records the trigger as well as the new review date.

Common tracker mistakes

Schools often run into the same tracker problems:

The tracker says the policy is current, but the evidence file is missing.
The policy owner is a role that no longer exists.
Review dates were rolled forward without actual review.
The website URL is missing, so publication cannot be checked quickly.
The policy title in the tracker does not match the document title.
Statutory and recommended items are mixed together without a status field.
Governor approval and operational review are treated as the same thing.
Old policies are kept live on the website after new versions are approved.

These are process gaps rather than technology problems, but the right tracker makes them visible.

A simple workflow for each term

A termly policy-tracker workflow can be lightweight:

Sort policies due in the next term.
Filter high-risk policies first.
Check whether any DfE or local authority updates affect the list.
Confirm owners and approval routes.
Add policies due for governor or committee review to the forward agenda.
Check that website links still point to current versions.
Report overdue or missing-evidence items to governors.

This gives governors a clear view without burying them in document administration.

How Edvance helps

Edvance helps schools replace scattered policy spreadsheets with a clearer governance workflow. It can help you:

Record owners, approval routes, review dates and publication links.
Flag missing evidence or potentially overdue policies.
Keep governor oversight separate from operational detail.
Separate maintained-school, academy, UK and Ireland requirements.
Prepare a Board or governor-ready policy status view.

Get free access to Edvance

FAQs

What is the most important field in a policy tracker?

The most important field is the next action, because it turns the tracker from a list into a workflow. After that, review date, owner, approval route and evidence location are essential.

Should every policy have a governor approval date?

No. Some policies require governing body or committee approval, while others are operational. The tracker should record the correct approval route for each policy rather than forcing every document through the same process.

How often should a school update its policy tracker?

At minimum, update it each term and after every policy approval, DfE guidance change, inspection finding, complaint pattern, serious incident or website publication change.

Should website publication be tracked separately?

Yes. Approval and publication are different controls. A policy can be approved but missing online, or published online in an old version. Track both.

Can Edvance import an existing spreadsheet?

A spreadsheet can be a useful starting point. The important step is cleaning the fields so the register can show owner, review date, approval route, evidence and publication status consistently.

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.

What is a school policy compliance tracker?

A school policy compliance tracker is a policy register that brings the information needed for oversight into one place: the current policy and version, named owner, last approval and next review dates, approval route, publication status, and links to minutes or other evidence. It supports compliance tracking by making possible gaps and next actions visible; it does not by itself confirm that every policy meets the latest requirement.

What should a school compliance tracker include?

A school compliance tracker should show the item, category, requirement status, school type, owner, approval route, approval and review dates, review frequency, evidence location, publication status, live URL, current status, risk, governor or committee oversight, meeting date and next action.

Sources

Department for Education, Maintained schools governance guide.
Department for Education, What maintained schools must or should publish online, updated 24 October 2024.
Keeping Children Safe in Education.
School Information (England) Regulations 2008, as amended.
Equality Act 2010.