COACHING MANAGEMENT · MULTI-CENTRE GOVERNANCE
Multi-Centre Coaching Management: Branch Operations and Owner Oversight
A practical boundary model for centre-level Campus work and eligible owner oversight across separate subscriptions.
THE SHORT ANSWER
Keep teaching, admissions, fee collection, attendance and other daily work inside each centre’s own Campus subscription. Owners may use the separate Admin Console for the oversight scope that is currently confirmed and eligible. It does not create, edit or delete operational records or trigger centre workflows; comparisons should prompt a local conversation rather than central intervention.
01 / CENTRE BOUNDARY
Keep day-to-day centre operations within the centre’s own account.
A coaching group may share a brand while each centre manages its own learners, batches, faculty, attendance and fees. These records depend on local schedules, policy and people who can resolve the underlying issue. Define the centre subscription that owns each operational record and keep staff actions in that context.
A consolidated owner view does not replace local work. When an owner notices an exception, the operational next step belongs to an authorised centre user. This preserves accountability and avoids a central person changing information without local knowledge.
02 / SEPARATE SUBSCRIPTIONS
Use separate centre subscriptions deliberately, not as a shared database.
Before adding a location, clarify its account boundary, user list and operating responsibilities. Each centre should know which subscription contains its records and how its staff request access. A group’s commercial structure should be confirmed from current terms rather than inferred from the existence of an oversight product.
Review what information, if any, must be summarised across locations and the minimum detail owners need. Do not promise that one centre can search or operate on another centre’s learner records unless the owner-approved capability declaration expressly permits it.
03 / OWNER QUESTIONS
Design group oversight around decisions an owner can actually make.
An owner may need to know subscription status or review a group-level pattern to decide where a conversation is needed. Define the question, period and source for each summary. Keep student-level details out of an owner view unless the declared scope and purpose require them.
Set expectations for how an owner escalates a concern. A dashboard can identify a topic; local management should verify the records, context and appropriate response. This prevents a high-level signal from becoming an automatic instruction.
04 / FAIR COMPARISON
Compare centres only after checking size, programme and period context.
Raw admissions, attendance or collection totals often reflect centre size and programme mix. Before comparing, confirm that definitions and dates match and that data completeness is similar. If the denominator or cohort differs, a direct ranking may mislead.
Use comparison to ask what changed, not to declare which branch is best. Invite local managers to explain schedules, staffing or cohort differences, and document what the summary cannot tell the owner.
05 / ADMIN CONSOLE LIMIT
Use Admin Console for oversight—not operational record maintenance.
Admin Console is a distinct owner-level layer for confirmed oversight across eligible subscriptions. It is not the interface for admitting students, editing fees, changing attendance or assigning batches. Those actions remain in the applicable Campus centre subscription.
If an owner requests a correction, route it to the centre’s authorised process and retain the normal review responsibility. Confirm eligibility and available views rather than assuming every subscription or product qualifies.
06 / PERIODIC GOVERNANCE
Revisit subscriptions, people and access as the group evolves.
A new centre, staff departure or change in ownership can alter the access map. Review who belongs to each subscription, which owners need oversight and whether the group still meets applicable eligibility conditions. Remove access that no longer has a business purpose.
Keep this governance review separate from operational reporting. Record unresolved product-scope questions and request confirmation before changing how the group uses its systems. The goal is informed visibility with local authority intact.
A FIELD GUIDE FOR YOUR TEAM
A multi-centre responsibility check
Use this to agree which work stays at each centre, who reviews group information and how an exception returns to the operational owner.
| Lens | Question to ask | What to record |
|---|---|---|
| CENTRE BOUNDARY | Keep day-to-day centre operations within the centre’s own account. | A subscription map showing each centre’s operational owner. |
| SEPARATE SUBSCRIPTIONS | Use separate centre subscriptions deliberately, not as a shared database. | A centre-to-subscription register with authorised users. |
| OWNER QUESTIONS | Design group oversight around decisions an owner can actually make. | A documented owner question, information need and local follow-up owner. |
| FAIR COMPARISON | Compare centres only after checking size, programme and period context. | Comparable definitions plus local context captured before conclusions. |
| ADMIN CONSOLE LIMIT | Use Admin Console for oversight—not operational record maintenance. | A clear path from owner observation back to the local operational team. |
| PERIODIC GOVERNANCE | Revisit subscriptions, people and access as the group evolves. | A periodic subscription and access review with recorded decisions. |
CODEPEX IN CONTEXT
Useful guidance begins with clear scope.
The approved model uses separate Campus subscriptions for centre operations and a distinct customer-facing Admin Console for eligible owner oversight across subscriptions. Cross-branch operational CRUD is not supported. Confirm eligibility, available views and current commercial terms; do not infer broader functions.
Product-specific statements are based on the current owner-controlled capability declaration. Ask CodePex to confirm any institution-specific configuration or unlisted requirement.