Troubleshooting guide for timetables and attendance

1. Describe the symptom

Record what a user expected, what they observed, when it happened, campus, period, class, room, role, device, version, integration, and whether the issue affects one record or a wider population.

Separate a wrong schedule, missing mark, late notification, duplicate mark, report mismatch, access error, integration delay, unavailable service, inaccessible control, and unclear policy. Different symptoms need different owners.

2. Protect the immediate decision

Choose a safe temporary action for the next lesson or attendance window. State which record is authoritative, who may make a correction, how temporary notes are protected, and when they must be reconciled or removed.

Do not ask staff to create uncontrolled copies or bypass permissions. Escalate urgent privacy, safeguarding, security, continuity, or records concerns through the approved route.

3. Check common causes

Review calendar, period, class, room, teacher, student, status, reason, identity, permission, published version, effective time, integration mapping, retry, duplicate event, report filter, and device or connectivity conditions.

Test absent teacher, substitute, room change, cancelled period, changed class, late arrival, partial attendance, transfer, duplicate mark, closure, outage, and report correction. Compare expected and observed results.

4. Preserve evidence

Keep timestamp, source, destination, record identifier, version, role, action, error, screenshot or log where appropriate, manual work, affected population, owner, and limitation. Avoid putting unnecessary student or family details in informal tickets.

The U.S. Department of Education data-quality guidance links reliable information with definitions, rules, validation, infrastructure, and professional learning. Evidence should help identify and prevent the cause, not merely close the ticket.

5. Check control and support

Review access, export, correction, backup, restoration, retention, disposal, supplier access, privacy, safeguarding, accessibility, security, records, and incident handling. The U.S. Department of Education governance checklist covers these lifecycle concerns.

GOV.UK guidance emphasises accountable and secure handling of school data. Apply qualified local review for legal, privacy, safeguarding, security, records, and accessibility interpretation.

6. Correct and communicate

Assign cause, remedy, approver, effective date, affected records, communication, rollback, and retest. Tell affected staff what changed, what remains manual, which record is current, and where to ask a follow-up question.

Preserve necessary history. A silent overwrite may remove the evidence needed to understand a report, correction, attendance follow-up, or timetable decision.

7. Prevent recurrence

At 30, 60, and 90 days, group incidents by data, process, permission, training, integration, support, calendar, product, or supplier cause. Check repeated conflicts, corrections, staff effort, support demand, access exceptions, and report confidence.

Decide expand, repair, document, train, configure, consolidate, narrow, or hold. Keep the troubleshooting record with the change decision and next review date.

Turn the guidance into an accountable decision

Apply this guidance to one bounded part of troubleshooting guide 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.