Opening a second branch feels like success. Opening a fifth feels like a different business. The owner who once knew every student by name now hears about problems weeks late, discovers that each branch charges fees differently, and finds that a parent who moves from one campus to another is treated as a stranger. This is the branch trap: five schools wearing one name, drifting apart. The pattern described here — how a multi-branch school in Pakistan runs five campuses as one system — is a realistic composite drawn from common experience, not a claim about any named school group. The lesson is structural: multi-branch management is a systems problem, and it is solved with systems.
The school group in this scenario has five branches across one city and a nearby town, around 2,000 students in total, and a small head office of three people. For years, each branch kept its own registers, its own fee records, and its own way of doing things. The turnaround was not a rebrand or a new logo — it was a decision to run one set of systems across all branches, with clear rules about what is central and what is local.
The Branch Trap: Five Schools Wearing One Name
The symptoms of the branch trap are easy to recognise. A student transfers from Branch A to Branch B and the new branch has no record of their fee history, attendance, or previous results — the family has to re-submit every document. The head office asks for monthly numbers and gets five different spreadsheets, each with its own format, none of them reconcilable. One branch gives discounts freely to fill seats; another refuses any concession and loses families. One branch's results are excellent; another's are slipping, and nobody notices until board results come out. Teachers are hired at different salaries for the same role, and the better-paid branch quietly poaches the others' best staff.
Underneath the symptoms is one root cause: each branch is running its own version of the school, because there is no shared system forcing a single version. Spreadsheets and registers cannot hold five branches together — they were never designed to. The fix is not more head-office meetings; it is a shared system of record that every branch uses for the same processes, in the same way, every day. Our guide to multi-campus rollout covers the practical steps of moving branches onto one system.
The first decision is what "one school" means in practice. The group writes it down: one admission policy, one fee policy, one academic calendar, one reporting format, and one student record that follows the child across branches. Everything else — local events, local staffing decisions, local parent relationships — stays with the branch. That written line between central and local is the constitution of the multi-branch school, and every later decision refers back to it.
One Record: Centralised Data, Local Access
The single most important system is one student record. Every student in the group has one record, with one admission number, one fee history, one attendance history, and one results history — visible at every branch. When a family moves from Branch A to Branch B, the receiving branch opens the existing record, updates the campus, and the child continues without a single repeated form. When head office asks how many students the group has, the answer is one number, not five guesses.
Centralised data also changes safeguarding and compliance. Student records, fee receipts, and staff records live in one place with controlled access, rather than in five offices with five filing cabinets. Access is role-based: a branch principal sees their own branch in full and other branches only where needed; a teacher sees their own classes; head office sees the group. Backups happen automatically rather than depending on someone remembering to copy a file. Our guides to user access control and school data backup cover the two disciplines that make centralised data safe rather than risky.
The migration is the hard part, and the group handles it honestly: one branch at a time, starting with the branch whose records are cleanest, with paper backups kept until each branch's data is verified. Cleaning five branches' worth of duplicate and inconsistent records is weeks of work, but it is work that pays for itself every day afterwards — every duplicate record removed is a parent who will not be double-billed or lost in a transfer.
One Policy: Fees, Admissions, and Standards That Match
With one system comes one policy. The group publishes a single fee schedule: the same fee for the same class at every branch, with any branch-specific difference (a transport charge, a location supplement) shown as a separate, approved line — not hidden in ad-hoc discounts. Discounts and scholarships follow one written rule with one approval path, so a family at Branch C gets the same treatment as a family at Branch A. Concessions are recorded in the system with the approver's name, which ends the quiet discounting that was eroding revenue at one branch while another turned families away.
Admissions follow the same logic: one admission form, one document checklist, one test format, and one waiting-list rule. A family that applies at one branch and is offered a seat at another is handled through the shared system, not through a phone call between principals. Academic standards follow too: one curriculum pacing plan, one test calendar, one marking scheme. Branch results are compared on the same measures, which is what makes the comparison honest — and what lets the group spot a struggling branch early and send help, rather than discovering the problem at board-result time.
One policy does not mean one price for everything regardless of context. A branch in a lower-income area may legitimately charge less than a branch in a wealthier neighbourhood — but the difference is a deliberate, published decision, not an accident of five separate offices. A student information system shared across branches is what makes that single policy enforceable without daily head-office policing.
Branch Autonomy: What Each Campus Decides for Itself
Centralisation fails when it tries to control everything. The group deliberately protects branch autonomy in four areas. Local hiring: each branch principal interviews and recommends teachers, within a group salary band and a group qualification standard. Local events: sports days, functions, and community activities are planned by each branch for its own families. Local parent relationships: parent meetings, complaint handling, and day-to-day communication stay with the branch — parents should feel they belong to a campus, not a call centre. Local scheduling: within the group calendar, each branch sets its own assembly times, activity periods, and van routes.
The balance is maintained by a simple rule: branches decide how to achieve the standard; the group decides what the standard is. A branch may choose its own sports-day format, but it may not choose its own fee schedule. A branch may hire its own teachers, but it may not pay outside the band. That clarity ends the two classic multi-branch arguments — "head office interferes in everything" and "branches do whatever they like" — because everyone knows which decisions belong where.
Branch principals meet monthly — in person or by video call — with a fixed agenda: numbers (admissions, attendance, collection), one academic item, one operational problem, and one idea worth sharing. The meeting is short, the numbers come from the shared system, and the best idea from any branch becomes group practice the next month. That loop is how five branches get smarter together instead of merely coexisting.
The Multi-Branch Rule
The Owner's Dashboard: Running Five Branches in One Hour a Day
The payoff for the owner is time. Before the systems change, running five branches meant five visits a week and a constant stream of phone calls. After it, the owner's morning routine is one dashboard: admissions this month by branch, attendance yesterday by branch, fee collection this month against target by branch, and any branch where a number has moved sharply. A branch that is slipping shows up as a number before it becomes a crisis. The owner still visits branches — but now the visits are for teaching quality and people, not for hunting down numbers.
The dashboard also makes growth decisions possible. When the group considers a sixth branch, it can answer the real questions from data: which areas are drawing applicants, what fee level the market accepts, how many students a new branch needs to break even, and which existing branch's principal is ready to lead it. Growth stops being a gamble and becomes a calculation. And the systems that made five branches manageable — one record, one policy, one rhythm — are exactly the systems that make a sixth branch a routine expansion rather than a new crisis.
AI Help: Muse AI
Muse AI is Meta's personal AI assistant, available in the Muse app. It can help you draft a one-page central-vs-local decision chart for your school group — which decisions belong to head office, which belong to each branch — so every principal works from the same rules.
Join Muse with invite code LTGSWD — in the Muse app, go to Settings > Redeem token and enter the code.
Disclosure: LTGSWD is the author's Muse invite code.