Most schools buy management software once every five to eight years. That's rare enough that nobody on staff remembers how the last decision was made — and long enough that a bad choice hurts for a long time. This guide walks through the questions that separate a tool your office will love from one it will quietly work around.
Start with the problems, not the feature list
Every vendor's brochure lists the same 40 modules. Before you compare any of them, write down the five things that cost your school the most time or money today. For most Indian schools the list looks something like this:
- Chasing fee payments and reconciling receipts by hand
- Taking and compiling attendance across sections
- Answering the same parent questions on the phone, every day
- Building report cards at the end of each term
- Keeping admissions enquiries from slipping through the cracks
Judge every product against your list. A system with 60 modules that handles your top five badly is worse than one with 20 that handles them well.
1. How is it priced — and what happens when you grow?
Per-student pricing looks small on the quote and large on the invoice three years later. Ask for the total cost at your current strength and at 30% more students. We've written about the hidden cost of per-student pricing in detail; the short version is that flat, tiered pricing makes budgeting predictable. Also ask what's not included: SMS credits, WhatsApp messages, the mobile app and payment-gateway setup are common extras.
2. Will parents actually use the app?
The parent app is where most of the value lands — fee payments, attendance alerts, homework and circulars. If parents don't install it, your office keeps fielding calls. Ask vendors for real adoption numbers and look at the app yourself on a basic Android phone. Our notes on designing for the parent end of the phone explain what makes the difference.
3. How long does migration take, and who does it?
If the answer is "send us the data in our template", expect weeks of your staff reformatting spreadsheets. A good vendor takes your existing files as they are. See our seven-day migration playbook for what a realistic timeline looks like.
4. Can it collect fees online properly?
"Online fees" can mean anything from a payment link to a full system with class-wise fee structures, late fees, concessions, instant receipts and a live defaulter list. Ask to see the defaulter report and a parent paying by UPI end to end. Our guide to UPI for school fees covers what to look for.
5. What does attendance look like on a busy morning?
Ask a teacher to mark a 45-student class in the demo. If it takes more than a minute, it will be skipped on busy days. Options like QR scanning or face-recognition attendance remove the bottleneck entirely.
6. Is it one system, or five glued together?
Some ERPs are a collection of separately built products sharing a login. You notice when a student's class changes in one place but not another. Ask how fees, attendance, exams and communication share data — and whether a parent sees all of it in one app.
7. Where is the data, and who owns it?
Under India's data-protection law, your school is responsible for the student data you hold. Ask where it's hosted, how it's backed up, who on the vendor's side can access it, and how you export everything if you leave. Our data security checklist for principals has the full list of questions.
8. What does support look like after the sale?
Ask for a named contact for onboarding, typical response times, and whether training is included for teachers as well as office staff. Then ask a current customer.
9. Does it cover the edges of school life?
Transport, library, gate passes, payroll and parent-teacher meetings are where many systems get thin. You don't need everything on day one, but you should know whether you'll need a second tool later. Some schools add specialist products for these — for example dedicated school bus tracking or an online PTM scheduler.
10–12. The quick final checks
- Trial: can you try it with your own data before paying?
- Contract: is there a lock-in period or exit fee?
- Roadmap: has the product meaningfully improved in the last year?
A simple scoring method
Give each shortlisted product a score of 1–5 against your top five problems, then weight price and support. Involve one office staff member and one teacher in the demo — they'll spot problems a principal won't. And insist on a trial with real data: it's the only test that matters.
If you're still deciding between product categories, read School ERP vs School CRM first. And if you'd like to test Schoolo against this checklist, the one-year free trial includes every module and free data migration.