What an IT lead should document about timetables and attendance

Document the operating map

List timetable, attendance, student, staff, room, calendar, reporting, identity, family, support, finance, activity, and safeguarding-related systems that exchange or depend on information.

For each, record owner, purpose, authoritative records, fields, identities, frequency, effective time, access, supplier, retention, backup, failure route, support contact, and evidence.

Document the information model

Define campus, calendar, period, class, room, teacher, student, attendance status, reason, version, correction, published, final, report, and integration event. Record duplicate, transfer, withdrawal, substitution, and merge handling.

The U.S. Department of Education data-quality guidance connects dependable information with definitions, rules, validation, infrastructure, and professional learning. Keep the dictionary beside validation and reconciliation rules.

Document control and continuity

Map view, create, edit, review, approve, publish, export, correct, archive, and delete by role, campus, class, student, family, supplier, support user, and temporary assignment.

Record backup, restoration, outage, integration retry, incident, access removal, retention, disposal, accessibility, privacy, safeguarding, security, and manual continuity. Test absent teacher, substitute, room change, changed class, late mark, duplicate mark, and report cases.

Document change and ownership

For each material change, record reason, affected calendar, campus, periods, classes, rooms, roles, statuses, reports, integrations, risk, test, approver, communication, rollback, effective date, and review.

At 30, 60, and 90 days, review failed deliveries, corrections, access exceptions, support demand, staff effort, report confidence, and unresolved owners. GOV.UK guidance emphasises accountable handling of school data.

Make the next improvement testable

Use this guidance to improve one bounded part of what an IT lead should document about 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.