Timing is the second decision, and in a school the calendar decides it for you. The gaps between terms, and the summer break in particular, give you a window to move without a live term relying on the switch. Avoid cutting over in the middle of admissions or reporting season. Agree a clear go-live date, keep the old system readable for a defined period afterwards, and confirm you can still retrieve historic records if you need them. Never delete the old data until the new system is verified and signed off.

Then look for the fees that hide between the lines. Common ones include charges for extra modules, for additional user accounts, for integrations with other tools, for data exports, and for support above a basic tier. Payment processing fees on parent transactions can add up quietly across a year, so ask exactly how those are charged and who absorbs them. None of these are unreasonable in themselves; the problem is only when they are not disclosed up front.

Support deserves its own line. Clarify what is included as standard, what a premium tier costs, the response times you can expect and where the support team is based. When a system is central to daily admin, slow or costly support is a real expense measured in staff time, even if it never appears on an invoice.

A modular system turns that around. You switch on the functions you need now, from attendance and admissions to billing, catering and parent communication,  [[https://www.governmentbusiness.co.uk/company-focus/compass-education-your-trusted-mis-partner-school-transformation|https://www.governmentbusiness.co.uk/company-focus/compass-education-your-trusted-mis-partner-school-transformation]] 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.

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.

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.