Integration architecture guide for timetables and attendance

1. Draw the information boundary

Inventory timetable, attendance, student, staff, room, calendar, reporting, family, identity, finance, transport, activity, support, and safeguarding-related systems that exchange or depend on information.

For each flow, name source, destination, purpose, fields, owner, frequency, event time, effective time, retry, failure route, retention, access, supplier, and evidence. Do not describe a system as “the source” without naming the record.

2. Define identity and meaning

Map stable identities for students, teachers, classes, rooms, campuses, periods, subjects, and reporting periods. Document duplicate, merge, transfer, withdrawal, substitute, and temporary assignment handling.

Agree definitions for present, absent, late, partial, authorised, unauthorised, pending, corrected, published, and final. Record who approves changes and how dependent reports are affected.

3. Design event and correction flow

Specify create, update, cancel, publish, correct, archive, and delete behaviour. Distinguish a timetable change from a correction, a late mark from a correction, and a report finalisation from ordinary synchronisation.

Test absent teacher, substitute, room change, cancelled period, changed class, late arrival, partial attendance, transfer, duplicate mark, closure, outage, retry, replay, and report reconciliation.

4. Plan failure and reconciliation

Define timeout, duplicate event, out-of-order event, rejected record, partial delivery, stale source, conflicting edit, replay, manual correction, and service outage. State which record wins and who resolves an unresolved conflict.

The U.S. Department of Education data-quality guidance links reliable information with definitions, rules, validation, infrastructure, and professional learning. Include validation, monitoring, reconciliation, and professional training in the architecture.

5. Control access and lifecycle

Map view, create, edit, review, approve, publish, export, correct, archive, and delete across systems, roles, campuses, suppliers, integrations, support users, and temporary staff.

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

Run ordinary schedule and attendance flows as well as room change, cover, late arrival, partial attendance, transfer, closure, report, integration delay, access removal, backup restore, and contract-end export.

For each, capture expected result, observed result, source, destination, timestamps, manual work, permissions, logs, notifications, correction, evidence, owner, and limitation. A successful API response does not prove a correct school decision.

7. Govern change

Require review for new field, campus, calendar, role, report, supplier, integration, status, or retention rule. Record reason, risk, test, owner, approval, communication, rollback, effective date, and post-change review.

At 30, 60, and 90 days, compare conflicts, missing or duplicate marks, corrections, latency, failed deliveries, staff effort, support demand, access exceptions, report confidence, and the original outcome.

Turn the guidance into an accountable decision

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