Running one school is a daily job. Running five is a different job: you can no longer walk the corridors, so you depend on numbers, routines and trusted branch managers. Groups that grow well decide early what is the same everywhere, what each branch decides for itself and how information flows to the owner. This article lays out a practical way to think about that.
Decide what is central and what is local
A simple table avoids many arguments. Write it down and share it with every branch manager.
| Topic | Usually central | Usually local |
|---|---|---|
| Brand, policies, code of conduct | Yes | |
| Academic calendar and curriculum framework | Yes | Local events |
| Fee structure and discount rules | Yes | Case-by-case approval within limits |
| Admissions criteria | Yes | Day-to-day enrolment |
| Hiring standards and pay scales | Yes | Interviewing and selection |
| Timetable | Yes | |
| Daily attendance and discipline | Yes | |
| Parent communication | Templates | Day-to-day messages |
| Purchasing | Contracts and suppliers | Small local purchases |
Your own table may differ, for example if branches serve different curricula or countries. What matters is that the line is clear.
Standardise the language of data
Comparing branches only works if "present", "enrolled" and "overdue" mean the same thing everywhere. Agree on:
- Names of grades, stages and subjects across branches.
- Definitions of key terms: when a student counts as enrolled, when a fee counts as overdue, how attendance rate is calculated.
- The academic year and term dates.
- The chart of fee items and the numbering of invoices.
Without shared definitions, a dashboard produces arguments instead of decisions.
Track a small set of numbers centrally
You do not need fifty indicators. Start with the few that tell you where to look.
- Enrolment. Students by branch and grade, against seats available, and the admissions pipeline for next year.
- Attendance. Student and teacher attendance rates by branch, and branches with unusual absence.
- Money. Revenue, collections and overdue balances by branch, and expenses against budget.
- People. Headcount, vacancies, staff turnover and open requests.
- Parent signals. Open complaints and how long they take to close.
Review them in a fixed monthly meeting with each branch manager, and use the same page for every branch so that the conversation is about the work and not about the report.
Give branch managers the right tools and boundaries
- Each branch manager sees their own branch fully and nothing else, unless they need a view of the group.
- Approval limits are written down: a branch can give a discount up to a set amount, above that it needs head office.
- Central finance can see all branches, with consolidated and per-branch views.
- Every sensitive action is logged, so that questions can be answered without suspicion.
A playbook for opening a new branch
- Before opening. Create the branch in the system with its own staff, classes, fee plan and calendar, copied from the group's standard.
- Hiring. Use the group's roles and pay scales so that the new branch is aligned from the first month.
- Admissions. Open the admissions page and track leads and visits from the beginning.
- First month. Assign an experienced manager from another branch as a mentor and review the core numbers weekly.
- First term. Hold a review against the standard and adjust.
The more of this you can copy rather than rebuild, the faster a new branch reaches the same quality.
Mistakes to avoid
- Letting each branch choose its own tools, then merging data by hand every month.
- Centralising everything, which slows branches and removes accountability.
- Measuring too many things and acting on none.
- Treating branches in different countries identically when currency, tax and regulations differ.
What Classti offers for groups
Classti includes a school owner dashboard that shows the key figures of every branch on one screen, compares branches, consolidates revenue, collections and overdue fees, lists staff across branches, raises alerts and lets the head office manage branches, subscriptions and permissions centrally, while each branch keeps its own data and roles. It supports branches in several countries and currencies. Read about the fees and finance module and the admissions module, compare ways of working in Classti vs traditional local systems, or book a demo for your group.