There’s usually a long gap between the moment a school realises its systems aren’t working and the moment it actually does something about it. Months. Sometimes years.
The friction is visible. People complain about it. The conversation has been had at SLT meetings, often more than once. And yet nothing changes. Or rather, nothing changes deliberately. The systems slowly get worse, the workarounds quietly multiply, and the institution carries on.
If that pattern sounds familiar, you’re in good company. It’s the single most common thing we see in schools weighing up a switch. The decision isn’t held up by lack of awareness. It’s held up by the gap between awareness and action.
Let’s talk about why that gap exists, and what tends to close it.
When schools eventually do switch, the reasons are rarely surprising. The drivers cluster into four recognisable patterns. Most schools have at least two of them. The ones that finally act usually have all four.
Walk into most school back offices and ask how many systems they use. The answer is usually wrong. Not because anyone’s lying, but because nobody’s counted recently.
There’s the main SIS. The finance platform. The communications tool. The activities sign-up thing. The thing for parent forms. The reporting platform somebody added for the IB. The transport rota that lives in Sheets. The boarding handover doc that nobody’s quite sure who owns.
Each one made sense when it arrived. Together, they make a stack that nobody actually designed. Nobody sat down and chose this. It accumulated.
The cost is felt mostly at the joins. Where two systems are supposed to talk to each other but don’t quite. Where a piece of information has to be re-entered. Where one team’s “single source of truth” is another team’s “we just don’t use that field.”
This is the one heads tend to notice first, usually when a senior staff member resigns and the exit interview reveals what they were actually spending their time on.
Manual reconciliation. Re-keying data. Producing the same report three different ways for three different audiences. Cross-checking attendance figures that should already match because they came from the same place.
None of this is anyone’s fault. It’s what the systems force. But the cost is real, and it lands on your most capable people, because they’re the ones the institution trusts to make the workarounds work.
There’s a particular sting to watching a registrar with twenty years of experience spend Wednesday afternoon copying values from one tab to another. Twenty years of judgement and institutional memory, and the system has them doing data entry.
In a fragmented setup, getting a clean answer to a basic question takes time. “How many Year 9 applications are still outstanding?” “What’s our retention rate by year group?” “Which departments are behind on reporting?”
These are not difficult questions. They’re the kind of thing a head should be able to pull up in two minutes. But when the data lives in four places and none of them talk, the answer involves emailing three people and waiting until Friday.
Decisions slow down. Boards get briefed on data that’s already two weeks old. Strategic conversations happen without the numbers in the room, because the numbers couldn’t be pulled together in time.
You don’t always notice this until you visit a school that has it sorted. Then the contrast is uncomfortable.
The fourth pattern is the one that finally tips schools over the edge, more often than not.
It’s the slow accumulation of frustration with the people on the other end of the helpdesk. Tickets that take a week to get a substantive answer. Generic responses that don’t engage with the actual problem. A sense that the provider is reactive rather than partnered. That the school is on its own when something breaks.
When this kicks in, schools start having a different kind of conversation internally. Not “is the system good enough?” but “do we trust the people behind it?” Those are very different questions, and the second one is much harder to recover from.
Here’s the puzzle. Once a school has two or three of these patterns running, the case for changing something is obvious. So why do most schools sit on the decision for so long?
A few reasons, in our experience.
The first is that the cost of staying is distributed and the cost of switching is concentrated. Staying is a hundred small frustrations a week, spread across the whole staff. Switching is a defined project with a budget line and a person who has to own it. The first feels like weather. The second feels like a decision you can be blamed for.
The second is that the worst-case scenarios are vivid and the upside is abstract. People imagine the disastrous data migration. The training that doesn’t land. The system that goes live and immediately falls over. They don’t, in the same vivid way, imagine the version of their school six months from now where the workarounds are gone and nobody emails the registrar at 9pm.
The third is timing. There’s never a good moment. Term starts. Term ends. Inspection coming up. Enrolment cycle. Budget cycle. Reporting cycle. If you wait for a calm window, you’ll wait forever.
The fourth, and probably the deepest, is that schools are conservative institutions for good reasons. Continuity matters. Predictability matters. Children’s education shouldn’t be the testing ground for a half-baked rollout. All of that is true.
But continuity isn’t the same as stasis. The schools that handle transitions well treat them with exactly the same seriousness as any other significant change, with planning, ownership, and structure. The risk isn’t in changing systems. The risk is in changing them badly, which is a different problem with a different solution.
There’s a point at which staying becomes more expensive than switching. It’s rarely a single dramatic event. It’s a gradual reweighting, where the cost of fragmentation becomes measurable enough that leadership stops debating whether to act and starts debating how.
A few signs you might be approaching it.
You can name three workarounds that are now considered “just how we do things.”
A specific staff member’s resignation would create a knowledge gap your systems couldn’t fill.
Producing a board report involves more than one person and more than one spreadsheet.
You’ve had the “we should look at switching” conversation more than twice in the past year.
If two or more of those land, you’re probably past the threshold and just haven’t named it yet.
Recognising that you’re ready to switch is the easy part. Doing it well is what most schools actually need help with.
We’ve put together a full guide on the how, including the five phases of a well-structured switch, what to ask of a provider during procurement, and how to keep the project on track once it’s underway.
If you take one thing from this piece, take this. The schools that switch successfully aren’t the ones with the fewest doubts. They’re the ones who stopped waiting for the doubts to disappear.
