COACHING MANAGEMENT · MULTI-CENTRE OVERSIGHT
How to Compare Coaching Centre Performance Without Misreading the Numbers
A fair framework for comparing coaching centres while accounting for programme mix, learner volume, calendars, definitions and local ownership.
THE SHORT ANSWER
Compare centres only when the measure, reporting period, programme context and subscription coverage are clear. A raw total can reflect centre size or course mix rather than performance. Use owner-level visibility to identify questions, then ask each local centre leader to verify source records and explain context; do not treat central oversight as operational control.
01 / COMPARISON PURPOSE
Define the owner question and the decision it may inform.
A comparison may help owners decide where to offer support, investigate a workflow or understand a centre’s operating context. Name that purpose before choosing metrics. A league table without a decision can create pressure while explaining little.
Be clear whether the review is for planning, exception follow-up or resource allocation, and who will see the result.
02 / CENTRE SCOPE
Verify that the right subscriptions and locations are represented.
List the eligible Campus subscriptions included, their effective dates and any centre that is unavailable or newly associated. A partial portfolio should not be presented as complete.
Confirm the owner-approved association between subscription and organisation. Similar names or shared contacts do not prove that an account belongs in the group view.
03 / COURSE & CALENDAR CONTEXT
Account for programme mix, enrolment cycles and different centre schedules.
A centre focused on one exam cycle may have a different enquiry and assessment pattern from a location running year-round courses. Batch sizes, faculty schedules and local calendars can also change totals.
Compare like programmes and periods where possible. If the data cannot support that distinction, state the limitation rather than forcing a common score.
04 / DEFINITIONS & SOURCE
Check the meaning and freshness of every indicator before using it.
Clarify what counts as an enquiry, active learner, attended session or collection, and when each record is included. Confirm filters and data freshness with the available reports.
Ask local staff to verify unexpected results against operational records. The central view identifies a question; it does not carry out the local correction.
05 / FAIR REVIEW
Use differences to invite explanation and shared learning.
A higher or lower measure may reflect operating conditions, staff capacity, record timing or cohort composition. It does not by itself establish quality or effort. Give centre managers an opportunity to explain context before deciding what action is fair.
Look for practices that may transfer between centres, but confirm they suit each local programme and team. Avoid comparing people using data that was not designed for that purpose.
06 / ACTION & GOVERNANCE
Assign local follow-up and revisit the comparison consistently.
Record the central question, the local owner, the action and the review date. Keep branch operations inside each centre’s account and use the authorised local team for any record-level change.
Repeat the comparison with the same definitions when possible. Clear limits and local accountability make owner oversight more useful and trustworthy.
A FIELD GUIDE FOR YOUR TEAM
A fair multi-centre comparison
Use this before discussing differences between coaching locations with owners or centre managers.
| Lens | Question to ask | What to record |
|---|---|---|
| COMPARISON PURPOSE | Define the owner question and the decision it may inform. | A defined owner question and audience. |
| CENTRE SCOPE | Verify that the right subscriptions and locations are represented. | A verified centre population and documented exclusions. |
| COURSE & CALENDAR CONTEXT | Account for programme mix, enrolment cycles and different centre schedules. | A comparison context with course and period assumptions explicit. |
| DEFINITIONS & SOURCE | Check the meaning and freshness of every indicator before using it. | A data-definition note and local source-validation owner. |
| FAIR REVIEW | Use differences to invite explanation and shared learning. | A contextual review with a fair response from each centre. |
| ACTION & GOVERNANCE | Assign local follow-up and revisit the comparison consistently. | A local action plan and a consistent follow-up method. |
CODEPEX IN CONTEXT
Useful guidance begins with clear scope.
Campus subscriptions support individual-centre operations. Admin Console is a separate oversight layer across eligible subscriptions and does not modify local records or trigger workflows. Verify data scope, reports and measures before comparison.
Product-specific statements are based on the current owner-controlled capability declaration. Ask CodePex to confirm any institution-specific configuration or unlisted requirement.