Institutions
How to choose school management software in India: a 12-point checklist
A 12-point checklist for choosing school management software in India: boards, fees and GST, UPI, WhatsApp, languages, DPDP privacy, AI, migration and support.
Choosing school management software is one of the few decisions that touches every person in a school: the principal, teachers, the office, accounts, parents and students. Get it right and the year runs more smoothly. Get it wrong and staff go back to WhatsApp groups and spreadsheets within a term.
Here is a checklist built for Indian schools. Use it in every demo, including ours.
Fit for how Indian schools work
1. Boards and curricula. The system should handle CBSE, ICSE and your state board: syllabus by chapter, grading schemes, report-card formats and holistic progress cards under NEP 2020.
2. Fees the way you actually charge. Look for instalments, concessions, sibling discounts, late fees, and fee plans by class and category. Accounts should cover vouchers, GST and TDS, with an export your auditor accepts (most often Tally).
3. UPI first. Parents expect to pay by UPI from their phone, with an instant receipt. Ask how payments are matched to dues, and what happens when a payment fails halfway.
4. WhatsApp and SMS, done properly. Families read WhatsApp. SMS must be DLT-registered. Ask whether absence alerts reach parents within minutes, not at the end of the day.
5. Your families’ languages. Circulars and messages should reach families in their own language, not only English. Jhamly supports English, Hindi, Kannada, Tamil, Telugu, Malayalam and Marathi.
Safety, privacy and trust
6. DPDP Act readiness. Ask how parental consent is recorded, how data can be deleted on request, and whether any data is ever sold or used for advertising (it should never be).
7. Who can see what. Each staff member should see only what their role allows, and a clerk at one campus should not see another campus’s fees. Ask how this is enforced: in the database itself, or only in the screens?
8. Sensitive identifiers. Aadhaar numbers should be encrypted, masked on screen and never sent to AI services.
Will it reduce work, or just move it?
9. What it does on its own. Ask what the system prepares without anyone clicking, such as cover plans, enquiry follow-ups, fee reminders and flags for learners who are slipping. If the answer is “reports”, it is a database.
10. AI with limits. AI should prepare drafts with sources, and people should approve anything involving money, marks, certificates or safety. Ask the vendor to show you those limits in the product.
Switching and support
11. Migration and timeline. Who moves your data from the current system or spreadsheets, how long it takes, and what it costs. (Jhamly: live in 14 days, with free data migration and training for every role.)
12. Training and adoption. Software fails when teachers do not use it. Ask how each role is trained, and whether the parent and student apps work on everyday phones without a download.
Bonus: think beyond one campus
If you run, or plan to run, more than one school, check for group dashboards, a single admissions application across campuses, and central fee and grading settings that each campus can apply.
Use the checklist
Print this list and score each vendor out of 12. The right system should make the hardest days of your year, such as admissions season, fee deadlines and exam week, noticeably calmer.
Want to see how Jhamly scores? Book a demo or browse all Jhamly features.