SchoolDeck generates a school timetable from teacher availability, subject periods per week, room and laboratory constraints, and then handles the daily reality — arranging cover for an absent teacher and notifying the affected sections in under two minutes.
Generation is constraint-based, not magic. A school short of teachers in a subject will get a timetable that says so rather than one that hides it.
Building the timetable is a fortnight in July. Amending it is every single morning, and that is the part software usually gets wrong. When a teacher calls in sick at 7:50, cover has to be arranged and communicated before the first bell, or the office reverts to a whiteboard and the system stops reflecting reality.
Clashes first, because a teacher in two rooms at once is not a preference to balance — it is invalid. Then weekly subject load per section, then room and laboratory availability, then the softer preferences: spreading a subject through the week rather than stacking it, keeping games away from the period before lunch.
Where the constraints cannot all be met, the generator reports which one it broke and why, rather than silently producing something workable-looking. A school genuinely short of a physics teacher needs to see that, not have it distributed across the week where nobody notices until October.
The flow that decides whether the timetable is trusted. A teacher is marked unavailable; the system proposes cover from teachers who are free that period, ordered by who is under their weekly load and who already teaches that section. The office confirms, and the affected sections, the covering teachers and the parent app all update from the same change.
No re-entry anywhere. If cover has to be recorded again in a register afterwards, the two will disagree within a week.
Phrased the way they arrive, answered so each one stands on its own.
Yes, from teacher availability, weekly subject load per section, and room and laboratory constraints. Where constraints conflict it reports which one it could not satisfy rather than producing a plausible-looking timetable that hides the shortage.
Under two minutes in practice. The system proposes free teachers ordered by weekly load and familiarity with the section; the office confirms, and section views, teacher views and the parent app all update from that one change.
Yes. Sections, streams and elective groups each carry their own schedule while sharing the teacher and room pool, which is where clashes are detected.
Checked by the Implementations desk on 1 September 2026. Corrections go in the page, dated, rather than quietly.
Pricing is on the page, in the open, with the counting rule written next to it. Nobody has to book a call to find out what it costs.
See pricingForty minutes with an implementation engineer — your classes, your fee heads, your grading scheme, entered as we go. No slides, no sample school.