School Management Software: The Features Checklist Before You Buy
Every school ERP demos well. The gaps show up in November, when you are generating term report cards and the system cannot handle your grading scheme. Use this checklist of school management software features during the demo, not after you have signed.
1. Fees: where most systems break
Fee management is the first place a weak school ERP shows its limits. Check that the system supports:
- Multiple fee heads with different due dates in the same term.
- Sibling, staff-ward and merit concessions applied as rules, not manual edits.
- Instalment plans with partial payment and an auto-calculated balance.
- Transport fees that vary by route and distance slab.
- Late fees that accrue automatically and can be waived with an audit trail.
- A defaulter report by class, section and branch, as of any date.
Ask the vendor to configure your actual fee structure during the demo. If they need a week to come back, it is a customisation, not a feature, and it will probably be priced as one.
2. Examinations and report cards
Boards differ, and your report card is not negotiable. Confirm that the system handles:
- Your board’s format (CBSE, ICSE, a state board or your own scheme)
- Co-scholastic grades
- Weighted term averages
- Re-examination records
- Printing that matches the layout parents already recognise
Ask for a sample report card built from your own marks, not a template from another school. A good exam and report card engine should let you generate a full class in a day, rather than rebuilding layouts every term.
3. Transport
Transport touches fees, safety and parent communication, so it should not be a separate spreadsheet. Look for routes and stops linked to student records, fees tied to route and distance slab, vehicle and driver records, and live transport tracking visible in the parent app.
4. The parent app
The purpose of the parent app is to stop the phone ringing at the front desk. That means it must cover:
- Attendance
- Homework
- Results
- Fee payment
- Circulars
- Transport tracking
Anything less, and parents keep calling. Also check how the app is published. It should appear under the school’s name on both app stores, from the school’s own developer account, not as a generic vendor app with your logo inside. That affects who controls the app if you ever change vendor. If you want to know how this works, see our page on mobile app development.
5. Questions people forget to ask
- Can we start mid-session? And how does the migration handle part-paid fees and existing balances?
- Who owns the data? Can you export the whole database whenever you want?
- What happens to the parent app if we change vendor? Will parents have to reinstall something new?
- Is there an audit log? It should show who changed a mark or waived a fee, and when.
- How are TC and bonafide certificates generated? These are needed constantly, and they should come from the system with correct details, not from a Word template.
A short demo checklist
Ask the vendor to show, live and with your own data:
- Your fee structure configured, including a sibling concession and a transport slab
- A part-paid fee with the balance calculated automatically
- A late fee waived, with the audit trail visible
- A defaulter report by class and section
- A report card in your board’s format
- The parent app showing attendance, results and fee payment
- A TC or bonafide certificate generated in seconds
If any of these needs “a customisation”, ask what it costs and how long it takes before you decide.
How ORVIA approaches school software
Our School & College ERP covers admissions, attendance, examinations, fees, transport and report cards on one platform, with a branded mobile app for parents and staff. Schools and colleges we work with report around 40% fewer front-desk calls, and report cards that used to take days are generated in one day. In one multi-campus school, we cut the fee collection cycle from 9 days to 1.
You get a written scope and fixed price within 24 hours, one named project manager and data migration handled with structured validation, including part-paid fees. We train your staff before go-live, support is free for the first twelve months, and your code, accounts and data stay in your name.
If you are also working on admissions, we build school websites and handle local SEO so parents find you before the new session starts.
Get a written proposal in 24 hours →
If you are comparing vendors, our guide on how to choose an ERP vendor has twelve questions to ask about scope, ownership and support.
Frequently asked questions
What features should school management software have?
At minimum: flexible fee management with concessions and instalments, an exam and report card engine that matches your board format, transport management, attendance, a parent app, an audit log and certificate generation (TC, bonafide).
Can a school ERP handle sibling and staff-ward concessions?
It should, as rules applied automatically rather than manual edits. Ask the vendor to set one up live during the demo.
Can we start using a school ERP in the middle of the session?
Yes, if the vendor handles migration properly. Ask how part-paid fees and existing balances are imported, and who validates the numbers.
Who owns the school’s data in a school ERP?
You should. Ask whether you can export the entire database at any time, and what happens to the parent app if you change vendor.
Should the parent app be published under the school’s name?
Yes. An app published from the school’s own developer account on both app stores gives the school control. A generic vendor app with your logo inside can disappear or change if the vendor relationship ends.