What a Substitute Teacher Needs by 8 A.M.
A school's operations are never really tested on a normal day. They are tested at 7:10 in the morning, when a teacher calls in sick and a deputy head has fifty minutes to find someone to stand in front of a class that does not yet know its teacher is gone. Cover is the stress test. If your systems can get a substitute into the right room, with the right plan, by 8 a.m., they work. If they cannot, all the polish elsewhere is decoration.
I have come to use that morning as a design benchmark, because it compresses everything hard about running an institution into a single hour.
The cascade behind one absence
One teacher away is never one problem. It is a chain. Who is free this period to cover? Are they free the next period too, or does covering now create a second hole later? What were the absent teacher's classes supposed to be doing today? Does the substitute know which room, which year group, which child needs watching? Every one of those questions has an answer somewhere in the school — in a timetable, a lesson plan, a head's memory — and the whole task of the morning is gathering those scattered answers fast enough.
When that gathering depends entirely on one person's memory, the school is one bad morning away from chaos. The job of software here is not to be clever. It is to put the scattered answers in one place, quickly, for a stressed human who has no time to learn an interface.
Designing for the worst hour, not the average one
Building for cover taught me to optimize for the bad morning rather than the good one. In practice that means:
- Surface the gap instantly. The moment an absence is logged, the affected classes and the staff free to cover them should be visible together. The deputy should not have to cross-reference three documents at 7:15.
- Carry the context with the slot. A substitute walking into an unfamiliar room needs the basics attached to the assignment — the room, the year group, what the class is working on — not a separate hunt for a lesson plan.
- Make the second-order cost visible. Good cover tooling shows that covering this period empties a slot two periods later, before the decision is made, not after.
- Degrade gracefully. On the morning the network is slow and everyone is in a hurry, the system has to still be usable. The worst hour is exactly when the infrastructure is also most likely to be strained.
There is a temptation in education technology to build for the calm demo: the empty timetable, the unhurried click-through. But schools do not live in the calm demo. They live in the 7:10 phone call. Build for that, and the ordinary days take care of themselves.
A school that can absorb an absence without anyone outside the staff room noticing has good operations. Quietly, invisibly, that is most of what the software is for.