Start with the problems you want to fix
Most schools look for software after something goes wrong: a fee receipt book goes missing, report cards take a week of late nights, or parents complain that they never heard about a holiday. Write those problems down before you look at any demo.
A short list keeps you focused. If fees and report cards cause the most pain, judge every system on those first. A long feature list is not useful if the two things your office does every day are still slow.
Core modules every school needs
School ERP products use different names, but the daily work of a school is similar everywhere. Check that these modules exist and that they share one database, so a student's details are entered once and used everywhere.
- Admissions and student profiles: admission numbers, photos, guardian details, and one parent login for families with more than one child.
- Classes, sections and subjects: section capacity, roll numbers and subject codes, including theory and practical subjects.
- Attendance: daily or period-wise registers with statuses such as present, absent, late, half-day and leave, plus monthly summaries.
- Timetable: a weekly schedule that warns you when a teacher or room is booked twice.
- Exams and results: term setup, maximum and pass marks, grade bands and printable report cards.
- Fees: fee heads per class, discounts, part payments, outstanding balances and numbered receipts.
- Staff records and leave: employee details, subject assignments and leave requests with approvals.
- Notices and reports: announcements to the right audience, and reports you can export for meetings and audits.
Academic year rollover
Ask what happens when students move up a class. Good software creates a new enrolment record for the new year and keeps the old year's marks, attendance and fee history intact. If promotion overwrites last year's data, you lose your records the first time you roll over.
Roles and permissions: who sees what
A school has many kinds of users, and each should see only what they need. A teacher should enter marks for their own sections, an accountant should handle fees but not change grades, and a parent should see only their own children.
Ask the vendor to list every role and show what each one can do. Typical roles are director or trustee, principal, office admin, teacher, accountant, student and parent. If you run several branches, you may also need a central login that manages all schools.
Permissions must be checked on the server
Hiding a button on the screen is not security. The system should check permissions every time data is requested, so a curious user cannot reach another class's marks by changing a link. Ask the vendor directly how this is enforced.
Fees and exams: where mistakes cost the most
Fee accounting
Fees are money, so the rules should be strict. Receipts should be numbered in sequence, a payment should not be recorded twice if two clerks click at the same time, and refunds should be added as reversal entries instead of deleting the original payment. That trail is what your auditor will want to see.
Check which payment modes you can record, such as cash, UPI, card and bank transfer, and whether parents get a PDF receipt straight away. If you want parents to pay online from a link, ask whether that is built in or needs a payment gateway added.
Exams and report cards
Look for a clear results workflow: teachers enter marks, someone approves them, and only then are results published to parents. Locking marks after approval stops quiet changes later. The system should also tell an absent student apart from a student who scored zero.
Parent communication on WhatsApp and email
In India, parents read WhatsApp far more reliably than email or a school app they installed once. Check whether the software can send report cards, fee receipts and notices over WhatsApp, and whether it uses the official WhatsApp Business platform rather than a personal number.
How documents are shared matters too. A report card sent as an open link that works forever can be forwarded anywhere. Safer systems send signed links that expire after a set time.
Data security and ownership
A school system holds children's names, photos, addresses and marks. Treat it with the same care as financial data, and get clear answers in writing.
- Are passwords stored hashed, and are failed logins recorded?
- Is there an audit log showing who changed a mark or fee entry, when, and what the old value was?
- Where is the data hosted, and who at the vendor can access it?
- How are backups taken, and have restores been tested?
- Can you export all your data if you stop using the product?
Subscription or your own copy
Hosted subscriptions are quick to start, but your data lives on the vendor's servers and fees continue every year. Owning the software and running it on your own server or cloud account gives you control over the data and the code, but someone has to manage hosting, updates and backups. Decide which trade-off suits your school.
Questions to ask a vendor before you buy
- 1Can you show a demo using our real workflows, such as our fee structure and our report card format?
- 2How do you handle academic year promotion and old records?
- 3What exactly is included: setup, training, data import from our spreadsheets?
- 4How long is support, and what does it cover after that?
- 5Can the report card and receipt templates be changed to match ours?
- 6What happens to our data if we leave?
Ask for the answers in writing. A vendor who is vague about data export or support terms now will be harder to deal with later.
A ready-made option you can own
Our School Management System covers the modules above: admissions with guardian linking, attendance, timetables with clash checks, exams with a draft, approve and publish workflow, PDF report cards, fee accounting with numbered PDF receipts and reversal entries, staff leave, targeted notices, reports and an audit trail. Report cards, receipts and notices can be shared over WhatsApp and email with expiring links.
It is delivered as source code that you run on your own server, with deployment help in some packages, and a multi-school console for groups with several branches. If your school needs something different, see our custom development service. Share your requirements in the form below to ask for a private demo or a fixed quote.