Spreadsheet replacement plan for timetables and attendance

1. Inventory the spreadsheets

Record file, owner, purpose, campus, calendars, periods, rooms, classes, teachers, students, attendance marks, reports, location, sharing, version, update frequency, dependencies, retention, and consequence of error.

Identify the authoritative record and every downstream copy. A file called “final” is not evidence of control.

2. Decide what should move

Classify each field and process as migrate, redesign, archive, export, or retire. Remove obsolete columns, duplicate schedules, unclear status definitions, stale marks, broken links, and unsupported history before migration.

The U.S. Department of Education data-quality guidance links quality with definitions, business rules, validation, infrastructure, and professional learning.

3. Design the target workflow

Define campuses, calendars, periods, rooms, classes, cover, attendance statuses, reasons, corrections, reports, permissions, publishing, integrations, retention, support, accessibility, privacy, and safeguarding.

Test absence, substitution, room change, cancelled period, changed class, late arrival, partial attendance, duplicate mark, transfer, closure, report, and outage.

4. Migrate and validate

Map source to target fields, identities, classes, rooms, periods, statuses, reasons, transformations, validation, rejected records, duplicate handling, version history, reconciliation, and approval.

GOV.UK school guidance emphasises accountable and secure handling. Apply qualified local privacy, safeguarding, records, security, and legal advice.

5. Train and cut over

Train by role, rehearse corrections and exceptions, publish the freeze window, communicate the current schedule and status definitions, provide support, define temporary work, test backup and restoration, and set rollback.

6. Retire safely

After acceptance, restrict or remove old spreadsheets according to the approved records schedule. Review duplicate copies, exports, links, support folders, backups, and supplier copies.

At 30, 60, and 90 days, measure conflicts, duplicate marks, corrections, staff effort, report reconciliation, access exceptions, support demand, and the original replacement outcome.

Turn the guidance into an attendance decision

Apply this guidance to one bounded part of spreadsheet replacement plan for school timetable and attendance software. Define the attendance or scheduling decision, record, purpose, authoritative source, accountable owner, permitted users, correction route, and evidence needed to approve the next step.

Test an ordinary timetable or attendance record and meaningful exceptions such as a changed class, missing mark, substitute teacher, room change, late arrival, early departure, partial attendance, transfer, duplicate mark, or reporting-period change. Record who resolved it and how the correction reached dependent views.

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

Review the result 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, 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, or a changed academic calendar.

Keep the evidence beside the decision record so a later reviewer can distinguish observed behavior from an assumption, estimate, or supplier statement. Name the next test where the current evidence is 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, or retention even when the workflow appears familiar.

Set the next review date and owner. A dependable timetable and attendance system is maintained through clear definitions, controlled change, professional judgment, 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 a correction is communicated without creating an uncontrolled copy.

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