What an RFP should say about timetables and attendance

Describe the school’s work

State campuses, calendars, working days, periods, rooms, classes, teachers, students, attendance sessions, reports, family communication, integrations, roles, support windows, and growth assumptions.

Describe schedule creation, conflict resolution, cover, attendance capture, corrections, reporting, notifications, and exceptional cases. Do not make a generic feature list responsible for explaining the school’s operation.

Require scenario responses

Ask suppliers to demonstrate absent teacher, substitute, room change, cancelled period, changed class, late arrival, partial attendance, transfer, duplicate mark, closure, report correction, outage, integration delay, and access removal.

Require expected result, configuration, manual work, roles, evidence, limitation, support route, response time, audit history, and total effort for each scenario. Score all responses against the same evidence standard.

Require governance detail

Ask about definitions, validation, identity matching, permissions, publishing, correction, exports, reports, accessibility, backup, restoration, retention, disposal, suppliers, subcontractors, incidents, privacy, safeguarding, records, and security.

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.

Require commercial and delivery clarity

Request one-time and recurring costs for setup, data cleanup, migration, configuration, integrations, training, support, storage, upgrades, internal time, reporting, and exit. Ask what the school must maintain after launch.

Specify acceptance tests, implementation owners, calendar windows, support coverage, data return, contract-end deletion, review measures, and change control. Keep the RFP honest about what is not yet known.

Make the next improvement testable

Use this guidance to improve one bounded part of what an RFP should say about 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.