School operations8 min read
School ERP is no longer a luxury. It is a necessity
For twenty years, school software was a convenience — nice to have, easy to postpone, replaceable by a good clerk and a better register. Four changes between 2023 and 2026 ended that argument, and none of them came from a software company.
Checked against official notices on .
iVake publishes this page, and sells software of the kind it describes. Every claim below about a rule, a deadline or a court order is sourced at the end so you can check it independently of us.
The honest case for school software used to be efficiency: fewer queues at the fee counter, faster report cards, fewer phone calls asking about homework. All true, all optional. A school that ran well on paper could keep running well on paper.
That is no longer the situation, and the reason has nothing to do with features. Between 2023 and 2026, the state changed what it asks a school to hold, and the things it now asks for cannot be produced from a register at the end of the year.
The short versionFour changes did it. UDISE+ became a per-student record that carries forward. APAAR arrived, and needs a consent decision recorded per child. The DPDP Act made your school a Data Fiduciary with duties starting May 2027. And board exams became two attempts a year. Each one demands a record kept continuously and produced on demand — which is the one thing a register and a spreadsheet cannot do.
1. UDISE+ became a per-student record
Since 2022–23, UDISE+ has held a record for each student rather than a headcount per class. Each child has a Permanent Education Number that follows them through progression and transfers, and in 2025–26 the system covered 14,66,682 schools and 24,72,19,766 students.
The consequence is quiet but total. A name typed wrongly in Class 1 is still wrong in Class 10, because the record carries forward. A leaver never marked as left blocks their new school from importing them. A child added as new when they already have a PEN becomes a duplicate. None of these errors is visible in a paper register — they surface at certification, in the week you have least time, and the principal or head teacher is the person held responsible for the accuracy.
A school that keeps one clean student master copies from it. A school that does not goes looking. Our note on the order of work is at UDISE+ 2026–27.
2. APAAR made consent a record, not a conversation
APAAR is the student's permanent academic ID, and it is voluntary. On 20 July 2026, in Abhishek Baxi v. Union of India, the Supreme Court directed the Centre and CBSE to change the model consent form so parents and guardians can clearly withhold or refuse consent.
Read that as an administrative instruction and it becomes concrete: for every child on your roll, your school must be able to say whether consent was given, refused, or never asked — with the date, the signed form, and who recorded it. A refusal is a valid answer that must not affect admission or promotion, and it has to stay refused rather than being overwritten by a default.
That is a per-child, dated, auditable decision for every student in the school. It is precisely the kind of thing a register cannot hold and a spreadsheet holds badly, because a spreadsheet has no idea who changed a cell or what it said before.
3. The DPDP Act made your school legally accountable
Under the Digital Personal Data Protection Act, your school is the Data Fiduciary — legally accountable for the personal data it holds — and your software vendors are Data Processors acting on your instructions. Their compliance does not transfer to you. If a parent complains or a regulator asks, the school answers. Most of these duties start in May 2027.
And nearly everyone whose data you hold is a child: names, addresses, photographs, medical notes, caste and income certificates, marks, attendance, fee history, a parent's phone number. The Act protects children most closely, and requires verifiable parental consent, clear notice, real erasure on request, breach reporting and security safeguards.
Every one of those duties requires the school to show something. Who consented, and when. What was deleted, and when. Who accessed a record. A filing cabinet cannot produce an access log, and a shared drive cannot prove a deletion. Our full note is at your school as a Data Fiduciary.
4. Board exams doubled, and so did the bookkeeping
CBSE ran its first two-exam Class 10 cycle in 2026. A student can now sit the board exam twice, which means the school has to hold two results side by side with the one that counts marked — and answer a parent's question about both, correctly, the first time.
Alongside it, the Holistic Progress Card asks for dated observations across a year rather than a marks table at the end of a term, and the three-language policy and new subject options change what a timetable has to accommodate. Each of these is manageable alone. Together, in one school year, they are not manageable by hand.
What "necessity" actually means here
It does not mean every school needs the most expensive system, or the longest module list, or AI. It means something narrower and harder to argue with: your school is now required to hold records continuously and produce them on demand, and the people asking are the Ministry, a board, a court-shaped consent rule and a data regulator.
A system of record does four things a register cannot:
- It writes a fact once. The applicant becomes the student without retyping, so a name or date of birth exists in one place and is reused by every return.
- It remembers who changed what. Every change logged with the person and the previous value — which is the raw material for a DPDP answer and an audit.
- It holds decisions, not just data. Consent given, refused or unasked. Dues cleared before a TC. A concession approved by a named person.
- It produces a list on demand. The students whose attendance slipped, the families whose instalment is late, the records that do not match the portal.
The objection worth taking seriously
The honest objection is cost, and it deserves a straight answer rather than a brochure. Most vendors in this market will not publish a price at all — five of the nine products we checked publish no figure on their own site — which makes it rational for a trustee to assume the worst.
So here is the arithmetic, in public. A 200-student school on iVake's published rate pays about ₹19,200 a year before GST. A 1,000-student school pays ₹84,000 before the yearly discount. Staff logins, the parent app, reports, upgrades and support are never charged extra. Whether that is worth it is your decision, but it should be made against a number, not a fear. Other vendors' published prices, in their own units, are at what an education ERP costs in India.
Where a school genuinely does not need this yet
- A very small school with a stable roll and an office that already produces clean UDISE+ data may reasonably wait. The argument here is about records you must hold, not about software for its own sake.
- A school mid-way through another system's contract should finish it. Switching badly is worse than switching late; get your data export terms in writing first.
- If you have engineers, a free self-hosted option exists — OpenEduCat's Community edition — and it meets the same record-keeping argument at no licence cost, with servers and support on you.
If you do one thingPick one child at random and try to produce, in ten minutes: their APAAR consent decision with a date, their current UDISE+ status, their fee ledger, and every change made to their record this year. If you cannot, that is the gap — and it is a compliance gap before it is a software one.
See one student record end to end
Frequently asked questions
Is school ERP mandatory in India?
No. No rule requires a school to buy software. What the rules require is the record: per-student UDISE+ data that carries forward, an APAAR consent decision per child, DPDP-grade evidence of consent, access and erasure, and two board results held side by side. Software is the practical way to hold those; it is not itself the mandate.
Can a spreadsheet do this?
For a small roll, partly. What a spreadsheet cannot do is tell you who changed a cell, what it said before, or prove that a record was deleted when a parent asked — which is exactly what the DPDP Act will require from May 2027.
What does a school ERP cost?
iVake publishes ₹8 per student per month to 200 students, ₹7 to 10,000 and ₹5 above, GST extra, with logins and the parent app never charged extra. Fedena publishes flat annual plans from ₹50,000. Five of the nine other products we checked publish no price at all.
Sources
- UDISE+ scale, the per-student record and the 2026–27 order of work, with Ministry notices: our UDISE+ guide, checked 21 September 2026
- APAAR consent and Abhishek Baxi v. Union of India (20 July 2026): our APAAR, ABC and NCrF guide
- DPDP Act, 2023, section 9 on children and the DPDP Rules, 2025, Fourth Schedule (PDFs)
- Two board exams a year, first cycle: our note on the 2026 cycle
- Vendor pricing as published, checked 18 September 2026: what an education ERP costs
- iVake: pricing
See iVake running on your own data
Share your fee structure and programmes before the call, or sample data with student names removed. We set them up, so you see your own institution on screen rather than a demo account.
- 45 minutes, your data. Not a generic tour of features.
- Migration mapped on the call. We show exactly where your current records land.
- A written rollout plan within two working days, with phases, owners and dates.
- No pressure to switch everything at once. Most schools and colleges start with one department or one intake.