Roll call in under a minute: attendance that doesn't eat class time
Do the arithmetic once and it is hard to unsee. Thirty-five students, three seconds each to find the name and tap a state, and you have spent nearly two minutes of a forty-minute period on administration. Five periods a day, five days a week, thirty-eight weeks. That is somewhere near thirty hours a year, or roughly a fortnight of lessons, spent recording that people who are in the room are in the room.
And the two minutes is the optimistic number. It assumes nobody arrives late, the list is in the order you expect, and you do not lose your place.
The design mistake
Most registers, on paper and on screen, ask you to assign a state to every student. Thirty-five decisions, thirty-five actions.
But that is not the shape of the information. On a normal day the fact is “everyone is here except Diego and Camila”. Two facts, not thirty-five. A register that requires thirty-five inputs to record two facts is not asking you to record attendance. It is asking you to prove you looked.
Present is not a decision. It is the default, interrupted occasionally.
Invert it
Open the class with everyone already marked present, tap only the exceptions, and save. A full attendance is one action. A day with three absences is four. The count at the top updates as you go, so you can glance at the room and check the number against what you see, which is the actual verification step and takes about two seconds.

the four states that actually matter: present, absent, late, excused — anything more granular gets used inconsistently within a fortnight
The second job of a register
Speed is the obvious problem, and it is the smaller one.
The real work a register does happens in November, when a parent asks why their child is behind, or a head of year asks whether there is a pattern. At that moment you need one student’s attendance across eleven weeks, and you need it before the meeting starts. If the register lives in a stack of paper or in a spreadsheet organised by date rather than by student, that question costs you an evening.
This is the argument for a digital register that has nothing to do with being modern. It is not that typing is faster than writing. It is that the data is queryable by student afterwards, and paper is not.
The same applies to noticing a pattern before it becomes a meeting. A student who is absent every Friday is invisible in a stack of daily registers and obvious the moment the days are grouped by name.
What to check in any attendance tool
- What is the default state? If it is blank or absent, the tool will cost you a minute a period forever.
- Can you take it from a phone at the door? Roll call happens while you are greeting people, not while you are seated at a laptop.
- Can you fix yesterday? You will forget one. A tool that only allows today turns a thirty-second correction into a request to an administrator.
- Can you get one student’s history in a few seconds? This is the whole point, and it is the feature most registers treat as an afterthought.
The honest caveat
Paper still wins in one situation, and it is worth naming: when the network is down and the device is dead, a printed list and a pen work. Any digital register you adopt should be something you can abandon for a day without losing the term, which in practice means being able to enter a missed day afterwards rather than pretending it never happened.
Everything else about it should be one tap.