The finding that recurs most consistently in External Reviews of Governance and strategic governance training across multi-academy trusts and the maintained sector is not that boards lack interest in their estate. It is that the governance architecture was never designed to support accountability for it. The board receives an estates update. It may receive it regularly, and from a capable person. But receiving an update is not the same as having the governance architecture to act on it. Those are different things, and conflating them is itself a governance design failure.
In External Reviews of Governance and strategic governance training across all educational settings, what I encounter is a recognisable structural pattern. The responsible person is named. The board receives reports. The chair may be reasonably satisfied that estate matters are receiving attention. But when you map the actual accountability structure, what you find is responsibility without authority, escalation paths that are informal or absent, and a board that is positioned to receive information rather than to exercise judgement. The governance architecture was not designed. It accumulated.
The distinction matters because the DfE Estate Management Standards do not ask whether there is a named responsible person. They ask whether the responsible body can demonstrate assurance across every domain of estate management, across all education sectors. That is a governance question, not a reporting question. It cannot be answered by producing a report. It can only be answered if the governance architecture was deliberately designed to produce the conditions in which assurance is possible.
Accountability must be allocated, not assumed
The most common design failure I encounter is not a gap in statutory knowledge, although knowledge gaps are common where professional governance support is limited.
It is the assumption that responsibility attaches automatically to a role title. The Responsible Person for fire safety exists as a named function. The Health and Safety lead is appointed. The facilities manager produces monthly condition reports. But in the absence of a deliberate accountability architecture, what each of these individuals is actually responsible for, what authority they hold to act, what escalation path exists when they cannot act, and what the board is required to do in response, none of that is defined. It is assumed.
When accountability is assumed rather than allocated, three things follow. First, the board cannot exercise judgement on estate matters because it does not have a clear view of where accountability sits. Second, escalation fails because the path from a practitioner-level concern to a board-level decision does not exist in any formal sense. Third, when something goes wrong, the organisation discovers that the governance architecture it thought it had was never there.
The pattern I encounter most often in complaints resolution work is this: a foreseeable estate-related issue, visible at practitioner level, does not escalate to the board in time for effective governance intervention. Increasingly, these matters present through perceived failures in safeguarding or SEND policy implementation, frequently intersecting estate based policies and procedures. The underlying weakness is rarely the performance of operational staff; it is the absence of a formal, designed escalation architecture. Without a defined route for risk, regardless of where it emerges, to travel from frontline practice to responsible-body decision-making, boards cannot exercise assurance. The governance architecture was never designed to support it.
Boards receive reports. They need to receive assurance.
There is a version of estate governance that looks complete from the outside: regular agenda items, a named lead, an annual condition survey, a report to the finance and resources committee. This version satisfies the visual requirements of governance without providing the structural conditions for it. A board that receives reports is not the same as a board that is positioned to exercise assurance. The difference is in the architecture.
For a board to receive assurance rather than information, four things must be true. The accountability structure must be explicit: who is responsible, for what, with what authority, and what happens when that person cannot resolve a matter within their own authority. The escalation path must be formal: there must be a defined mechanism for risk to travel from practitioner level to board level before it becomes a crisis rather than after. The board must have the capacity to exercise judgement rather than simply note a report: that means it must receive information in a form that requires a decision, not information in a form that permits passive reception. And the responsible body must be able to demonstrate, at any point, that the accountability structure exists and is functioning, not simply that a report was produced.
None of this is produced by appointing a responsible person and scheduling a committee item. It is produced by deliberate governance design.
Governance architecture is a design task
In governance capacity building work across system leadership programmes, the question that most consistently reveals the gap is this: can you show me the accountability structure for your estate, as a designed system rather than as a set of role titles? In every organisation where I have examined this, the answer requires a conversation rather than a document. The document does not exist because the design process did not happen.
Designing the accountability structure for an education estate requires decisions, not defaults. It requires a board to determine what it needs to be able to demonstrate and to design backward from that requirement: what information it needs, in what form, from whom, at what frequency, and what the escalation path is when the information it receives indicates a risk that requires board-level intervention. It requires the responsible body to define the boundary of practitioner authority and the conditions under which matters must escalate to board level. And it requires those decisions to be documented, not in a policy that sits on a SharePoint drive, but in a governance framework that the board actually uses.
The organisations that manage this well have, in my experience in External Reviews, one thing in common: they treated governance architecture as a deliberate design task at the point when their estate accountability was first formalised, and they have returned to that design task each time the organisation has changed. The organisations that manage it badly have a different thing in common: they inherited arrangements from a previous configuration, never redesigned them, and have been operating under the assumption that inherited arrangements are adequate arrangements.
What this requires of responsible bodies
The DfE Estate Management Standards are explicit about what responsible bodies must be able to demonstrate. The standards do not require a report. They require evidence that accountability is allocated, that assurance is exercised, and that the responsible body has a functioning governance architecture, not simply a named person and a committee agenda item.
Meeting that requirement starts with accepting that the governance architecture for an education estate is not a default outcome of having governance structures in place. A trust can have a well-functioning scheme of delegation, a rigorous finance committee, and a competent leadership team, and still have an estate governance architecture that was never designed. The two things are not the same thing.
What governance architecture for estate management actually requires is a deliberate act of design: mapping the accountability structure, defining escalation paths, establishing what the board is required to decide rather than merely to note, and building the formal mechanisms through which assurance travels from practitioner level to responsible body level. That is not a reporting exercise. It is a governance design exercise. And until it is treated as one, the gap between receiving reports and exercising assurance will remain.
Mel Stokes is a governance architecture specialist with named experience in External Reviews of Governance, complaints resolution, and system-wide governance capacity building. She works with trusts and responsible bodies across the education sector.