Reporting requirements for timetables and attendance

1. Define the decision behind the report

State whether the report supports cover, timetable quality, attendance follow-up, family communication, leadership assurance, records, finance, safeguarding, statutory or local reporting, or operational planning.

Name audience, owner, population, campus, academic calendar, period, date range, frequency, deadline, authoritative source, action, acceptance test, and consequence of a wrong or late result.

2. Define terms and measures

Document campus, term, working day, period, class, room, teacher, student, present, absent, late, partial, authorised, unauthorised, pending, corrected, published, final, conflict, cover, and completion.

For each measure, state numerator, denominator, exclusions, time basis, source, refresh, correction, rounding, missing value, duplicate handling, and limitation. A polished chart cannot repair an undefined measure.

3. Define scope and scenarios

Test ordinary days and absent teacher, substitute, room change, cancelled period, changed class, late arrival, partial attendance, transfer, duplicate mark, closure, report correction, outage, and late integration.

Check campus, phase, class, room, teacher, student, period, status, reason, date, version, and reporting-period filters. Confirm that a user can understand whether the report describes entry time, event time, or effective time.

4. Make corrections visible

Show report version, refresh time, source, status definitions, correction window, finalisation state, owner, and contact route. Preserve necessary history so a later reviewer can explain why a figure changed.

The U.S. Department of Education data-quality guidance links reliable information with definitions, rules, validation, infrastructure, and professional learning. Include reconciliation and correction evidence in report acceptance.

5. Control access and export

Separate view, filter, create, approve, publish, export, correct, archive, and delete by role, campus, class, student, family, supplier, and support user. Check shared links, downloads, email, print, and spreadsheet copies.

The U.S. Department of Education data governance checklist covers quality, access, security, lifecycle, sharing, disposal, and monitoring. GOV.UK guidance emphasises accountable and secure handling of school data.

6. Design for use

Provide plain-language labels, accessible structure, keyboard and assistive-technology support where required, readable dates and times, meaningful errors, alternative formats, and a path to question or correct a record.

Ask teachers, attendance staff, leaders, records, families, students, IT, finance, privacy, safeguarding, and support what decision they make from the report and what they do when the result is incomplete or disputed.

7. Govern reporting change

Record new field, filter, measure, audience, source, status, integration, calendar, privacy purpose, retention, owner, approval, test, communication, rollback, and effective date for every material change.

At 30, 60, and 90 days, review reconciliation, corrections, report confidence, access exceptions, export activity, support demand, staff effort, and the original decision outcome. Expand, repair, narrow, consolidate, or hold.

Turn the guidance into an accountable decision

Apply this guidance to one bounded part of reporting requirements for school timetable and attendance software. Define the scheduling or attendance decision, authoritative record, accountable owner, permitted users, correction route, evidence, and review date.

Test an ordinary case and meaningful exceptions such as an absent teacher, substitute, room change, cancelled period, changed class, late arrival, early departure, partial attendance, transfer, duplicate mark, closure, outage, or reporting-period change.

Keep supplier capability, school responsibility, professional judgement, legal advice, and measured outcome separate. If evidence is incomplete, narrow the claim and pilot the smallest safe change.

Review at 30, 60, and 90 days. Check completeness, timeliness, consistency, corrections, access exceptions, staff effort, support demand, reporting confidence, and the original outcome. Decide whether to expand, repair, consolidate, narrow, or hold.

Before approval, ask a reviewer who was not involved in the design to challenge the strongest assumption. Replace broad language with the exact evidence, population, date, and limitation the school can verify.

Document what was tested and what was not. A successful demonstration with a simple timetable does not establish readiness for substitutions, absences, split attendance, late marks, new periods, multiple campuses, or a changed academic calendar.

Keep evidence beside the decision record so a later reviewer can distinguish observed behaviour from an assumption, estimate, or supplier statement. Name the next test where evidence remains incomplete.

Revisit the boundary when the school adds a campus, year group, role, integration, reporting period, or policy. A small change can alter permissions, definitions, timing, retention, or support demand.

Set the next review date and owner. A dependable timetable and attendance operation is maintained through clear definitions, controlled change, professional judgement, and visible accountability rather than a one-time setup.

Make the handoff readable to a teacher, attendance officer, leader, and reviewer. State what passed, what remains manual, which records are authoritative, who owns unresolved conflicts, and how corrections are communicated without creating an uncontrolled copy.

Keep approved definitions beside validation rules, training notes, support routes, and change history. New rooms, periods, roles, integrations, or calendars can change the risk even when field names stay the same.