Choosing school management software is a bigger decision than it looks. The system you pick will hold your students’ records, your fee ledger and your staff payroll for years, and moving away from it later is painful. This checklist is written for school owners, principals and trustees, not for IT teams.
Start with problems, not features
Before you see a single demo, write down the five things that hurt most today. For many schools they are the same: fee counter queues, attendance that reaches parents too late, report cards that take weeks, staff payroll that depends on one person, and parents who keep phoning the office. Judge every vendor against your list instead of their feature sheet.
The 10-point checklist
1. Is it one system with one student record?
The biggest source of rework is typing the same student into several tools. Check that admissions, attendance, exams, fees and communication all share one record. If a vendor sells “modules” that are really separate products, ask how data moves between them. See what a joined-up school ERP covers.
2. Can you write your own roles?
Your accountant should not see marks, and your class teachers should not see payroll. Ask whether roles are fixed or whether you can build your own from individual permissions, and whether those permissions are enforced on the server. Hiding a menu item is not security. Read how role-based access control should work.
3. Does it work with the hardware you already own?
If you have biometric or gate devices, ask whether the software ingests punches from them or insists you buy new ones. The cheapest hardware is the hardware you already paid for. We explain the options in our guide to biometric attendance for schools.
4. How does it reach parents?
In India, a notice that never reaches WhatsApp or SMS is often a notice that was never read. Check which channels are supported, and whether you can choose a different channel for each type of message. Ask whether each message is recorded.
5. How are fees and accounts protected?
Ask what happens when a receipt is entered wrongly. If staff can simply edit or delete it, so can anyone else. A trustworthy ledger is append-only: corrections are reversals and both entries stay visible. This is explained in our guide to automating school fee collection.
6. Who owns your data?
Ask for it in writing: can you export all of your data and files, in a usable format, whenever you want, including if you leave? If the answer is vague, treat that as the answer.
7. Are schools’ records kept separate and backed up?
If you run several branches or the vendor serves many schools, records should be kept separate between them. Ask how access is controlled, whether activity is logged, and where backups live. A good vendor will happily talk your trustees through it.
8. Is the price easy to predict?
Per-student pricing grows with your admissions, and per-module pricing grows with your needs. Ask for the cost at your current size and at 20 percent larger, and ask what is not included. Our guide to school ERP cost shows how to compare quotes.
9. How hard is it to move in?
Ask how existing student, staff and fee records are imported. The best answer is a spreadsheet import with a dry run, so you see the errors before anything is saved. Our implementation checklist walks through the rollout.
10. Can you talk to a person who has done this?
Ask for a demo on your own sample data and a reference school of similar size. Notice how quickly and specifically the vendor answers when you ask about something awkward.
Red flags worth walking away from
- “Unlimited customisation” with no clear price for it.
- No export of your data, or an export that is “on request, charges apply”.
- Roles that cannot be changed, so everyone gets the same broad access.
- A demo that never uses your school’s own data or workflows.
- Parent messaging that only works through one channel.
- A ledger that lets entries be edited or deleted without a trace.
How NQ School answers these ten questions
NQ School is built around these checks: one student record across every module, roles you write yourself and enforce on the server, ingestion from the biometric and gate devices you already own, five parent channels chosen per event, an append-only fee ledger, a full data export on request, separate records for each school, and a flat ₹10,000 a year for schools under 1,000 students. The quickest way to test any of this is to book a demo and ask us to prove it.