The Governance Backstop for Deputy Principals

In the independent school world, governance has a home. It sits with the Business Manager. The BM holds the compliance calendar, the risk register, the policy library, the board papers. The Principal leads. The BM assures. The division of labour is clean.

In the public school world, that division of labour broke years ago, and nobody noticed.

The operational half of the Business Manager role moved to the Deputy Principal. The governance half was absorbed by "the system." The governance half is the one nobody is actually doing.

Except the Deputy Principal is doing it. Quietly. In the margins of a role that was never redesigned to carry it.

What the Deputy Principal Actually Does

A Deputy Principal in a public school is one of the most load-bearing positions in the system.

Officially, the role covers:

• Operational leadership of the site.
• Backstop for the Principal when they are unavailable.
• Oversight of timetables, staff rostering, student engagement.
• Line management of middle leadership.
• Supervision of behaviour, wellbeing and attendance.

Unofficially, the role has absorbed:

• Compliance calendar execution.
• Risk register maintenance.
• Policy implementation at the site level.
• Post-incident review coordination.
• Assurance evidence gathering for Department reporting.
• Governance preparation for Council meetings.

The first list is in the job description. The second list is what actually happens. And the second list is what keeps the school governable.

This is not a title inflation problem. It is a structural one. The governance work has to be done. The role that used to do it does not exist. So the Deputy has quietly become the backstop.

Why the Backstop Breaks

The problem is not capability. Deputies are capable. The problem is that the backstop role was never designed.

Without design, three things happen.

First, the work becomes invisible. Because it is not in the job description, it is not measured, not resourced, and not acknowledged. The Deputy is doing it. Nobody outside the school can see it.

Second, the work becomes person-dependent. When a Deputy changes roles, the governance work leaves with them. Their replacement inherits a calendar of obligations and a folder of partially-completed artefacts, and has to reconstruct the picture from scratch.

Third, the work becomes fragile. The backstop has no backstop. When the Deputy is sick, on leave, or dealing with a student crisis, the assurance work does not get rerouted. It just does not happen.

In a well-run school, none of this shows up in a crisis, until it does.

What a Designed Backstop Looks Like

The governance backstop role does not need a new person. It needs a system that holds the work the role is carrying.

Specifically:

• A compliance calendar that shows what is due, who owns it, and what evidence has been captured, without requiring the Deputy to hold it all in working memory.
• A risk register that updates itself as incidents are logged and treatments are closed, not one that has to be rebuilt before every Council meeting.
• An action register that carries decisions from leadership meetings through to outcomes, without the Deputy having to chase.
• Post-incident reviews that feed findings back into the risk register and training plan, automatically.
• Council pack content that builds from the work the Deputy has already done, rather than requiring another evening of assembly.

When this infrastructure exists, the Deputy's role becomes visible. Their backstop function becomes defensible. Their workload becomes sustainable. And, critically, their work becomes transferable, because the record of it lives in the system, not in the Deputy's head.

The Deputy Is the Proxy

In the founding customer cohort for EthosGov, the Deputy Principal at Norwood International, Reece Freak, is the operational lead. Not the Principal. Not the Business Manager. The Deputy.

This is not accidental. In the public system, the Deputy is the closest analogue to the Business Manager role EthosOne was built for. They carry the operational weight. They run the assurance rhythm. They are the person who notices when the calendar slips.

The product surface has to mirror that reality. The daily user of Assure is the Deputy. The logic of Improve is built around the way the Deputy runs leadership cycles. The escalation routing of Oversee presumes that the Deputy is the first person the Director will phone when something moves on the heat-map.

This is not a design choice. It is a recognition.

What It Changes for the Role

When the backstop is held by a system rather than by a person, the Deputy's role changes in three ways.

First, it becomes leadership work rather than administration work. The Deputy is not chasing compliance. They are analysing patterns, coaching middle leadership, and running improvement cycles.

Second, it becomes recognised work. The system shows what the Deputy is carrying. That visibility is the precondition for the role being resourced properly.

Third, it becomes coachable work. A Deputy aspiring to a Principalship is learning the assurance and oversight rhythm by doing it, not by inheriting a folder of dead artefacts. The next generation of public school leaders is made or broken in this role.

Take the Next Step

If this article speaks to your situation, two routes from here.

Go deeper on the verb. Read the Assure cornerstone. It is the deep page that sits underneath every article in this category.

See it on your site. Book a Governance Review. 45 minutes. No deck. We measure what the friction is costing you and whether EthosGov reduces it measurably.

---

Part of the EthosGov resources library. Governance infrastructure for public school systems. Lead. Improve. Assure. Oversee.