A Class 11 student at a CBSE school in Pune missed 42 days in the first semester. The school only noticed when it was time to fill the board examination registration form. The student was short of the 75% attendance threshold. The school had no formal record of why the absences happened, no communication trail with parents, and no process that would have flagged it earlier.
The board exam registration was delayed. The student's parents disputed the records. Three weeks of back-and-forth followed - with the school pulling together handwritten registers, attendance sheets, and leave slips that may or may not have matched.
This situation is not unusual. It happens every year at schools across India. The underlying problem is not that schools do not know the rule exists. It is that most schools do not have the operational infrastructure to enforce it consistently and document it defensibly.
What CBSE Actually Requires
Under CBSE circular No. CBSE/AFF/Circular/2024, schools are required to ensure that students appearing for board examinations have attended a minimum of 75% of working days in Classes 9–12. For Classes 9 and 11, condonation up to 25% (i.e., attendance as low as 50%) can be granted by the school for documented reasons such as medical illness, participation in national/international events, or natural calamity. For Classes 10 and 12, the regional officer handles condonation cases below 75%.
The school's obligation under this rule is threefold:
- Track and maintain accurate daily attendance records for every student.
- Identify students approaching or below the threshold with enough lead time to act.
- Document condonation cases with appropriate evidence before submitting board examination forms.
Where most schools fail is on points two and three. Attendance is tracked daily, but there is no automated aggregation that gives the school a live view of who is at risk. Condonation documentation is assembled retroactively, often from incomplete records.
The Most Common Compliance Mistakes
Tracking daily attendance without tracking cumulative attendance. A teacher marks present or absent each day. That data goes into a register. No one is computing running totals against working days. The first time anyone sees the full picture is when the board form deadline arrives.
Treating all absences equally. Medical leave, approved leave, unapproved leave, and suspension are different categories with different implications for condonation. If all absences are recorded as a single mark in the register, there is no basis for a condonation application - you cannot demonstrate that a student's absences were for documented medical reasons if the records do not distinguish medical absences from unexplained ones.
No parent notification loop for accumulating absences. CBSE guidance recommends that schools notify parents when a student's attendance drops below 75%. Most schools do not have a defined trigger for this notification. By the time a teacher or admin notices, the student may already be below the threshold with no room to recover.
Inaccurate working day counts. Schools are required to calculate attendance as a percentage of working days - days when the school was operational. Holidays, school-declared off days, and examination days need to be correctly excluded from the denominator. In paper-based systems, this calculation is done manually and is frequently wrong.
What the Documentation Trail Actually Needs to Look Like
If a student applies for condonation, the school needs to produce:
- Daily attendance records with dates marked present, absent, or on approved leave.
- The approved leave application with the reason stated, signed by the parent, and acknowledged by the school.
- For medical absences: a medical certificate covering the period of absence.
- The total count of working days, days attended, and the computed percentage.
This documentation needs to be consistent. If the attendance register shows 60 days absent and the leave applications account for only 30, the remaining 30 are unexplained - and the condonation application is weakened.
In a paper-based system, building this documentation trail requires cross-referencing multiple registers and files, often under deadline pressure. In a digital system, it is generated on demand.
How Schools Should Approach the 75% Threshold Operationally
The 75% rule is easier to comply with if you treat it as a continuous monitoring obligation rather than a point-in-time calculation at exam registration time.
Set an internal warning threshold. Do not wait for students to hit 75%. Flag students internally when they reach 80% attendance. That gives the school and parent a window to correct the trajectory before it becomes an eligibility issue.
Separate leave categories in your records from day one. Every absence should be tagged: present, absent (unexcused), absent (medical), absent (school-approved leave). This is not more work - it is the same work done once correctly rather than reconstructed later incorrectly.
Generate attendance reports monthly, not termly. A principal reviewing attendance percentages in February can intervene with a student who is at 77% and trending down. A principal reviewing attendance in September for board registration cannot.
Keep the parent notification documented. When you notify parents about low attendance, record it - date, method (call, letter, portal), and who was notified. If a condonation case is ever disputed, the evidence that the school fulfilled its communication duty matters.
What This Looks Like in Practice
A school running attendance through a digital platform gets a live dashboard. Every student's cumulative attendance percentage is visible at any time, calculated automatically against the school's configured working days calendar. Students who cross the 80% warning threshold appear in a flagged list. The school can generate a class-wise or student-wise attendance report in under a minute - the same report that would take hours to assemble from registers.
Leave applications submitted through the platform are tagged to the attendance record automatically. When a parent submits a leave request with a reason, that tag is applied to every absent day in that period. The resulting documentation is clean, consistent, and ready for condonation submissions without any retroactive reconstruction.
The CBSE 75% rule does not require complicated software to comply with. It requires accurate records, categorized absences, and monitoring that happens continuously rather than at deadline. Most schools that struggle with compliance are not failing on intent - they are failing on infrastructure.