Start with the support model. Ask specifically whether support is UK-based, what hours it operates, and what the guaranteed response time is for a genuine outage versus a routine query. A vendor's answer here should be specific and contractual, not a general assurance about „excellent customer service,“ which means little without a defined service level attached to it.
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.
Build a simple total-cost model across the contract term. Put licensing, onboarding, training, add-on modules, transaction fees and support side by side for each provider, projected over three to five years. A modular provider such as Compass Education makes this easier to reason about, because you can see which functions you are paying for and add others only when you need them, rather than buying a bundle you half use.
None of these five questions guarantees a good outcome on their own, but a vendor unwilling or unable to answer any of them plainly before a contract is signed is worth treating as a warning sign, whatever the rest of the proposal looks like.
None of this needs to become an exhaustive audit for every school, but a business manager or IT lead signing off on a cloud MIS contract should be able to answer, with evidence rather than assumption, where data is hosted and which certifications back that hosting. That is the baseline, not an optional extra.
Security is the third reason to move. A spreadsheet emailed between offices is hard to control and easy to lose. A proper MIS keeps records behind role-based access, holds an audit trail, and backs data up centrally. For a trust handling sensitive records at scale, that governance is not optional.