Picture a bursar on a Thursday evening. Three browser tabs open. A spreadsheet that started life as a “temporary fix” sometime in 2021. She’s cross-referencing student records between the school’s main system and the finance platform because the integration “kind of works, but you have to check the year groups manually.” That spreadsheet has a name now. People email it around. New starters get shown how to use it on day three.
You probably know that spreadsheet. Every school has one.
Sometimes it’s a spreadsheet. Sometimes it’s a shared inbox that one person knows how to triage. Sometimes it’s a printout taped to the side of a monitor. Whatever shape it takes, it’s a symptom of the same thing: operational debt.
The phrase is borrowed from software engineering, where “technical debt” describes the cost of shortcuts taken in code. You build something quickly, you mean to clean it up later, and the cleanup never happens. Years pass. The shortcut becomes load-bearing. Eventually somebody has to spend three weeks unpicking it.
Operational debt works the same way, but in a school it shows up in workflows, processes, and the little workarounds nobody quite remembers agreeing to.
It’s the duplicate data entry between admissions and the SIS. The Google Form that feeds a spreadsheet that feeds a report. The handover document that lives in one teacher’s inbox and nobody else can find. The system that worked beautifully when the school had 400 students and now creaks a bit at 700.
None of these things are catastrophic on their own. That’s the problem. They’re all small enough to live with.
Nobody sits down on a Monday morning and says, “Right, let’s design a fragmented, manually-reconciled operations stack.” It happens in increments.
A new initiative arrives and needs a quick solution. Someone sets up a tool. Six months later, the tool still hasn’t been integrated with anything else, so a staff member starts copying data across by hand. A year after that, the staff member leaves. The person who replaces them inherits the copying job and assumes it’s just how things are done.
Multiply that pattern across admissions, curriculum, activities, transport, reporting, and parent communications, and you start to see the shape of it.
I’ve spoken to schools running eleven different platforms. Eleven. Not because anyone planned it that way, but because each one made sense at the moment it was added. And once a system is in place, the cost of pulling it out always feels higher than the cost of leaving it alone.
So you leave it alone. And the debt quietly accrues interest.
Here’s what makes operational debt sneaky. The cost isn’t sitting in a line item anywhere. There’s no invoice that says “fragmentation: £24,000 this year.” It hides in places that are harder to measure.
It hides in your registrar’s evenings. The ones spent reconciling enrolment data across three systems before a board report.
It hides in your heads of department, who can’t get a clear view of curriculum coverage without asking four different people for spreadsheets.
It hides in your IT team, who spend a disproportionate amount of time being a human integration layer between platforms that don’t talk to each other.
It hides in the new staff member who quits in their second term because they spent half of it learning workarounds instead of doing the job they were actually hired for.
And it hides, most expensively, in the decisions that don’t get made because nobody has a clear enough view of the data to make them confidently.
There’s a reason operational debt is so easy to ignore. The pain is distributed. Nobody experiences it all at once.
Your bursar feels the finance side. Your admissions team feels the admissions side. Your boarding supervisors feel the communication gaps. Your head feels the reporting bottleneck. Each one assumes their bit of friction is just the nature of the work.
It’s only when somebody zooms out, often a new head or a new ops director arriving with fresh eyes, that the full picture comes into focus. The conversations sound the same every time. “How is everyone holding this together?” Followed by: “Why are we doing it this way?”
The honest answer is usually, “Because we always have.”
You don’t need a consultant to diagnose operational debt. Try this. Pick one routine process. Re-enrolment, say. Or end-of-term reporting. Or the activities sign-up cycle. Then ask yourself three questions.
How many systems touch this process? If the answer is more than two, you’ve probably got reconciliation happening somewhere.
How many people would have to be on holiday simultaneously for this process to break? If the answer is one or two, the process is held together by individuals rather than by systems.
How long does it take to produce a clean report on it? If the answer involves the word “depends,” or the name of a specific staff member, there’s debt.
None of this means your school is badly run. It usually means the opposite. Schools accumulate operational debt precisely because the people inside them are good at making things work despite the constraints. The workarounds are evidence of competence. But they’re also a ceiling on what the institution can do next.
Recognising operational debt is the first step. Doing something about it is the second, and that’s where a lot of schools stall.
Switching systems feels disruptive. Auditing workflows feels like a project nobody has time for. The status quo, however imperfect, has the advantage of being familiar.
Here’s the thing, though. The debt doesn’t pause while you decide. It compounds. Every term you defer is another term of staff time absorbed, another cohort of decisions made on patchy data, another set of workarounds embedded a little deeper.
The schools that handle this well don’t do it in a panic. They treat it as a structured project with clear phases, named owners, and realistic timelines. They start by mapping where the debt actually sits, then work outwards from the most expensive parts.
We’ve put together a full guide on how to approach exactly this, if you’re at the point of thinking it through seriously. It walks through a five-phase framework for switching providers, the questions to ask on the procurement side, and what good implementation support actually looks like.
For now, though, here’s a question worth sitting with. If your school carries on exactly as it is for another three years, what’s that going to cost you? Not in pounds. In hours, in clarity, in the things your team could be doing if they weren’t holding the spreadsheet together.
That number, even roughly estimated, tends to make the case on its own.
