Lotus Public School: what changes when a CBSE school stops keeping two sets of records
| School | Lotus Public School |
|---|---|
| Location | Gorakhpur, Uttar Pradesh |
| Owner | Amit Srivastva |
| Students | 500 |
| Board | CBSE |
| Staff | 20 |
| Plan | Foundation |
| Live since | July 2026 |
| Modules in use | Students, Staff, Attendance, Examinations and report cards, Fee collection, Parent communication |
Gorakhpur is a city of nearly seven lakh people in eastern Uttar Pradesh, and it has the school market that goes with a city that size: dozens of private CBSE schools competing for the same families, most of them running on paper. Lotus Public School has 500 students and 20 teachers, which puts it at the top of what our Foundation plan is built for and near the bottom of what most ERP vendors will quote for.
Amit Srivastva, who runs the school, came to Campus 24x7 in July 2026 with a problem that is specific to CBSE and almost invisible from outside it. The school was not drowning. Attendance was being taken, fees were being collected, report cards were going out. The trouble was that every one of those things existed twice.
Campus 24x7 has helped us bring important operations together, improve communication with parents, and make everyday tasks more organized.
Amit Srivastva, Lotus Public School, Gorakhpur
The problem: everything recorded twice
A CBSE 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 eligibility and the report card want. Marks are recorded by subject teachers in their own books, then assembled into the CBSE format with its split between internal assessment and the term examination.
None of that is hard. It is just done twice, by hand, by people who already have a full day. And the second copy is the one the board and the parent see, which means an error introduced during transcription is the error that becomes official.
The cost of that is not usually a crisis. It is a steady tax: a week of a clerk's time each term, and a quiet unease that the numbers going out might not match the numbers that were taken.
Why a 500-student school is a hard size to buy for
Worth saying plainly, because it is the reason schools of this size stay on paper longer than they should. At 500 students a school is too big for a spreadsheet and too small to interest the vendors who sell to 2,000-student chains. The quotes that come back are priced for an institution three times the size, and they arrive with implementation fees attached.
Lotus is on Foundation, which caps at 500 students and 30 staff. The school is at 500 and 20. That is the plan working as designed rather than a discount, and it is also the honest limit: if Lotus admits another section next year, it moves up a plan. We said that during the first conversation rather than after the first invoice.
Why attendance came first, again
Same sequencing as Kadapa and Jhajjar, for the same reason. Attendance is the process that runs every single morning, which makes it the thing staff learn fastest and the thing that proves the system within a week rather than a term.
It also happens to be the one with the most downstream value in a CBSE school. Once attendance is captured digitally at the point it is taken, the term percentage is 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.
What 20 teachers for 500 students means for a rollout
A ratio of one teacher to twenty-five students is a lean staff room. Every teacher at Lotus is teaching close to a full load, which has a direct consequence for training: there is no slack in the timetable to pull people out for a session.
So training happened the way it has to at a school like this, in person and in short sessions arranged around when teachers were actually free, rather than one long afternoon that nobody could attend. The principle we keep repeating applies here more than anywhere: a school ERP that only the principal can operate is a school ERP that 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 schools where this goes slowly are the ones with sixty teachers across four buildings.
The rollout
The same four steps as the other two schools, and no shortcuts for a school already familiar with its own processes.
Meetings first, to find out what Lotus needed configured rather than what the software defaults to. Configuration to match how the school already works, including its own class and section structure and its own fee heads. Then in-person training for teachers and administration staff. Then go-live, in July 2026, at the start of the session rather than in the middle of a term.
That last detail is worth copying. 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
The same fortnight of people asking where things are that both other schools describe, and we would be suspicious of a school that reported otherwise. The software works on day one. The habit does not exist yet.
What we have learned to tell schools, and told Lotus, is to budget for it rather than be surprised by it. A principal who expects day-one fluency concludes in week two that the system is wrong, when it is only unfamiliar. A principal who expects a fortnight of questions gets through it and stops noticing.
Where things stand now
Attendance, examinations and report cards, fee collection and parent communication run through one system. The register is no longer the master copy of anything.
The change a school this size notices is not dramatic and it is not a number. It is that a question like how many days a particular student attended last term stops being a task someone has to go away and do, and becomes something the office answers while the parent is still on the phone.
Lotus went live in July 2026, which at the time of writing is one term of use rather than several years. We would rather say that than imply a longer track record than exists.
What we still do not do well
Foundation is Android-only. iOS arrives from the Growth plan upward. In an urban CBSE 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, and it applies to Lotus more than it applies to either of the other two schools on this page.
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.
Foundation also caps at 500 students. Lotus is at that cap. If the school grows, the plan has to grow with it, and we would rather that was written on a public page than discovered at renewal.
What Lotus Public School uses
See it with your own data
Bring your class list and fee structure to the demo. Twenty minutes is enough to tell whether it fits how your school already runs.
Book a demo