Your School MIS Is Not Your System

Most schools treat school MIS procurement as an IT decision. It is also an infrastructure decision. The distinction matters because a management information system is only one part of the way a school works.

Attendance, safeguarding, assessment, behaviour, parental communication and statutory reporting involve people, decisions and responsibilities. Software supports those activities. It does not automatically make them coherent.

When the information does not move cleanly between them, staff create workarounds. A teacher enters the same detail twice. A leader reconciles several reports. An administrator checks a spreadsheet because nobody trusts the dashboard. The cost is not always visible on the software invoice. It appears in the work required to make the software useful.

The right procurement question is therefore not simply which school MIS has the most features. It is which arrangement supports the school's actual work with the least avoidable friction.

School MIS fit begins with the work

Before comparing suppliers, map a small number of consequential journeys. Start with attendance recording, a change to pupil information, an assessment review and a safeguarding escalation. Follow each journey from its origin to the person who must act.

For each step, identify who enters information, who checks it, who can change it and what happens when it is missing. Record where the same detail is copied into another system. Distinguish a necessary professional judgment from a manual task that exists only because two tools cannot communicate.

This produces a specification grounded in reality rather than a list of attractive product names. A feature can exist in a demonstration and still fail to support the school's working practice. A report can look comprehensive while arriving too late for the decision it is supposed to inform.

The most useful requirements describe an outcome and the conditions under which it must work. For example, a corrected contact detail should reach the relevant communications tool without creating a second conflicting record. That is more precise than asking whether a supplier offers integration.

A school is not a software template

Every off-the-shelf platform makes assumptions about its users. Those assumptions shape fields, permissions, reporting structures and the sequence of common tasks. Many schools can work effectively within those assumptions. Others have requirements that need configuration, integration or a different delivery model.

The gap should be examined before procurement, not discovered after migration. It may concern the organisation of a trust, a particular reporting responsibility or the way staff collaborate across settings. None of these automatically means a bespoke system is the right answer.

A configured standard platform may be the most dependable option. A targeted integration may solve a genuine gap without replacing the core MIS. A bespoke or semi-bespoke approach can be appropriate where requirements justify the additional delivery and maintenance responsibilities.

The decision is architectural. Compare the whole arrangement, including ongoing support, data portability, supplier dependence and the capacity of the school to manage change. A custom system is not inherently coherent, and a familiar commercial platform is not inherently unsuitable.

Design the information responsibilities

A school can have several useful applications and still lack a trustworthy information model. The issue is not necessarily the number of tools. It is whether anyone has defined which tool owns each piece of information.

Decide where the authoritative pupil record lives. Identify the source for contact details, attendance records and assessment information. Specify which systems can read those records and which people can amend them. Keep access proportionate to the role.

Safeguarding requires particular care. Integration can support the timely presentation of relevant information, but automated rules should not be treated as a replacement for professional assessment. Staff need to understand how an alert was produced, how it is reviewed and who owns the response.

This is the same principle explored in The Load Path Before the Load: understand what must carry the responsibility before adding more activity to it. Information should arrive where it is needed without becoming accessible everywhere merely because a connection is technically possible.

Test the school MIS before committing

Use realistic, appropriately anonymised scenarios in supplier demonstrations. Ask staff who perform the work to test the sequence, not merely watch the sales presentation. Include an exception as well as the normal path.

For instance, change a pupil's contact information and follow it through each connected service. Check what happens when a sync is delayed. Review the audit trail. Ask whether staff can distinguish an old record from the current one without opening several applications.

Migration deserves the same attention. Agree who cleans the source data, how records will be mapped, how permissions will be checked and what evidence establishes that the migration is complete. Plan training around actual tasks rather than a tour of every menu.

A staged trial with explicit acceptance criteria is more informative than a feature count. It reveals the difference between software that can perform a task and a system that enables staff to perform it reliably under everyday pressure.

Measure what the arrangement removes

Useful measures include repeated data entry, the time needed to produce a routine report, unresolved sync failures and the number of manual steps in a common process. Establish a baseline before change so that improvement can be assessed rather than assumed.

Do not optimise for removing every human decision. Some decisions exist because accountability matters. The purpose of good infrastructure is to remove avoidable administrative effort while making necessary judgment easier to exercise.

The school MIS is part of the system. The system is the relationship between the work, the information and the people responsible for both.

Schools do not need a more impressive collection of software. They need an arrangement they can trust when the work becomes demanding.

Cover image: Peter Morch on Pexels.