School management systems: the MIS features that actually matter

The short answer

The MIS features that matter most are the unglamorous ones: registers that are right, census returns that validate, attendance data that reaches the Department for Education without anyone touching it, and a single pupil record that other systems read from instead of copying. Those jobs carry legal weight, and every school does them every day.

After that, a feature earns its place only if it removes work you can measure — usually re-keying between the MIS and the other tools a school runs. This article covers state-funded schools in England; the rules differ elsewhere.

The statutory core

• Registers, twice a day. The Department for Education's attendance guidance (July 2026 edition) says schools must take the register at the start of each morning session and once during each afternoon session, at the same time for all registered pupils, recording each absence with the national attendance and absence codes. It expects registers to be kept in an electronic MIS.
• Daily attendance data. State-funded schools must provide specific pupil information on request, including daily attendance. The guidance describes an MIS the Department can access as the easiest way to comply; once permission is granted the flow is automated.
• The school census. A statutory return every term — autumn, spring and summer.
• The admission register. Who is on roll, and when and why they joined or left.
• Safeguarding, SEND and behaviour records. Held securely, with access limited to the people whose role needs them, in line with Keeping Children Safe in Education.

An MIS that does these reliably is doing its main job. One that does them badly cannot be rescued by any number of extra features.

The volume, in arithmetic

Maintained schools must be open to educate pupils for at least 380 sessions (190 days) a year, and every session produces a mark for every pupil. For an illustrative school of 900 pupils:

900 × 380 = 342,000 attendance marks a year — 1,800 every school day, each of which feeds the census, the daily data share and any follow-up.

The marks themselves are quick. The follow-up is not. Suppose, illustratively, 15 pupils a day are absent without an explanation and each takes 6 minutes to follow up — a call, a text, a note on the record:

15 × 6 minutes × 190 days = 285 hours a year, about 1.5 hours every school day. Automating the first contact to parents, and logging the reply against the right session, is one of the clearest time savings an MIS can offer.

The features that actually matter

1. Registers that are fast and hard to get wrong, on whatever device teachers actually carry, with the current codes built in.
2. Census validation before submission, so errors are found by the school, not returned by the Department.
3. Automated attendance data sharing, set up once and then left alone.
4. First-day absence contact, sending a message to parents automatically and recording the reply — see notifications.
5. Access by role, so a safeguarding note is visible to the people who need it and nobody else, with an audit trail of who viewed what — see access control.
6. A parent view of attendance, reports and messages, so the office is not the only route to information — see portals.
7. A proper way to get data out, through an API or complete exports, so other systems read from the MIS instead of being typed into.

What matters less than the demonstration suggests

• Dashboards. Useful if someone owns them; decorative if nobody opens them after the first month. See reporting for what makes one worth having.
• Features that duplicate a tool staff already use well. A second messaging app is not an improvement.
• Anything that only works if data is entered twice. That is a cost disguised as a feature.

Demonstrations show the happy path. Ask instead how the system handles a mid-year admission, a pupil registered at two schools, a change of parental responsibility, and a census return that fails validation. The exceptions are where schools lose time.

Where the hours hide: the seams

Most schools run more than an MIS: a parent app, a payments system, a safeguarding tool, a SEND tracker, a timetabling tool, a learning platform. When each keeps its own copy of the pupil list, every admission, leaver and change of contact has to be made several times, and the copies drift apart.

That is the same pattern we describe for colleges in why most have a seam problem rather than an MIS problem, and the admissions version in how many staff-hours admissions admin takes. The fix is usually to make the MIS the one record the others read from, through an integration hub, rather than to replace it.

Switching: when, and how carefully

Change MIS only for a clear reason: the statutory core is unreliable, the system cannot share data with the tools around it, or a trust needs one record across several schools. Moving means every pupil record, register history and contact, and a mistake can surface in the census or the attendance data.

If you do move, plan the migration around the census calendar, reconcile the migrated data against the old system before switching off, and train the people who take registers first. If the MIS does its statutory job and the pain is elsewhere, connect rather than replace. For how we approach whole-school platforms, see software for schools.