One Platform, Not Five: The Real Cost of Stitching
Attendance here, grades there, timetable in a spreadsheet, messages in a third app. The hidden tax of running school operations across stitched-together tools — and the case for one system.
Nobody sits down and decides to run a school on five disconnected systems. It happens the way most tangles happen — one good decision at a time. The attendance app solved a real problem in 2021. The gradebook was a bargain the year after. The timetable has always lived in a spreadsheet the deputy head guards. Messaging to parents went through whatever was easiest at the time. Each choice made sense on its own. The sum of them is a school where nothing quite talks to anything else.
The cost of that arrangement is real, but it is distributed so thinly across so many people that no one ever sees the whole bill.
Where the money actually leaks
The licence fees are the part everyone can see, and the smallest part of the problem. The expensive bit is the human glue.
Picture a new student enrolling mid-term. Their details have to be typed into the attendance system, then again into the gradebook, then added to the right timetable groups, then into the parent messaging list. Four systems, four chances to fat-finger a name or a class, and no single place that is authoritative when they disagree. Multiply that by every enrolment, every leaver, every student who changes set, across a year. The registrar is not doing admin; they are being a very expensive synchronisation service between machines that refuse to speak to each other.
Then there is reporting. The head wants a simple picture — how is attendance tracking against achievement for this year group. In a stitched setup that is an afternoon of exporting from one tool, exporting from another, and lining up two spreadsheets that identify the same student in two different ways. The question was reasonable. The friction in answering it means it gets asked less often than it should, which is its own quiet cost.
The integration mirage
The usual reassurance is "it's fine, the systems integrate." Sometimes they genuinely do. Often "integration" means a nightly export, a fragile connector someone built and left, or a promise in a sales deck that turns out to require a paid add-on and a consultant.
Every seam between two systems is a place where data can diverge and a place that breaks when either vendor ships an update. The more seams you have, the more of your week is spent tending them. A connected set of best-in-class tools can be excellent. A loosely-taped set of adequate ones is a maintenance liability wearing the costume of a solution.
What a single system removes
When attendance, grades, timetable and communication share one foundation, a set of chronic annoyances simply stop existing.
- The student exists once. Enrol them a single time and they are present everywhere — in the register, in the gradebook, on the right timetable, reachable by their family. No re-keying, no drift.
- The timetable feeds attendance directly. The schedule that defines classes is the same one that generates the sessions you take attendance against. One source, not two that disagree by Wednesday.
- Reports cross the boundaries. Attendance against achievement is one view, not a weekend of spreadsheet surgery, because the data was never separated in the first place.
- Access rules apply once. A head of year's permissions are defined in one place and hold across the whole platform, rather than being set up — and inevitably set up slightly differently — in four separate tools.
The honest counter-argument
Consolidation is not a free win, and pretending otherwise is how schools get burned. A single platform means a single vendor relationship, which is a concentration of risk: if they are poor at one thing, you own that weakness everywhere. Migrating off four entrenched tools is a real project, not a weekend. And the mythical system that is the undisputed best in the world at every single function does not exist.
So the question is not "single platform or best-of-breed" as an article of faith. It is a trade: how much is the stitching actually costing you in staff time, errors and unanswered questions, against the value of a specialist tool in each niche. For most schools — the ones without a dedicated IT team to mind the connectors — the stitching tax is higher than it looks, because it is paid in minutes by people who would rather be teaching or helping students.
A reasonable test
Before adding a sixth tool, ask a blunt question: who will keep this in sync with everything else, and how many hours a term will that take. If the honest answer is "the registrar, and quite a few," that is the real price, and it rarely shows up on the invoice.
Classable brings attendance, grades, timetable and parent and student access onto one multi-tenant platform for exactly this reason — so a school maintains one source of truth instead of paying, in staff hours, to keep five of them agreeing with each other.
Related reading
Catch Timetable Clashes Before the Term Starts
A teacher booked in two rooms at once, a class scheduled against itself — timetable clashes are cheap to fix in August and expensive to discover in September. How conflict detection catches them before the first lesson.
Tardiness and Late Arrivals: Policies That Actually Stick
Lateness is where attendance policy most often falls apart. How to code lates honestly, set thresholds people respect, and treat the causes instead of punishing the symptom.
Multi-Campus Attendance: Reporting Across a District
A group of schools wants one honest picture of attendance — without flattening each school into the same mould or letting one campus see another's data. The balance a district has to strike.
Get attendance ideas in your inbox
Occasional, practical guides on attendance and running a school. No spam, unsubscribe anytime.