A parent sends a WhatsApp message to the class teacher on Monday morning: "Arjun will not be coming today, he has a fever." The teacher reads it during the morning rush, marks Arjun absent, and moves on. Three weeks later, Arjun's attendance is at 68%. The school sends a letter home. The parent responds that ten of those absences were communicated and approved. The teacher cannot locate half the WhatsApp messages. No leave applications were ever formally filed.
This scenario plays out in schools every term. The problem is not that the parent failed to communicate. It is that the school has no defined process for what "communicating leave" means, what documentation is required, and what constitutes formal approval.
The Four Ways Schools Currently Handle Leave
Most schools operate with one or more of these approaches, none of which produces a reliable record:
Verbal requests through the student. The student tells the teacher they are going to be absent tomorrow for a family function. The teacher acknowledges it informally. Nothing is written down. If the absence is later contested, there is no record.
Written slips sent via the student. The parent writes a note and sends it with the student. The teacher may or may not file it. These slips are routinely lost, and there is no way to verify that a slip from last month actually preceded the absence it supposedly explains.
WhatsApp messages to the class teacher. These are convenient for parents and create a digital trail - but only on the teacher's personal phone. The school has no access to this record. If the teacher changes, the history is gone. There is no formal approval step, and the leave reason is unstructured and unsearchable.
Formal written application submitted to the office. This is the most defensible process, but it is rarely used consistently because it is inconvenient - it requires physical presence or sending a document through the student, it has no acknowledgment mechanism, and schools rarely communicate what the format or process should be.
The result is that schools have daily attendance records, but the underlying data on why students were absent - and whether those absences were formally sanctioned - is fragmented across personal phones, filing cabinets, and memory.
Why This Creates Downstream Problems
Attendance percentage disputes at examination time. When a student is flagged for low attendance before board exams or final assessments, the school needs to distinguish excused from unexcused absences. If leave records are incomplete, the school cannot defend the absence count. Parents who did communicate will dispute it. The school is put in the position of asking teachers to reconstruct records from memory.
Inability to identify patterns. A student who takes leave regularly on Mondays and Fridays is exhibiting a pattern worth investigating. A student whose absences cluster around examination weeks may be avoiding assessments. These patterns are only visible if leave data is structured and searchable. In a WhatsApp-based system, they are invisible.
No accountability for unapproved absences. If there is no formal leave process, there is no distinction between a student who was absent with a genuine illness and a student who skipped school without any communication from the parent. Both are marked absent. Neither has a formal record. The school has no basis for differential follow-up.
Leave policy is unenforceable. Most schools have a leave policy in their handbook - specifying how many days of leave can be taken per term, what documentation is required, and what the approval process is. If the actual process bears no resemblance to the policy, the policy is performative.
What a Functional Leave Process Requires
A leave management process that produces defensible records has four components:
A structured submission step. Leave requests should be submitted through a defined channel - not the teacher's personal number - with required fields: student name, class, dates of leave, reason, and parent contact. This does not need to be a digital form; a standardized paper form works. But the channel should be consistent and the fields should be required.
A formal approval step. Submitted leave requests should be reviewed and either approved or declined by the class teacher or a designated admin. The outcome of this review - with the reviewer's name and the date - should be recorded. "The teacher read the WhatsApp" is not an approval. An approval is a documented decision.
Automatic tagging to the attendance record. Once leave is approved, the corresponding absent days in the student's attendance record should be marked as approved leave - not generic absence. This is what makes the documentation trail complete. Approved leave counts differently from unexcused absence for condonation purposes.
Parent acknowledgment. The parent should receive confirmation that the leave request was received and whether it was approved or declined. This closes the loop and prevents the situation where a parent believed leave was approved and the school has no record of it.
The Digital Version of This Process
A digital leave management system is not significantly different from a paper-based one in structure. The difference is in friction and completeness. A parent submits a leave request through a portal - which takes two minutes - and the teacher receives a notification, reviews it in one tap, and approves or declines with a written note if needed. The record is created automatically, linked to the student's attendance record, and accessible to any authorized staff member.
The documentation that takes hours to reconstruct in a paper-based dispute is generated as a standard output of the process. Leave reports - showing approved leave, unapproved absences, and leave reasons - can be pulled for any student or class at any time.
Schools that have moved to structured leave management consistently report two things: fewer attendance disputes, and better visibility into absence patterns that were previously invisible. Neither of these outcomes requires sophisticated technology. They require a process that is consistent, documented, and actually followed.
The WhatsApp-based system that most schools currently operate is not a process. It is the absence of one.