What procurement teams ask about school management, ERP, and SIS

Ask for comparable answers

Procurement teams need more than a yes or no against a feature list. Ask each vendor to respond to the same workflow, role, exception, evidence, implementation responsibility, commercial assumption, and contract question.

Require vendors to label behavior as available now, configurable, integrated, manual, roadmap, or unknown. An unknown is a risk to manage, not an automatic yes.

Question the operating model

Ask who owns discovery, data preparation, migration, validation, configuration, permissions, training, support, incident response, updates, exports, and contract-end data return or deletion.

• Which tasks must school staff perform?
• What happens when the school has no specialist available?
• How are subprocessors and support access governed?
• How are changes, outages, and incidents communicated?
• Which acceptance tests must pass before launch?

Question evidence and boundaries

Request a data-flow map, role matrix, migration sample, security scope, support commitments, pricing assumptions, and written exclusions. GOV.UK guidance recommends early involvement of data protection expertise and attention to minimum necessary data, access control, security, subprocessors, breach notification, and end-of-contract handling.

The U.S. Department of Education data governance checklist offers a useful structure for quality, access, security, lifecycle, sharing, disposal, and monitoring. Adapt it to the school’s jurisdiction and policy.

Keep the decision defensible

Publish the scoring method before responses arrive. Separate must-have workflows, control requirements, evidence quality, implementation risk, commercial clarity, and preferences. Record unresolved questions and decision rights in one register.

A procurement record should explain why the selected scope fits the school’s work and capacity. It should not rely on unsupported savings, generic transformation language, or a polished demonstration that omitted failure cases.

Make the next step specific

Use this guidance to improve one bounded part of what procurement teams ask about school management software. Name the person who owns the decision, the record or workflow affected, the evidence needed, and the date for review. A short test with real operators is more useful than a broad claim that the whole school has been transformed.