Running a Multi-Branch School: Central Control Guide

On one campus the owner can walk the corridors. With three campuses, information arrives through phone calls and weekly summaries, and each branch develops its own habits. The fee structure drifts, receipts look different, report cards use different grading wording, and the owner cannot answer “how many students do we have?” without making calls.

Three symptoms usually appear first. Numbers do not match: enrolment according to the accounts office differs from the branch’s own figure. Policies diverge: one branch allows late-fee waivers, another never does. And talent is stuck: a good coordinator in branch A has no way to share her timetable method or her circular templates with branch B.

The most useful exercise for a group is a one-page table that settles ownership. Treat it as a draft for the trustees or directors to approve.

Write the table first, then check whether your software can enforce it. Many tools can show data for all branches but cannot restrict a branch administrator to their own records, or require central approval for a concession above a limit.

Choose a short list of things that must be identical everywhere, because they affect the parent’s trust and the owner’s control.

• Student admission numbers and ID formats, so a transfer between branches is simple.
• Fee heads and names (tuition, annual charges, transport), even if amounts differ.
• Receipt design and numbering approach, with a branch code in the series.
• Grading scale and remark wording on report cards.
• Attendance rules and the daily cut-off for marking.
• The calendar template, with branch-specific days layered on top.

Differences should be deliberate. A branch in a hill town may start later in winter; a branch in a metro may need longer bus routes. Record such exceptions in one place so they can be explained.

The group dashboard needs a small set of numbers, branch by branch, on one screen. Active students and new admissions this month. Fees due, collected and overdue. Attendance for yesterday and the week. Staff present and on leave. Open complaints and incidents. Enquiries and conversion. Anything else is detail to open when a number looks wrong.

The rule that makes group reporting trustworthy is that every figure comes from the same records the branches use daily. If the branch sends its own monthly report in Excel, it will differ from the system, and the owner will spend time on arguments instead of decisions. Our guide to the principal’s daily dashboard lists ten numbers that also work at group level.

Fee control is the first financial worry. Define who may approve a concession, up to what amount, and what must go to the centre. Make waivers and late-fee reversals visible in a report, with the approver’s name, so patterns are easy to spot. Reconcile branch collections to the bank daily; consider separate gateway accounts per branch, or per entity if the branches are different legal entities, and discuss the structure with your chartered accountant.

For cash, set a limit that a branch may hold and a rule for depositing. For purchases, publish approval levels. These are management practices, but good software records them: if the approval step exists in the system, you can audit it later.

1. Pick a pilot branch with a willing principal and a competent accountant. Do not begin with the most troubled one.
2. Standardise the master data: fee heads, class names, subjects, grading scales, staff designations.
3. Run the pilot for one fee cycle and fix process problems before copying.
4. Replicate to the next branch using the same structure and lessons, with a day of on-site training.
5. Introduce group reports once at least two branches are live and trusted.
6. Review quarterly, with every principal presenting their own dashboard.

On our side, Takshiva supports multi-branch groups with branch records, an overview and per-branch administrator access. This is part of a higher plan and is set up with our team rather than self-service, as described on the multi-branch solution page. Ask any vendor the same question: what happens after the demo, and who does the setup?

Software helps, but a group lives on its principals. Give each one clear authority and a clear scorecard. Hold a monthly review in which branch heads compare dashboards and share one practice that worked. Rotate a coordinator between branches once a year so methods spread. And be cautious about league tables that humiliate; the aim is to lift the weakest branch, not to rank them in public.

Parents judge a group by its weakest branch. A mother who enrols a second child at a newer campus expects the same circular style, the same receipt, the same answer to “how do I pay?” as at the first. When these differ, she assumes the group is disorganised, and she is partly right.

Create a small communication kit that each branch uses: a notice template with the school name and branch, a standard message for fee reminders, a one-page admission guide, and a short script for answering the phone. Let each principal add local content, such as a bus route change, but keep the frame constant. This also saves time, since new branch staff do not have to invent their own formats.

Reserve some channels for group-wide use. The owner or director may send a single message at the start of the year, and the group website carries each branch’s page with up-to-date contact details. Make sure each branch has a named contact for parent complaints, plus an escalation route to the centre when a branch cannot resolve something within an agreed time. Parents should never need to guess whom to approach.

Finally, plan for staff movement. Teachers sometimes transfer between branches, and the system should carry the person’s record without re-creating it, so service history, leave balance and training remain intact. Agree one rule for how transfers are approved and communicated, and apply it to every branch.