Building a timetable that survives week three
Timetables do not break in week one. They break in week three, when a teacher is on leave and a room is double-booked. Here is how to build one that holds.
A timetable survives week three when clashes are impossible to introduce, not when it is cleverly built. The grid is drawn once, against a fixed bell schedule and the school's own periods; every lesson is assigned a subject, a teacher and a room; and the system refuses to let two things occupy the same teacher, class or room at the same time. A timetable built that way does not need to be redrawn when a teacher is away — it needs one substitution, and the substitution is checked against the same rules.
The timetable that breaks is the one drawn on a whiteboard or in a spreadsheet and then photocopied. It looks settled on the first Monday. By week three, a teacher is on leave, someone has moved a period to cover, and a room has two classes booked into it. Nobody did anything unreasonable; the grid simply had no way to say no.
Fix the bell schedule before you place anything
Every timetable sits on a bell schedule: the periods of the day, the breaks between them and the working days of the week. Define that once for the academic year and reuse the same grid everywhere — for every class, every section and every teacher. Most timetable chaos is not about lessons at all; it is about the bell schedule existing in three slightly different versions, one per section head.
This is the base layer, and it belongs with the rest of the academic structure — sessions, terms, class timings and the subjects being taught. Get the calendar and the periods right once and the timetable has something stable to sit on.
Assign a subject, a teacher and a room to every period
A timetable cell is not just "Maths". It is Maths, taught by a named teacher, in a named room, for a named class. Three facts per period, not one. The moment a cell is missing any of them, the timetable can no longer answer the two questions that matter: who is teaching what right now, and where are they doing it.
Room allocation is where quiet clashes hide. Two sections of the same class sharing a classroom is fine when nobody checks and a problem the day both have a lesson in the same period. Recording the room for each lesson means the grid can see the conflict before it happens rather than the class discovering it at the door.
| What is placed | Against what | Why it prevents a clash |
|---|---|---|
| Subject | The class and its curriculum | Two subjects cannot fill one period for the same class |
| Teacher | Their own week across every class | One teacher cannot be in two rooms in one period |
| Room | Every other lesson in that period | One room cannot hold two classes at once |
Detect the clash before you publish, not after
The difference between a timetable that survives and one that does not is when the clash is found. Found before publishing, it is a five-second fix on the screen. Found in week three, it is an apology to two classes, a displaced teacher and a phone call from a parent. Clash detection is the single feature that decides which of those two weeks you have.
Edumia shows overlapping assignments while the timetable is still being built, so a double-booking is visible before the grid is published rather than after it has been pinned to the notice board.
Give each teacher their own week, not the whole school's grid
A wall chart of the entire school's timetable is useful for the office and useless for a teacher. What a teacher needs is their week across every class they teach, in one view, so they can see their own free periods and their own load. A timetable that only exists as one giant grid means every teacher has to trace their own name through it — and the ones who trace it wrong are the ones who turn up in the wrong room.
Give the office the whole grid and give each teacher their own week, from the same data. That is the difference between a document and a working timetable.
Publish it once, and keep last year's
When the grid is settled, it gets published — printed for the notice board, or exported for the record. The printed copy matters more than it sounds: a timetable that only lives on a screen is one power cut away from being reconstructed from memory.
Archive the grid by academic year as well. A question in June about what a class was taught in the previous year, or how a teacher's load compared term to term, should be answerable from the record rather than from a photograph someone took of the notice board.
Cover and substitution: where the grid actually breaks
A whiteboard timetable handles the week that was planned. It is the unplanned days that break it — a teacher calls in sick at seven in the morning, a class is left without someone to teach it, and the office has to find cover from a grid it can only read, not search. That is the moment that decides whether the timetable survives.
A timetable that holds makes cover a question with an answer: who is free this period, in a room that is also free, and not already committed elsewhere? The office can ask the grid and trust the reply, because the grid already knows every teacher's load. Finding cover becomes a search of the same data the timetable was built from, not a guess followed by a phone call.
It helps that the two constraints underneath are set once and then respected — the holiday calendar and the class timings define which days and which periods even exist, so a substitution on a half-day is checked against the real day, not a generic one.
Rooms, labs and shared spaces
Most classrooms can be swapped at a push. A laboratory, an art room, a computer room or the hall cannot — there is one of each, and only one class can be in it at a time. These are the resources a timetable has to protect first, because a clash there has no workaround. Two classes booked into the science lab in the same period do not have a third room to move to.
So the shared rooms should be placed before the ordinary ones and checked hardest, with the rest of the grid fitted around them. A timetable built that way treats the lab as the scarce thing it is, rather than realising it was overbooked after the term has started.
The report worth having at the end of the exercise is the one that shows how full each period is — where the pressure sits, and which room or which teacher is carrying more than a fair share. That is the thing management asks for, and it should come out of the grid rather than a recount.
What this looks like when it works
The test of a working timetable is not the first Monday. It is the Thursday in week three when a teacher goes on leave. In a timetable that holds, the office opens their own week, sees the periods they were due to teach, and finds a free teacher who is not already committed in that period and not already in that room. The substitution is checked against the same rules the grid was built on, so it cannot introduce a clash. The change takes a few minutes, and it is recorded against the grid rather than scrawled in the margin.
In a timetable that does not hold, that same Thursday is a series of phone calls and a guess about who is free, and the guess is sometimes wrong. Nobody plans a clash; they simply have no way to prevent one.
The metric to watch
Watch the number of times the published timetable changes in a term. A little change is normal — leavers, joiners, a teacher's long leave. A timetable that is revised most weeks is not being managed; it is being rebuilt. If you had to print a new grid every fortnight, the grid was never the problem — what was missing was the check that stops a change from creating a clash in the first place.