MAT Policy Management: Keeping Policies Consistent Across Schools

A trust policy can be current in the central folder while several academies still use an earlier version. A newly joining school may have a complete policy library whose approval routes, terminology and review dates differ from the trust's. Consistency therefore needs more than a shared template: it needs an agreed way to control changes, preserve necessary local detail and show what is in use.

This guide offers a practical workflow for multi-academy trusts in England. Use it to connect each master policy to its academy versions, approval evidence and next review. The aim is a useful governance readiness record, with differences and unfinished work visible to the people responsible for resolving them.

Decide what is common and what can vary

For each policy, distinguish the trust's common position from information that needs local completion. A model might contain agreed principles and processes, alongside an academy appendix for relevant contacts or operational arrangements. Identify which fields may be completed locally and which changes need a separate decision. Do not assume every policy can use the same structure.

The DfE's academy trust governance guide says boards decide whether and how to delegate policy creation, maintenance and approval unless relevant guidance states otherwise; boards remain accountable. Check policy-specific requirements alongside the trust's governing documents. A model policy is not permission to override those requirements.

Use the scheme of delegation checklist to confirm the approval route. This article concerns how versions follow that route, rather than redesigning the trust's governance structure. Record who drafts, who checks local context, who approves and who confirms implementation for each policy family.

Give the master version a clear owner

Name a subject lead responsible for the master content and an administrative owner for the register. In a smaller central team, one person may do both, but the responsibilities should still be explicit. Give each policy a stable identifier, version number, approval record, effective date and next review date. Separate drafts from approved versions.

Extend the fields in the school policy tracker guide with a master-version reference, academy coverage, local variation status and implementation evidence. One master record can link to several academy records. This avoids maintaining unrelated rows that happen to have similar titles but cannot be compared reliably.

For example, if master version 3 is approved, the register should show which academies use it, which need a revised appendix and which are awaiting action. Do not replace the old approval date with the latest file-upload date. Those dates answer different questions about the policy's history.

Reconcile inherited policies when an academy joins

Agree a policy handover with the joining school's leaders. Ask for the current policy list, approved documents, review dates, approval evidence and any known gaps or pending changes. Preserve a dated baseline so the trust can distinguish inherited issues from later decisions. Include documents used by staff, not just the files easiest to find centrally.

Compare each inherited policy with the trust's corresponding model and classify the next step: retain temporarily pending review, adopt the model, adapt with approval, or investigate missing information. Record the reason, owner and target date. These are suggested working statuses, not a standard DfE classification or permission to retain an unsuitable policy.

Prioritise using the significance of the difference, upcoming deadlines and the practical effect on pupils or staff. Seek specialist advice where a change may affect contractual arrangements or consultation requirements. Avoid replacing an inherited set overnight simply to make the register look uniform. Agree interim arrangements through the proper authority and keep unresolved questions visible.

Make local variations explicit and reviewable

Use a variation record that identifies the master version, affected academy, proposed wording, reason and approval route. Attach the relevant advice or local evidence. Distinguish completing an authorised field from changing a substantive rule. If a principal proposes a different process, check whether it falls within an existing permission before treating it as a routine edit.

The authorised decision should say what is approved, when it takes effect and when it will be reconsidered. A rejected or deferred request also needs a clear outcome. Local leaders should be able to see what they may use while an issue is being resolved, without relying on an informal email chain.

When the master changes, revisit linked variations. A variation approved against version 2 may no longer fit version 3. Flag it for manual review and record the result. Keep superseded versions under the trust's retention arrangements while directing everyday users to the current approved material.

Run a planned review and change cycle

Build the review calendar around the applicable requirements and the trust's meeting timetable. The DfE governance guide recommends annual review of policies related to the statutory guidance and resources it lists. Confirm any policy-specific timing, consultation and approval requirements; a general calendar cannot replace those checks. Allow time for academy feedback before the decision date.

A practical cycle is to review the source guidance, assess the master and local variations, consult where needed, approve through the agreed route, communicate the change and check implementation. Assign an owner and evidence field to each stage. Schedule additional review when a material change, incident or joining academy creates a reason to act sooner.

Check the effective date of new guidance before changing the policy. As at 11 September 2026, the Academy Trust Handbook collection identifies the 2025 edition as effective from September 2025 and the 2026 edition as effective from 1 October 2026. Record any relevant transition action separately from the current position.

Check adoption through a small evidence sample

After approval, ask each academy to confirm the version it uses and any associated briefing or local action. Where publication is required, include confirmation that the appropriate version is available. Keep this step connected to the policy register so an approval record is not mistaken for completed implementation.

Choose a proportionate sample to check the returns. For example, ask a colleague at two academies to locate the current policy, identify the local appendix and explain a changed process. Record what was checked, the date and any limitation. If an academy still uses an earlier version, assign a suggested next action and verify the correction.

Give trustees a clear account of exceptions

Present a readiness snapshot showing policies due for review, overdue actions, unapproved variations and academies awaiting implementation checks. Explain the significance of exceptions and the support or decision needed. Distinguish “approved”, “communicated” and “implementation checked” so a single completion percentage does not conceal unfinished work.

Link the summary to underlying versions, decisions and follow-up evidence. The central-team oversight guide explains the wider assurance trail and how to respond to a DfE request. For policy matters, make the chain retrievable from master approval to academy use, and match any external response to the actual request's scope and period.

At the next review, check whether recurring exceptions point to an unclear template, an unrealistic timetable or missing support. Update the working process as well as individual files. Consistency is strongest when people understand what they can adapt, where approval sits and how to raise a possible gap before it spreads across the trust.

Frequently Asked Questions

Must every academy use identical policy wording?

Check the requirements for the policy and the trust's approved approach. A common model can allow clearly defined local information or approved variations. Record what may change and who can authorise it rather than assuming all differences are permitted or prohibited.

What should happen to policies when an academy joins a trust?

Capture the inherited set and its approval evidence, compare it with trust models and assign a prioritised reconciliation plan. Confirm interim arrangements and obtain relevant advice before making changes that may require consultation or affect existing commitments.

How should the central team track local policy variations?

Link each variation to its master version and academy, with the reason, approved wording, decision record and review date. Recheck the variation when the master changes so earlier permissions are not carried forward without review.

What evidence helps trustees oversee policy consistency?

Provide a readiness snapshot of reviews, variations and implementation checks, with clear exceptions and owners. Link it to approval records and academy evidence, distinguishing an approved document from a change that has been communicated and checked in use.