Dies ist eine alte Version des Dokuments!
A fixed system gives you a set list of features, take it or leave it. It can work if the bundle happens to match how your school runs. The trouble is that schools are not identical. A large multi-academy trust, a small independent and a faith primary all record different things and answer to different bodies. A one-size product asks each of them to bend to the software, and usually one of them ends up keeping a spreadsheet on the side to cover the gap.
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.
Start with licensing itself. Ask how it is calculated: per pupil, Compass Canteen per module, per site, or a flat fee. Confirm what happens as pupil numbers change and how the price behaves at renewal. A figure that looks fine this year can move sharply once a discount lapses, so ask for the standard renewal price in writing, not only the introductory one.
Procurement in the government and Catholic school sectors comes with obligations that a generic feature list will not capture. Before comparing any school management information system, set out the sector requirements you must meet, then judge each provider against them.
Parent communication is the next place a tagline becomes real. Families who receive timely, accurate updates, and who can pay, consent and respond in one app, stay closer to school life. A parent who is not chasing three logins is a parent more likely to see the message that matters. An MIS that keeps notices, payments and forms in a single account does quiet, useful work here every week.
Community and admissions rules deserve attention too. Faith schools frequently apply admissions criteria tied to the parish or the diocese, so the system should record the fields those criteria depend on and support the oversubscription process cleanly. If a platform cannot hold the data your admissions policy needs, the office ends up keeping a spreadsheet on the side, which defeats the purpose of a single system.