COACHING MANAGEMENT · EVALUATION GUIDE
How to Evaluate a Coaching Institute Management Software Demo
A centre-specific demonstration plan covering enquiries, admissions, batches, attendance, fees, examinations, staff and owner questions.
Conceptual product view · no customer records or performance figures
THE SHORT ANSWER
Prepare coaching-centre scenarios and ask the provider to follow each from enquiry through the relevant learner or batch record. Test fees, attendance, examinations, staff administration, communication and reports with the people who own those tasks. Record what was shown versus described, confirm capability boundaries and keep multi-centre oversight distinct from centre operations.
01 / CENTRE SCENARIOS
Bring the institute’s actual operating questions to the demonstration.
Ask counsellors, faculty, accounts staff and centre managers to nominate one ordinary task and one exception. A prospective learner may become an admission; a learner joins or changes a batch; an instalment is partly collected; an attendance entry needs review; an examination result is discussed. These scenarios reveal how records connect in daily work.
Agree the scope and time before the call. Use fictional names and data, and ask which Campus subscription or configuration is being shown. Keep a note-taker focused on behavior and unresolved questions rather than screen count.
02 / ENQUIRY & LEARNER
Follow an enquiry into admission and the learner’s current context.
Ask how a counsellor records programme interest, assigns a follow-up and identifies when the institute has made an admission decision. Then review how the learner is associated with course and batch context. Include a possible duplicate or an incomplete contact detail.
Check who decides admission, who verifies the record and which data carries forward. Separate the institute’s policy from what the product stores. Confirm exact fields and transitions rather than accepting ‘complete student management’ as a precise answer.
03 / BATCH, ATTENDANCE & FEES
Test a routine centre day and one change to the learner’s records.
Review batch assignment, schedule context and attendance for a representative session. Ask how corrections are handled and what history is visible. Confirm actual attendance methods and configuration; do not assume unverified capture devices or integrations.
Trace a fee obligation through an instalment, payment and receipt. Ask how a recent or partial payment affects the balance and which reconciliation work remains with the institute. Payment provider integration or automatic settlement must be confirmed separately.
04 / EXAMS, FACULTY & COMMUNICATION
Check academic and staff workflows without merging their boundaries.
For examinations, ask how course, batch, subject, schedule and maximum marks are represented and how results are reviewed. Negative marking and online exams are declared; OMR and question-bank tools are not supported. Confirm exact behavior and avoid assuming a particular assessment format.
Review faculty profiles, assignments, attendance/leave and payroll as separate concerns. Ask how communication is directed to learners, parents/guardians or staff and which channels are confirmed. Campus communication does not establish two-way replies.
05 / REPORTS & MULTI-CENTRE
Ask what an owner can learn and what remains local to each centre.
Choose a real management question and ask to trace the report’s period, filters and source records. Review how exports are controlled. A chart or rank does not explain causes; ask what staff should validate before acting.
If the institute has several centres, distinguish each Campus operational subscription from the separate Admin Console oversight layer. Ask which owner views are currently confirmed and what eligibility applies. The oversight console does not create or edit operational records.
06 / EVIDENCE & FOLLOW-UP
Leave with a written record of shown, unshown and unresolved scope.
For every scenario, write what the provider demonstrated, what was only described and what requires evidence or clarification. Categorise a gap as configuration, training, policy, current capability or a future proposal. Do not convert roadmap language into a released claim.
Compare results against your requirements with the people who will use the product. Request written confirmation for material commercial or technical assumptions and read current pricing and policy pages. The demonstration is one source of evidence, not a commitment by itself.
A FIELD GUIDE FOR YOUR TEAM
A coaching-centre demo evidence log
Use the same scenarios for each provider. Capture the evidence, current capability and open question without assigning unsupported scores.
| Lens | Question to ask | What to record |
|---|---|---|
| CENTRE SCENARIOS | Bring the institute’s actual operating questions to the demonstration. | A short scenario set with role-specific observers and fictional data. |
| ENQUIRY & LEARNER | Follow an enquiry into admission and the learner’s current context. | A demonstrated hand-off with ownership, identity and an exception. |
| BATCH, ATTENDANCE & FEES | Test a routine centre day and one change to the learner’s records. | A batch/session scenario and a fee/receipt exception walkthrough. |
| EXAMS, FACULTY & COMMUNICATION | Check academic and staff workflows without merging their boundaries. | An evidence record for academic, staff and channel boundaries. |
| REPORTS & MULTI-CENTRE | Ask what an owner can learn and what remains local to each centre. | A report definition and an explicit centre-versus-owner system boundary. |
| EVIDENCE & FOLLOW-UP | Leave with a written record of shown, unshown and unresolved scope. | A follow-up register with each open item assigned to an owner. |
CODEPEX IN CONTEXT
Useful guidance begins with clear scope.
Campus-specific claims should be checked against the owner-controlled capability registry. The demo should use fictional data. OMR and question-bank features are not supported, two-way replies are not declared, and Campus Transport/Library are not public released capabilities. Admin Console is a separate oversight layer, not centre-level operational CRUD.
Product-specific statements are based on the current owner-controlled capability declaration. Ask CodePex to confirm any institution-specific configuration or unlisted requirement.