Questions to Ask an MIS Vendor Before Signing a Multi-Year Contract
Angus
0
4
09.19 14:15
A multi-academy trust or independent school signing a multi-year contract with a school management information system vendor Compass MIS is making a decision that is expensive and disruptive to reverse. A short list of direct questions, asked before signature rather than after, reduces the risk of discovering a gap once the school is committed.
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.
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.
Hosting location is the first thing worth confirming directly, in writing, rather than assumed. Where is student and financial data physically stored, and does that location bring specific regulatory obligations with it? A school should ask this plainly of any vendor rather than accepting a general answer about "secure cloud infrastructure," which describes almost every provider on the market and tells a procurement team nothing distinctive.
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.
Fourth, ask about price increases over the life of the contract. Is any annual increase capped, and is it tied to a transparent measure such as inflation, or left at the vendor's discretion? An uncapped renewal clause is one of the more common sources of budget surprise for school business managers a few years into a contract.
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.
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.
Hosting location is the first thing worth confirming directly, in writing, rather than assumed. Where is student and financial data physically stored, and does that location bring specific regulatory obligations with it? A school should ask this plainly of any vendor rather than accepting a general answer about "secure cloud infrastructure," which describes almost every provider on the market and tells a procurement team nothing distinctive.
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.
Fourth, ask about price increases over the life of the contract. Is any annual increase capped, and is it tied to a transparent measure such as inflation, or left at the vendor's discretion? An uncapped renewal clause is one of the more common sources of budget surprise for school business managers a few years into a contract.
공지
