Agree what belongs to the group and to each campus
List decisions that the central team owns and those that stay with the campus. The group may want a consistent reporting period, while each school handles its own daily attendance and reception work. Make the boundary explicit. Otherwise, a central administrator may assume a local team has completed a task that was never assigned to anyone.
Build a simple responsibility sheet for student records, fees, staff access and parent notices. Identify who corrects an error and who approves a change affecting more than one campus. Consistency does not require every school to use identical class labels or fee arrangements. It requires the group to understand those differences when records are compared or actions are coordinated.
Define comparable figures before building a report
Agree the reporting date, academic year and meaning of each measure. Collections, revenue, outstanding dues and cash held are different questions. Ask the accounts owners to explain the source records and exclusions for the figures they use. A campus with an incomplete setup should not quietly appear as a campus with no activity simply because the dashboard has an empty value.
Use an illustrative comparison with two campuses and one reporting period. If Campus A reports 200 enrolled students and Campus B reports 150, confirm both counts use the same active-student definition. Then inspect a sample from each. The purpose is to make the combined figure explainable, not to create a league table from numbers whose underlying definitions differ.
Test central access and the campus context
Sign in with an authorised central role and a separate campus role. Check which schools each can see and which actions they can perform. When switching campuses, look for a clear indication of the active workspace before editing a student or sending a notice. Similar class names across branches make an incorrect context easy to overlook during a busy office day.
SkoolMatic includes a Campuses area with access checks, campus summaries and switching for an authorised central user when multi-campus access is enabled. The screen includes measures such as students, teachers and fee-related summaries. Demonstrate the exact permissions and underlying records with your group. Do not infer that every staff role can switch campuses merely because the central administrator can.
Keep student movements and staff changes controlled
A student moving between campuses needs more than a copied name. Confirm the receiving class, guardian details, previous academic references and the financial handover that the school owners approve. Decide which campus remains responsible for historical records. Use the supported transfer or reviewed record process rather than independently creating a second active profile without a clear reason.
Similarly, review staff access when a teacher changes campus or an administrator leaves the group. The new work location should not accidentally preserve access that is no longer required. Ask the product team to demonstrate the supported membership and permission process. A multi-campus overview should not be described as an automatic student transfer or shared payroll service unless those particular workflows have been verified.
Coordinate communication without losing the audience
Before a group announcement, identify whether the message concerns every campus or a selected school, class or group. Check language, dates and contact details for each audience. A notice about one campus’s closure can confuse families elsewhere when sent from a group-wide list. Keep an authorised reviewer for broad announcements and a clear route for campus-specific corrections.
Review each campus’s configured channels and services. Messaging approvals, sender arrangements and available credit may affect whether a notice can be sent. Ask the demonstrator to select a small sample audience and show the resulting scope without sending an unnecessary live message. Central oversight does not remove the need to respect the active campus and the current communication configuration.
Review exceptions with the campus team
Use the group view to identify questions worth asking: an unexpected change in student count, an unusual collection pattern or a campus whose data has not been reviewed. Ask the local owner to explain the records before deciding what action to take. A dashboard should support a conversation about the work, particularly when a school is onboarding or correcting imported records.
Pilot the arrangement with two campuses and a small set of agreed reports. Check central access, campus restrictions and a correction made by the proper owner. The student information system guide is useful when deciding which profile details need consistent handling. Bring the reporting definitions and role list to a SkoolMatic demo so your group can test its own operating model.
What schools should check
Ownership
Separate central decisions from campus responsibilities.
Definitions
Compare the same periods and record definitions.
Context
Confirm the active campus before edits or notices.
Review
Ask local owners to explain unusual figures.
Related questions
Can every school employee access every campus?
Access should follow the assigned role and enabled services. In SkoolMatic, central campus switching is permission-dependent. Test a central role and a campus role separately before rollout.
Does a group dashboard automatically transfer students between schools?
Do not assume that it does. A transfer needs a supported process for student identity, class placement, history and financial responsibility. Verify that workflow separately from campus reporting.
How should a trust compare collection figures?
Agree the date range, record source and meaning of the measure with the accounts owners. Compare equivalent periods and investigate missing or unusual data before combining figures or judging campus performance.
Explore the school software behind these workflows
Review the product workflow with your school team, then bring your current records and questions to a live demo.
Explore SkoolMatic featuresBook a Demo