Buying

Choosing school management software: a buyer's checklist for Indian schools

18 July 2026 · Buying · 10 min read

Most schools do not choose their management software so much as inherit it — a vendor a trustee knew, a system the school next door used, a package bundled with the biometric machines. Two years later the office is running three tools that do not talk to each other, exporting to Excel to answer any real question, and paying an annual maintenance fee for a product nobody enjoys. Choosing well the first time is not about finding the flashiest demo. It is about knowing which questions expose a weak system before you sign. This checklist is written for Indian schools — CBSE, ICSE and state board — and is deliberately vendor-neutral. Use it on us too.

Start from the work, not the feature list

Every vendor's brochure lists forty modules. That tells you nothing, because a checkbox for "Fees" says nothing about whether it handles a parent paying in three instalments. Before you look at any product, write down the ten things your office actually does in a week: publish an admission merit list, invoice a class, collect a part-payment, mark daily attendance, enter term marks, generate report cards, chase overdue fees, answer a parent's "what does my child owe" call, produce a transfer certificate, and pull a board-ready student list. Judge every system against your ten, not their forty.

The modules that matter — and how to test each

An integrated platform beats a pile of point tools for one reason: a student, once admitted, should flow into fees, attendance and results without being re-typed. Here is what to probe in each core area.

Admissions

Ask to run one enquiry all the way to an enrolled student on screen. A good admissions module captures the enquiry, moves an application through review, produces a merit or waiting list, allocates a seat, and — critically — converts the applicant into a student record without anyone re-keying the name, class and parent details. If the demo person opens a second system to "complete the enrolment", that seam will cost you every year.

Fees

This is where most systems quietly fail. Insist on three tests: invoice a whole class from a fee structure in one action; record a partial payment and watch the balance update; and apply a concession above a threshold and confirm it needs an approval before it reduces the balance. A fees module that only understands "paid" and "unpaid" will force your staff to fudge every instalment. Ask to see the collected and outstanding totals reconcile live.

Attendance

Daily marking has to be faster than a paper register or teachers will not do it. Time it in the demo: a class of forty should be markable in under a minute, with defaults for "all present". Then check that a parent can see it. An attendance system that produces month-wise percentages and flags chronic absentees earns its place; one that just stores ticks does not.

Exams and report cards

Board fit lives here. A CBSE school needs grade and CGPA handling; an ICSE school needs percentage aggregates; a state board school needs its own mark pattern. Ask the vendor to produce a report card in your board's format, and to show an approve-then-publish step so a teacher's raw entry is not visible to parents until it is checked. Bulk transcripts and transfer certificates should be one action. See how a strong exams module handles this.

The rest

Transport, hostel, library, HR and payroll, and a learning module matter to the degree your school uses them. Do not pay for a boarding module you will never open — but if you run buses or a hostel, test them with the same rigour. Explore the full module list and be honest about which you will actually switch on in year one.

Board and compliance fit

Software built for American K-12 or generic "education" often fits Indian schools awkwardly. Check for the things a foreign product forgets:

• Board formats. CBSE, ICSE and your state board's report-card and result templates, not a single generic one.
• RTE handling. A way to mark and track 25% reserved seats and their fee treatment, so quota admissions and reimbursement claims are not a separate spreadsheet.
• Indian fee reality. Rupee formatting, term and monthly schedules, transport slabs, and concessions with approval — not a flat annual tuition assumption.
• Documents you actually issue. Transfer certificate, bonafide certificate, character certificate — generated, not hand-typed.
• Language and SMS/WhatsApp reach. Parents who read a reminder in the medium they use pay and respond sooner.

Data security is not optional

You are handing a vendor the names, addresses, photographs and fee records of every child in your school. Under India's Digital Personal Data Protection framework, that is your responsibility as much as theirs. Ask — and get answers in writing:

1. Where does the data live, and is it hosted in India?
2. Who inside the vendor can see it, and is access logged?
3. Is every user's access scoped to their role — a class teacher should not see the whole school's fee ledger?
4. How is the data encrypted, in transit and at rest?
5. Can you export everything and leave, and what happens to your data if you do?

A vendor who treats these as reasonable questions is one you can trust. One who gets defensive has told you something. Our own answers live on the security page.

Pricing: read past the sticker

Indian school software is sold in confusing ways — per student, per year, per module, plus "one-time setup", plus SMS credits, plus a charge to migrate your old data. The sticker price is rarely the real price. Build a three-year total and put every vendor in the same table.

Simple, published pricing is itself a signal — it means the vendor is not planning to negotiate a different number with every school. See how we do it on the pricing page.

Rollout and support — the part that decides success

The best software fails if the switch-over is botched in September when the office is busiest. Ask concretely: how long does onboarding take, who migrates last year's students and fee balances, is there training for teachers and clerks, and what does support look like on a real Tuesday — a phone that a human answers, or a ticket into the void? A three-month rollout that lands in a quiet month beats a "go live tomorrow" promise that collapses at admission season.

The one-hour demo script

Do not let the vendor drive the demo through their happy path. Hand them yours:

1. Take one new enquiry and enrol the student — no re-typing.
2. Invoice that student's whole class from a fee structure.
3. Record a part-payment; show the balance and the receipt.
4. Apply a large concession; show it waiting for approval.
5. Mark a class present in under a minute.
6. Enter marks and publish a report card in our board's format.
7. Pull the list of students who owe fees, and send one a reminder.
8. Log in as a class teacher and prove they cannot see the whole school's ledger.

Any system that does these eight without switching tools or opening Excel is a serious candidate. Most will stumble on three of them — and now you know which three before you have paid.

How Vidyalaya measures up

Vidyalaya was built as one platform for exactly this flow: an admitted student moves straight into fees, attendance and results with nothing re-typed. Fees handles part-payments and routes large concessions through a bursar's approval; attendance marks a class in seconds and shows parents the same day; exams publishes in CBSE, ICSE and state formats behind an approve-then-publish step; and every user's access is scoped to their role, hosted with security we document openly. Pricing is published, not negotiated.

If admissions is your first switch-over, read how to run admissions online; if fees is the mess you most want gone, start with our practical guide to fee management.