When a school group opens a second campus, the hardest question is often not “Which software do we use?” It is “Which record should staff trust when the same family appears in central admissions, a campus spreadsheet and a finance inbox?”
Direct answer
Multi-campus schools need a short, written data-governance model: name the source of truth for each core record, define who owns each lifecycle stage, limit access by role and campus, publish shared reporting definitions, and review exceptions regularly. This gives group leaders comparable information without removing local teams’ ability to serve families.
Start with the records that cross campus boundaries
KPM’s Private Education Division is responsible for standards, registration and oversight in the private-education sector, while Malaysia’s government portal distinguishes several kinds of private educational institution. That is a reminder not to assume every campus has identical operating requirements. Start by mapping the records that must travel safely between central and local teams.
| Record | Source of truth | Typical owner | Handover moment |
|---|---|---|---|
| Enquiry and application | Admissions workflow | Central admissions or named campus admissions lead | Offer accepted or applicant withdrawn |
| Student profile | Student record | Receiving campus administrator | Student transfer, withdrawal or graduation |
| Fee responsibility and balance | Billing record | Finance team with approved campus input | Enrolment confirmation, fee change or exit |
| Attendance | Class attendance record | Campus teaching and operations team | Daily close and group reporting cycle |
| Parent communication | Approved communication record | Named sender and receiving campus | Change of campus or case ownership |
The “source of truth” is not necessarily one team. It is the place staff are expected to check and update before creating another version.
Agree common definitions before building reports
Group dashboards become misleading when each campus counts differently. Define terms in a shared one-page dictionary.
| Term | Definition to agree | Decision owner |
|---|---|---|
| Enquiry | The event that creates a prospect record | Admissions lead |
| Confirmed enrolment | The exact acceptance and payment or document condition | Admissions and finance leads |
| Overdue balance | The due-date and exception rule | Finance lead |
| Attendance rate | Included sessions, exclusions and reporting period | Operations lead |
| Withdrawal | The effective date and required approval | Campus leader and finance lead |
Use the definitions in training, report labels and monthly reviews. If a campus needs an exception, document it rather than silently changing a field or formula.
Give people only the access they need
Student and family information should not become more widely visible simply because the group has grown. The Department of Personal Data Protection provides guidance through its FAQ that schools can use when reviewing their privacy approach. Apply your own policies, contracts and legal advice to the data you hold.
A practical access matrix lists role, campus scope and permitted actions:
| Role | Campus scope | Permitted action |
|---|---|---|
| Teacher | Assigned classes | View teaching-relevant student and attendance information; record attendance |
| Campus administrator | Own campus | Maintain operational records and route exceptions |
| Group finance | Assigned group entities | View billing records and process approved adjustments |
| Group leader | Defined reporting scope | View consolidated reporting, not necessarily every detailed note |
Review access when staff join, move campus, change responsibilities or leave. A strong permission model is part of everyday operations, not an annual IT task.
Run a monthly exception review
Once a month, a small group—usually operations, admissions and finance—should review duplicates, unowned records, campus transfers, unresolved fee-owner changes and unusual report values. Keep a simple log: issue, record owner, decision, due date and closure date.
This is where hidden workarounds surface. It is more useful to fix one recurring handover than to ask every campus for another spreadsheet.
A 30-day implementation checklist
- List the five core records shared by central and campus teams.
- Name one source of truth and owner for each.
- Publish the definitions used in group reporting.
- Map role, campus scope and permitted actions.
- Document the handover for transfers, withdrawals and fee-responsibility changes.
- Schedule a monthly exception review with named attendees.
- Train staff on the rule: check and update the agreed record before creating a parallel list.
How Oodlins can help
Oodlins can help groups organise student, attendance, billing and parent-operation records around clear roles and operational follow-up. Explore school management, staff management, and the broader multi-campus school operations guide.