August in a Caribbean school office has a soundtrack: fans humming, papers shuffling, and a deputy principal muttering over a timetable grid. The work is heroic — and every year, a handful of the same avoidable mistakes quietly sabotage it, surfacing in the first week of term as clashes, complaints, and re-dos. After enough Augusts, the patterns are unmistakable. Here are the seven mistakes we see most, and what the schools that avoid them do differently.
1. Starting from last year's grid
It feels efficient: take last year's timetable and patch it. But a timetable is a solution to last year's constraints — this year two teachers left, enrolment shifted, and Form 4 options changed. Patching an old solution to new constraints piles compromise on compromise, and by the third edit you're maintaining an archaeology site. Start from this year's facts: current staff, current loads, current rooms. Reuse the rules, never the grid.
2. Trusting memory instead of writing constraints down
"Everyone knows Mr. Joseph coaches on Wednesday afternoons." Everyone, that is, except the timetable. Unwritten constraints — the shared PE field, the teacher who splits time with another school, the lab that floods when it rains — live in heads, and heads go on leave. The schools that finish in a week write every constraint down first, however obvious. If it isn't recorded, the timetable will violate it, and you'll find out in September.
3. Placing subjects before scarce resources
Filling in the easy classes first feels like progress — until you reach the single science lab, the one IT room, and the three classes that all need them at once, with no free slots left. Scarcity goes first: labs, specialist rooms, part-time specialist teachers, shared spaces. The abundant stuff fits around the scarce stuff; it never works the other way.
4. Forgetting the teachers are human
A grid can be clash-free and still be cruel: a teacher with six consecutive periods, another split across distant buildings back-to-back, a third with every free period on Monday and none for the rest of the week. These timetables technically work — and then absenteeism, burnout, and grievances arrive by October. Balance of workload across days isn't a luxury; it's what makes the timetable survivable.
A timetable without clashes is the minimum. A timetable teachers can actually live inside is the goal.
5. Leaving no slack for September's surprises
Every year, September brings a surprise: a resignation, a late hire, an enrolment bulge that splits a class. A timetable packed to 100% density has no room to absorb any of it, so one surprise forces a full rebuild. Experienced timetablers leave deliberate slack — a protected free period here, an unassigned room there — as crumple zones for the crash they know is coming.
6. Publishing without stakeholder eyes
The timetabler checks the grid; only the people in it can check reality. The music teacher knows the choir clash. The senior mistress knows 5B can't be trusted with last-period freedom. Circulating a draft to department heads for 48 hours catches errors no solo review ever finds — cheaply, before printing, instead of expensively, in week one.
7. Doing all of it by hand in the first place
The deepest mistake isn't any single error — it's accepting a process where one person manually reconciles hundreds of interlocking constraints by eye, under deadline, in August heat. That process produces mistakes 1 through 6 as a matter of course. Constraint-solving software like Ednovum Timetable exists precisely to absorb this: you enter the teachers, rooms, loads, and rules (including the human ones, like workload balance), and it searches for a schedule where everything holds at once. When September's surprise lands, you adjust the inputs and re-solve in minutes — instead of re-living August.
The schools that glide into September aren't luckier. They wrote the constraints down, scheduled scarcity first, left slack, invited eyes — and let a solver do the reconciling. See how Ednovum Timetable works before next August finds you at the grid again.