Chess Academy Attendance Tracking: Retention System

Five things per student per session: the status, the reason if absent, who marked it, when it was marked, and what the mark triggered. A bare present-or-absent register answers the question nobody asks (was Aarav here on the 14th?) and fails the questions that matter: is this family drifting, does this absence earn a make-up credit, and did anyone follow up.

• Status: present, absent, or late, with late recorded separately because a creeping lateness pattern means something different from absence.
• Reason: excused with notice, excused after the fact, or unexplained. The unexplained ones are the signal.
• Marked by and marked when: a register marked three days later by an admin is fiction, and the timestamp proves which kind you have.
• Trigger: an excused absence should create a make-up credit; a second unexplained absence should create a follow-up task with a name on it.
• Batch context: the same student's record reads differently in a twice-a-week batch than a weekly one, so the mark needs to know its schedule.

Notice what is not on the list: biometrics, GPS, or anything heavier than a tap. A chess class of eight students does not need an access-control system; it needs a record honest enough to read patterns from. Paper achieves the marking half and fails the pattern half, because nobody re-reads a paper register, which is the whole argument for keeping the register digital.

The coach who is teaching the session marks it, inside the first five minutes of class, from their phone. Not the admin at the front desk, not the owner reconciling at night, not the coach from memory the next morning. The person looking at the room is the only one who knows the truth, and the truth decays fast: by evening, was-Riya-there becomes a guess.

The whole routine is about 60 seconds: open the batch, today's roster is already listed, tap the absentees, add a one-word reason where known, done. Anything longer than a minute will be skipped on busy days, and a register with gaps teaches you to distrust it everywhere. Late arrivals get upgraded from absent to late as they walk in, which takes one more tap and preserves the lateness pattern.

Substitute coaches are the routine's weak point. A substitute who does not mark attendance leaves a hole exactly where scrutiny is highest (parents notice cover classes). Make marking part of the handover: the substitute gets the batch roster with the cover request, and the session is not closed until the register is.

Yes, on two rhythms: same-day for an absence, monthly for the full picture. A same-day message when a child was expected and did not arrive is partly safety and partly signal that the academy noticed; silence teaches families that attendance does not matter here. The monthly summary, attendance alongside rating movement, is what makes the fee feel accounted for.

Channel matters as much as rhythm. A notice board or a portal the parent must remember to open will lose to the app already on their home screen; WhatsApp Business exists precisely so small businesses can meet customers in that app [1], and WhatsApp's own help centre documents the business-account features academies lean on, such as labels and quick replies [2]. Whether a dedicated guardian portal beats a WhatsApp group for the richer monthly view is a real trade-off, and we compare the two in a separate guide.

What parents should not get is a raw feed of every mark in real time. A push notification per tap trains families to ignore the channel, and one mistaken absent-mark broadcast instantly is a trust wound. Send the absence message after the coach has confirmed the room, and keep everything else for the monthly rhythm.

Absence patterns are the earliest churn warning an academy gets, weeks before a parent says anything. Families almost never quit by announcement; they quit by drift. Attendance softens first, then homework stops, then the fee is paid late, then the quiet WhatsApp message that this term will be the last. By the time the conversation happens, the decision is weeks old, which is why the register, read properly, is your retention radar.

The working rule is the 2-absence rule: the second unexplained absence inside a month triggers a personal message from the coach the same day. Not a fee reminder, not an automated nudge, a human note: we missed Riya on Thursday, is everything alright, here is what the batch covered. One unexplained absence is noise (traffic, a cold, a birthday). Two in a month is a pattern with a reason behind it, and the reason is almost always something a conversation can still fix: a school-tuition clash, a child losing confidence after a tournament, a fee concern the family is too polite to raise. Waiting for the third absence usually means there is no fourth.

Two patterns in that table are timetable problems wearing an attendance costume: the repeated-weekday miss and the whole-batch dip. Treat those as scheduling work, covered in our batch scheduling guide, not as seven separate parent conversations. The rest are retention work, and the deeper reasons families leave (and the saves that work) are a topic of their own in our guide to why students quit.

The register should be the only door into the make-up ledger: an absence marked excused creates a credit, automatically and immediately, and nothing else does. When credits are granted by side agreement (a parent asks at the counter, an owner says fine on WhatsApp), the ledger and the register drift apart, and every dispute becomes archaeology.

Wiring the two together also keeps the policy fair in both directions. The family that gives notice gets its credit without asking, which rewards the behaviour you want; the unexplained absence earns a follow-up instead of a credit, which keeps make-ups from becoming a discount on commitment. Where the credits get redeemed is a scheduling question (standing make-up slots in the weekly grid), and the policy itself, expiry windows, credit caps, and what counts as notice, is covered in full in our make-up classes guide.

Thirty minutes, once a month, owner and coaches together, four questions per batch. It is the cheapest retention meeting an academy can run because the data is already collected; the review just forces someone to read it.

1. 1Read each batch's attendance percentage for the month and compare it with the previous two months, looking for direction, not the absolute number.
2. 2List every student under 70 percent or with two or more unexplained absences, and confirm each one already got the 2-absence message; assign any that slipped.
3. 3Check the make-up ledger: credits issued versus redeemed. A pile of unredeemed credits means the make-up slots are at the wrong time.
4. 4Pick one action per flagged batch: a slot change, a parent call, or a coach conversation, with a name and a date on it.

For online and hybrid students, complement the physical register with platform activity: the Lichess API exposes a student's games and puzzle history [3], so a student who attends class but never plays between sessions is visible too, and that combination (present in class, absent from the board) predicts plateau and frustration. The review's output also feeds the parent rhythm: the monthly summaries that go out on WhatsApp, the app most families already live in [4], should match what the review saw, so a family never hears everything is fine in the same month the register said otherwise. How to present the progress half of that summary is its own craft, covered in our guide to showing parents rating progress.