The Multi-Campus Management Trap
Most school groups start with one successful campus. They open a second. Then a third. By campus four, the group director is managing five different accounting systems, three different timetable formats, and receiving fee reports in four different Excel templates — none of which are comparable. The people running each campus have adapted their processes independently. There is no consolidated view of anything.
This is not a management failure. It is a systems failure. Each campus developed its process in isolation because there was no shared system to build on.
What Centralisation Actually Means
Centralisation does not mean every campus principal calls head office before making a decision. It means data flows to a central dashboard automatically, so leadership can see what is happening across all campuses without anyone preparing a report.
In Skoo, a multi-campus setup gives the group director:
- Consolidated fee collection view — total collected vs outstanding, broken down by campus and class
- Comparative attendance — which campus has the lowest average attendance this month, and why
- Staff payroll overview — total salary liability across all campuses, with variance from last month
- Exam results comparison — grade distribution by campus for the same exam
Each campus principal still has full control of their data. The group director simply has read access to everything without anyone sending them a file.
Fee Structure: Unified vs Campus-Specific
The biggest multi-campus fee management question: should all campuses charge the same fees?
Skoo supports both approaches. You can set a group-wide fee structure that all campuses inherit, with campus-level overrides for transport fees, facility charges, or local pricing. Concessions and scholarships can be set at group level (scholarship policy) or campus level (individual approvals).
Whatever the structure, the fee report always rolls up correctly at the group level. No manual consolidation.
Staff Management Across Campuses
- Teacher transfers between campuses are tracked — the staff record moves with them
- Payroll runs independently per campus but consolidates at group level for cash flow planning
- Leave calendars are campus-specific — different public holidays for different cities where needed
- HR policies can be set at group level so all campuses operate with the same rules
The Independence vs Standardisation Balance
Campus principals resist centralisation when it means losing control. The framing that works: centralisation means the group director sees your data, not that they control your decisions. A principal who manages a high-performing campus should welcome the visibility — it is their track record being surfaced.
Standardise the things that should be consistent: fee structure, payroll policy, report card format. Leave campus-specific: local event calendars, section names, transport routes.
Common Mistakes in Multi-Campus Rollouts
- Migrating all campuses simultaneously: Start with one campus, stabilise, then roll out. Each campus migration needs 2–4 weeks of focused attention.
- Different staff training for each campus: Train a "super user" per campus who trains everyone else — consistency compounds.
- Not setting group-level fee structures first: Set the structure before enrolling students, or you will reconcile differences manually for months.