Five Systems, One School: The Cost of Fragmented MIS
Walk into most school offices and you will find the same picture. There is one system for the timetable, another for attendance, a third for assessment and reporting, something separate for talking to parents, and a finance package that nobody on the teaching side ever logs into. Each was bought for a sensible reason, at a sensible moment, by someone solving a real problem in front of them. None were chosen to work together, because no single decision created the situation. It accumulated.
The result is a school that runs on five systems and has a clear view through none of them. That cost is rarely written down anywhere, which is precisely why it goes unchallenged year after year. This piece is about making it visible.
How a school ends up with five systems
No business manager sets out to buy five overlapping tools. The fragmentation arrives one decision at a time, and each is defensible on its own.
The timetabling software came in because the existing approach could not cope with option blocks and shared teaching. The parent communication app was adopted during a year when getting messages home reliably mattered more than anything else. A new head of assessment brought a familiar tool with them. Finance sits in its own world because it always has, often run by someone who reports to the trust. The core management information system holds the statutory record and not much else, because everyone gradually routed around it.
Each purchase solved the problem it was bought for. What none of them solved was the problem of the whole. A school is one organisation with one set of pupils, yet it is asked to describe itself five ways and to keep all five descriptions in agreement.
The double data-entry tax
The first hidden cost is re-keying, paid daily.
A new pupil joins in March. Someone enters them into the central record. Then someone adds them to the timetable so they appear in the right classes. Then they are set up in the attendance system. Then a parent contact is created in the communication app. Then, if meals or trips are charged, they appear in finance too. One child, the same name and date of birth typed or imported five times, by people who each assume the others have it under control.
The same tax is levied on every change, not just every arrival:
- A pupil moves teaching group, and the move has to be reflected in the timetable, attendance and assessment tools separately.
- A parent updates a phone number, and it is now correct in one system and stale in four.
- A staff member leaves, and their access lingers in the tools nobody remembered to revoke.
None of this is dramatic. That is the trap. Each re-key takes a minute, so it never feels worth fixing. Multiplied across a school year and every pupil, parent and staff change, it becomes a standing cost measured in days of office time. And because the entry points are separate, the systems drift apart. The phone number that was right in September is wrong by Christmas, and nobody can say which of the five holds the truth.
No single view, and what that costs leadership
The second cost is harder to quantify and more damaging. When the data lives in five places, nobody can see the pupil whole.
A head of year wants to understand a child who is struggling. The attendance picture is in one tool, the assessment trajectory in another, the record of contact with home in a third, and any note about a trip the family could not afford in finance. Building a single picture means logging into several systems, exporting from each, and assembling it by hand in a spreadsheet. By the time it is assembled it is already days out of date, and building it was itself a job for someone.
For senior leaders the same gap appears across the whole school. A simple question, which pupils have falling attendance and slipping results at once, cannot be answered by either system alone, because the two halves of the answer live apart. So it gets asked once a term in a leadership meeting, laboriously, rather than being visible on any given Tuesday. Oversight becomes a periodic reporting exercise, and decisions that should be early become late.
This is the part that fragmentation hides best. The re-keying is at least visible to the people doing it. The absence of a single view is invisible, because you cannot miss a question you have stopped asking.
The administrative burden lands on the wrong people
There is a quieter cost again, and it falls on teachers.
When systems do not talk, the gaps get filled by people, and the people nearest the gap are often classroom staff. A teacher chasing a register that did not sync, re-entering marks because the assessment system would not export cleanly, or copying a message into the parent app because it does not pick up the right contacts, is doing administration that exists only because the tools are separate. It is not teaching, nor preparation for teaching. It is friction created by the software estate.
Office staff carry the heaviest share, but the load spreads outward, onto exactly the people whose time the school most wants to protect. A unified education MIS does not make administration disappear, and it would be dishonest to claim it does. What it removes is the work that exists purely to keep separate systems in step. That category is large, and it is the easiest to give back.
What consolidation actually delivers
The case for a single management information system is not that it is newer or has more features. It is that the school stops describing itself five times. In concrete terms, consolidation delivers three things.
- One record. A pupil, a parent, a staff member exists once. Their details are entered once and are the same everywhere, because there is no “everywhere” any more, only the one place.
- Less re-keying. When attendance, assessment, communication and the core record share a foundation, a change made in one is a change everywhere. The standing tax on every arrival, move and update largely goes away.
- Real-time visibility. Leadership can see attendance and attainment against the same pupils at the same moment, without an export-and-assemble ritual. The question that used to wait for the termly meeting can be answered today.
It is worth being plain about what consolidation does not do. It does not remove the need for judgement, it does not make difficult conversations with families easier, and moving to a single system is itself a project that takes planning, data cleaning and a term or two of patience. The honest claim is narrower: you stop paying the fragmentation tax, and the time it was quietly consuming comes back.
Frequently asked questions
Do we have to replace everything at once?
No, and you should be wary of any approach that insists on it. Most schools consolidate in stages, beginning with the systems that re-key against each other most often, usually the core record, attendance and assessment. Communication and finance can follow once the foundation is stable. The aim is a single record underneath, reached at a pace the office can absorb.
Will a single system mean less choice for our staff?
It means a different kind of choice. Today the choice is which of five tools to log into; consolidation replaces that with one place and fewer logins to manage. Specialist needs do not vanish, but they sit on top of one shared record rather than each carrying its own copy of your pupils.
How do we know the data is right when we consolidate?
Migration is the moment to find out, and that is a feature, not a risk. Bringing five systems together surfaces every disagreement between them, the stale phone numbers and mismatched groups, and forces a single correct version. The data-cleaning that consolidation requires is work you needed to do anyway.
A school is one organisation, and its software should describe it as one, rather than asking staff to reconcile five accounts of the same pupils by hand. Fragmentation is not a single bad decision to regret; it is the absence of a decision to join things up. Making that decision, deliberately and at a sensible pace, is how the hidden cost stops being paid.
T.R.