It's easy to see lesson notes as a compliance chore — something teachers file because they're asked to, and something administrators collect because policy says to. That framing misses what the record is actually for: confirmation that the curriculum scheduled for a given day was the curriculum that was taught.
Without a submission record tied to the timetable, a school only finds out about a delivery gap when it shows up somewhere else — a poor assessment result, a parent's complaint, an external inspection. By then, the gap has usually existed for weeks.
Treating lesson notes as an operational signal changes what the record needs to look like. It needs a deadline relative to the lesson itself, not the end of term. It needs to be tied to the specific class and period it covers, not submitted in a batch. And it needs to surface as an exception the same day it's missed, not discovered in a term-end audit.
This is the model RollCall uses: every scheduled lesson has an expected submission, every submission has a deadline, and anything missing appears as an exception immediately — giving administrators the chance to follow up while it's still that day's problem, not last month's.