Written for the people who choose school platforms
Practical guides for committees, registrars, bursars and IT reviewers โ how to evaluate, implement and govern institutional software. No fluff; the same advice we give across the table.
The school platform buyerโs guide: what committees should actually compare
Feature lists all look the same. The differences that matter live in the data model, the governance and what happens at cutover โ here is how to compare them.
ImplementationFrom sign-up to go-live: how a school actually goes onto a platform
The honest sequence โ structure, people, policies, records, then habits โ and the order of operations that makes the first month calm instead of chaotic.
ImplementationThe migration checklist: switching school systems without losing a record
What to demand, verify and keep when your institution moves platforms โ a checklist written from the discipline of real cutover nights.
EvaluationHow to run a security review of school software (without a security team)
Institutions hold data about children โ the review standard should match. Seven checks any administrator can run, and the answers that should worry you.
Prefer answers with your own context?
Tell us your institution type and student strength โ we'll answer specifically.