Education
Bringing four school campuses onto one operating system
- Client
- Multi-campus school group
- Industry
- Education
- Technologies
- Next.jsNode.jsPostgreSQLDockerAzure
This is an illustrative example. It describes the kind of problem we take on and how we would approach it — not a specific client engagement. No client is named or implied, and the outcomes listed describe what the delivered system does rather than measured results from a particular project.
What was not working.
Each campus kept its own spreadsheets for enrolment and fees, and its own paper registers for attendance. Producing a group-level figure for outstanding fees or headcount meant a manual collection exercise that was already out of date by the time it was finished. Parents had no way to check anything without phoning the office.
How we would tackle it.
- 1
Consolidate the data model first
Before any interface work, agree one definition of a student, a class, an invoice and an academic term across all four campuses — the reason the old numbers never reconciled.
- 2
Migrate one campus at a time
Roll out to the smallest campus first, fix what the real users find, then move the remaining three with the rough edges already resolved.
- 3
Open a parent portal last
Only expose data to parents once staff trust it internally. Publishing attendance or fee balances that staff know are wrong destroys confidence immediately.
What the delivered system does.
- Single group-level view of enrolment, attendance and outstanding fees
- Fee invoicing and payment tracking handled in-system rather than in spreadsheets
- Parent portal for attendance, results and fee status
- Per-campus roles so staff see only their own campus data
Built on School Management.
Related projects.
Recognise this problem in your own business?
Tell us what you are trying to achieve. We will help you figure out the best way forward — and tell you honestly if we are not the right fit.
Prefer email? hello@novista.io