How multi-campus teams coordinate timetables and attendance

Choose what should be shared

List the definitions and controls that should be common across campuses: person identity, class, subject, room, period, attendance status, reason, correction, report, role, retention, and support.

Then identify legitimate local differences in calendar, working day, bell time, language, programme, reporting, staffing, room names, policy, and family communication. Shared does not mean identical.

Set decision rights

Name central and campus owners for schedule creation, publication, attendance correction, permissions, integrations, training, support, incidents, backup, restoration, privacy, safeguarding, records, and change.

Define when a local change needs central review. Record effective date, affected campus, impacted reports, communication, rollback, and evidence for every material change.

Test movement and exceptions

Rehearse a teacher working across campuses, shared room, substitute, absent teacher, changed class, late arrival, partial attendance, student transfer, duplicate identity, closure, integration failure, and report reconciliation.

Check whether access follows campus, role, class, person, temporary assignment, or support function. Inspect exports and notifications for accidental cross-campus exposure.

Operate the network

The U.S. Department of Education data-quality guidance connects quality with definitions, rules, validation, infrastructure, and professional learning. Use a cross-campus dictionary, sample validation, reconciliation, and role training.

GOV.UK guidance emphasises accountable and secure handling. At 30, 60, and 90 days, compare conflicts, marks, corrections, staff effort, support demand, access exceptions, report confidence, and local differences.

Make the next improvement testable

Use this guidance to improve one bounded part of how multi-campus teams coordinate school timetable and attendance software. Name the owner, timetable or attendance record, evidence, correction route, and review date so staff can apply it consistently.

Check an ordinary case and one meaningful exception. If either depends on undocumented knowledge, add the missing definition, validation rule, permission, training note, or support route.

Record what changed, what remains manual, and who reviews the result before the next lesson cycle or attendance report.

Keep the decision beside its evidence so the next teacher or attendance officer can understand the rule without relying on informal memory.

Use the review to decide whether the change should be expanded, repaired, narrowed, or held.

Recheck the boundary when a campus, period, role, integration, calendar, or policy changes. A familiar workflow can carry a different access or reporting risk after a small change.