How to build a school timetable that doesn't burn out your teachers
Ask any school administrator where the timetable went wrong and you will rarely hear "the maths was hard". You will hear "Mr. Ahmed has seven periods on Tuesday and Ms. Fatima finishes at break" — a fairness failure discovered after the schedule was already printed and announced.
Why class-by-class scheduling breaks fairness
The traditional method fills the grid one class at a time. Early classes get generous placements; the last teachers compete for whatever cells remain. The result is predictable:
- Front-loaded teachers — some teachers absorb most first and last periods of every day.
- Scattered days — one lesson at 7am, another at 1pm, dead hours between.
- Invisible overload — nobody counts anyone else's load until complaints arrive.
Fixing it by hand means re-laying the whole puzzle — which is why most schools simply live with it for the term.
Flip the order: workload first, grid second
A fair timetable starts by counting, not placing:
- Compute each teacher's demand total — sum the weekly periods their qualifications commit them to.
- Compare against capacity — official load, minus duties, within daily and consecutive caps.
- Rebalance the demand itself before any cell is placed — shift a class's lessons to a less-loaded qualified colleague.
When the demand list is fair, the grid that follows inherits the fairness automatically.
What software can enforce that a spreadsheet cannot
Workload-aware generation — the approach Haneen uses — treats fairness as a constraint, not an afterthought:
- Lessons are placed most-constrained-first with bounded backtracking, so rare resources (labs, split classes) are secured early.
- Teacher selection weighs current load, spread across days, and daily caps — not just "who is free".
- A workload report afterwards lists every teacher's totals and day distribution, so fairness is provable to staff — not a promise.
A practical checklist for your next timetable
- Set a daily cap per teacher before generating — even a soft one changes outcomes.
- Block unavailability honestly; phantom availability produces phantom fairness.
- Generate, then read the workload report first — not the grid.
- Publish, and share teacher timetables by link so every teacher sees only their own verified schedule.
The principle behind Haneen is simple: the timetable should follow the workload, not the other way around. Fairness designed in is fairness you never have to defend.