Case studies
No school has approved a public case study yet.
We publish a case study only with the school's written consent and review. Until one exists we will not show invented schools, quotes, logos or results. This page shows how a rollout runs and what to measure, so you can judge us on your own numbers.
How a rollout is staged
The shape we plan a migration around. Timing depends on your data and your calendar.
- Audit the dataInventory students, staff, fees and history in the current system.
- Dry-run importLoad a copy, review the rows that need a decision, change nothing live.
- Run in parallelStaff work in both for a short, agreed window and compare.
- Cut overSwitch the school to the new system at a calendar boundary.
- Review a termCheck the measures below against your baseline.
What to measure
Record your baseline before cutover. The blank column is yours to fill in; we do not fill it for you.
| Measure | How to count it | Where it lives | Your baseline |
|---|---|---|---|
| Enquiry to enrolled | Days from first enquiry to an enrolled student record. | Admissions | |
| Attendance on time | Share of sessions marked before the period ends. | Attendance | |
| Fees collected | Amount received against amount invoiced for the term. | Fees & Payments | |
| Report cards out | Days from the marks deadline to published reports. | Grading | |
| Staff hours on re-keying | Hours a week spent copying data between sheets. | Your own time log |
The case study we would write with you
If you agree to document your rollout, this is the sheet we would complete together. Every field is filled by your school, not by us.
- School type
- System replaced
- Modules adopted
- Cutover date
- Baseline and result
- What did not go well
- Approved by (name, role)
- Date approved