All resources Guides

How to choose a school ERP: a practical checklist for Indian schools

Feature lists all look the same. Here's how to judge a school management system by the way your school actually works — with the questions to ask in every demo.

The Takshova team · 5 October 2026 · 4 min read

Every school ERP brochure promises the same thing: admissions, attendance, exams, fees, transport, an app for parents. Put three of them side by side and the feature lists are almost identical. Yet schools that pick the “right” list are often back on spreadsheets within a year.

The difference is rarely what a system does. It’s how it does it, for the people who use it every day. This checklist will help you see past the brochure.

1. Start from your school’s day, not a feature list

Before you see a single demo, write down what actually happens in your school on an ordinary day — and on a hard one:

  • How does an enquiry become an admission? Who calls the family back, and how do you know nobody was forgotten?
  • What happens at 8:45 when attendance is marked? How quickly does a parent learn their child is absent?
  • What does the accounts team do at the end of each day? How long does it take?
  • What happens in the week before an inspection, or before report cards go out?

Take these stories into every demo and ask the vendor to walk through them, on screen. A system that looks good in a scripted demo can fall apart on your real Tuesday morning.

2. One record, or many logins?

The single most important question: is there one record for each student, staff member and fee account, shared by every module?

Many systems are several products stitched together. The fee module keeps its own list of students; transport keeps another; the parent app syncs overnight. The result is the same detail typed three times, and three versions that never quite agree.

Ask: “If a parent’s phone number changes, where do we update it — and where does the new number appear?” The right answer is “once, and everywhere”.

3. Money, the Indian way

Fees are where schools feel the difference first, and Indian schools have their own realities:

  • Concessions for siblings, staff wards and merit — with approvals, so they don’t become a habit.
  • Instalments and late fees that follow your own rules, not a fixed template.
  • UPI first. Most parents will pay from their phone. Receipts should reach them instantly, without the office doing anything.
  • Day close. The counter should end each day with one clear total for cash, cheques and online payments.
  • Payroll with PF, ESI, professional tax and TDS worked out every month, if you plan to run payroll in the same system.

4. How will families actually be reached?

A beautiful parent app is useless if half your families never open it. Check how the system reaches parents who don’t use the app — WhatsApp and SMS — and whether replies come back to one place where the office can see them.

Also look at the little things: can a parent with two children see both from one sign-in? Can they ask for leave or download a receipt without calling the office?

5. Count the clicks for teachers

Teachers are the busiest users and the least patient — rightly. For the three things they do most (attendance, homework, marks), count how many screens it takes. Ask to try it yourself on a phone. If it’s slow in the demo, it will be slower on a Monday morning with 40 students waiting.

Equally important: teachers should see only their own classes and students. That’s good for privacy and makes every screen simpler.

6. Privacy is no longer optional

India’s Digital Personal Data Protection Act, 2023 applies to the personal data schools hold — and much of it belongs to children, which carries extra obligations. Ask:

  • Can families see and manage their own consents (for example, for photos on the website)?
  • Is every change recorded in an audit log?
  • Can you control which roles see sensitive data such as health records?
  • Where is the data hosted, and how is it backed up?

7. Getting your data in — and out

Ask exactly how your existing data will be moved: students, families, staff, fee balances, last year’s results. Ready-made Excel templates help; a team that has done it before helps more.

Then ask the opposite question: “If we ever leave, how do we get our data out?” A confident vendor will have a clear answer.

8. Support, training and the first month

The first month decides whether a system sticks. Who trains your office, accounts team and teachers? Is there someone you can call — or WhatsApp — when a fee plan doesn’t look right the day before collections open?

Questions to ask in every demo

  1. Show me an enquiry becoming an admission, with a follow-up that was nearly forgotten.
  2. Mark attendance on a phone, and show me what the parent of an absent child receives.
  3. Take a UPI payment and show me the receipt and the day-close total.
  4. Change a parent’s phone number. Where else does it change?
  5. Log in as a subject teacher. What can’t they see?
  6. Show me the audit log for a fee concession.
  7. How would our data come in from our current system — and how would it go out?

A good system won’t just answer these questions. It will make them look easy.


Campus Flow was designed around these questions. If you’d like to see it walk through your school’s day, book a demo.