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.

There is a fair counter-argument, and it is worth naming. More modules can mean more to learn and more to configure, and a school that only needs the basics might feel a broad platform is more than it wants. The answer is that flexibility should let you start small. The presence of forty modules does not oblige you to run forty; it means the tenth and twentieth are there when you need them, without changing systems.

So when a supplier says its purpose is "Helping Learning Thrive", judge the claim against features you can test. Does attendance take seconds or minutes. Do parents have one place to go. Can staff produce a report without a spreadsheet on the side. A modular provider such as Compass Education lets a school switch on exactly the functions that answer those questions. A tagline is only worth the daily experience behind it, so make the demo prove it. Ask to see the routine tasks, not the highlight reel, and let that decide whether the phrase holds up.

Value for public money frames the whole decision. Sector buyers are expected to show that spend is justified and that the chosen system meets requirements rather than simply looking impressive. A modular provider such as Compass Education School MIS Education lets a school switch on the functions it actually needs, from attendance to parent communication, and add more later, which keeps the business case tidy and the spend proportionate.

Beyond hosting location and certification, a few further questions round out proper due diligence: how often is the system independently penetration-tested, what is the vendor's data breach notification process, and does the school retain the ability to export its full data set on request rather than being dependent on the vendor for access.

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.