The rule before buying coaching software: a written requirements checklist — each daily task on one line, with its verification method beside it. Coaching’s work differs from schools — batches, slot conflicts, multi-course, instalments — so generic school checklists lead to the wrong purchase.

What to verify: an operational spec covering batch membership and conflicts

The requirements sheet:

# Requirement Verification method Criterion
1 Batch = course + slot + capacity have them create a batch in the demo done in 3 minutes
2 One student, multiple courses (one ID) enrol into a second course no duplicate created
3 Conflict warnings (teacher/room/student) create a deliberate conflict warned at entry
4 Batch-wise attendance + SMS take the evening class roll-call SMS sent
5 Fee structure attached to batch admission + partial payment receipt correct
6 Model test + missing marks skip an entry, run report pending list shown
7 Session rollover close old + open new data intact
8 Batch summary report one click printable

If a row’s criterion fails, that requirement is “not present” — a vendor’s “coming soon” gets documented with a version date.

A usable sample: the batch-needs matrix

Build the document on this skeleton:

  1. Introduction: batch count, student count, shifts (morning/evening), course list.
  2. Operational requirements: the 8 rows above.
  3. Roles: who creates batches, who sees fees, who sees reports.
  4. Connections: batch↔fees, batch↔tests, student↔multiple batches.
  5. Implementation: data import, training, who configures.
  6. Limits: what the software will not do.

Batch management requirements: workflow steps and limitations

  1. Fill the checklist yourself before the vendor meeting — every requirement’s verification method is yours.
  2. Drop the word “will” — write “shows / does not show in the demo today”.
  3. Limitation: not all 8 requirements exist in every vendor — hence this is a checklist, not an assumption; a failing score can still be a good vendor, but the risk stays counted in your decision.

Needs checklist: questions to ask before your demo

  • Which of the 8 can you demo now, which later?
  • What is the proposed solution for the gaps?
  • Which version of this document did your quotation assume?

Verify each requirement’s feature on the coaching page, fees on fee management, tests on the exam module and price on the pricing page.

Needs checklist FAQ

Should we send the checklist to vendors beforehand?

Yes — prepared vendors give straight demos; answers also come structured.

The vendor says they can do everything?

In writing — the demo’s verification of the 8 rows is the truth.

Does this checklist work for madrasas/schools too?

The core differs — madrasas need the Hifz-department checklist, schools the class checklist; this one is coaching’s.