Compliance software for schools
Compliance software for UK schools
EduComply turns the contractor certificates and survey reports your school already receives into a live, inspection-ready compliance record - automatically. Forward a certificate by email and the evidence, expiry dates and follow-up actions update themselves.
What is school compliance software?
School compliance software is a system that keeps track of a school’s statutory and estates compliance - fire, asbestos, electrical, water, gas and more - so the school can show, at any moment, what is covered, what is due, and what has lapsed. EduComply does this by reading the compliance documents a school already receives, linking them to the relevant requirements as evidence, and updating the compliance position automatically.
It is not a shared drive or a spreadsheet. Instead of filing PDFs and hoping someone remembers the renewal date, EduComply extracts the data from each document, tracks the recurring checks that sit alongside it, and surfaces risk early - so nothing quietly expires between inspections.
Who it is for
EduComply is built for the people responsible for keeping a school safe and compliant, whether that is a single school or one school within a larger trust.
Estates and compliance leads
The person who has to know, on any given day, whether the school is compliant and can prove it.
School business managers
Juggling compliance alongside finance, HR and operations, and needing it to run without constant manual chasing.
Site and premises teams
Carrying out and recording the recurring checks - weekly, monthly and annual - that keep the estate safe.
Headteachers and SLT
Accountable for statutory compliance and needing a clear, current picture rather than a pile of certificates.
The compliance-administration problem
Statutory and estates compliance generates a constant stream of certificates, reports and recurring checks from many different contractors, all renewing on different dates. Managed manually, it is slow, easy to let slip, and hard to evidence when an inspector arrives.
- •Certificates arrive by email and get filed - or missed - across inboxes and shared drives.
- •Renewal and re-inspection dates live in people’s heads or a spreadsheet that goes stale.
- •Remedial actions from a report get lost between the survey and the fix.
- •When an inspector or auditor asks for proof, assembling it is a scramble.
How requirements, evidence, checks and actions connect
EduComply models compliance as a state that keeps itself current from real-world evidence, not a to-do list you maintain by hand.
- 1
Requirements
Each school has a set of compliance requirements - the things it must keep in date, per regime, drawn from statutory templates.
- 2
Evidence
Documents are read and linked to the requirements they satisfy. Valid, in-date evidence is what makes a requirement compliant.
- 3
Operational checks
Recurring checks - weekly, monthly, annual - are generated automatically and tracked alongside document evidence.
- 4
Actions
Where a document shows a defect or a check is overdue, follow-up actions are raised and tracked to completion.
- 5
Status
The compliance position for each requirement, regime and school is computed from valid evidence - deterministically, never from UI guesswork.
- 6
Reassessment
When evidence expires or a new certificate supersedes an old one, the status updates on its own.
What EduComply does today
Automated document handling
- Forward contractor certificates and reports in by email, or upload them.
- Automatic classification of the document and the compliance regime it relates to.
- Data extraction - issue and expiry dates, outcomes, and defects - from the document.
- Evidence linked to the requirements it satisfies, with the compliance status updating automatically.
Evidence expiry and reassessment
- Every piece of evidence carries validity dates; expired evidence stops counting toward compliance.
- A newer certificate supersedes the one it replaces, keeping the record clean.
- Requirements move back to "attention needed" as their evidence lapses - no manual reset.
Recurring operational checks
- Weekly, monthly and annual checks generated automatically from each requirement’s schedule.
- Checks completed on-site from a mobile web app, with photos captured in the field as proof.
- Overdue checks escalate through configurable rules to the right person.
Visibility, actions and reporting
- A single work queue of what needs attention, prioritised overdue-first.
- Remedial actions tracked from a document’s findings through to verified completion.
- A compliance heatmap by regime, plus exportable, audit-ready reports.
- Building-level applicability, so requirements can be scoped and recorded building by building where an estate spans several.
An example: a fire alarm service certificate arrives
This is the end-to-end path a single document takes, with no manual data entry.
- 1
The certificate is forwarded in
A contractor emails the annual fire alarm service certificate; the school forwards it to its EduComply address (or it is ingested directly).
- 2
It is read and classified
EduComply recognises the document, its regime, the service date and the next-due date, and any defects noted.
- 3
Evidence is linked
The certificate is attached to the school’s fire alarm requirement as evidence, with its validity dates.
- 4
Status updates automatically
The fire alarm requirement shows compliant, and the next-due date drives the reminder for the following service.
- 5
Any defects become actions
If the certificate flags a fault, a remedial action is raised and tracked until it is resolved and verified.
- 6
The record is inspection-ready
The evidence, dates and history are there to show an inspector immediately - no scramble.
Supported compliance areas
EduComply covers the core statutory and estates regimes schools have to manage. Each area has a practical guide to the underlying legal duty.
Evidence and auditability
Compliance in EduComply is evidence-driven. A requirement is compliant because valid, in-date evidence proves it - not because someone ticked a box. Completing a task never marks compliance as met on its own; only accepted, non-expired evidence can.
Every document, evidence link, check and action is recorded, and changes are captured in an audit trail with who did what and when. When an inspector or auditor asks for proof, the evidence and its history are already assembled rather than reconstructed after the fact.
Onboarding
Getting started is designed around the documents you already hold. Your existing certificates and reports are ingested and matched to the right requirements, so the compliance picture is built from real evidence rather than manual data entry.
From there, recurring checks are scheduled and the school’s live position comes into view. We work closely with the teams onboarding so the setup reflects how your school actually manages compliance.
Security and data hosting
EduComply is hosted in the UK, with data encrypted in transit and at rest, role-based access control, per-school data separation, and a full audit trail. Sign-in is via your organisation’s Google or Microsoft account.
Read how EduComply protects school and trust data, including hosting, encryption, access control and audit trails.
Frequently asked questions
- How is this different from a shared drive or a spreadsheet?
- A shared drive stores files; a spreadsheet records dates you have to keep updating by hand. EduComply reads each document, links it to the requirement it satisfies, tracks the recurring checks around it, and computes the compliance status automatically - so the record stays current on its own and is ready to show at inspection.
- Do I have to enter data manually?
- The aim is zero manual data entry for the core flow. You forward or upload a certificate and EduComply extracts the dates and outcomes, links the evidence, and updates the status. You confirm and manage exceptions rather than typing records in.
- What happens when a certificate expires?
- Every piece of evidence has validity dates. Once evidence expires it stops counting toward compliance, the requirement moves back to needing attention, and it surfaces in the work queue - so lapses are caught rather than sitting unnoticed until the next inspection.
- Which compliance areas does it cover?
- The core statutory and estates regimes schools manage: fire (risk assessments, alarms, emergency lighting), asbestos, electrical (EICR and PAT), water and legionella, and gas safety, among others. Each area has a practical guide to the underlying legal duty.
- Can it handle a school made up of several buildings?
- Yes. Requirements and recurring checks can be scoped building by building where an estate spans several buildings, and evidence can be recorded against a specific building - so coverage is tracked at the level it actually applies.
- Where is our data hosted?
- In the UK, encrypted in transit and at rest, with role-based access, per-school data separation and an audit trail. The security page has the detail on hosting and data handling.
See EduComply on your own compliance documents
We will walk you through the flow - from a forwarded certificate to an updated, inspection-ready compliance record for your school.