Multi-campus
One trust, several campuses, one set of records
Campuses sit under a single organisation. Each has its own students, staff, rooms, holidays and fee structures, while academic sessions, board affiliations and the people who oversee them are shared.
What multi-campus support covers
Campuses as their own records
Name, code, address and contact details for each campus, with one marked as the primary campus.
Students and staff per campus
Every student and staff member belongs to a campus, so each branch has a roster of its own.
Rooms per campus
Rooms belong to the campus they are in, so timetable clash checking works against rooms that physically exist at that branch.
Campus holidays
A holiday can apply to one campus or to all of them, so a local closure at one branch does not mark every school shut.
Fee structures per campus
Two branches of the same trust rarely charge the same fees. A structure can be set for the campus it applies to.
Shared sessions and boards
Academic sessions and board affiliations belong to the organisation, so year-end and result rules are configured once, not once per branch.
Where a campus stops and an organisation begins
A trust running three schools usually starts with three separate systems and then spends years reconciling them — three fee reports, three student databases and three sets of logins for the same accountant. The opposite mistake is one flat system in which a branch's records are indistinguishable from everybody else's.
Here the organisation is the boundary for data, and the campus is the boundary for day-to-day operations. Students, staff, rooms, holidays and fee structures belong to a campus. Sessions and board affiliations belong to the organisation, which is what lets promotion and result rules be set up once rather than three times.
One consequence is worth stating plainly. Data is isolated between organisations, not between campuses of the same organisation, and the organisation's administrators work across all of its campuses. If two branches must never see each other's records, they should be separate organisations — and we will say so before setup rather than after.
How many campuses you can run depends on the plan. The number is a limit in the plan catalogue and is listed on the pricing page, so a growing trust moves to a higher limit rather than re-importing into a new system.
Multi-campus: common questions
Can we manage several school branches in one account?
Yes. Campuses sit under one organisation, each with its own students, staff, rooms, holidays and fee structures, while academic sessions and board affiliations are shared across them.
Can each campus charge different fees?
Yes. Fee structures can belong to the campus they apply to, so two branches of the same trust can charge different amounts without running separate systems.
Are campuses of the same organisation isolated from each other?
Not in the way separate schools are. Data isolation is between organisations, and an organisation's administrators work across all of its campuses. Branches that must never see each other's records belong in separate organisations.
How many campuses does each plan allow?
The campus count is a limit set in the plan catalogue and shown on the pricing page. A trust that outgrows it moves to a plan with a higher limit without re-importing anything.
See Multi-campus against your own school's setup
Tell us your board, your class structure and how you collect fees today, and we will show you the parts that matter to you rather than a generic tour.