The rule for identifying irregular students: look at attendance percentages over a fixed window — not guesswork or “feels like” punishment. Coaching’s biggest loss is the silent decline: a student reduces attendance by a day or two, nobody notices, and then suddenly “no admission anymore”. A weekly report makes the silent decline visible.
What to verify: attendance over a fixed window; no guesswork punishment
The report structure:
| Student (ID) | Membership | This week | Last 4 weeks | Class |
|---|---|---|---|---|
| 31 | Maths | 2/3 | 8/12 | regular |
| 22 | Physics | 1/3 | 5/12 | declining |
| 44 | Chemistry | 3/3 | 11/12 | good |
Keep the class definitions written: regular (≥75%), watch (50–75% — ask why), risk (<50% — guardian contact). Without written thresholds, every week starts punishment on “seems less” guesses — which hurts the wrong students and never brings back the real risk cases.
A usable sample: the attendance exception sheet
Rules for the weekly exception sheet:
- Only “watch” and “risk” students make the list — regulars are not read.
- Per risk student, two fields: last attended date + last contact date.
- The contact note records what happened — promise, illness, another coaching.
- If the same student re-appears as risk next week — the muhtamim’s personal phone call.
Irregular-student detection: workflow steps and limitations
- Guardian contact is the first action in the watch class — enquiry, not pressure.
- On a negative cause (another coaching), ask a service question: which subject felt weak?
- Month-end: count the classes — is the risk group growing? An institution-level signal.
- Limitation: attendance records honesty — buddy-marking corrupts classes; spot-check rooms occasionally.
Irregular-student detection: questions to ask before your demo
- Does the 4-week attendance percentage come per student?
- Can a class filter (risk list) be built?
- Does it show the “last attended” date?
The weekly report’s sources: the attendance module and attendance documentation; guardian contact via the communication module; coaching-specific structure on the coaching page.
Irregular-student detection FAQ
Is changing batches or removing students the right punishment?
No — irregularity is usually a time or load problem. Learn the cause first; removal is the last resort, not the first.
Is attendance mandatory in coaching?
Yes — coaching sells results plus consistency; an irregular student’s poor results become your failure.
Who reviews the report — teachers or management?
Both: teachers for their own batches; management for the institution-level class counts.