COACHING MANAGEMENT · MULTI-CENTRE OVERSIGHT
What Should a Multi-Centre Coaching Owner See in a Management Dashboard?
Define useful owner-level visibility across coaching subscriptions while keeping enquiry, learner, batch and fee operations with local teams.
THE SHORT ANSWER
A multi-centre owner view should identify eligible subscriptions, show the context and period behind permitted measures, and make missing or incomplete data visible. Owners use the overview to ask questions and coordinate support; each centre team remains responsible for its Campus records and workflows. Confirm what the Admin Console actually exposes before specifying a dashboard requirement.
01 / SUBSCRIPTION COVERAGE
Make each centre and its product account easy to distinguish.
The owner should understand which subscriptions appear, how each centre is identified and what is excluded. Subscription association needs an authorised basis, not a display-name guess.
Check how a newly added centre or changed subscription enters the view and who approves that relationship.
02 / DECISION-LED MEASURES
Show only information that supports a defined portfolio decision.
Owners may need to review subscription status or permitted operational summaries to identify questions. Each measure should have a clear definition, period and local contact responsible for explaining it.
Avoid an overloaded dashboard that encourages constant monitoring of local work. A few trustworthy indicators can be more useful than many unexplained totals.
03 / PRODUCT & PROGRAMME CONTEXT
Keep centre type, course mix and reporting period visible.
Different centres may run different programmes, academic cycles or fee schedules. A side-by-side value can be misleading without that context. Distinguish Campus subscriptions and avoid comparing them with School ERP measures as if workflows were identical.
Ask how filters, unavailable data and freshness are represented. Test a real comparison with representative centres before relying on it.
04 / LOCAL DETAIL BOUNDARY
Route operational questions back to the responsible centre.
The owner view can reveal an exception that needs explanation. The centre’s authorised staff inspect the local record and decide what action is appropriate within their responsibilities.
The Admin Console does not become a shared Campus workspace or perform operational edits. Set expectations so users know when to switch from portfolio oversight to local follow-up.
05 / ACCESS & PRIVACY
Limit central visibility to the owner roles and information they need.
Define which owners need subscription summaries, financial context or other details. Confirm role controls and avoid exposing learner-level information where a summary answers the management question.
Review who can access the portfolio when ownership or responsibilities change. Confirm product behavior rather than assuming that a given permission model is available.
06 / ACCEPTANCE & GOVERNANCE
Test edge cases and assign an accountable owner for the dashboard itself.
Test a new subscription, a centre with incomplete data, a period boundary and a comparison across different programme contexts. Validate each displayed measure against authorised local evidence.
Name who maintains definitions, reviews access and communicates changes. A useful owner dashboard depends on governance as much as its visual design.
A FIELD GUIDE FOR YOUR TEAM
A coaching owner-dashboard requirements guide
Use these requirements when evaluating central visibility across distinct coaching-centre subscriptions.
| Lens | Question to ask | What to record |
|---|---|---|
| SUBSCRIPTION COVERAGE | Make each centre and its product account easy to distinguish. | A current subscription roster with owner-verified associations. |
| DECISION-LED MEASURES | Show only information that supports a defined portfolio decision. | A concise measure set mapped to decisions and owners. |
| PRODUCT & PROGRAMME CONTEXT | Keep centre type, course mix and reporting period visible. | Visible product, programme, date and data-availability context. |
| LOCAL DETAIL BOUNDARY | Route operational questions back to the responsible centre. | A defined escalation path to the local record owner. |
| ACCESS & PRIVACY | Limit central visibility to the owner roles and information they need. | A proportionate owner-role matrix and review process. |
| ACCEPTANCE & GOVERNANCE | Test edge cases and assign an accountable owner for the dashboard itself. | A dashboard test plan, definition owner and review cadence. |
CODEPEX IN CONTEXT
Useful guidance begins with clear scope.
Campus remains scoped to an individual centre subscription. The separate Admin Console provides authorised oversight across eligible subscriptions; it does not create, edit or delete learner, fee or batch records or trigger local workflows. Verify roles and information scope directly.
Product-specific statements are based on the current owner-controlled capability declaration. Ask CodePex to confirm any institution-specific configuration or unlisted requirement.