Decision matrix for timetables and attendance

1. Define the decision

State the timetable or attendance problem, users, campuses, calendars, periods, rooms, records, outcome, constraints, timeline, current process, and non-negotiable controls.

Name decision owner, evidence standard, review group, conflict-of-interest process, acceptance test, pause rule, and date. Do not let the matrix hide an undefined decision.

2. Set hard gates

Create pass or fail gates for schedule integrity, attendance meaning, correction, access, accessibility, privacy, safeguarding, security, continuity, records, reporting, integration, data return, and support.

A high preference score cannot compensate for a failed safety, privacy, accessibility, continuity, data-ownership, or minimum operational gate. Record evidence and approver for every gate.

3. Define weighted criteria

Weight usable fit, information quality, exception handling, staff effort, implementation capacity, support, reporting, integrations, accessibility, change control, total cost, supplier dependence, maintainability, and exit.

Publish weights before demonstrations. Record why a criterion matters, who validates it, and what evidence earns each score. Avoid double-counting a feature under several vague headings.

4. Run comparable scenarios

Test 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.

Record expected result, observed result, manual work, configuration, limitation, role access, support route, evidence, response time, and residual risk. Score observed behaviour separately from supplier claims.

5. Compare information and control

The U.S. Department of Education data-quality guidance connects dependable information with definitions, rules, validation, infrastructure, and professional learning. Score calendar, identity, class, room, status, reason, version, correction, and reconciliation.

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

6. Compare cost and delivery

Include discovery, schedule cleanup, status mapping, migration, setup, integrations, testing, training, support, security, privacy, accessibility, storage, upgrades, internal time, incident response, and exit.

Ask who maintains calendars, periods, rooms, classes, statuses, reports, permissions, integrations, validation, documentation, backups, retention, corrections, and support after launch.

7. Decide and review

Publish scores, gates, evidence, weights, assumptions, missing information, limitations, owners, acceptance conditions, and decision date. Invite 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, continuity, and outcome. Change the decision only through a recorded review.

Turn the guidance into an accountable decision

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