A timetable looks like a calendar only after the difficult work is finished. Underneath it sits a network of constraints: room capacity, teacher availability, subject requirements and the rhythms of different age groups.
When those constraints live in spreadsheets, every change creates a trail of manual checks. A single absence or room closure can consume an administrator’s afternoon.
A shared operating record makes the timetable responsive. The system can show which choices are truly blocked, which are preferences, and which change has the smallest effect on the rest of the school day.