Guide
The pre-publish timetable checklist: what to verify before staff see it.
Staff trust is spent on the errors they find, not earned on the sessions that were right. Run this checklist before publishing and the timetable conversation stays boring — which is the goal.
Updated 8 July 20267 min read
Key takeaways
- Check per-person promises first: planning-time delivery to the minute, part-timer days, job-share handovers — these are the errors staff find in the first hour.
- Check the silent structural errors second: room double-bookings, meeting clashes, duty gaps — these are the ones nobody finds until they hurt.
- Publish from one source of truth with per-teacher views, and version it: "current" must be unambiguous all term.
- Keep the receipts: the agreements and trade-offs behind the timetable, written down for the week-five question.
Why a checklist at all
A finished-looking timetable is a wall of small promises: this teacher gets released here, this class is in the hall then, this meeting fits there. In a thirty-staff primary school the promise count runs into the hundreds, and visual inspection of a full grid verifies almost none of them — the grid looks equally convincing whether the promises hold or not.
The checklist below is ordered by political blast radius: the things staff will find within an hour of publication come first.
The per-person checks (staff find these in an hour)
Go teacher by teacher, not slot by slot. Each person will read exactly one row of your timetable — their own — with total attention.
- Planning time: every teacher receives their full entitlement — APT, RFF, NCT, DOTT or NIT — to the minute, pro-rata for part-timers, on days they actually work
- Part-timers: no sessions, duties, or meetings on non-work days; correct arrival and departure part-days
- Job-shares: both partners' days correct, the handover point clean, no orphaned sessions, each partner's pro-rata release delivered on their own days
- Dual-role staff: classroom days and specialist days match the agreed pattern; no self-coverage paradoxes (a teacher cannot release themselves)
- Negotiated arrangements: every documented agreement — late starts, early finishes, no-Friday-duty deals — visibly honoured
- Meetings: every attendee of every meeting is actually free at that time, including part-timers and specialists
The structural checks (nobody finds these until they hurt)
These errors survive publication because no individual owns them — they surface as a corridor collision in week two.
- Rooms: no space double-booked — halls, libraries, STEM rooms, and shared spaces used by external providers are the usual offenders
- Staff double-booking: nobody teaching, meeting, or on duty in two places at once, including specialists counted in two roles
- Specialist rotations: every class receives its full program; no class silently dropped from a rotation after a late edit
- Duty roster: every zone covered every break; no duty assigned to someone who is teaching, in a meeting, or not at school that day
- Fixed events: assembly, chapel, sport, and interschool commitments present and not overwritten by later edits
- Bell-time arithmetic: session boundaries actually match the bell schedule, including the early-finish day if you have one
The publish process itself
How you publish determines how errors are reported and fixed. Publish one authoritative version from one system, give each staff member a view of their own week, and state clearly where "current" lives. The fastest way to lose the term is three PDF versions in circulation, each partly right.
Version deliberately: when a post-publication change lands (and it will), the old version should be visibly superseded, not competing. And archive a published snapshot — it is your fallback pack if systems are unreachable some morning, and your evidence when memories differ.
- One source of truth, named: staff know exactly where the current timetable lives
- Per-teacher views so each person can verify their own week in under a minute
- A feedback channel with an owner: errors reported once, to the right person, fixed in the source
- A printed or exported fallback pack: current timetable, duty roster, and daily plan
- The decision record: agreements and trade-offs behind this version, written down
Automate the checkable
Everything in the per-person and structural lists is mechanically checkable — which means every item is software's job, not a Sunday afternoon's. Bell Path runs these checks continuously during building and as a final validation before publishing: planning-time delivery per teacher, availability and double-booking, room clashes, meeting conflicts, rotation completeness, and duty coverage, with each failure named in plain language while it is still cheap to fix. The checklist above is exactly what its Final Check automates; keep the human review for what software cannot judge — whether the trade-offs are the ones your school meant to make.
Common questions
- When should the timetable be published to staff?
- After validation passes and leadership has walked the per-teacher views — and with enough lead time before term for staff to check their own week and report anything odd. Publishing a validated timetable a few days early beats publishing an unchecked one a fortnight early and spending the fortnight on corrections.
- Who should review the timetable before publication?
- Whoever built it should not be the only checker. A second leadership reviewer walking the per-teacher views catches assumption errors the builder cannot see, and the specialists and part-timers with the most complex arrangements are worth a quiet pre-publication confirmation of their own rows.
- What if an error is found after publishing?
- Fix it in the source of truth, republish as a new visibly-current version, and tell the affected people directly. What corrodes trust is not the error — staff expect a few — it is discovering that the fix lives in an email while the published timetable still shows the mistake.
From the Bell Path workspace
Forty-plus of these checks, automated
Bell Path's Final Check validates planning time, clashes, rooms, meetings, and duty coverage before you publish — and explains every issue in plain language.
See how validation worksKeep reading
How to build a primary school timetable, step by step.
The order you make timetabling decisions in matters more than the tool you make them with. This guide walks through the sequence experienced timetablers use — and the traps that cause the mid-term rewrite.
Planning time in Australian primary schools: APT, RFF, DOTT, NIT and NCT, explained.
Every state calls it something different, but the problem is the same everywhere: release time is an entitlement you must deliver to the minute, every week, and someone must teach the class while you do.
School timetable generator
Bell Path helps assistant principals and principals move from spreadsheet sprawl to a timetable they can trust, explain, and publish without dread.
Choosing school timetabling software
This is not a neutral ranking. It is an honest guide from Bell Path about what matters when a primary school is choosing timetabling software, what questions to ask vendors, and where we fit in the picture.