Attendance registers
When attendance lives in too many registers.
Theory in one register, practical in another, and the timetable somewhere else. The clerk rebuilds the day before anyone can trust the export.
Friction
What breaks on paper
How the mess shows up when fees, attendance, or the timetable run in silos.
Theory and practical diverge
Marks sit in separate books or sheets. Nobody can say which class ran against which approved slot.
The timetable is a third copy
Sessions get invented by hand when the live schedule is missing, stale, or still pending approval.
The export is a rebuild
The clerk stitches percentages from those books before a report leaves the department. The download is not the same record professors marked.
Already live
The flow already running
How Spanworth holds the same work end to end, without a side spreadsheet.
The day
Working and substituted dates come from the academic calendar. Lecture sessions appear only against approved timetable slots.
The mark
The professor opens Attendance, picks the date and session that match the approved slot, then sets each student present or absent.
Theory and practical
Both sit on that day through the same hub. There is no second register to keep in sync.
The export
The clerk chooses course, semester, and a percentage threshold, then downloads the report. The export is that record, not a reconstruction.
Span
Where that record lives
Open the live capability that already closes this mess, then the role that runs it.