Academics
The people behind timetables and attendance
The people behind school timetable and attendance software: teachers, attendance staff, administrators, leaders, records, families, students, IT, support, and suppliers.
Teachers and attendance staff
Teachers use the timetable to understand planned work and may record or correct attendance according to school policy. Attendance staff maintain definitions, follow up exceptions, and protect the distinction between plan and observation.
Both groups need clear status, class, period, date, correction, and support routes.
Leaders and records staff
Leaders set outcomes, capacity, priorities, and accountability. Records staff protect identity, class, transfer, history, retention, and report integrity.
Test absent teacher, changed class, transfer, duplicate mark, report correction, and reporting-period change.
Families, students, IT, and support
Families and students need appropriate, accessible information. IT maintains identity, integration, continuity, and technical controls. Support connects a reported problem to the right academic or technical owner.
GOV.UK school guidance emphasises accountable and secure handling. The U.S. Department of Education data governance checklist covers quality, access, security, lifecycle, sharing, disposal, and monitoring.
Make responsibility visible
Separate view, create, edit, review, approve, publish, export, correct, archive, and delete. The U.S. Department of Education data-quality guidance links quality with definitions, rules, validation, infrastructure, and professional learning.
Review unresolved ownership, corrections, staff effort, support demand, access exceptions, and report confidence at 30, 60, and 90 days.
Make the next improvement testable
Use this guidance to improve one bounded part of the people behind school timetable and attendance software. Name the owner, timetable or attendance record, evidence, correction route, and review date so staff can apply it consistently.
Check an ordinary case and one meaningful exception. If either depends on undocumented knowledge, add the missing definition, validation rule, permission, training note, or support route.
Record what changed, what remains manual, and who reviews the result before the next lesson cycle or attendance report.
Keep the decision beside its evidence so the next teacher or attendance officer can understand the rule without relying on informal memory.
Use the review to decide whether the change should be expanded, repaired, narrowed, or held.
Recheck the boundary when a campus, period, role, integration, calendar, or policy changes. A familiar workflow can carry a different access or reporting risk after a small change.

