System-selection scorecard for timetables and attendance

1. Set gates before scores

Define non-negotiable requirements for timetable integrity, attendance meaning, correction, access, accessibility, privacy, safeguarding, security, continuity, records, reporting, integration, and data return.

A high weighted score cannot compensate for a failed safety, privacy, continuity, accessibility, or data-ownership gate. Record who approves each gate and what evidence is acceptable.

2. Define comparable scenarios

Use schedule construction, room conflict, cover, absent teacher, substitute, cancelled period, changed class, attendance capture, late arrival, partial attendance, transfer, duplicate mark, report correction, integration failure, and outage.

For every vendor or option, record expected result, observed result, manual work, configuration, limitation, evidence, support route, response time, and unresolved question. Do not score a scenario from a sales statement alone.

3. Score the information model

Check definitions for campuses, calendars, periods, rooms, classes, subjects, teachers, students, attendance statuses, reasons, versions, corrections, reports, and audit history.

The U.S. Department of Education data-quality guidance connects quality with definitions, business rules, validation, infrastructure, and professional learning. Score validation, duplicate handling, reconciliation, and correction visibility.

4. Score control and lifecycle

Assess view, create, edit, review, approve, publish, export, correct, archive, and delete permissions. Ask how the option handles leavers, substitutes, support users, suppliers, failed integrations, backup, restoration, retention, disposal, and incidents.

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.

5. Score delivery and ownership

Include schedule cleanup, status mapping, identity matching, migration, integration, testing, training, support, documentation, change management, academic-calendar timing, internal capacity, and recurring administration.

Ask what the school must maintain after launch and who owns a wrong mark, stale timetable, failed notification, report mismatch, permission error, or integration delay.

6. Compare complete cost and exit

Include subscription or build cost, setup, data preparation, training, support, integrations, security, privacy, accessibility, storage, upgrades, internal staff time, incident response, reporting, and contract-end return.

Score exit evidence: export format, history, definitions, attachments, permissions, logs, deletion, transition support, and the ability to operate safely during a supplier or integration change.

7. Decide and review

Publish the scorecard with assumptions, evidence, weights, excluded items, conflicts of interest, unresolved risks, decision owner, review date, and acceptance conditions. Ask an independent reviewer to challenge the result.

At 30, 60, and 90 days, compare conflicts, mark completeness, corrections, staff effort, support demand, access exceptions, report confidence, and the original outcome. Change the decision only through recorded evidence.

Turn the plan into an accountable decision

Apply this guide to one bounded part of system-selection scorecard 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: absent teacher, substitute, room change, cancelled period, changed class, late arrival, early departure, partial attendance, transfer, duplicate mark, closure, outage, or reporting-period change. Record the observed result and manual work.

Keep supplier 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 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, 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.