Most schools treat scheduling and attendance as two jobs done by two people in two tools: the timetable belongs to whoever builds it in August, and the register belongs to the teacher, in a notebook or a spreadsheet tab. They are one system. The timetable states what should happen — this class, this teacher, this hour, every Tuesday for twelve weeks. Attendance records what did. Every operational question a small school gets asked, from "was my daughter in class on Thursday?" to "why did that group shrink?", is answered by comparing the two, and it is answerable in seconds or not at all depending on whether they are the same record.
This cluster covers the pair. The first article is the timetable: the distinction between a recurring slot and a dated session, the order to build in, and why a timetable is a term artefact rather than a calendar. The second is the register: the four statuses, who marks them, and what a live online class can reasonably infer. The third is what you do with it — same-day follow-up, the patterns worth watching, and the reports parents, inspectors and owners actually ask for.
The distinction that makes attendance tractable is the one most spreadsheets blur. A slot is the repeating fact: B1 teens, Tuesdays and Thursdays at five, with a teacher and a room, for the term. It has no date, because it is every Tuesday. A session is one occurrence of it: Tuesday 14 October at five, which happened, or was cancelled, or was covered by someone else. Attendance attaches to the session, never to the slot, because a student is not present at "Tuesdays".
Schools that keep only slots — a timetable grid and nothing else — have no place to record what happened, so attendance ends up in a parallel document that has to be reconciled with the timetable by hand whenever either changes. Schools that keep only sessions, creating each class as a one-off calendar entry, spend their August making eighty entries and their October editing them one at a time. You need both, with the session generated from the slot, which is how SprintUp models it: a recurring weekly slot with no date, and dated sessions against which presence is recorded.
A register with two states — here or not here — cannot answer the questions a school is actually asked. Four can: present, absent, late and excused. The difference between absent and excused is the difference between a pattern that needs a phone call and a family who told you in advance, and a school that cannot distinguish them will either chase parents who already explained, or fail to chase the ones who did not. Late matters separately because lateness is the leading indicator of disengagement in teenagers and of a timetable problem in adults.
For a class held in a room, the teacher marks the register and there is nothing to automate. For a live online class the platform knows something the teacher does not: how long each student was actually connected. SprintUp uses that to suggest a status against a policy the school sets — connected for at least a set share of the call's length counts as present, joining more than a set number of minutes after the host started counts as late — and the defaults are 75% and 10 minutes. The suggestion only pre-fills the register. The teacher confirms or overrides it, because the platform does not know that a student's connection dropped for twenty minutes through no fault of theirs, and a register that marked them absent without asking would be wrong in a way that matters to a family.
That division — the platform proposes, the teacher decides — is the right shape for every piece of attendance automation, and the second article goes through it properly, including the cases where the suggestion is reliably wrong and the policy settings that fit different kinds of class.
Attendance carries two different weights depending on who you teach. For children and teenagers it is a safeguarding obligation before it is anything else: a school that does not know a twelve-year-old is missing, and does not tell the family the same day, has failed at something more serious than administration. The specific legal duties differ by country and by whether the school is part of compulsory education, and they are worth confirming for your jurisdiction rather than assuming — but the operational rule is the same everywhere: absence is noticed the day it happens and followed up the same day.
For adult classes, online schools and tutoring, attendance is the best churn signal a school has. A student who missed two sessions in a fortnight has usually decided to stop before they have told you, and often before they have admitted it to themselves. A school that sees the pattern on Friday can make a call on Monday; a school that discovers it at re-enrolment has lost the student and the fee. The third article covers both uses — the duty and the signal — and the follow-up that serves each.
Attendance data is only worth collecting if something is produced from it. A small school needs three things and rarely more. The parent report: did my child attend, at what rate, and were there absences I did not know about — one screen, per student, per term. The operational view: which classes have falling attendance, which students are trending down, which slots are quietly dying, read weekly by whoever can act. The compliance record: a register per session that can be produced on request, with who marked it and when, which matters the day an inspector, a funder or a parent's solicitor asks.
On SprintUp, attendance is recorded per student per session with a status, a comment and, for online classes, the minutes attended, and an attendance rate is computed into the school dashboard and analytics alongside enrolment and revenue. What the platform will not do is decide your thresholds or make the phone call — the follow-up rule and the person who owns it are the school's, and the third article is about designing both.
Build the timetable as slots and sessions, record attendance honestly with a teacher in the loop, and act on it the same day. Each article ends with a checklist.