How to choose coaching institute software: a 20-point evaluation checklist

To choose coaching institute software, test four areas in order: fee depth (installments, dues, late fines, partial payments, receipts), daily operations (enquiries, attendance, exams), trust features (verifiable certificates, role-based access), and commercial honesty (published pricing, data export, real trial). A product that fails the fee-depth questions fails the institute — start there.

We evaluated coaching software as buyers before we built any — a purpose-built IMS, the famous apps, a WordPress patchwork. Each demo was impressive; each gap surfaced only months in, at the counter, mid-argument. This checklist is the one we wish someone had handed us: the questions that expose gaps during the demo, when switching is still free. Yes, we now build Amatya — so the checklist sticks to questions any vendor can be tested against, ours included.

Part 1 — Fee depth (questions 1–6, where products fail first)

1. Can a student have an installment plan with custom amounts and dates, agreed at admission — not just "monthly fee"?
2. Can I record a partial payment against a due and see the balance carry forward on the receipt?
3. Do late fines apply automatically per a policy (grace days, amount), with waivers logged by name and reason?
4. Is there a dues screen that answers "who owes what today" in one view — without generating a report?
5. Are receipts numbered automatically in one unbroken series, with amount in words and balance shown?
6. Can I see collections vs. expected for a month in one number?

Part 2 — Daily operations (7–12)

1. Do enquiries carry a source, an owner and a follow-up date — and does anything happen when the date passes?
2. Can a demo class be scheduled and its outcome recorded, converting to admission without re-typing?
3. Is student attendance markable batch-wise in seconds?
4. Does staff attendance exist with something stronger than the honour system (photo, geotag), and does payroll read it?
5. Do exams and results flow into marksheets without transcription?
6. Can online tests run with secure per-student links, results landing in the same records?

Part 3 — Trust & control (13–16)

1. Are certificates publicly verifiable (QR/code) without a login — so an employer can check one in 10 seconds? (Why this matters: the fake-certificate problem.)
2. Is access role-based — counter staff cannot delete records or grant discounts; teachers see their batches only?
3. For multiple centres: is data isolated per centre with one owner console — structurally, not by promise?
4. Does every payment, edit and waiver leave an audit trail with a name on it?

Part 4 — Commercial honesty (17–20)

1. Is pricing published — can you compute your exact cost without a sales call? Quote-based pricing is a negotiation posture, not a price.
2. Can you export your data — students, fees, history — in a usable format, any time, without begging?
3. Is the trial a real instance of the product with your data, or a canned sandbox demo?
4. Who does the migration from your registers/Excel/current software — you, or them, and at what cost?

Scoring it like an operator

Don't average the score — gate it: any "no" in Part 1 disqualifies, because fees are where software pays for itself. Then compare the survivors on Parts 2–4 and on price-for-your-size. For transparency: Amatya's answers to all twenty are on the platform pages and the pricing page (₹360–450 per student per year, published), and the 14-day trial is a real provisioned panel — the checklist was, honestly, our product spec.