School management platform
A single platform across every campus, with one source of truth for each record and reporting the group office can trust.
- Sector
- Education
- Engagement
- Fixed scope, then retainer
- Pods involved
- Product, Frontend, Backend, QA, DevOps
- Status
- Live and supported
Every campus kept its own spreadsheets, and every campus had quietly evolved its own column names, its own fee categories and its own definition of what counted as attendance. Each was internally consistent. None of them agreed with each other.
The group office could not answer basic questions — how many students, how much outstanding, how many staff — without a week of manual reconciliation, by which point the answer had moved.
- 01
One record per student
Admissions through to exit on a single record, so a transfer between campuses stops being a re-entry exercise.
- 02
Attendance that matches across campuses
One definition, one flow, one report. The disagreement between campuses was a data-model problem, not a discipline problem.
- 03
Fees and collections
Structures, schedules, receipts and outstanding balances, with the group view derived from the same records the campus works in daily.
- 04
Reporting the group office can act on
Current numbers on demand, rather than a reconciliation exercise that is out of date by the time it finishes.
We migrated one campus first and ran it alongside the spreadsheets for a full cycle before touching the others. Rolling out to every campus at once would have been faster to plan and considerably worse to live through.
- TBDcampuses running on it
- TBDstaff using it daily
- TBDreporting turnaround, before and after
Let’s map your business.
Tell us how your business runs today. We will show you what it could look like with the right system behind it. We reply within one working day.
PDF · 12 pages · 5 MB