Build a School Timetable That Survives the Term

The timetable is the operating system of a school. Every other system (attendance, schemes, assessments, payroll) runs on top of it, and when the timetable is bad, everything downstream hurts in ways people don't trace back to it. The teacher rushing across campus with five minutes between distant classrooms, the class that has mathematics last thing on Friday every single week, the resource room double-booked on Wednesdays: these are timetable problems wearing other costumes. Here's how to build one that survives contact with a real term.

Start from constraints, not from wishes

The amateur way to build a timetable is to start placing lessons and discover conflicts. The professional way is to write the constraints down first, because constraints are the actual material you're working with. Teacher availability (who is part-time, who shares across schools, who can't do first period because of the school run). Room dependencies (science labs, the ICT suite, the field). Level requirements (primary breaks at fixed times; SHS electives must run in parallel). And the non-negotiables your school already has: assembly, breaks, devotions, the days the market fills the road outside.

Most schools have never written these down; they live in the deputy head's head. Getting them onto one page is the first hour of timetable week, and it saves the whole second day.

Anchor the immovable things first

Build in this order. One: breaks, assembly and any whole-school rituals. Two: the shared specialist rooms and the teachers who serve multiple levels, because they're the scarcest resources and everything else flexes around them. Three: the elective and practical blocks that need parallel scheduling. Four: everything else, which is the majority of the grid and the easy part once the scarce things have homes. Schools that build in reverse order (filling easy lessons first, then discovering the lab is triple-booked) spend timetable week redoing work.

The quality checks that separate good grids from bad ones

• The heavy-subject spread. Mathematics and English should appear across the week, at varied times, not bunched. A subject that only ever meets last period on Friday is a subject the timetable has quietly demoted.
• The teacher's day. No teacher should carry four consecutive doubles, and the run between consecutive classrooms matters at real schools with real distances. Walk the worst teacher's day physically before publishing; you'll catch things no grid shows.
• Double periods where doubles matter. Practicals and extended writing need them; drill subjects don't. A timetable that gives double periods to the wrong subjects wastes its scarcest asset, contiguous time.
• The spare. Good timetables leave slack: free periods that can absorb a lost lesson, a cover, a mass. A timetable at one hundred percent capacity shatters the first time a teacher is ill.

Timetabling is also workload policy

Two teachers with identical teaching loads can have wildly different weeks depending on how the timetable scatters their lessons. Six single periods spread across five days is a different life from three doubles bunched at both ends. When the deputy builds the grid, they are making workload decisions whether they intend to or not, so make them deliberately: spread the demands evenly, keep each teacher's free periods genuinely usable, and publish early enough for people to plan their lives. The schools that treat the timetable as a staff-welfare document have measurably calmer staffrooms, at zero cost.

When the term attacks it

No timetable survives the term unchanged: a teacher leaves, an exam block eats a week, the inter-house sports day appears from nowhere. What separates resilient schools is that changes happen through the grid, not around it. A cover lesson takes the absent teacher's spare, not a colleague's break. A lost week is recovered by pre-agreed squeeze weeks in the scheme, not by secretly abandoning the last topics. This is where the timetable and the scheme of learning meet: the scheme's slack weeks are the timetable's shock absorbers. Build both with the term's real shape in mind, and the June panic becomes a shrug.

The tooling question

Timetabling on paper or in a spreadsheet works up to a surprising size, then collapses under its own conflict-tracking. If your school is past a few hundred students, multiple levels or shared specialist staff, generate the grid with software and spend the saved days checking it on foot, which is the part humans are actually better at. Inside LexsEdu the timetable lives with everything else: lessons appear on teacher and student views, attendance and schemes key off the same structure, and a change propagates the same afternoon instead of requiring a noticeboard campaign (School ERP).

Publish it like it matters

Finally, treat the published timetable as a promise. Same format everywhere, in every classroom, on every phone through the platform, with the version date on it. A school running on "the new timetable, haven't you seen the noticeboard?" is a school that hasn't finished the job. The grid you built carefully becomes real only when every teacher, student and parent can see their version of it without asking. Build it on constraints, protect its slack, walk its worst day, publish it properly, and it will hold the term the way it should: invisibly.

The annual timetable review

Give the grid a one-hour post-mortem every term's end, while the term's frictions are fresh. Which periods were chronically lost? Where did covers fail? Which corridor run defeated three teachers? Did the elective blocks actually fit the students' choices? Five notes per term, carried to next year's build, compound into a timetable that fits the school like tailoring rather than off-the-rack. The best timetables in the business aren't the cleverest; they're the ones that have been quietly corrected for a decade, and that compounding is available to any school that keeps the notes.

One last discipline: whoever builds the grid keeps a dated copy of every version, because the timetable is also the school's legal record of what was taught when. When a parent disputes attendance in exam season, when a teacher's load is questioned, when the inspector asks how a syllabus was covered, the term's grids are the answer. Three minutes of filing per version, and the school never argues from memory again. Build on constraints, publish like it matters, keep the slack, walk the worst day, and file each version; that is the whole craft, and it holds the term.