Multi-Campus School Management: What to Centralise

Why the second branch is where it breaks

One campus can run on habit. The owner walks the corridor, knows the accountant, and can see the fee register on the desk. A second campus removes all three. Each branch starts keeping its own registers in its own format, and within a term the two are no longer comparable. Nothing dramatic has gone wrong. It is simply that nobody can answer a basic question across both branches without a phone call and a spreadsheet.

• Fee collection is known per branch, days late, and never as one number.
• The same fee head is named differently at each campus, so totals cannot be merged.
• A family with children at both branches is two unrelated families on paper.
• A student who moves branch is re-admitted from scratch, and the history stays behind.
• Exam results use slightly different grading at each campus, so comparison is meaningless.

What to centralise

Centralise whatever has to mean the same thing everywhere. If a number will ever be compared or added across campuses, its definition must be set once, at the top.

• The student and family record, so a child exists once in the network, whichever campus they attend.
• Fee heads and the rules around them: late fines, arrears, discounts and sibling concessions.
• The grading policy and report card format, so a B means the same thing in every branch.
• Roles and permissions, decided by the head office rather than by each campus.
• Reporting: collection, admissions, attendance and enrolment, per campus and combined.
• The audit trail, so every change shows who made it and at which campus.

What to leave with each campus

The usual mistake after a bad first year is to centralise everything. That is just as damaging, because a head office cannot run a school day from across the city. Anything that depends on being in the building should stay with the people in the building.

• Daily attendance marking and the follow up with absent students.
• The timetable, which depends on that campus, its rooms and its teachers.
• Collecting fees at the counter and issuing receipts.
• Communication with that campus's parents about that campus's events.
• The fee amounts themselves, where campuses genuinely differ.

Fee amounts are a campus matter, fee rules are not

This distinction matters more in Pakistan than most guides admit. A campus in one area often charges differently from a campus in another, and in provinces where the private school regulator approves fee structures, approval is tied to the registered institution. So the amounts legitimately vary by campus. What must not vary is how fees work: the heads, how arrears carry forward, when a fine applies, how a concession is recorded. Set the rules centrally, set the amounts per campus, and the network stays both flexible and comparable.

The reporting test

There is a simple way to tell whether a school network is actually being managed centrally. Ask these questions and time the answers. If any of them takes more than a minute, or needs someone at a branch to prepare it, the network is running on separate systems regardless of what the software is called.

• What did each campus collect this month, against what it billed?
• Which campus has the most overdue fees, and how old are they?
• How many admissions did each campus take this term compared with last?
• Which campuses have classes with no attendance marked today?
• How many families have children at more than one campus?

What to ask a multi-campus software vendor

Almost every vendor will say yes to multi-campus. These questions separate a real multi-campus school ERP from a single school system installed several times.

• Is it one account with campuses inside it, or a separate installation per branch that someone has to merge?
• Can a branch user be limited to their own campus while a director sees all of them?
• Can fee amounts differ per campus while the fee heads and rules stay shared?
• Are consolidated reports built in, or exported and combined by hand?
• Can the director switch campus from a phone, without a separate login for each?
• How is pricing affected when a new campus opens, and is there a student cap per campus?
• Is every change logged with the user and the campus?

Put the system in before the next campus, not after

The cheapest moment to standardise is before a new branch opens, while there is only one way of doing things to write down. Once a second campus has run for a year on its own registers, consolidation means reconciling two sets of habits as well as two sets of data. Schools that plan a second branch should treat the management system as part of opening it, the same as furniture and staff.

How eSchools handles multiple campuses

A school network on eSchools runs as one account with its campuses inside it, in a database that belongs to that school alone and is never shared with another school. Staff are assigned to campuses and roles decide what they see, so a branch coordinator works within their own campus while a director sees every one. Fee structures can differ by campus while reporting consolidates across all of them, and the admin mobile app has a campus switcher for directors who move between branches. Pricing is per campus with unlimited students, and the Enterprise plan covers unlimited campuses under one account.