How to build a primary school timetable, step by step.

Most failed timetables fail before the grid is opened. The cause is almost never the software — it is a missing fact about a person. A teacher who leaves at 2:30 on Thursdays for a standing medical appointment. A job-share pair who split the week Wednesday lunchtime, not end-of-day. A specialist who also carries a classroom role two days a week.

Before you place anything, build a complete picture of your staff: employment fraction, days worked, fixed commitments, dual roles, and any negotiated arrangement — formal or informal. If it lives in someone's head or a hallway conversation, write it down now. Every one of these facts is a constraint your timetable must satisfy, and the ones you discover late are the ones that force a rebuild.

In a primary school, planning time and the specialist program are the same decision viewed from two sides: a classroom teacher is released because a specialist is teaching their class. That coupling is why planning time — APT in Victoria, RFF in NSW, NCT in Queensland, DOTT in WA, NIT in SA — is the hardest constraint in the build, and why it has to come early.

Work out the total release minutes each teacher is entitled to under your current agreement, pro-rata for part-timers. Then check the supply side: do your specialist hours actually generate enough release, on the right days, for the right teachers? If the arithmetic does not work at this stage, no amount of grid-shuffling later will fix it — you have a staffing decision to make, not a timetabling one.

Watch the day-of-week trap with part-timers: a teacher who works Monday to Wednesday can only receive release on Monday to Wednesday. It is common for the total specialist supply to be sufficient while being undeliverable to specific people because it falls on days they do not work.

Specialist programs — Art, PE, Music, Languages, STEM — run best as consistent rotations: the specialist takes a year level's classes in a block, moving through the school across the week. Blocks reduce transitions for the specialist, keep equipment set-up sane, and make the released planning time predictable for classroom teachers.

Decide the rotation shape deliberately. Back-to-back sessions for the same class (a specialist "double") suit some subjects and not others. Whole-year-level sweeps create natural team planning windows — if Year 2's three classes all have specialists on Tuesday morning, the Year 2 team can plan together. That is a feature worth designing for, not an accident.

Staff meetings, professional learning communities, leadership meetings, assembly, and chapel or community time are fixed events that both consume time and constrain it: a teacher in a meeting cannot teach, supervise, or be released. Place them before filling the rest of the grid, and check each one against the people it involves — an "all staff" meeting has different consequences than a meeting of the Year 6 team.

This is also the point to place fixed room bookings: the hall's PE slots, the library's timetabled sessions, shared spaces used by outside providers. Rooms clash silently — two classes booked into the hall is exactly the kind of error that survives review because nobody was looking for it.

With constraints locked, drafting is the quick part — whether you are dragging boxes in a spreadsheet or generating with software. The discipline that matters is validation: a systematic check of every promise the timetable makes, done before staff see it.

Check planning-time delivery per teacher, to the minute, against entitlement. Check every part-timer only appears on days they work. Check job-share handovers do not orphan a class. Check no room is double-booked and no teacher is in two places at once. Check meeting attendees are actually free for their meetings. In a school of thirty staff this is hundreds of individual checks — which is exactly why "it looks right" fails, and why schools either build a checklist or use software that validates automatically.

The credibility of a timetable is set in the first week after publication. If staff find errors — a missed release, a duty clash, a part-timer scheduled on their day off — every future version gets read with suspicion, and the quiet renegotiations begin.

Publish one version, from one source of truth, with per-teacher views so each person can check their own week quickly. Keep a record of what was agreed and why: which teachers get released when, who covers what, what trade-offs were made. When a question comes back in week five — and one will — you want an answer that starts with "here is what we agreed", not with an archaeology dig through old spreadsheets.

A staffing change mid-term is not an edge case; it is the normal life of a primary school. A teacher goes on leave, a new student support arrangement lands, a specialist's days change. The test of a good timetable process is not whether the first version was right — it is how cheaply you can absorb a change without rebuilding the week from scratch.

Keep your constraints documented separately from the grid itself, so a change to one person's availability is a one-line edit followed by a regeneration or targeted fix — not a fresh negotiation with the whole timetable. And version everything: when the week changes, staff should be looking at the current version, not the one from the fridge door in February.