A Sports School in Jhajjar and the Attendance Problem Nobody Designs For
Attendance software assumes a question with two answers. Was the child in class: yes or no.
That assumption holds for most schools most days. It falls apart in a sports school, a residential school, or any school where students are routinely somewhere legitimate that is not the classroom — and when it falls apart, it does so quietly, in a way that only surfaces months later when somebody runs a percentage.
This post is about a school where that was the problem from day one, and what it taught us about a limitation worth naming in our own product.
The School
World Vidya Sports Sainik School is in Chhara, Jhajjar, in Haryana, with around 450 students and 25 staff. It follows the Haryana Board and runs on our Foundation plan. It went live on 3 September 2026. Isha Rathi, who runs it, is quoted throughout this post with the school's permission; the full write-up is in the World Vidya Sports Sainik School case study.
She knew what she wanted before the first conversation, which is less common than you would think. Not a broad digitisation project — three specific things: attendance, timetable and syllabus.
Her reasoning is the best short argument for rollout sequencing we have heard from a customer:
"Those are things we deal with every single day. If attendance or the timetable isn't managed properly, it affects the whole day's schedule. We wanted those basic processes to become more organized first."
The instinct with a new system is to switch everything on. Starting with the two processes that run every single morning means staff learn the software on the thing they do most, and you find out within a week whether it fits.
The Problem: A Third State
Here is where a sports school stops resembling a regular one.
A student is away at a competition. They are not in class. They are also not absent in any sense that matters — not truant, not ill, not unaccounted for. The school knows exactly where they are and approved it.
A system with two states has nowhere to put that student. So the school picks the least-wrong option, and both options are wrong:
- Mark them absent, and the attendance percentage drops for a student who was representing the school. At the end of the year that number sits next to an exam eligibility threshold and means something it should not.
- Mark them present, and the register says a child was in a classroom they were nowhere near. Now the record is simply false, and on the day it matters — an audit, a dispute, a safeguarding question — it cannot be relied on.
Isha's framing of the requirement is better than ours:
"We can handle it based on the student's activity or situation rather than simply treating them as absent. The important thing for us is that the attendance record should reflect where the student actually is and why they're not in the regular class."
The attendance record should reflect where the student actually is. That is a one-sentence specification, and most attendance software fails it.
Why This Is Not a Niche Problem
It is easy to read the above and conclude it only applies to sports schools. It does not. The same shape appears in most schools; the sports school just hits it every week instead of twice a term.
The student on approved medical leave with a certificate on file. The class away on an educational trip. The student at a board practical in another room. A residential school's student who went home for a family event with permission. A student representing the school at a debate, an olympiad, an NCC camp.
Each one is a child who is not in the classroom and should not be counted as a truant. In a regular school these are rare enough to be fixed by hand later — which is exactly why nobody notices the software cannot express them. The sports school is the case where the workaround stops scaling, so the gap becomes visible.
If you run a residential, sports, or heavily co-curricular school, this is worth testing before you buy anything. Ask the vendor to mark a student as away at a competition, then produce an attendance report that distinguishes it from truancy. It takes four minutes in a demo. A surprising number of systems cannot do it, and you will not find out from the feature list, because "attendance tracking" is a tick on every one of them.
What Campus 24x7 Actually Does Here — Including Where It Falls Short
We would rather write this part plainly than let the case study imply more than the product delivers.
Student attendance in Campus 24x7 is built around present and absent. The roster shows each student with a status, you mark everyone present in one tap and change the exceptions, and the totals show attendance percentage, present, absent and not marked. That is the model.
The mechanism that carries the why is the correction trail. A correction is made against one student and cannot be saved without a reason. Each correction stores the old status, the new status, the reason, and who made it — and the roster shows the last correction next to the child. So "away at the state-level athletics meet" can live on the record as the recorded reason for that day, attached to that student, auditable afterwards.
That is a real answer and it is how a school can keep an honest record today. It is not the same thing as a first-class attendance state, and we should be clear about the difference:
- The reason is attached to a correction, not a status in its own right.
- It does not change how the percentage is calculated. A student marked absent with a reason is still counted absent in the attendance total.
- There is no built-in "on duty" or "excused" category for students that reports separately from absence.
Interestingly, the limitation does not apply across the product. Staff attendance has five statuses — present, absent, late, half-day and leave — with late and half-day counting under present, and leave under absent. Teachers get the nuanced model. Students, today, do not.
Two further limits worth stating in the same breath, because a school evaluating on this basis should hear them now rather than at renewal:
- Attendance reports in the Reports module are marked coming soon. Today you review attendance through the daily, weekly and monthly views. If your requirement is an exportable report that breaks absence down by reason, that is not there yet.
- There is no biometric, RFID or face-recognition attendance. Marking is done by staff in the app. For a school that wants a fingerprint device at the gate, that is a straight no rather than a roadmap promise. Biometric vs mobile app attendance compares the two on cost and maintenance if that is a firm requirement.
We are writing this up as a gap rather than a feature because a school with this requirement deserves to evaluate it with the facts. The attendance management system page documents what is there in full.
The Timetable That Holds Two Schedules
The attendance problem has a sibling, and it is the reason Isha named timetable in the same breath.
A sports sainik school does not run a normal school day. There is an academic timetable and there is a training schedule, with coaches who are not subject teachers, and students who move between both. In her words:
"Our requirements are a little different because of the students' training and activities. We needed to consider coaches, training schedules and students who may be away for tournaments. So the system had to work around those requirements rather than just a normal classroom schedule."
That last clause is the whole argument for configuring a system around a school instead of asking the school to adapt. A school that has to force its real schedule into a template built for a regular day school ends up keeping the real schedule somewhere else — a whiteboard, a WhatsApp group, the sports head's notebook. Which defeats the entire purpose of having one system.
What makes this workable in practice is that periods and breaks are defined once for the whole school, with start and end times, and you can add a period or a break at any point in the day. A training block is a period. The grid is built from your school day rather than an assumed one.
The parts that do real work here are the conflict checks. Saving a timetable that double-books a teacher, puts two classes in one room, or gives one class two lessons at once is refused outright, and the dashboard counts conflicts, unassigned lectures and room utilisation. In a school where a coach and a subject teacher might both lay claim to the same hour, that check earns its place. The timetable management system covers auto-generation and faculty workload in detail, and the timetable software guide covers what to look for generally.
One limit, again stated rather than buried: there is no separate substitution or teacher-leave module. Covering an absent teacher means editing the slot.
Syllabus Tracking, and Why Framing Decides Adoption
Isha's third priority was syllabus coverage, and her description of what it is for is the most useful thing in this post for anyone about to roll something out:
"It gives us a clear idea of how much of the syllabus has been completed and what is still pending. It's useful for planning because we don't have to depend completely on individual teachers giving us updates."
Planning, not policing. That distinction decides whether a feature gets used.
Syllabus tracking introduced as management oversight gets quiet resistance — updates stop being entered, or get entered inaccurately at the end of term, and the data becomes worse than useless because somebody is now making decisions on it. The same feature introduced as a planning view, with teachers updating their own coverage, tends to get used. The feature is identical. The framing is the whole difference.
It applies well beyond syllabus tracking. Most ERP features that require teachers to enter something live or die on this.
Week One
We ask every school about this, because the answer is always the same and schools about to go live deserve to hear it:
"There was some confusion because we were moving from our old way of working to a new system. A few people needed help understanding where to enter things and how the workflow worked. But that was mostly part of the transition."
The software works on day one. The habit does not exist yet. A school that budgets a fortnight of people asking where things are comes through it; a school expecting day-one fluency concludes in week two that the system is wrong when it is only unfamiliar.
What changed afterwards was visibility rather than any single feature:
"Earlier, we had to ask different people for different information. Now we can see much more of it in one place, and that makes it easier to keep track of students, attendance and the overall schedule."
For a school where a student might be in class, at training, or away at a tournament on any given morning, knowing which one without ringing three people is most of the benefit.
What to Test If You Run a School Like This
Five things, in the order they will bite:
- Mark a student away at a competition, then produce a report that separates it from truancy. The core test. If the vendor reaches for a workaround, you have your answer — and ask specifically whether the reason is a status or a note, because that determines whether it affects the percentage.
- Ask how the attendance percentage treats it. A reason on the record is not the same as a reason excluded from the calculation. Find out which you are getting.
- Put a training block in the timetable. Not a lesson labelled "training" — an actual block, at the real time, with a coach who is not a subject teacher.
- Create a deliberate clash. Book a coach and a subject teacher into the same hour and confirm the system refuses it rather than saving quietly.
- Ask what it 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.
The Honest Summary
Sports schools, residential schools and heavily co-curricular schools share a requirement that mainstream school software does not design for: attendance with more than two states, and a timetable that holds more than one kind of day.
Campus 24x7 handles the timetable side well — periods you define yourself, training blocks as first-class entries, conflict checks that refuse to save a double-booking. It handles the attendance side partially: the reason for an absence is captured with a mandatory, auditable correction, but it is not a separate status and it does not change the percentage. If that distinction matters to you, test it before you buy, from us or from anyone else.
A school this size can see the whole picture in one place, and for most of them that is the win. But the right question to ask a vendor is never "do you do attendance". It is "what happens to the student who is at a tournament".
If you want to try that question against your own classes and training schedule rather than sample data, we set demos up that way, and the first two months cost nothing.
Figures and quotations for World Vidya Sports Sainik School — 450 students, 25 staff, Haryana Board, live since 3 September 2026 — are published with the school's permission. Product capabilities and limits described above are current at the date of this post; see the attendance management system page and the pricing page for live details.
