A school trust running four branches usually starts each one the same way its founding school began: with its own office, its own accountant, and its own set of spreadsheets. It works fine at one campus. At three or four, the trust's leadership ends up flying blind — nobody at the top can say, without a round of phone calls, how many students are enrolled group-wide or which branch is behind on fee collection this term.
It starts small. Branch A's accountant tracks fee dues in one spreadsheet format, Branch B's uses another, and Branch C still keeps a physical ledger for cash payments. Six months in, nobody at the trust office can produce a single, trustworthy number for total outstanding fees across the group without asking each branch to send its own file and then manually reconciling three inconsistent formats. The problem isn't that any one branch is doing something wrong — it's that there was never a shared structure to begin with.
The instinct when this pain shows up is to force every branch onto one identical fee structure and one identical academic calendar. That usually backfires — a branch in a rural area with a different admission cycle, or one that runs a different board curriculum, has legitimate reasons to differ. What actually works is a school ERP built for multi-campus groups, where each branch keeps its own fee structure, holiday calendar, and staff roster, while the trust office gets a single consolidated dashboard rolled up from all of them. Autonomy at the branch, visibility at the top — not one or the other.
Consider the audit scenario that trips up most groups: a branch principal quietly approves a fee waiver for a handful of families, and the trust finds out only when the annual accounts don't add up. With every branch's fee data flowing into one system, the trust office can see waivers, discounts, and installment plans as they're approved — not months later during a reconciliation exercise. It also means a student transferring from one branch to another keeps a continuous academic and fee record instead of starting from a blank file at the new campus.
Board meetings for a school group almost always need one number: total enrollment, or attendance percentage, across every campus, as of today. Without a shared system, producing that number means calling every branch office and waiting for someone to count. With centralized reporting, a trustee opens one dashboard and sees enrollment, attendance, and fee collection broken down by branch and rolled up for the group — the kind of number that used to take a full day to compile now takes a few seconds to look up.
Fees and enrollment get the most attention, but staff records fall into the same trap. A teacher who transfers from one branch to another mid-year often ends up as two separate, disconnected records — one at the old campus, one at the new — because each branch's office maintains its own staff register. That makes it nearly impossible for the trust to answer a simple question like total teaching staff across the group, or to track a teacher's full service history when it's split across two local systems that were never designed to talk to each other. A shared staff directory at the group level, with branch-level scheduling and payroll layered on top, keeps that history intact no matter how many times a person moves between campuses.
The rollout matters as much as the software. Pick the branch most willing to change first, get it running for a full term, and use it as the reference point for the others — don't attempt a simultaneous switch across every campus on day one. Let each branch's admin team keep the parts of their process that already work, such as their own fee due dates or their own attendance-marking habits, and standardize only what genuinely needs to be shared: the underlying data structure, not every local workflow. Groups that force uniformity from day one tend to face the most resistance; groups that centralize visibility while preserving local control tend to get adoption without a fight.
Book a 30-minute walkthrough of how Ellifo consolidates fees, enrollment, and attendance across every campus in your group.
Book Free Demo
