Multi-Campus Nigerian Schools: Keeping Fees Consistent Across Branches

A single school brand running several campuses — a Lagos group with an Ikeja site and a Lekki site, say, or a chain spanning Lagos and Abuja — faces a decision that a single-site school never has to make: should every campus charge the same fee, or should each location price on its own? There's no single published answer, because the honest answer is that Nigerian school groups do it both ways, and the harder, less-discussed problem is the one underneath either choice — getting one trustworthy financial view across branches that aren't actually all keeping the same books.

Same brand, different fee — and that's often deliberate, not sloppy

Fee figures reported for the same school brand across different Lagos locations are genuinely inconsistent in the public record — different aggregator sites quote noticeably different per-term tuition for the same named school group depending on which campus and which year they're citing, and the figures don't always agree with each other even for the same campus. That inconsistency partly reflects real variation (a Victoria Island or Lekki campus commonly costs more than a Mainland campus of the same brand, which tracks with older reporting that Lagos Island private-school pricing has generally held up better than Mainland pricing, partly for reasons that go beyond facilities) and partly reflects that these are aggregator estimates, not each school's own published schedule, so treat any specific cross-branch figure as something to confirm with the school directly rather than take at face value.

Either choice — one fee schedule group-wide, or per-campus pricing — is defensible, and the right one depends on what's actually driving cost at each site. If every campus has comparable facilities, staffing ratios, and overheads, a single group-wide fee is simpler to communicate and avoids the awkward perception that one campus's families are subsidising another's. If campuses genuinely differ — a flagship site with more specialist staff and newer facilities versus a smaller satellite campus — pricing each on its own cost base is more honest than forcing one number across both, the same logic that applies to pricing tuition per grade rather than flat across very different class levels.

The administrative trap: one brand, several sets of books

Whichever pricing decision a group makes, the real operational risk shows up a layer below it: campuses that grew up somewhat independently — a founding site plus branches added over time, sometimes each with its own bursar, its own bank account, and its own informal process — end up keeping separate records that were never designed to roll up into one group-wide picture. A group's central leadership can end up needing to call around to each campus's bursar to find out how collection is actually going that term, which is the exact problem single-site schools have with a spreadsheet that's perpetually a few days behind reality, just multiplied across however many campuses the group runs.

This tends to get worse, not better, as a group grows, because each additional campus is one more place a parent's payment can land, one more local reconciliation process that may or may not be rigorous, and one more place sibling or staff discounts have to be checked consistently. A family with children at two different campuses of the same group is a genuinely common case worth planning for specifically — if each campus runs its own disconnected records, a sibling discount that should apply across campuses can be missed entirely, or applied inconsistently, simply because neither campus's bursar can see the other's roster.

What a unified view across campuses actually requires

• Every campus's fee structure, discount rules, and payment records live in one system rather than parallel, locally-maintained records — a group leader should be able to see collection status across all campuses without phoning each bursar individually.
• A student's campus (and, if pricing varies, the fee rate that follows from it) is set explicitly per student rather than assumed, so a transfer between campuses within the group updates the correct fee automatically instead of carrying the wrong rate forward.
• Sibling and family relationships are tracked at the group level, not per campus, so a family with children at two different sites of the same group is recognised as one family for discount and communication purposes.
• Each campus can still see and manage its own students and collections day to day — centralising the view doesn't mean forcing every campus's staff to lose visibility into their own site.

None of this requires picking identical fees everywhere — a group can price campuses differently and still have one accurate, real-time view of collection across all of them, as long as the underlying system treats "which campus" as one more attribute of a student's record rather than a reason to keep an entirely separate ledger.

Related questions