SCHOOL ERP · MULTI-BRANCH GOVERNANCE
Multi-Branch School Management: What Should Stay Local and What Owners Should See Centrally
A practical governance model for keeping branch operations local while giving authorised owners a clear, bounded oversight view.
THE SHORT ANSWER
A multi-branch school group should distinguish the work performed at each branch from the information owners need to review across subscriptions. Keep attendance, fees, student records and other operational actions within each branch’s School ERP account. Use the separate Admin Console only for its confirmed owner-level oversight functions; it is not a central operational workspace.
01 / TWO RESPONSIBILITY LAYERS
Separate the branch’s operational account from group-level oversight.
A school group may want consistent visibility while each campus handles its own day-to-day work. Those needs are connected, but they are not the same system responsibility. Branch staff need the tools and permissions for the records they maintain; owners need an appropriate view to understand the group without taking over each local task.
Define the boundary before comparing dashboards. Student admissions, attendance, fee records and corrections remain operational work in the relevant subscription. An owner-level overview is not a substitute for branch staff entering or approving those records.
02 / LOCAL RESPONSIBILITIES
Keep decisions close to the people accountable for each branch.
Each branch should identify who owns student administration, fee review, attendance exceptions and staff access. Local context matters: a schedule change or collection discrepancy often needs the person who understands the underlying event. A group-wide view can surface a question, but it cannot supply all the details needed to resolve it.
Document which decisions are local and how they are escalated. Avoid a process where every exception waits for a central owner to perform an action that belongs to the branch. Clear local ownership makes oversight more useful because the next step is assigned to someone who can actually take it.
03 / OWNER INFORMATION NEEDS
Decide which cross-branch questions are genuinely useful.
Owners may want to know whether subscriptions are active, whether a group trend deserves discussion or which branch needs a follow-up conversation. Translate these interests into specific review questions and identify what information is appropriate to see centrally. Avoid collecting detailed student records simply because a summary view is available.
For every owner view, document its source, period, meaning and limitation. If the owner sees a difference between branches, the next step should normally be to ask the local team for context—not to assume that the number proves performance or cause.
04 / COMPARISON WITH CONTEXT
Compare branches only when the measures and operating conditions are comparable.
A larger branch may have more admissions, collections or attendance entries simply because it serves more learners. Raw totals can mislead when enrolment, programme mix, timing or data completeness differ. Confirm the definition and period for each measure before drawing a comparison.
Use comparisons as a starting point for a conversation. Ask local managers what changed, whether the records are complete and which operational factors matter. Avoid rankings or automatic interventions based on an unexplained outlier.
05 / ACCESS & NON-INTERFERENCE
Give owners oversight access without turning it into branch CRUD.
Assign owner-level visibility to authorised people and review it when responsibilities change. Branch staff should continue using their individual operational accounts. Keep credentials separate and make it clear where a user should go to perform a task versus review group context.
The Admin Console boundary is deliberate: it supports eligible owner-level oversight and does not create, change or delete operational records or trigger branch workflows. If an owner needs an operational correction, the request should return to the branch process with an accountable local actor.
06 / GOVERNANCE CHECK
Review the model as subscriptions, people and processes change.
When a branch opens, changes ownership or adopts another product, revisit which subscription contains its records and who can review the group. Confirm eligibility requirements and current Admin Console scope rather than assuming every account or product is included.
Keep a periodic review of owner access, local responsibilities and unresolved comparisons. Record the date, the information sources consulted and any follow-up assigned. The goal is informed oversight—not central micromanagement or duplicated operations.
A FIELD GUIDE FOR YOUR TEAM
A branch-versus-owner responsibility map
Before connecting branches, document where work is performed, what an owner may review and who can act on exceptions.
| Lens | Question to ask | What to record |
|---|---|---|
| TWO RESPONSIBILITY LAYERS | Separate the branch’s operational account from group-level oversight. | A responsibility diagram naming the branch operator and owner reviewer. |
| LOCAL RESPONSIBILITIES | Keep decisions close to the people accountable for each branch. | Named branch owners for recurring workflows and exception resolution. |
| OWNER INFORMATION NEEDS | Decide which cross-branch questions are genuinely useful. | A short owner-view inventory tied to decisions and minimum necessary detail. |
| COMPARISON WITH CONTEXT | Compare branches only when the measures and operating conditions are comparable. | A comparison note that records denominator, period and relevant local context. |
| ACCESS & NON-INTERFERENCE | Give owners oversight access without turning it into branch CRUD. | A documented access boundary and correction hand-off back to the branch. |
| GOVERNANCE CHECK | Review the model as subscriptions, people and processes change. | A periodic subscription, user and oversight-scope review. |
CODEPEX IN CONTEXT
Useful guidance begins with clear scope.
The approved architecture keeps each branch’s operational records and workflows within its separate School ERP subscription. Eligible owners use CodePex Admin Console for the confirmed cross-subscription oversight scope. Admin Console cannot create, edit or delete operational records or trigger branch workflows. Verify eligibility and currently declared oversight views.
Product-specific statements are based on the current owner-controlled capability declaration. Ask CodePex to confirm any institution-specific configuration or unlisted requirement.