Skip to main content

School ERP

School ERP Software in Gorakhpur: What a 500-Student School Actually Changed

What school ERP looks like in Gorakhpur — the duplicate-records problem CBSE and UP Board schools share, what a real 500-student school changed, and what it still cannot do.

By Campus 24x7 • 02 Nov 2026 • 9 min read

School ERP Software in Gorakhpur: What a 500-Student School Actually Changed

School ERP Software in Gorakhpur: What a 500-Student School Actually Changed

Most articles about school ERP in a particular city are the same article with the city name swapped in. This one is built around a school we actually work with in Gorakhpur, including the parts that did not go well.

Gorakhpur had a population of 673,446 at the 2011 census, and it has the school market that goes with a city that size: dozens of private schools competing for the same families, a deep UP Board base, a growing CBSE sector, and most of them running on paper.

That last fact is not a failure of effort. It is a buying problem, and it is worth naming before anything else.

Why Schools This Size Stay on Paper Longer Than They Should

At around 500 students a school is in an awkward gap. It is too big to run on a spreadsheet and too small to interest the vendors who sell to 2,000-student chains.

Ask for a quote at that size and what comes back is usually priced for an institution three times larger, with an implementation fee attached. The rational response is to stay on the register for another year. Many Gorakhpur schools have made that decision several years running, and they were not wrong to.

So the first question is not "which ERP" but whether the pricing is built for the school you actually run. Our pricing page lists three plans by student strength rather than quoting after a demo, which is the part worth comparing across vendors — including ours.

The Problem Nobody Calls a Problem: Everything Recorded Twice

The schools that move off paper in eastern UP rarely do it because they are in crisis. Attendance is being taken. Fees are being collected. Report cards go out.

The trouble is that every one of those things exists twice.

A school keeps records the way the board wants them and the way the school actually works, and those are rarely the same shape:

  • Attendance is taken in a class register. It is then needed again as a percentage per student per term, because that is what the report card and eligibility want.
  • Marks are recorded by subject teachers in their own books, then assembled into the board's format — with its split between internal assessment and the term examination.
  • Fees are collected at a counter, written into a receipt book, and totalled again into a ledger.

None of that is difficult. It is just done twice, by hand, by people who already have a full day.

And here is the part that matters: the second copy is the one the board and the parent see. An error introduced during transcription is the error that becomes official. A mark that was 68 in the teacher's book and 86 on the report card is a problem that surfaces at a parent meeting, not at the moment it was made.

The cost is rarely a crisis. It is a steady tax — roughly a week of a clerk's time each term, plus a quiet unease that the numbers going out might not match the numbers that were taken.

What Lotus Public School Changed

Lotus Public School is a CBSE school in Gorakhpur with 500 students and 20 teachers. Amit Srivastva, who runs it, brought the school onto Campus 24x7 in July 2026. It runs on our Foundation plan.

That staffing ratio — one teacher to twenty-five students — is a lean staff room, and it shaped the rollout more than anything else.

Attendance went first. Not because it is the most valuable module, but because it runs every single morning. That makes it the thing staff learn fastest, and the thing that proves the system within a week rather than a term.

It also has the most downstream value. Once attendance is captured digitally at the point it is taken, the term percentage becomes a query rather than a counting exercise, and the number on the report card is the same number the teacher marked. The second copy stops existing.

Training happened in short sessions, in person. With every teacher carrying close to a full load, there was no slack in the timetable to pull people out for a long afternoon nobody could attend. The principle matters more at this size than at any other: a school ERP that only the principal can operate is abandoned by March. With 20 teachers, every one of them has to be able to mark a class.

The thin staff room cuts the other way too. Twenty people is few enough to train properly, and few enough that everybody knows who to ask. The rollouts that drag are the ones with sixty teachers across four buildings.

Go-live was at the session boundary. July, at the start of the session, not the middle of a term. This detail is worth copying regardless of which vendor you pick: going live at a session boundary means the opening student roll is the roll, rather than a mid-year snapshot that has to be reconciled against a register for the months before it. Schools that switch in October spend the rest of the year with a seam in their data.

Week one was a fortnight of questions. We would be suspicious of a school that reported otherwise. The software works on day one; the habit does not exist yet. A principal who expects day-one fluency concludes in week two that the system is wrong, when it is only unfamiliar.

What changed is not dramatic and it is not a number. It is that a question like how many days did this student attend last term stops being a task someone goes away to do, and becomes something the office answers while the parent is still on the phone.

Lotus went live in July 2026. At the time of writing that is one term of use, not several years, and we would rather say so than imply a longer track record than exists.

The Two-Board Problem, and What Software Can Honestly Do About It

Gorakhpur schools run UP Board and CBSE patterns, sometimes in the same building. These are genuinely different: an annual marks-led pattern against a term pattern with internal assessment.

Here is where most vendor copy overreaches, so let us be precise about the line.

What is real: you configure each pattern once. Set the pass percentage, give each subject its theory, practical and internal split, define your own grading bands with their own minimums and maximums, and choose a scale — percentage bands, a 10-point CGPA, or grades only. Both patterns can sit in the same school. Results then compute into a card per student with marks, total, percentage, grade, rank and attendance, and stay as drafts until someone publishes them.

What is not real, from us or from anyone claiming it casually: board-specific report card formats are not built into Campus 24x7. There are three card templates — traditional, modern and cumulative — and they are layouts, not board-issued formats. There is no template library that updates itself when a board revises its format.

If a vendor tells you their software generates an exact board-issued layout and keeps it current automatically, ask to see it against your current report card before you sign. That demonstration takes four minutes and settles the question.

More on how this works in practice: CBSE report card generation.

Hindi, and What "Hindi Support" Should Mean

The parent base here reads Hindi first. A notice drafted in English reaches the parents who read English and surfaces on Saturday for everyone else.

What is worth checking in any demo is which part is in Hindi. In our case, WhatsApp templates are supported in Hindi — along with English, Tamil, Telugu, Kannada and Malayalam — and go out from your school's own WhatsApp Business number rather than a shared gateway number parents will not recognise. The apps themselves are in English.

One practical note that catches schools out: WhatsApp only lets a business open a conversation using a template Meta has approved, and each language is approved separately. A Hindi version and an English version of the same notice are two submissions. That is worth settling during setup rather than discovering in week three. The mechanics are covered in how school ERP works with WhatsApp.

What We Still Do Not Do Well

Three limitations, stated because a school that discovers them at renewal has been badly served.

Foundation is Android-only. iOS arrives from the Growth plan upward. In an urban school in a city like Gorakhpur, a meaningful share of parents carry an iPhone, and those parents are on the web version until the school moves up a plan. This is the limitation we hear about most.

There is no biometric or RFID option. Marking is mobile-only by design. A school that wants a fingerprint device at the gate does not get one from us, and we say so rather than promising it for a future release. If that is a firm requirement, biometric vs mobile app attendance compares the two honestly on cost and maintenance.

Foundation caps at 500 students. Lotus is at that cap. If the school admits another section next year, the plan has to grow with it. We said that during the first conversation rather than after the first invoice.

A Practical Sequence for a Gorakhpur School

If you are considering this for the coming session, the useful work is not in June.

  1. Count your duplicate records. Walk one term end to end and note every place a number is written twice. That list is your actual requirement document, and it is more useful than any feature comparison.
  2. Decide your go-live boundary now. Aim for the start of a session. If you miss it, wait rather than switching mid-term — the seam is worse than the delay.
  3. Get your student data into one spreadsheet. Whatever system you choose, the import is a CSV, and tidying that sheet is almost always the longest single step. Starting it early costs nothing.
  4. Test the demo against your own report card, not the vendor's sample. Hand them your actual format and your actual grading bands.
  5. Ask what the software does not do. If the answer is "everything you need", keep asking. Every system has limits; the question is whether you hear them before or after you sign.
  6. Budget a fortnight of questions after go-live, and tell your staff to expect it.

The Honest Summary

School ERP in Gorakhpur is not a transformation story. For most schools here it is a record-keeping story: the end of keeping two sets of books that have to agree and sometimes do not.

That is worth less than the brochures claim and more than the register suggests. A clerk's week back each term, a report card that matches the teacher's book, and a parent question answered on the call rather than after it.

If you want to see it running on your own classes and grading bands rather than sample data, we set up demos that way, and the first two months cost nothing. If you would rather read about a school nearer your size first, the Lotus Public School write-up includes the rollout timeline and the limitations in full.


Figures for Lotus Public School — 500 students, 20 teachers, CBSE, live since July 2026 — are published with the school's permission. Gorakhpur's population figure is from the 2011 Census of India; municipal boundaries have changed since. Plan prices and capacity limits are current at the date of this post; check the pricing page for the live figures.

Book a live demo of Campus 24x7

See admissions, attendance, fee workflows, examinations, and communication automation in one integrated ERP platform.

See pricing

Share this article