Breadth matters too, not just flexibility. A range that stretches past forty modules means the awkward, school-specific needs are more likely to be covered natively rather than bolted on from a third-party tool. Every extra integration is another login, another support line and another thing to break, so a wide native range genuinely reduces day-to-day friction for the office.

Data portability is the second essential question, and it should be asked before any enthusiasm about features clouds the discussion. If the school management information system ends the contract in three or five years, can it export its full historical data, in a usable format, without additional fees or delay? Get this answer in writing as part of the contract itself, not as a verbal assurance during the sales process, since it is precisely the point where the balance of power shifts away from the school once a contract is signed.

A modular system turns that around. You switch on the functions you need now, from attendance and admissions to billing, catering and parent communication, and add others when the school is ready. That has three practical benefits. First, cost tracks use: you are not paying for functions sitting idle. Second, rollout is calmer, because staff adopt a few modules well rather than a whole suite badly at once. Third, the system grows with the school, so a decision made this year does not box you in next year.

Any vendor claiming ISO 27001 or PCI-DSS Level 1 certification, Compass Education included, should be able to produce current, dated certification evidence on request rather than a general assurance statement. A useful due diligence exercise is to ask every vendor on a shortlist for that evidence side by side. A vendor that can produce an up-to-date certificate on request has clearly built the audit process into how it runs the business; one that cannot has usually not been through that audit at all.

Take attendance. Registers are a legal duty and a daily routine, so automating them matters more than it sounds. When an MIS captures attendance quickly, flags patterns for the office and feeds the figures straight into reporting, staff spend less time on administration and more on the pupils in front of them. That is a small, concrete example of a system helping learning by removing friction around it.

None of this means throwing every spreadsheet away. A quick model or a one-off analysis still has its place. The point is that the system of record, the place your live data lives, should not be a shared file that anyone can overwrite. As a trust adds schools, the case for a single, permission-controlled MIS only gets stronger. Start by mapping what each school records today, agree a common structure, then move to a platform that holds all of it in one place.