The rule for testing coaching software: run one real batch end-to-end in the demo — admission → attendance → fees → report. The core unit of coaching is the batch (not a school-style class); software that cannot smoothly run one batch’s full lifecycle fails everything else, whatever else it claims.

What to verify: one batch’s admission-attendance-fee workflow

Make the vendor run this sequence in one session (your sample data):

Step Task Verification question
1. Create batch “SSC-2027 Physics, 7 PM” time-slot and capacity captured?
2. Admit 3 students; one also in a second batch same student in two batches — any issue?
3. Attendance evening class roll-call guardian SMS on absence?
4. Fees admission fee + partial first month receipt and dues both correct?
5. Test model-test marks entry batch-wise merit list generated?
6. Report batch summary admission/attendance/fees on one page?

Rule: proof at every step (screenshot/printout) — an unproven step is not a pass.

A usable sample: the batch demo checklist

Per vendor, record:

  1. Steps 1–6: pass / partial / fail.
  2. Time per step (minutes) — estimates daily staff cost.
  3. Non-batch needs (library etc.) — separate small demo.
  4. Decide the pass rule upfront: 5 of 6 = conditional accept; steps 3–4 failed = eliminate.

Batch-based demo: workflow steps and limitations

  1. Feed real batch numbers (student count, fees) into the demo.
  2. Do not skip the evening batch — coaching’s main shift is evening, and that is where software gets tested hardest.
  3. Limitation: demo environments are fast — pad time estimates by 25%; and a demo does not prove sustained usage — ask for a trial.

Demo: questions to ask before your demo

  • Does a batch change keep attendance and fee history?
  • Same teacher, two batches, same time — is the conflict caught?
  • Can the full batch’s data be used in the trial?

All coaching-specific features are on the coaching page; fee flow in fee management, test flow in the exam module, and to start see contact.

Demo FAQ

How many vendors get the same demo?

Two or three with the same checklist — comparison only works on the same measure.

They show heavy features but skip the batch cycle?

Record “batch-cycle demo not performed” — make it mandatory in the trial before deciding.

Does a small coaching (50 students) need this much verification?

A shorter checklist, yes — but the batch cycle is all of coaching’s daily work; a system failing here fails daily.