Multi-Campus Groups

Managing a Multi-Campus School Group

By Scolvia Team · · 8 min read

A school that opens its second campus discovers quickly that running two schools is not twice the work of running one. It is a different kind of work. The principal of each campus still runs their day. But now someone has to answer questions no single campus asks: which campus is collecting fees best, why attendance differs between two campuses with similar families, whether the fee policy is being applied the same way everywhere, and what the group as a whole actually earned last month.

Most groups answer those questions by collecting spreadsheets from each campus and combining them. By the time the combined report exists, it is out of date, and the numbers from each campus were prepared slightly differently. This guide covers how successful groups run several campuses as one organisation without taking away the control each campus needs.

Central standards, local control

The central question in any group is what to standardise and what to leave to each campus. Get it wrong one way and every campus reinvents its own processes, making comparison impossible. Get it wrong the other way and campus leaders cannot respond to their own families.

A useful split:

Usually set centrallyUsually left to each campus
Fee heads, fee policy and concession rulesDay-to-day collection and follow-up
Academic calendar and examination structureTimetables and teacher allocation
Grading schemes and report card formatClass and section arrangements
Salary scales and HR policiesLeave approval and cover
Attendance categories and rulesDaily marking and family contact
Reporting definitionsLocal events and communication

The principle is simple: define what centrally, let campuses decide how day to day. Then every campus produces numbers that mean the same thing.

One set of numbers

Group reporting only works when every campus records data the same way, in the same place. When each campus keeps its own system or its own spreadsheets, consolidation is a monthly project and comparisons are arguments about definitions.

When campuses share one platform, group reporting becomes a view rather than a task. The owner or group director sees, at any time:

  • Enrolment by campus and class, against capacity
  • Fees collected against expected, and outstanding by age
  • Attendance rates for students and staff
  • Examination results by campus and subject
  • Staff numbers and payroll cost
  • Admissions pipeline by campus

Comparing campuses fairly

Campus comparisons are useful and dangerous. A campus with lower results may be serving very different families; a campus with lower fee collection may have a deliberate scholarship policy. Compare like with like:

  • Use rates, not raw totals.
  • Compare each campus with its own previous year as well as with the others.
  • Look at trends over several months, not single snapshots.
  • Discuss differences with campus leaders before drawing conclusions.

Used this way, comparison spreads good practice: when one campus has noticeably better attendance, find out what they do and share it.

Fees across a group

Fee policy is one of the most important things to set centrally. Families talk to each other, and inconsistency between campuses quickly becomes a complaint. Set fee heads, concession rules and approval limits for the group, then let each campus collect and follow up locally. Central finance sees collections and arrears for every campus without asking for a report.

Families with children at different campuses should still have one family record and one statement wherever possible. It is a small detail that families notice.

Staff across campuses

Groups often move staff between campuses or share specialists. One personnel record for each person, with their campus assignment changing over time, keeps history intact: payroll, leave, training and appraisals follow the person rather than starting again at each campus.

Access and permissions

In a group, who sees what matters. A campus principal needs full access to their own campus and none to others. A group finance team needs fee data from every campus but not student pastoral records. The owner may want everything. Permissions should be set by role and by campus, so each person sees exactly what their job requires.

Opening a new campus

When systems are shared, opening a campus is mostly configuration rather than invention. A practical checklist:

  1. Create the campus with its classes, sections and capacity.
  2. Apply the group's fee structures, grading schemes and calendar.
  3. Set up staff records and assign roles and permissions.
  4. Open admissions, using the group's enquiry process.
  5. Give the campus leader the same reports every other campus uses.

A new campus that starts on group standards is comparable from its first month.

Franchise and partner campuses

Some groups operate campuses through franchise or partnership arrangements. These need a clear agreement on what is standard (curriculum, branding, fee bands, reporting) and what is local, and the same reporting visibility the group has for its own campuses. Shared systems make that visibility possible without asking partners for monthly spreadsheets.

Governance and boards

Boards and owners need a short, regular pack: enrolment, collections, results, staffing and any significant risks, by campus and in total. When the data comes from one system, the pack can be produced from the same reports every month, and board time goes on decisions rather than on questioning the numbers.

An illustrative example: from four spreadsheets to one view

Consider a group with four campuses: a large flagship, two mid-sized campuses in the same city, and a newer campus opened two years ago in another town. Each campus was set up at a different time, and each has drifted into its own way of working.

Every month, the group finance manager emails the four campus accountants for their collection figures. Three reply within a week; the fourth after reminders. The figures arrive in different formats: one campus reports collections including advance payments, another excludes them, the newest counts transport fees separately. Consolidating takes several days, and by the time the owner sees the group total, the month is half over.

Attendance is worse. Two campuses count late arrivals as present; one counts them as half days; one does not record them at all. When the owner asks why the newest campus has the best attendance in the group, nobody can say whether it is genuinely better or simply counting differently.

Now consider the same group after moving every campus onto one platform with shared definitions. Fee heads and concession rules are set at group level, so "collected" means the same thing everywhere. Attendance categories are identical across campuses. Each principal still runs their own campus day to day, but the owner opens the group dashboard on the first of the month and sees collections, arrears, enrolment and attendance for every campus, already consolidated.

The first comparison that is genuinely like for like reveals something useful: one mid-sized campus collects fees noticeably faster than the others. Its accountant sends reminders a few days before the due date rather than after. Within a term, the practice is adopted across the group. That kind of improvement was impossible while the numbers were being argued about rather than read.

Common mistakes to avoid

  • Standardising everything. Campuses need room to respond to their own families. Standardise definitions and policies, not every daily decision.
  • Standardising nothing. If every campus defines attendance or collections differently, group reporting is meaningless.
  • Ranking campuses publicly on raw numbers. Comparisons without context damage morale and encourage gaming the figures.
  • Giving everyone access to everything. Group-wide access should be limited to the people whose role requires it.
  • Opening new campuses on new systems. Every campus that starts outside the shared platform becomes the next consolidation problem.
  • Letting the board pack change shape every month. A consistent pack is what lets a board see trends.

Frequently asked questions

Should each campus have its own fee structure?

Often, yes: campuses in different areas may charge differently. What should be shared is the set of fee heads, the concession rules and the approval limits, so that structures differ in amounts but not in logic.

How much should the group office control?

Enough to make the group comparable and compliant, and no more. A common pattern is central control of policy, standards and reporting, with campus control of operations, staffing decisions within budget, and local communication.

Can families move between campuses easily?

When campuses share one platform, a transfer moves the student record, results history and family details to the new campus, and fees follow the new campus's structure from the transfer date. Families should not have to start again.

How do we report to investors or a board?

Agree a fixed set of measures (enrolment against capacity, collections, arrears, attendance, results, staffing cost) and produce them from the same reports every period. Consistency matters more than detail.

What is the biggest risk when growing from one campus to several?

That the first campus's informal ways of working, which depended on everyone knowing each other, are copied to campuses where nobody shares that knowledge. Writing down standards early, while the group is small, is far easier than retrofitting them across many campuses later.

A 30-day plan for group consistency

Week 1: agree the definitions

With campus principals and finance, agree what "collected", "outstanding", "present", "late" and "enrolled" mean for the whole group. Write the definitions down and circulate them.

Week 2: decide the split

Use the table above to agree what is set centrally and what is left to campuses. Record the decisions, including approval limits for concessions and staffing.

Week 3: align the setup

Bring fee heads, attendance categories, grading schemes and the calendar into line across campuses. Set permissions by role and campus.

Week 4: the first group pack

Produce the first monthly group report from the shared data: enrolment, collections, arrears, attendance and staffing by campus. Discuss it with principals before it goes to the owner or board, and agree what will be reviewed each month from now on.

Bringing it together

A group runs well when campuses share standards and data while keeping control of their own day. That is the approach behind Scolvia for multi-campus groups: one platform across every campus, group-level reporting, shared settings set centrally, and campus-level access for each principal.

Checklist

  • A written split between central standards and campus control.
  • Every campus recording data the same way, in one place.
  • Group reports available as a view, not compiled by hand.
  • Campus comparisons using rates and trends, discussed before judged.
  • Central fee policy with local collection.
  • One personnel record per person across campuses.
  • Permissions by role and by campus.
  • A repeatable checklist for opening a campus.
  • A monthly board pack from the same reports every time.

See how it would run at your institution

A guided walkthrough of Scolvia with your own processes. No commitment.

Book a demo

Keep reading

28-Oct-2026 · 6 min read

One Set of Numbers Across Every Campus

When three campuses report three different totals for the same thing, the problem is rarely arithmetic. It is definitions. Here is how groups get to one trusted set of numbers.

By Scolvia Team

28-Oct-2026 · 5 min read

Comparing Campuses Fairly

A league table of campuses can spread good practice or poison a leadership team. The difference is in how the comparison is built and how it is discussed.

By Scolvia Team