Spot the 75% problem before March. Auto-flagged. Ranked. Followed up.
A live watchlist that flags every student whose attendance has crossed below 75% — the RTE Act 2009 norm — with trend arrows, parent contact, full session register link and a school-configurable threshold.
How most Indian schools find chronic absentees today
In February, the principal of a Class 9 CBSE school in Lucknow opens her office drawer and pulls out the 'shortage list' — a stapled set of A4 sheets her head clerk types every month. The clerk has copied attendance percentages from forty-five class registers into one Excel sheet, sorted by percentage, and circled every student below 75% in red pen. Eighty-three names. Some of them are flagged for the first time this month — their parents will get the standard 'attendance shortage' letter on school letterhead. Some have been flagged for three months running — the principal has to decide whether to bar them from the board exam.
The data is from January. The list arrived on her desk on 11 February. The shortage letters will go out on 15 February. By the time a parent receives one, opens it, drives to the school and sits across from the principal, it is the third week of February and the year is over. The student has already missed the chance to bring her attendance up before the board cut-off. Every Indian school plays this game with the calendar — and almost every Indian school loses, every year, to the lag between the data and the action.
The Chronic Absentee Watchlist in Inkwelly removes the lag. The list is live — every student whose attendance has dropped below the school's threshold (default 75% per RTE Act 2009) appears the moment her percentage crosses, not at the end of the month. Trend arrows show whether she is climbing back up or sliding further down. The principal sees the new entries on the Student Attendance dashboard every morning. By October, she already knows who needs a parent meeting in November — not in February when it is too late.
How the watchlist works
The watchlist runs against the same daily attendance data the class teacher marks every morning and the head clerk reviews on the monthly register. For every student in every class, the system computes the running attendance percentage — days present divided by working days till date in the academic session, with leave days excluded or included per school configuration.
The moment a student's percentage drops below the school threshold (default 75%, configurable per school), her name appears on the watchlist on the principal's dashboard. The list is ranked by percentage, lowest first — the most urgent cases at the top. Each row shows the student's photo, name, class, current percentage, days absent vs working days, and a trend arrow. Up arrow (green) = improving over the last 7 days. Down arrow (red) = sliding further down. Flat dash = no change.
Next to every row is a Contact Parent button. Clicking it opens a side panel with the parent's name, primary phone number, secondary phone, last successful contact attempt, and a 'mark contact made' action with a free-text remark. The principal can call from her own phone, then click 'parent contacted' with the remark 'Mrs. Sharma agreed to send Aarav daily, asked about home tuition'. The audit log records the attempt. If the student climbs back above 75% within two weeks, the row drops off the watchlist; if she does not, the row turns dark red and a 'second contact' prompt appears.
The head clerk's view of the watchlist is slightly different — it shows the same students but in a printable table format, with a column for 'last contact made by' and 'date'. She prints this at the end of every month for the principal's record file. The same data drives the 'attendance shortage letter' template the office uses for parent meetings — no separate Excel sheet, no manual percentage calculation, no chance of a typo.
What the watchlist tracks for every student
- Live attendance percentage — days present / working days till date in the academic session, recomputed on every save
- Threshold flag — default 75% per RTE Act 2009, configurable to 80% (CBSE pre-board) or 85% (some board schools) per school
- Trend arrow — 7-day comparison: improving, sliding, flat — helps prioritise which student to call first
- Days absent vs working days — raw numbers behind the percentage, e.g., '13 absent out of 78 working days till date'
- Class and section — every row links directly to the class register grid for context
- Parent name and primary phone — from the student's profile, no separate data entry
- Last successful contact attempt — date, made-by user, free-text remark, on hover
- Contact prompt count — first contact, second contact, escalation — visible status badge per row
- Auto-removal — row drops off when student climbs above threshold for 14 consecutive working days
- Per-class breakdown — sidebar shows watchlist count by class, helps the principal spot a class-wide problem
- Reason ledger — if approved leave applications dominate the absences, the row shows a 'leave-driven' tag
- Export to PDF or Excel — for the office's monthly attendance shortage letter cycle
See the watchlist in action
Trend arrows that change the question you ask the parent
A student at 68% with a green up arrow is a different conversation from a student at 72% with a red down arrow. The first is recovering — the parent meeting is 'keep going.' The second is sliding faster than her percentage suggests — the parent meeting is 'what changed two weeks ago.' Most school chronic-absentee tools report only the percentage; the trend hides inside it.
The watchlist computes the trend over the last 7 working days vs the previous 7. Up arrow — attendance percentage in the last 7 days is higher than the previous 7 by more than 5 points. Down arrow — lower by more than 5. Flat — within 5 points either way. Schools that have used this for a term tell us the down-arrow rows get the principal's morning call within 24 hours, and that early intervention reverses about half of the slides before the student crosses the 65% mark.
One-click parent contact with audit log
Next to every watchlist row is a Contact Parent button. The panel that opens shows the primary and secondary phone numbers from the student's profile, the last successful contact attempt (with date and the user who made it), and a free-text 'remarks on contact' field. The principal calls from her own phone — the system does not auto-dial — and clicks Mark Contact Made.
The audit log records every contact attempt: which user clicked the button, when, and the remark they typed. 'Called Mrs. Sharma. Aarav had typhoid in October, recovering. Mother says he will be back from 15 November.' Two weeks later, the same row shows that history on hover. If a third party (the head clerk, the academic head) needs to follow up, they see the timeline without having to chase the principal for context. The same audit data feeds the parent-meeting summary report that the school files for affiliation renewals.
Configurable threshold — 75%, 80%, or your school's own bar
The RTE Act 2009 sets 75% as the legal minimum for promotion at the elementary level. CBSE for board exams uses 75%, with relaxation up to 25% on medical / sports grounds. ICSE asks for 75%. Some private boarding schools enforce 85%. The watchlist threshold is school-configurable — set it once in the dashboard's settings, every percentage flag, every shortage letter and every report uses that number consistently.
The threshold can be changed mid-year only by a school admin, with a mandatory reason field. The audit log records the change — 'threshold changed from 75% to 80% by Principal on 1 December 2025, reason: pre-board cohort enforcement'. Every previous report continues to show the historical threshold the data was generated against, so retrospective reporting stays honest. We have schools that run a 75% bar for Class 1–8 and a 75-with-medical-relaxation bar for Class 9–12 — the watchlist segments them into separate sub-lists with the rule applied per group.
Per-class breakdown spots class-wide problems
A single student below 75% is a personal-circumstances story. Eleven students in Class 8 A below 75% is a class-management story. The watchlist sidebar shows a per-class breakdown — number of flagged students per class, sorted by count. Classes with more than 5 flagged students are highlighted in red.
When Class 8 A turns up with eleven flagged students one Tuesday morning, the principal does not call eleven parents. She calls the Class 8 A teacher into her office and asks one question: 'what is happening in your class?' That is sometimes a teaching-style issue, sometimes a peer-bullying issue, sometimes a teacher-on-leave issue. The point is the watchlist surfaces the right question to ask. The same breakdown also drives the class-pulse grid on the dashboard — marking-coverage and absentee-density per class on a single screen.
“October mein hi pata chal gaya ki teen students 70% pe hain. Maine November mein parent meet kar liya. Ab board exam tak 78% pe le aaye. Pehle yeh sab February mein hota tha — tab tak khel khatam ho jata tha.”
Five real-world watchlist moments
1. October catch (Class 9 CBSE). The principal sees three Class 9 students at 71-73% on the October 1 watchlist. She calls the parents the same week. Two students return to regular attendance immediately; one had a medical issue and a leave application gets filed retroactively. By February, all three are above 80% and board-eligible. Without the watchlist, the principal would have found out in February.
2. Class-wide pulse (Class 8 A). The watchlist sidebar shows Class 8 A with eleven flagged students — highest in the school. The principal calls the class teacher. It turns out the maths teacher's transfer in mid-September has caused a teaching gap; students have been bunking maths and the absence pattern has cascaded. The school assigns a substitute and runs catch-up sessions over the next month. The flagged count drops to four by November.
3. Pre-board enforcement (December). The school runs a stricter 80% threshold for Class 12 only, from 1 December. The watchlist flips to a 80% bar for that one cohort while staying at 75% for everyone else. The audit log records the threshold change with the reason 'pre-board cohort enforcement'. The shortage letter template auto-includes the 80% language for Class 12 parents and the 75% language for the rest.
4. Leave-driven cases. Three Class 7 students appear on the watchlist at 72-74%. The watchlist marks all three as 'leave-driven' — most of their absences are approved medical leaves, not unexplained skips. The principal does not call the parents because the school knows the context. The watchlist row stays visible (the percentage still matters for board eligibility) but the contact prompt is suppressed.
5. Affiliation renewal evidence. During CBSE affiliation renewal in March, the board asks the school to demonstrate it actively tracks chronic absenteeism. The school exports the watchlist's audit log for the past three sessions — every flagged case, every parent contact attempt, every remark, every resolution. The board accepts it as documentary evidence and the affiliation renewal closes in three weeks instead of three months.
Common operations on the watchlist
- Open watchlist — from the attendance dashboard, one click
- Filter by class — see only one section's flagged students
- Filter by trend — only the students sliding (red down arrow), only the recovering ones (green up arrow)
- Click a row — jump to the per-student attendance profile and the register grid for context
- Contact parent — see phone numbers, last attempt, log a new contact with remark
- Print shortage list — monthly PDF for the principal's office file
- Export shortage data — Excel for the head clerk's records or for board affiliation evidence
- Change threshold — admin-only, with audit reason, applies forward; historical reports keep their threshold
- Suppress leave-driven cases — hide rows where most absences are approved leave applications
- Mark intervention — record a parent meeting, a counselling session, a medical-leave note for follow-up
- View timeline — see when the student first crossed the threshold, every contact attempt, every recovery
See the watchlist on your school's data
20-minute walkthrough on the Inkwelly demo school. Bring your last term's shortage list — we will load the same students into the watchlist and show you trend arrows, parent-contact log, and the threshold-configuration audit live.
Limits, safety and the small print
The watchlist does not auto-bar a student from a board exam. It surfaces the case, logs every parent-contact attempt, and produces the documentation the school needs — but the decision to bar belongs to the principal and the board examination authority. The percentage and the audit trail support the decision; they do not replace it.
Threshold is school-wide unless segmented. By default the threshold applies to every student in the school. Schools that need different thresholds per cohort (e.g., 75% for primary, 80% for Class 12) configure named segments — every segment runs its own watchlist with its own rule. We do not allow per-student thresholds because that opens the door to inconsistency and audit-log challenges in disciplinary cases.
Privacy. The watchlist is visible to the principal, the head clerk, the academic head, and the class teacher of each flagged student's class — not to other class teachers, not to any teacher who does not teach the student. Parents see only their own child's percentage and history on the parent app, never the watchlist itself. The audit log is admin-only.
Late marking can artificially flag a student. If the class teacher forgets to mark today's attendance for an entire class, every student of that class gets one 'absent' day until the marking is corrected. The watchlist re-computes on every save, so a corrected mark drops false positives within minutes. The marking-coverage card on the dashboard helps the principal spot classes with missing marks before they leak into the watchlist.
Auto-removal threshold and re-flag. A flagged student is removed from the watchlist after 14 consecutive working days above the threshold. If she dips again, she re-flags. The 14-day buffer prevents flicker (a student at exactly 75% bouncing on and off the list every day). The buffer is configurable per school.
Find shortage cases in October, not February
The chronic absentee watchlist is one of seven [Student Attendance](/modules/students-attendance) features Indian schools rely on every term. Book a demo and see it on your own data.
Belongs to
1 moduleFrequently asked
10 questionsIs the 75% threshold the RTE Act 2009 minimum?
Yes. The Right to Education Act 2009 specifies 75% minimum attendance for promotion at the elementary level. CBSE applies the same 75% bar for board-exam eligibility, with up to 25% relaxation possible on medical or sports grounds. The watchlist defaults to 75%; schools can raise it to 80% or 85% per their internal rules.
How is the percentage calculated?
Days present ÷ working days till date in the academic session, with leave days included or excluded per the school's configuration. Default is *'leave days count toward working days'* (the strict interpretation). The watchlist row shows the raw numbers (*'13 absent out of 78 working days'*) so the calculation is auditable.
Does it count working days from the academic session start or from the student's admission date?
From the student's admission date. A child admitted on 18 August has her percentage computed against the working days from 18 August onwards, not from 1 April. A child transferred out on 12 December has her denominator stop on 12 December. So mid-year admissions and exits do not show false-positive shortage cases.
Can I run different thresholds for different classes (e.g., 75% for primary, 80% for Class 12 pre-board)?
Yes. The school admin creates named segments and assigns a threshold per segment. Each segment runs its own watchlist with its own rule. The audit log records every segment-rule change with the user, timestamp and reason. The shortage letter template can be configured per segment too.
Does the watchlist contact parents automatically (SMS, WhatsApp, IVR)?
No. The contact button surfaces the parent's phone number and logs the attempt; it does not send automated messages on behalf of the school. The principal or head clerk calls from their own phone, then logs the attempt with a remark. We deliberately do not auto-message parents — a real human voice changes the conversation in ways an automated message does not.
Are leave-driven absences flagged as chronic too?
The student stays on the watchlist while her percentage is below the threshold, regardless of cause. But rows where most absences come from approved leave applications get a *'leave-driven'* tag, and the contact-parent prompt is suppressed. The principal still sees the case but treats it differently from an unexplained-absence case.
What happens when a student's percentage climbs back above the threshold?
She is removed from the watchlist after 14 consecutive working days above the threshold. The 14-day buffer prevents a student at exactly 75% from bouncing on and off the list every day. The buffer is configurable per school. Her historical record (when she was first flagged, every contact attempt, every recovery) stays in the audit log forever.
Can the watchlist data be used as evidence during board affiliation renewals?
Yes. The CBSE / ICSE / IB affiliation renewal questionnaires ask schools to demonstrate active tracking of student attendance. The watchlist's audit log — every flagged case, every parent contact, every resolution remark — is exportable as a PDF report and accepted by most boards as documentary evidence of active intervention.
Can parents see the watchlist?
No. The watchlist is visible only to the principal, head clerk, academic head, and the relevant class teacher. Parents see their own child's percentage and the daily attendance history in the parent app — they never see the cross-school list. This protects privacy and avoids exam-eligibility disputes spilling out before they are formally decided.
Does it work alongside the parent-app daily attendance notification?
Yes. Parents receive their child's daily attendance status in the parent app every school day. The watchlist works behind the scenes for school staff. When a child crosses the 75% bar, the parent sees a *'attendance below 75% — please discuss with the class teacher'* note in the parent app, and the school staff sees the watchlist entry on the principal's dashboard.
You might also like
2 readsSee Inkwelly on your school
30-minute demo. We open your current ERP with you and load your data into Inkwelly on the call. Dated go-live plan by the end of it.