Statutory compliance and evidence
Every statutory obligation is held as a scheduled task with a named owner, a due date, and a risk rating. Completing the work builds the evidence record as it happens: certificates, inspection reports, and log entries land in a central evidence store with expiry tracking, and a requirement-level register shows the position for every site against every requirement. Curriculum and departmental obligations run on the same engine as estates obligations, so a science department's COSHH work and a site team's fire safety work feed one record, not two systems.
What is in this area
Statutory Tasks
The statutory task register: overdue, in-flight, and completed views. Each task carries stream, site, owner, due date, risk rating, statutory flag, and status
Evidence Store
Central evidence library with compliant, non-compliant, and expiring views, expiry warnings, and filters by stream, evidence type, and expiry date
Compliance Register
One row per site per requirement with RAG status, next review, and expiry; filter by stream; export
Compliance Overview
The compliance position across twelve compliance streams (Fire Safety; Water Safety and Legionella; Electrical Safety; Gas, Heating and Ventilation; Lifting and Pressure Systems; Asbestos and Hazardous Substances; Building, Structure and Accessibility; Grounds, Land and Transport; Security and Public Protection; Catering and Curriculum Facilities; Environmental, Energy and Cyber; Health and Safety Management), each with compliant, in-flight, and overdue counts, a maturity level indicator and expiring evidence feeds. The same twelve streams classify planned maintenance, so compliance and maintenance read through one set of headings
Compliance Triggers
Maps asset types to compliance task templates. When a matching asset is registered, the engine drafts a schedule for human review; it never activates a task automatically
Remedial Actions
A follow-up action raised automatically when a compliance task records a problem: a failed inspection, an out-of-range reading, an identified defect. The generated action carries the source task, the finding, and the affected asset
Asbestos Register
ACM register with condition grading, friability, location, material type, next survey date, and status, with survey due warnings
COSHH Register
Substance register with GHS hazard flags, quantities, site, assessment due dates, risk levels, and stock status
Accessibility Audits
Accessibility audit register: audit date, auditor with credentials, actions and budget, review date, status lifecycle
Building Safety (Higher Risk Buildings)
Building Safety Act 2022 module: higher risk buildings register with BSR registration status, golden thread document counts, and occurrence reporting
CDM Projects
CDM client duty tracker: projects with RAG, site, category, lifecycle stage, and F10 notification status
Environmental Hazards
Radon testing register with action level exceedance, mitigation, and retest cycle, plus environmental hazard records
Departments Overview
The departmental responsibility layer: departments carry a risk classification, a named lead, and their own task position; estates is the default owner for unassigned tasks
Curriculum Task Catalogue
Curriculum-specific task types with frequency and statutory reference, activated into a department; an activated curriculum task becomes an ordinary compliance task and its completion feeds the same evidence record as any estates task
| Module | What it does |
|---|---|
| Statutory Tasks | The statutory task register: overdue, in-flight, and completed views. Each task carries stream, site, owner, due date, risk rating, statutory flag, and status |
| Evidence Store | Central evidence library with compliant, non-compliant, and expiring views, expiry warnings, and filters by stream, evidence type, and expiry date |
| Compliance Register | One row per site per requirement with RAG status, next review, and expiry; filter by stream; export |
| Compliance Overview | The compliance position across twelve compliance streams (Fire Safety; Water Safety and Legionella; Electrical Safety; Gas, Heating and Ventilation; Lifting and Pressure Systems; Asbestos and Hazardous Substances; Building, Structure and Accessibility; Grounds, Land and Transport; Security and Public Protection; Catering and Curriculum Facilities; Environmental, Energy and Cyber; Health and Safety Management), each with compliant, in-flight, and overdue counts, a maturity level indicator and expiring evidence feeds. The same twelve streams classify planned maintenance, so compliance and maintenance read through one set of headings |
| Compliance Triggers | Maps asset types to compliance task templates. When a matching asset is registered, the engine drafts a schedule for human review; it never activates a task automatically |
| Remedial Actions | A follow-up action raised automatically when a compliance task records a problem: a failed inspection, an out-of-range reading, an identified defect. The generated action carries the source task, the finding, and the affected asset |
| Asbestos Register | ACM register with condition grading, friability, location, material type, next survey date, and status, with survey due warnings |
| COSHH Register | Substance register with GHS hazard flags, quantities, site, assessment due dates, risk levels, and stock status |
| Accessibility Audits | Accessibility audit register: audit date, auditor with credentials, actions and budget, review date, status lifecycle |
| Building Safety (Higher Risk Buildings) | Building Safety Act 2022 module: higher risk buildings register with BSR registration status, golden thread document counts, and occurrence reporting |
| CDM Projects | CDM client duty tracker: projects with RAG, site, category, lifecycle stage, and F10 notification status |
| Environmental Hazards | Radon testing register with action level exceedance, mitigation, and retest cycle, plus environmental hazard records |
| Departments Overview | The departmental responsibility layer: departments carry a risk classification, a named lead, and their own task position; estates is the default owner for unassigned tasks |
| Curriculum Task Catalogue | Curriculum-specific task types with frequency and statutory reference, activated into a department; an activated curriculum task becomes an ordinary compliance task and its completion feeds the same evidence record as any estates task |
Derived from the framework, not a generic checklist. The preconfigured task set is reasoned from the DfE framework and current law, each task traceable to the duty it discharges and reconciled against fifteen years of compliance delivery in the sector. It is the statutory spine an organisation starts from and extends with its own tasks, rather than a template it has to build from nothing.
One engine, many surfaces. Curriculum tasks, estates tasks, and department tasks all run on the same compliance engine and feed the same evidence record. Registering an asset drafts its statutory schedule automatically, for human review. A claim about covering both estates and curriculum compliance on one record with automatic schedule drafting is not one a generic task tool can make.
Evidence lifecycle. Evidence carries type, stream, expiry, and compliance status; expiring evidence surfaces on the home dashboard; imported history is flagged as migrated rather than presented as native. The migrated flag is an honesty feature: the record distinguishes what the system witnessed from what it inherited.
The Building Safety Act higher risk buildings register with golden thread, and CDM client duty, are part of the education-specific statutory spine.
How does EstatesBase track statutory compliance tasks?
Every statutory obligation is a task in the statutory task register, with overdue, in-flight, and completed views. Each task carries its stream, site, owner, due date, risk rating, statutory flag, and status. When a matching asset is registered, the compliance triggers draft a schedule for human review; the engine never activates a task automatically.
Where does compliance evidence live?
In the Evidence Store: a central evidence library with compliant, non-compliant, and expiring views, expiry warnings, and filters by stream, evidence type, and expiry date. The Compliance Register reads the same record at requirement level: one row per site per requirement, with RAG status, next review, and expiry.
Can curriculum compliance run in the same system as estates compliance?
Yes. Curriculum task types are activated into a department from the curriculum task catalogue, and an activated curriculum task becomes an ordinary compliance task: its completion feeds the same evidence record as any estates task. Departments carry a risk classification, a named lead, and their own task position, with estates as the default owner for unassigned tasks.
Where do the compliance tasks come from?
The task set is derived from the DfE framework and current health, safety and estates law, with every task traceable to the duty it discharges, and reconciled against the team's compliance delivery in education. It preconfigures as a statutory spine across twelve compliance streams, and an organisation adds its own tasks on top. The platform is kept current against the wider canon of published DfE guidance as it grows.
The education-specific statutory spine this area sits on, from the Building Safety Act higher risk buildings register to CDM client duty, is described in full in Insight and reporting. Insight and reporting
Compliance Register
SearchBook a Consultation: see EstatesBase working, from a site team phone to the board view, and talk through how it would work in your organisation.
Book a Consultation