How to choose school software: 12 questions to ask any vendor.
To choose school software, check whether it keeps one record per student, covers your board and language, makes fees predictable, protects children's data, lets you export everything, and shows who did what. These twelve questions apply to any vendor, and we answer each for EduCampusOS.
Who should be in the room
Software for a whole school should not be chosen by one person. A sensible evaluation group has:
- the owner or trustee, who cares about cost, risk and exit;
- the principal, who cares about teaching time, parent communication and reporting;
- the accountant or accounts head, who will live in the fee module;
- the admissions or front office lead;
- whoever coordinates IT or administration;
- if possible, one parent, who will judge the app.
The twelve questions
1. Is there one record per student, shared by every module?
Good looks like: admissions, fees, attendance, exams and transport read the same record. EduCampusOS: one data layer and one login per role.
2. Does it support our board and curriculum?
Good looks like: grading, report cards and board-exam workflows for your own board and state. EduCampusOS: works with any state or board and any curriculum.
3. Can parents and staff use it in their own language?
Good looks like: the app follows the chosen language. EduCampusOS: 11 Indian languages, plus names in regional script.
4. How are fees handled when things change mid-year?
Good looks like: concessions, proration and route changes billed from the real effective date. EduCampusOS: one shared billing engine with several concessions per student.
5. Can parents pay online, and who holds the money?
Good looks like: payments settle to the school's own bank account. EduCampusOS: Cashfree Payments settles to the school's bank; EduCampusOS does not hold fee money.
6. What does it really cost?
Good looks like: a quote in writing with no hidden per-module or per-message fees. EduCampusOS: priced by school size and service tier, all modules and notifications included, no setup fees.
7. How is children's data protected?
Good looks like: encryption, role-based access, audit trail, backups, two-step sign-in and DPDP Act 2023 workflows. EduCampusOS: all of these. See security and trust.
8. Can we leave and take our data?
Good looks like: full export in a usable format with no exit fee. EduCampusOS: yes, any time.
9. Does it use AI responsibly?
Good looks like: answers grounded in the school's own material, cited, and honest about limits. EduCampusOS: Class IQ, Report Assistant and Library Study Assistant are scoped by design. See AI in schools.
10. Is there a mobile app for every role?
Good looks like: separate, role-fit apps that work on weak connections. EduCampusOS: apps for parents, students, teachers, staff and drivers; leave requests and bus boarding work offline and sync later.
11. How are problems fixed?
Good looks like: a reference number, a named owner, tested fixes and a reply that says what changed. EduCampusOS: see how we support you.
12. Will it still fit in five years?
Good looks like: regular releases and compliance updates without re-implementation. EduCampusOS: updates come to your system in place.
Ten things to ask to see live in a demo
- Create a student from an enquiry and follow the record into fees, attendance and a report card.
- Build your own fee structure and apply two concessions to one student.
- Change a student's transport route mid-year and show the credit and the new charge.
- Take a payment online and show the invoice marking itself paid.
- Show what a teacher, a principal and an accountant each can and cannot see.
- Show the audit trail for a change someone made.
- Open the parent app in the language your parents use.
- Export a class list and a fee ledger.
- Ask the AI feature something outside the syllabus and see what it does.
- Raise a support case and show how it is tracked.
Contract points to settle in writing
- Total price for your school size, every recurring charge, and the renewal terms.
- Whether messages, extra users, extra modules or storage are charged separately.
- Data export on exit: format, timing and cost.
- Where data is hosted and whether dedicated infrastructure is available if your policies need it.
- Support: how problems are reported, prioritized and closed.
- Who is responsible for what under the DPDP Act 2023.
To see EduCampusOS on your own setup, talk to us.
Frequently asked questions
How do I choose a school ERP?
List your must-haves (board support, fees, language, data protection, mobile apps), ask each vendor to demonstrate them on your own data, get written pricing that includes every recurring fee, and speak to a school already using the product.
What are red flags when buying school software?
Separate logins and data for each module, per-student or per-message charges that grow with your school, no clear data export, AI answers with no source, and no named process for fixing problems.
How long should school software implementation take?
It depends on the vendor and the school's size. On EduCampusOS's standard cloud most schools go live within days; larger multi-branch schools or those needing dedicated infrastructure take longer, and we give a specific timeline after understanding the school.
Why would a school pick EduCampusOS?
Schools choose it when they want every module on one record, board and language support for Indian schools, scoped and cited AI, predictable pricing that does not grow per student, and a guaranteed way to export their data.
Keep reading
Published by EduCampusOS, a product of Stavion Technologies, part of Stavion Private Limited. We build school software, so we have a view; the claims here match our platform, pricing and security pages. Worked examples are marked illustrative. Last updated 23 October 2026.