The Register Is a Promise
An attendance register looks like the most boring object in a school. A column of names, a column of ticks. But it is one of the few pieces of data in an institution where a mistake is not an inconvenience — it is a child whose whereabouts nobody can account for. The register is not a list. It is a promise: that the school knows who is here, who is not, and who has been told.
Once you see it that way, you build it differently.
The moment the data matters
Most of the time, attendance is a formality. The class is full, everyone is marked present, the day proceeds. The register earns its keep on the rare morning when it does not match reality — a child marked present who never arrived, a name skipped in a hurry, a class register saved over the top of yesterday's. On an ordinary day nobody notices. On the wrong day, those are the gaps a parent's phone call falls into.
Software that treats attendance as just another form misses this entirely. The register has a single moment where correctness is everything, and a system has to be built for that moment even though it almost never comes.
What a register actually has to guarantee
When I work on this part of a school system, I hold it to a higher standard than almost anything else, because the cost of being wrong is not measured in time:
- It must be hard to lose. A mark, once made, should survive a dead battery, a closed browser, a lost signal. Attendance taken and then silently dropped is worse than no system at all, because it manufactures false confidence.
- It must remember who said what. If a record changes, the system should know who changed it and when. Not to assign blame, but because in the moment a child is unaccounted for, the question "who marked this, and when?" is the first thing anyone asks.
- It must work at the speed of a corridor. A register is taken by a teacher with thirty children in front of them, not by someone at a desk. If it is slower than a paper sheet, it will lose to the paper sheet, and it should.
- It must fail loudly. If a class has not submitted attendance by a certain time, somebody should know — quietly, automatically — before it becomes a problem rather than after.
None of this is glamorous. There is no dashboard that makes "we always know where every child is" look impressive in a demo. But that quiet guarantee is the entire reason the register exists, and it is the standard the software underneath it has to meet.
A register is a promise a school makes to every family that hands over a child each morning. The least the software can do is keep it.