Most organisations managing an education estate have some form of digital tool in place. They use it to schedule tasks, log completed work, and produce a report when one is requested. In my experience, the people responsible for that tool believe it is doing its job. The compliance dashboard shows what it shows, the tasks are running, and the annual return is approaching with reasonable confidence behind it.
The problem is that the gap between what a tool records and what the DfE Estate Management Standards actually require is rarely visible until you look for it. Over twenty years of building and working with compliance infrastructure for education organisations across every type and size of Responsible Body, I have encountered that gap more consistently than almost any other single failure mode. Not in organisations that have ignored digital compliance management, but in organisations that have invested in it and assumed the investment was sufficient.
That assumption is what this article examines.
What compliance infrastructure actually means
Before addressing what the Standards require of digital tools, it is worth being precise about what compliance infrastructure is. It is not a synonym for a compliance platform or a task management system, though both may form part of it. Compliance infrastructure is the digital layer that allows a Responsible Body to run its estate, capture evidence of what has been done, and report with assurance on the state of compliance at any given point. It is the operational architecture through which an organisation translates its statutory obligations into documented activity, and through which it can demonstrate to its board, to its auditors, and from autumn 2026 to the DfE via the annual return, that those obligations have been met.
That definition matters because it shifts the question. The question is not whether an organisation has a digital tool. Almost all do. The question is whether the tool they have is designed to support assurance, or designed simply to support administration. Those are different things, and the Standards have always implied the distinction, even when they have not always stated it explicitly.
What the Standards expect at each maturity level
The Estate Management Standards describe four maturity levels, from baseline compliance through to fully effective estate management. The digital infrastructure requirements are not confined to Level 3 or Level 4. They are implied throughout, and explicit at Level 3, where the Standards name digital technology requirements as a component of effective estate management in their own right.
At Level 1, the Standards require a statutory compliance register, a record of all statutory inspections and certificates, and a register of all plant and equipment requiring statutory inspection. These are not documentation requirements in the informal sense. They are structured, retrievable, auditable records. For any organisation managing more than a single small site, these requirements cannot be reliably met without a digital system. Paper-based approaches fail at scale because the evidence cannot be searched, the status cannot be reported, and the gaps cannot be identified before they become audit findings.
At Level 2, the Standards require proactive use of condition survey data and CDC data in planning, and a managed balance between planned preventative maintenance and reactive activity. This requires data that is stored, accessible, and actionable, not just logged. An organisation cannot demonstrate a proactive maintenance posture from a spreadsheet or a filing cabinet. The data must be connected to the asset, linked to the maintenance history, and available for planning decisions. A digital tool that records completed tasks without connecting them to the asset or the inspection cycle meets the administrative requirement but not the assurance requirement.
At Level 3, the Standards are explicit. Digital technology requirements must be considered as a component of effective estate management. This is not a suggestion. It is a named element of what a fully effective organisation looks like. Alongside this, Building Information Modelling requirements appear for the first time, confirming that the digital infrastructure expectation at this level extends beyond compliance task management into asset information management.
At Level 4, the Standards expect the performance of the estate to be understood, measured, and used to demonstrate value for money. This requires not just task completion records but trend data, KPI reporting, and the kind of analysis that allows a board or an external reviewer to assess whether the estate is performing against its objectives. A tool that records tasks but cannot produce that analysis is not performing the Level 4 function.
The specific gaps most current implementations leave open
The organisations I have worked with have not typically failed to use digital tools. They have failed to use digital tools designed for what the framework requires. The gap is specific, and it recurs in consistent patterns.
The first pattern is evidence capture without traceability. Tasks are recorded as complete, but the evidence that completion is valid, the certificate, the inspection report, the contractor's confirmation, is stored elsewhere or not stored at all. The compliance record shows green. The underlying evidence would not survive scrutiny. For the annual return, the record is not the evidence. The evidence is the evidence.
The second pattern is asset records that exist without being linked to compliance activity. An asset register is a list of things. An asset record that supports assurance links the asset to its inspection cycle, its statutory requirements, its maintenance history, and the evidence that each requirement has been met. Most implementations I have encountered have the first. The Standards require the second.
The third pattern is task scheduling without maturity progression. The Standards are staged. An organisation at Level 1 has a different compliance posture to one at Level 3. A digital tool that schedules tasks without distinguishing between statutory requirements, framework-required improvements, and aspirational best practice conflates three different things and gives the responsible person no clear view of where they actually stand against the Standards.
The fourth pattern is reporting that serves the team but not the board. A compliance manager needs operational visibility. A board of trustees needs assurance. These are different outputs, and they require different information presented at different levels of abstraction. Many tools produce operational reports with sufficient granularity for the estates team. Very few produce the governance-level reporting that allows a board to discharge its accountability for statutory compliance without relying on verbal assurance from the person managing the system.
The annual return changes the question
From autumn 2026, Responsible Bodies for schools must make an annual return via the DfE's Manage Your Education Estate service confirming they are meeting the Estate Management Standards. The DfE's own Estates Strategy is explicit that better data managed through digital tools will empower Responsible Bodies to meet the Standards and make accurate returns.
The annual return is not a new obligation in substance. The Standards have always existed. What the return does is formalise the accountability and require an organisation to make a confirmed declaration, rather than simply manage compliance internally and hope the picture is clear if anyone ever asks. An organisation whose digital infrastructure cannot produce the evidence to support that declaration is exposed in a way it may not fully recognise until the return is due.
That exposure is specific. Not having a system, having a system that does not produce auditable evidence for each requirement at the relevant maturity level.
The infrastructure question is a governance question
Here is where many organisations locate the question incorrectly. They treat it as a software procurement question. Which platform should we use? What does it cost? Does it integrate with what we already have?
These are not irrelevant questions. But they are the wrong starting point. The right starting point is: does our current digital infrastructure support the governance assurance the framework requires? Not the task management. Not the scheduling. The assurance. The ability to tell the board, the DfE, and an external reviewer what the compliance position is, based on evidence that would survive scrutiny.
If the answer to that question is yes, the procurement question may not arise. If the answer is no, the procurement question is secondary to the design question: what does infrastructure that supports assurance actually look like, and does any system we are considering meet that specification?
The organisations that go straight to procurement without answering the design question tend to acquire a more capable version of what they already have. The task management improves. The dashboards get better. The underlying structural gap, between recording activity and producing assurance, persists, because the question was never asked.
The Standards are clear about what a Responsible Body at each maturity level must be able to demonstrate. The digital infrastructure question is not whether an organisation has a tool. It is whether the tool they have is designed to produce that demonstration.
Richard Bunting has spent twenty years building and working with compliance infrastructure for education organisations across England, including MATs, maintained school trusts, and further education providers.