Book a Demo
Book a Demo

Running your school

What breaks when you open your second campus

Managing Multiple School Campuses — What Breaks and Why | GLOWSIMS

Muhammad Shahbaz Akbar · · 6 min read

Most owners prepare for the second campus as a problem of scale. More students, more staff, more fees to collect, so more of everything that already works.

That is not what happens.

The second campus does not double the work. It changes what the work is. On the day it opens you stop running a school and start running a standard — and almost nobody is told that in advance.

The thing that breaks first

Not the finances. Not the staffing. The definitions.

Campus one has been running for years. Over that time it built up its own vocabulary without anyone deciding to. The fee heads have names somebody chose in a hurry. Classes are called something specific. There is a sibling discount with rules that live in the head of one person in accounts. The academic calendar has local adjustments nobody wrote down.

None of that is a problem while there is one campus. It is only a problem the moment there are two, because campus two will build its own vocabulary, and it will be different.

Six months later the head office asks a simple question — how many students are on a discount across the group — and discovers there is no answer. Campus one calls it a sibling discount. Campus two calls it a family concession and applies it differently. The numbers cannot be added together because they are not the same thing.

This is the real cost, and it is invisible until you try to consolidate. Two sets of books that each make sense on their own and cannot be combined.

The owner becomes the integration layer

Here is the pattern I see most often, and it is the one that does the quiet damage.

With one campus, the owner knows everything because he is there. With two, he becomes the only person who knows both. He is the one who remembers that campus two's fee structure was changed in March, that campus one's head of admin does the defaulter list differently, that the two campuses count attendance from different dates.

That knowledge is not written anywhere. It is carried, by one person, between two buildings.

It works. For a while it works well, because the owner is capable and the group is small. But it does not survive the third campus, and it does not survive the owner being unwell for two weeks. The group's operating knowledge is sitting in one head, and that is a structural risk, not a personal failing.

Every network that grows well does the same thing at this point: it moves knowledge out of the owner's head and into a standard. The ones that struggle keep the owner as the integration layer and wonder why growth feels heavier each time.

What month-end looks like when it goes wrong

The clearest symptom is the consolidated report that takes two weeks.

Each campus sends its numbers. The formats differ. One sends a spreadsheet, one sends a figure on WhatsApp, one sends a printed sheet. Somebody at head office re-types them into a single sheet. Then the questions start, because the totals do not agree with what the campuses believe is true.

By the time the group's real position is known, the month it describes is already over. The report is history, not management.

An owner in that position is not short of data. He is short of agreement about what the data means.

What to standardise, and when

The answer owners want is a system. The honest answer is that a system will not save you if you have not made the decisions a system needs. Settle these first — ideally before campus two opens, and if it is already open, now:

One fee head list for the whole group. Not one per campus. If campus two genuinely needs a head the others do not, it gets added to the single list and the others simply do not use it.

One naming convention for classes and sections. This sounds trivial. It is the single most common reason two campuses' reports cannot be merged.

One discount policy, written down. Who qualifies, how much, who approves it, and what happens when a family stops qualifying. The verbal version does not survive a second campus.

One academic calendar, with local exceptions declared. Campuses will differ on some dates. That is fine — as long as the difference is a declared exception, not a quiet drift.

One rule about who can change these things. This is the one owners skip, and it is the one that matters most. If a campus can rename a fee head on its own, every other agreement above decays within a year.

That is five decisions. None of them requires software. All of them determine whether software will help you or just record the confusion faster.

Where we come in

We run the whole group on one system, so the head office sees every campus in the same shape, in one place, without anybody re-typing anything.

But we have learnt not to lead with that. A group that has not settled the five decisions above will get a faster, better-organised version of the same disagreement. So when we come in on a multi-campus rollout, the first work is not installation. It is sitting with the head office and agreeing the standard — the fee heads, the naming, the discount rules, the approval rights — and then building that standard into the system so it holds by itself.

Then we roll out campus by campus, not everything in one weekend. Each campus goes live, settles, and the next one follows. It takes longer on paper and it is far faster in practice, because a rollout that breaks in three campuses at once stops the group.

We have been doing this since 2013, for more than 1,200 schools across Pakistan, holding over a million student records — single campuses and networks both.

If you are about to open campus two

Do the five decisions before you open, not after. Retro-fitting a standard onto two campuses that have already diverged is three times the work of agreeing it once.

And if you already have three or four campuses and month-end is a fortnight of reconciliation, that is not a reason to wait. It is the reason to start.

If you want to talk it through — not a demo, a conversation about how your group is actually set up — we are happy to.

Message us on WhatsApp or book a demo.

Muhammad Shahbaz Akbar is the CEO of GLOWSIMS, built in Phalia and running Pakistani schools since 2013.

← All posts