Multi-branch school management software, without one campus reading another's books
A trust running four schools usually ends up with four systems and a spreadsheet that reconciles them once a quarter. The group gets its numbers late, and gets them by retyping.
SkoolBook treats the group as a first-class structure rather than four unrelated tenants. A campus keeps its own students, staff, ledgers and day-to-day autonomy — but access is granted per campus, so the head of one school does not silently acquire the ability to read, or edit, another's.
What you get
Access is granted per campus, and read is not write
A regional academic head can be given read access to three campuses and write access to one. The two are separate grants, because someone who should review a campus's results usually should not be able to change them.
A transfer carries the balance, not the history
Moving a child to a sister campus snapshots what they owe at the moment it is approved. Attendance, marks and ledger entries stay recorded at the campus where they actually happened — a transfer does not rewrite either school's past.
Seeing a transfer and performing one are different rights
The Managing Director can review transfers across the group without being able to move a child. Oversight and execution are deliberately not the same permission.
Campuses compared side by side
Collection, enrolment and staffing across every campus you have access to, in one view, rather than four exports pasted into a spreadsheet.
Group panels over the same data
Finance, admissions, academics and people each roll up across campuses — reading the same records the campus itself uses, so the group and the school are never quoting different numbers.
How it works
- 1
Group the campuses
Campuses are collected into a group, each keeping its own records and its own day-to-day operation.
- 2
Grant access per person, per campus
Read or write, campus by campus. Nobody gets a whole group by default because they are senior.
- 3
Roll up the panels
Finance, admissions, academics and people aggregate across the campuses that person may see — and only those.
- 4
Move a child properly
A transfer is requested, approved and completed as distinct steps, carrying the balance forward at approval.
Frequently asked
Does a group login let someone see every campus?
No, and this is the point of the design. Access is granted campus by campus, and read access is a different grant from write access. Someone with read access to three campuses and write access to one sees three and can change one.
What happens to a child's records when they move between our campuses?
Their attendance, marks and ledger entries stay at the campus where they were recorded. The transfer carries forward the outstanding balance, snapshotted at the moment the transfer is approved so that a payment made next week does not retroactively change what was agreed to be carried.
Can the group see one campus's fee collection?
Anyone with access to that campus can, and the comparison view puts campuses next to each other. What it will not do is show a campus's figures to someone who was never granted access to it.
Is this for a trust with several schools, or several branches of one school?
Both — the structure is the same. What differs is usually how much you want standardised centrally versus left to each campus, and that is worth a conversation rather than an assumption.