Skip to main content

Guide

Running a multi-campus school: what changes operationally

What actually changes when a school grows from one campus to several, and which decisions to make before the software is chosen.

By The EDUTIG team at RNDSOLPublished Updated 6 min read

Growing from one campus to several changes more than headcount. Processes that worked fine with one principal and one office suddenly need explicit rules about who can see what, and reports that used to be a single spreadsheet now need to roll up from multiple locations without losing branch-level detail.

What breaks first when a single-branch system scales

The most common failure point is permissions: a system built for one campus often has no real concept of "this admin should only see Branch A." The second is reporting: consolidating financials or attendance across branches by manually combining exports from each location.

What multi-branch operations actually require

  • Branch-level permissions. Campus administrators manage their own branch; head office roles see everything, consolidated.
  • Consolidated reporting. Attendance, finance, and academic reports that roll up across branches without manual combination.
  • Branch-level and consolidated accounting. Cost centers and branch accounting that support both local bookkeeping and group-level financial statements. See our fee and ledger guide for the accounting foundation this depends on.
  • Shared masters, local execution. Academic years, grading scales, and fee structures often need to be shared or templated across branches, while day-to-day execution (attendance, exams) stays local.
  • Multi-tenancy under one account. Organization-level structure that supports multiple branches without duplicating setup work for each one.

Where EDUTIG stands on this

EDUTIG can record more than one campus under a single school account, and the operations area covers the library, inventory and transport records that each campus keeps.

Before you commit to running several campuses in any system, be specific about who should be able to see and change another campus's data. Talk to us about your structure and we will tell you exactly what is handled today and what would need a manual arrangement, rather than letting you discover the boundary after the second campus is live.

FAQ

Common questions

What institute groups ask when consolidating multiple campuses.

Does each branch need its own separate software account?

No, and it shouldn't. Separate branches under separate accounts is exactly the fragmentation multi-branch software is meant to remove. One account with branch-level permissions and consolidated reporting is the goal.

How should permissions work across branches?

Branch administrators should see and manage their own campus, while a head office role sees consolidated data across all branches. Getting this permission boundary wrong is one of the most common multi-branch rollout mistakes.

Can financial reporting stay separate per branch while still consolidating?

Yes, this is a core requirement, not an edge case. You need branch-level books for local accountability and consolidated books for group-level financial reporting, generated from the same underlying data.

Every module

Twelve areas, one set of records behind all of them.

Compare them all