Requirements framework for timetables and attendance

1. Describe the operating context

State campus, calendar, period, class, subject, room, teacher, student, attendance role, report, integration, device, language, accessibility, and staffing context. Include the problem and desired outcome.

Separate hard requirements, weighted preferences, school responsibilities, supplier responsibilities, and evidence requirements.

2. Define scheduling requirements

Specify timetable creation, conflict detection, room and teacher constraints, cover, split classes, changes, publication, versioning, effective dates, calendars, substitutions, and communication.

Require scenarios for room change, absent teacher, cancelled period, changed class, closure, transfer, and new academic period.

3. Define attendance requirements

Specify capture role, class and period context, status and reason definitions, late and partial attendance, early departure, correction, approval, history, report, family view, and reconciliation.

Do not let a vendor blur an observed mark with a planned schedule.

4. Define controls and quality

Require view, create, edit, review, approve, publish, export, correct, archive, and delete permissions. Ask about validation, audit, staff leavers, suppliers, backup, restoration, retention, disposal, incidents, accessibility, privacy, and safeguarding.

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.

5. Define delivery and support

Require migration, configuration, integration, training, support, calendar planning, temporary work, rollback, acceptance, documentation, internal capacity, total cost, and contract-end arrangements.

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

6. Define acceptance and review

For each requirement, record expected result, observed result, manual work, evidence, limitation, owner, and approval. Review conflicts, marks, corrections, staff effort, support demand, report confidence, access exceptions, and outcome at 30, 60, and 90 days.

Turn the guidance into an attendance decision

Apply this guidance to one bounded part of requirements framework 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, teacher absence, 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, room conflicts, 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.