What is a school ERP, and does your school need one?

ERP stands for enterprise resource planning, a term borrowed from manufacturing and finance software. In a school the resources are students, staff, classes, rooms, money and time, and a school ERP is the system that records all of them in one place.

The defining feature is the shared record. When a teacher marks a student absent, the same student appears on the fee ledger, in the marks register and on the report card. A change of address entered once is the address everywhere. That is the difference between an ERP and a set of separate apps that happen to share a login screen.

You will also see the terms school management software, school management system and student information system (SIS). They overlap heavily. “SIS” usually means the records core; “school ERP” and “school management software” usually mean that core plus fees, examinations, timetables and portals.

Feature lists run to dozens of items, but the modules a school uses every week make a shorter list — and each replaces something the office is doing by hand today.

Around that core sit homework, announcements, an online result portal and support for several campuses. Some vendors also sell transport, library, hostel, payroll and admission-enquiry modules. Those can matter a great deal to a particular school, so check which ones a vendor actually ships rather than which ones appear in the brochure.

A school ERP has four kinds of user, and a good one gives each of them a different view of the same data.

• Administrators and the office run admissions, fees, examinations and settings across the school.
• Teachers see their own sections: attendance registers, marks entry, homework and their timetable.
• Parents see their own children: attendance, fees due, homework, results and notices.
• Students see their own attendance, timetable, homework and results.

The scoping is not a detail. A teacher who can see every class's marks, or a parent who can register against any admission number, is a data-protection problem as well as a design one. Ask any vendor how access to a child's record is granted, not only what each portal contains.

The gains are real, but they are rarely where the brochure puts them. The ones a school notices first tend to be unglamorous.

• The office stops re-typing. A student's details are entered once at admission and reused on the fee receipt, the report card and the transfer certificate.
• Fee dues become a report instead of a reconciliation. What is outstanding, by class, is available at any moment rather than after a weekend with the receipt books.
• Results follow the rules. Result processing applies the board's grading and pass rules the same way every time, instead of depending on whoever maintains the spreadsheet formulas.
• Parents phone less. Attendance, dues and results are visible to the family directly, which removes a large share of routine calls to the office.

What does not change on its own is the process around the software. An ERP records what the school does. If fee concessions are agreed verbally and never written down, the system will faithfully record the wrong fee.

Most vendors selling to Indian schools price per student per year, sometimes with a minimum annual charge, a one-time setup or onboarding fee, and extras for messaging credits, payment gateway charges or additional modules. Flat per-school pricing exists, but it is less common for anything beyond a very small school.

When comparing quotes, the headline price per student matters less than four questions:

1. What counts as a student? Some vendors bill every student ever admitted, others only current enrolments. Over five years the difference is large.
2. Is there a minimum charge? A per-student rate with a high floor behaves like a flat fee for a small school.
3. What is extra? Setup, data migration, training, SMS, additional campuses and particular modules are the usual line items.
4. Is GST included? Software subscriptions in India attract GST, and quotes are not always explicit about whether the figure includes it.

AcadiFlow publishes its own plans in rupees on the pricing page, including what counts as a billable student.

An ERP is not automatically the right answer. A small school with one section per class and one person running the office may be well served by a good spreadsheet and a receipt book, and would spend more time configuring software than it saved.

The signs that a school has outgrown that setup are specific:

• The same student details are typed into three or more places.
• Fee dues are only known after a manual reconciliation.
• Result processing depends on the one person who understands the spreadsheet.
• More than one campus or session has to be compared.
• Parents routinely call the office for information the school already has.

If two or three of those are true, the shared record is worth more than it costs to set up.

Start with the records, not the features. Most rollouts begin by importing students, classes and sections from a spreadsheet, then add attendance, then fees, then examinations — the order in which mistakes are cheapest to fix. The implementation guide sets that out as a six-week plan, and the buyer's checklist lists the questions to settle before signing anything.