Academics
What procurement teams ask about timetables and attendance
What procurement teams should ask about timetable and attendance software: scope, schedule and marking fit, migration, school effort, permissions, support, total cost, and exit.
Ask what is included
Request scope by campus, calendar, period, class, room, user, attendance role, report, integration, family view, support tier, storage, and growth.
Ask which functions are native, configured, integrated, manual, planned, or unavailable. A feature list is not a delivery plan.
Ask who does the work
Who cleans schedules, maps statuses, migrates marks, links classes and rooms, validates data, trains staff, supports exceptions, reconciles reports, handles corrections, and owns changes?
Require answers for absence, substitution, room change, cancelled period, changed class, late arrival, partial attendance, duplicate mark, transfer, closure, and reporting cases.
Ask about control and cost
How are roles, approvals, publishing, exports, retention, incidents, backup, restoration, suppliers, accessibility, privacy, safeguarding, and contract-end return managed?
GOV.UK guidance emphasises accountable and secure handling. The U.S. Department of Education data governance checklist covers quality, access, security, lifecycle, sharing, disposal, and monitoring.
Make responses comparable
Score the same scenarios, evidence, manual work, limitations, risk, support, implementation effort, and total cost. Review the selected option at 30, 60, and 90 days against conflicts, marks, corrections, staff effort, support demand, and report confidence.
Make the next improvement testable
Use this guidance to improve one bounded part of what procurement teams ask 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.
