Statutory Compliance Monitoring in Schools – How Should Schools Monitor, Evidence and Assure Compliance?

Knowing what a school needs to monitor is only the starting point.

The harder question is whether the school has a reliable system for making sure required inspections, assessments, examinations, servicing and other compliance activities actually happen — and, crucially, whether problems identified through them are acted upon.

A school can have folders full of certificates and contractor reports and still have significant compliance gaps.

Effective statutory and premises compliance management therefore needs to connect:

Requirement → Responsibility → Schedule → Inspection/Test/Assessment → Evidence → Findings → Actions → Escalation → Completion → Assurance

The objective is not simply to demonstrate that an inspection took place. It is to demonstrate that the school understands its compliance position and is managing the significant issues identified.

What does compliance monitoring mean in a school?

For the purposes of this guide, compliance monitoring means the system a school or trust uses to maintain oversight of its premises and related statutory compliance arrangements.

Depending on the school and estate, this can involve areas such as fire safety, asbestos, electrical safety, gas, water hygiene, lifting equipment, work equipment and other premises risks. The statutory compliance checklist for schools remains the detailed SchoolSafe guide to the areas schools may need to monitor.

Compliance monitoring is not simply:

• keeping a calendar;
• storing certificates;
• paying contractors;
• receiving service reports; or
• maintaining a spreadsheet showing green status.

A useful system needs to establish what applies, who is responsible, what evidence exists, what problems have been identified and whether necessary actions have actually been completed.

Start by establishing what applies to your school

Before a school can monitor compliance effectively, it needs to understand the requirements that apply to its premises, equipment and activities.

This can vary considerably between schools.

Factors may include:

• school type and governance arrangements;
• ownership and control of premises;
• age and construction of buildings;
• boarding or residential accommodation;
• specialist teaching areas;
• plant and equipment;
• catering facilities;
• water systems;
• lifts and lifting equipment;
• asbestos-containing materials;
• sports and play facilities;
• grounds and trees;
• recent construction or refurbishment; and
• contractual or landlord arrangements.

This is why simply downloading a generic compliance calendar can be problematic.

A template can provide a useful starting point, but the school still needs to establish which requirements apply to its own estate and who is responsible for managing them.

Build a live compliance register

Once the school understands what it needs to manage, that information should be brought together into a usable compliance register or equivalent system.

The system does not need to be complicated software.

Depending on the size and complexity of the organisation, it might be a structured spreadsheet, database, premises-management system or trust-wide compliance platform.

The important issue is what the system tells you.

For each relevant compliance area, a useful register might identify:

• asset, building or compliance area;
• requirement or control being monitored;
• responsible person or role;
• competent contractor/provider where applicable;
• relevant inspection, assessment, servicing or examination arrangements;
• last activity/completion date;
• next required action or review point where established;
• location of supporting evidence;
• significant findings or defects;
• outstanding actions;
• action owner;
• target date or priority;
• current status; and
• escalation where required.

The register should operate as a management tool rather than simply an archive of historical dates.

Be clear about responsibility

One of the most common weaknesses in school compliance management is uncertainty about ownership.

A contractor may carry out an inspection, but that does not necessarily mean the contractor owns the school's subsequent actions.

Likewise, a site manager may coordinate appointments without holding the organisation's underlying legal duty.

Schools and trusts should distinguish between:

• Duty or accountability — where the relevant legal or organisational responsibility sits.
• Operational responsibility — who arranges and coordinates the activity.
• Technical competence — who is competent to undertake the specialist inspection, assessment, examination, servicing or remedial work.
• Action ownership — who ensures findings are addressed.
• Assurance — who needs visibility that the system is working.

These roles may involve different people.

The precise legal dutyholder arrangements vary according to the subject and type of school, so schools should avoid assuming that every statutory responsibility automatically sits with the premises manager, headteacher or contractor.

The contractor report is not the outcome

A common compliance failure occurs when the process is treated as complete once a contractor has attended.

Consider the difference:

“The inspection has been completed.”

versus:

“The inspection has been completed, the report has been reviewed, significant findings have been identified, actions have been allocated and completion is being tracked.”

The second is a compliance-management process.

When a report, certificate or assessment is received, an appropriate person should consider whether it identifies:

• defects;
• recommendations;
• limitations;
• failed items;
• inaccessible areas;
• further investigation;
• remedial work;
• changes to risk;
• actions for the school; or
• matters requiring escalation.

A document marked “completed” in a tracker should not automatically mean the underlying compliance issue is complete.

Understand what the report is telling you

Contractor and specialist reports can vary significantly in quality and clarity.

Some clearly distinguish urgent defects from recommendations. Others contain technical codes, observations or limitations that may not be immediately meaningful to school staff.

Where the significance of a finding is unclear, the school should seek appropriate clarification rather than simply filing the document.

A practical review might ask:

• Was the intended scope completed?
• Were any areas, assets or systems excluded or inaccessible?
• Did anything fail?
• Were defects identified?
• Has further investigation been recommended?
• Are there actions for the school?
• Is anything potentially urgent or significant?
• Does another risk assessment, register or compliance record now need updating?

The person reviewing the report does not need to reinterpret specialist technical findings beyond their competence. Where necessary, competent advice should be sought.

Turn findings into actions

Once a defect or recommendation has been identified, it should move into an action-management process.

A useful action record should establish:

• what the issue is;
• where it is located;
• source of the finding;
• significance or priority;
• immediate controls where required;
• action required;
• person responsible;
• target date;
• current status;
• supporting evidence; and
• completion/verification.

Avoid allowing actions to remain buried within PDFs or contractor reports.

If a fire risk assessment contains 15 actions, an electrical report identifies defects and a water-hygiene assessment identifies remedial measures, the school needs a way of seeing those outstanding issues collectively rather than expecting managers to repeatedly reopen individual reports.

Prioritise according to risk

Not every compliance action carries the same significance.

Schools should therefore avoid managing every defect solely according to the date it was raised.

The priority should reflect the nature of the issue, potential consequences, people exposed, existing controls, specialist advice and any relevant requirements applying to the particular issue.

Some findings may require immediate action or temporary controls.

Others may reasonably form part of planned remedial works.

The important point is that the prioritisation is understood and deliberate rather than being determined by whichever contractor follows up most often.

Where a specialist report provides a priority or classification, the school should understand what that means before translating it into its own action-management system.

Escalate overdue and significant actions

A compliance tracker becomes ineffective if actions can remain overdue indefinitely without anyone noticing.

Schools should establish an escalation process proportionate to the significance of the issue.

This might consider:

• high-risk or significant findings;
• actions that remain overdue;
• repeatedly deferred work;
• interim controls that cannot be maintained indefinitely;
• recurring defects;
• areas where required evidence cannot be located;
• contractor performance issues; and
• significant expenditure or capital works required to resolve a problem.

Escalation does not necessarily mean every overdue action goes directly to governors.

It means the organisation has a defined way of ensuring important unresolved issues become visible at the appropriate management level.

Don't close an action simply because an invoice has been paid

One of the most useful questions in compliance management is:

How do we know the problem was actually fixed?

An invoice, job sheet or contractor email may demonstrate that work was undertaken, but the level of verification required should reflect the issue.

Depending on the work, evidence might include:

• contractor completion information;
• certification or test results where applicable;
• photographs;
• physical inspection;
• updated drawings or records;
• commissioning information;
• revised risk information;
• specialist confirmation; or
• follow-up inspection.

The objective is not to create unnecessary administration.

It is to avoid closing significant compliance actions without reasonable evidence that the required outcome has been achieved.

Fire doors provide a useful example

A fire-door inspection might identify a number of defects.

Simply recording that the annual or periodic inspection occurred tells senior leaders very little about the current condition of the doors.

A better compliance process would establish:

Inspection completed → defects reviewed → actions prioritised → repairs allocated → completion evidenced → significant repairs verified → register updated

This is set out in more detail in Fire Doors in Schools – Checks, Defects and Effective Management.

The same management principle can be applied across other compliance areas without assuming that every technical regime has identical requirements.

Capture changes to the estate

Compliance systems can quickly become inaccurate if changes to buildings, equipment or activities do not feed back into them.

Examples might include:

• refurbishment;
• extensions;
• new plant;
• new equipment;
• changes to room use;
• access-control installations;
• electrical alterations;
• new water outlets;
• removal or relocation of equipment;
• changes to fire precautions;
• changes to occupancy;
• contractor penetrations through walls or ceilings; and
• newly identified asbestos information.

A project may be successfully completed while still creating a compliance-management gap if the relevant register, maintenance programme or risk information is never updated.

Change management should therefore form part of the school's contractor management and project handover process.

Monitoring the system itself

Compliance management needs monitoring at two levels.

The first is whether individual activities are taking place.

The second is whether the system itself is working.

Useful management questions include:

• are scheduled activities being completed?
• are reports being received?
• are reports being reviewed?
• are significant findings becoming actions?
• are actions being completed?
• are overdue items being escalated?
• are recurring problems being identified?
• are changes to the estate being captured?
• can supporting evidence be found?
• do responsible managers understand their role?

This moves the organisation from simply tracking dates towards obtaining meaningful assurance.

How often should the compliance system be reviewed?

There is no single universal review interval appropriate to every element of a school's compliance system.

Different statutory and technical regimes have different requirements, and review arrangements may also be influenced by risk assessments, competent advice, equipment, manufacturers' information and the particular circumstances of the premises.

Schools should therefore avoid treating a generic compliance calendar as the legal source for every inspection or servicing frequency.

Instead, the compliance system should record the arrangements that have been established for each relevant area and provide sufficient oversight to identify when required activity or actions are becoming overdue.

The management system itself should also be reviewed when significant changes occur, such as building projects, new equipment, changes in responsibility or significant findings from inspections and assessments.

Providing assurance to senior leaders

Senior leaders do not normally need every certificate or technical report reproduced in management meetings.

They need sufficient information to understand whether the compliance system is functioning and where significant concerns exist.

A useful compliance summary might therefore show:

• overall status of key compliance areas;
• significant inspections or assessments completed;
• missing or overdue activities;
• high-priority outstanding actions;
• overdue actions;
• significant new findings;
• recurring issues;
• major remedial projects;
• areas requiring management decisions; and
• significant limitations in the available assurance.

RAG ratings or dashboards can help present this information, but only if the underlying status is meaningful.

A green box should mean more than “a contractor attended”.

Governors and trustees – assurance rather than administration

Governors and trustees should not normally need to manage individual maintenance actions.

Their role is better supported by proportionate assurance information that allows them to understand whether appropriate systems exist and whether significant risks or unresolved issues are being managed.

Depending on governance arrangements, useful assurance information might include:

• significant compliance risks;
• material overdue actions;
• major fire or premises issues;
• significant audit or assessment findings;
• trends in outstanding actions;
• major planned remedial programmes;
• limitations in compliance evidence; and
• management assurance that appropriate systems are operating.

Schools should distinguish between good governance reporting and specific statutory reporting requirements. There is no universal legal requirement for governors or trustees to receive a particular compliance dashboard, report format or reporting frequency.

The wider discussion of H&S inspections, audits, incidents and governance oversight is covered in How is health and safety monitored in schools?

Compliance monitoring across a multi-academy trust

Trusts face an additional challenge: achieving consistency across multiple schools without assuming every site is identical.

A trust-level system can provide useful consistency in:

• terminology;
• compliance categories;
• evidence expectations;
• action status;
• escalation;
• reporting;
• contractor arrangements; and
• assurance.

However, central oversight does not remove the need to understand individual sites.

Different schools may have different buildings, plant, risks, contracts and legacy information.

A trust dashboard showing every school as green is only meaningful if the underlying information has been checked and the criteria for green status are understood.

Effective trust-level monitoring therefore combines common systems with appropriate local ownership and evidence.

Common compliance-monitoring failures in schools

The spreadsheet is green but the reports haven't been read

Dates are tracked successfully, but findings and remedial actions are not.

Actions remain inside individual reports

There is no central view of outstanding issues across fire, electrical, water, asbestos and other compliance areas.

Nobody owns the action

The contractor identified the issue, the site team received the report and the business manager paid the invoice — but nobody was clearly responsible for resolving the defect.

Overdue actions simply stay overdue

There is no escalation process for significant or repeatedly deferred issues.

Completion is assumed

Actions are closed when work is ordered or invoiced rather than when there is reasonable evidence of completion.

The register doesn't reflect the current estate

New plant, refurbished areas and building alterations never make their way into the compliance system.

The system relies on one person

Knowledge exists in the head of an experienced site or business manager but is not sufficiently documented to remain effective during absence or staff turnover.

Every school in a trust is treated identically

A central template is applied without accounting for differences in premises, equipment and local risks.

Compliance is measured by paperwork volume

The presence of certificates is treated as evidence of effective compliance management without considering their findings or limitations.

When is independent review useful?

Independent review can be useful where a school or trust:

• is unsure whether its compliance register is complete;
• has inherited fragmented or inconsistent records;
• has significant outstanding actions;
• has recently changed estates personnel;
• is integrating schools into a trust-wide system;
• has undergone significant building work;
• cannot reconcile contractor reports with its action tracker;
• wants assurance that its monitoring process is operating effectively; or
• needs an objective view of areas requiring improvement.

The purpose should be to test the effectiveness of the management system rather than simply generate another report for the compliance folder.

How effective is your current compliance system?

The SchoolSafe Systems Compliance Scorecard can help schools review their wider compliance arrangements and identify areas that may need greater attention.

How SchoolSafe Systems can help

SchoolSafe Systems provides independent health and safety and compliance support to schools and academy trusts.

Support can include reviewing compliance-management arrangements, registers, evidence, outstanding actions and assurance processes to help schools establish a clearer and more manageable picture of their current position.