Guide
How to build a primary school timetable, step by step.
To build a primary school timetable, collect every staffing fact first, place planning time and specialist rotations before anything else, then check each teacher's week before staff see it. The order you make decisions in matters more than the tool you use. This guide walks through the order experienced timetablers follow, and the mistakes that cause a rebuild halfway through the term.
Updated 20 August 202610 min read
Key takeaways
- Collect every staffing agreement in writing before you place a single session. The verbal ones are the ones that break the timetable in week three.
- Place the hardest constraints first: part-timers and job-shares, then planning time, then specialist rotations, then everything else.
- A timetable that looks finished is not finished. Check planning time per teacher, room clashes and meeting clashes before anyone else sees it.
- When you publish, keep a written record of who is released when, who covers what, and why.
Start with a staffing audit, not a grid
Most timetables that fail do so before the grid is opened, and 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 appointment, a job-share pair who hand over at Wednesday lunchtime rather than at the end of the day, or a specialist who also teaches a classroom 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 a fact lives in someone's head or came from a hallway conversation, write it down now. Every one of these facts is a rule the timetable must follow, and the ones you discover late are the ones that force a rebuild.
- Employment fraction and exact days for every part-timer
- Job-share pairs: who works which days, and where the handover falls
- Dual-role staff: which days are classroom days and which are specialist days
- Fixed outside commitments: network meetings, regional roles, medical arrangements
- Informal agreements a previous leadership team made that staff still expect
Lock in planning time before specialist programs
In a primary school, planning time and the specialist program are the same decision seen from two sides: a classroom teacher is released because a specialist is teaching their class. That is why planning time (APT in Victoria, RFF in NSW, NCT in Queensland, DOTT in WA, NIT in SA) is the hardest part of the build, and why it has to come early.
Work out the release minutes each teacher is entitled to under your current agreement, pro-rata for part-timers. Then check the supply: do your specialist hours generate enough release, on the right days, for the right teachers? If the arithmetic does not work at this stage, no amount of 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 school's total specialist supply to be enough while still being undeliverable to particular people, because it falls on days they do not work.
Design specialist rotations as blocks
Specialist programs (Art, PE, Music, Languages, STEM) run best as consistent rotations: the specialist takes a year level's classes in a block and moves through the school across the week. Blocks reduce transitions for the specialist, keep equipment set-up manageable, and make the released planning time predictable for classroom teachers.
Decide the shape of the rotation deliberately. Two sessions in a row with the same class (a "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 worth designing for rather than leaving to chance.
Place meetings and fixed events next
Staff meetings, professional learning communities, leadership meetings, assembly, and chapel or community time are fixed events. They both use time and limit it: a teacher in a meeting cannot teach, supervise, or be released. Place them before you fill the rest of the grid, and check each one against the people it involves. An "all staff" meeting has different consequences from 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, and shared spaces used by outside providers. Room clashes are silent. Two classes booked into the hall at once is exactly the kind of error that survives review because nobody was looking for it.
Draft quickly, then check everything
Once the constraints are settled, drafting is the quick part, whether you are dragging boxes in a spreadsheet or generating with software. The work that matters is checking: every promise the timetable makes, confirmed before staff see it.
Check planning time per teacher, to the minute, against their entitlement. Check that every part-timer only appears on days they work. Check that job-share handovers do not leave a class without a teacher. Check that no room is double-booked and no teacher is in two places at once. Check that meeting attendees are actually free for their meetings. In a school of thirty staff this is hundreds of individual checks, which is why "it looks right" fails, and why schools either build a checklist or use software that checks automatically.
Publish once, with a record
Staff decide whether to trust a timetable in the first week after it is published. If they find errors (a missed release, a duty clash, a part-timer rostered on their day off), every later version is read with suspicion.
Publish one version, from one place, with a view for each teacher so they can check their own week quickly. Keep a record of what was agreed and why: who gets released when, who covers what, and what trade-offs were made. When a question comes back in week five, you want to be able to answer "here is what we agreed" instead of digging through old spreadsheets.
Plan for change
A staffing change mid-term is normal life in a primary school. A teacher goes on leave, a new student support arrangement arrives, or a specialist's days change. The test of a good process is not whether the first version was right. It is how cheaply you can absorb a change without rebuilding the week.
Keep your staffing facts and rules recorded separately from the grid, so a change to one person's availability is a one-line edit followed by a regeneration or a targeted fix, not a fresh negotiation with the whole timetable. Keep versions, too: when the week changes, staff should be looking at the current version, not the one pinned to the fridge in February.
Common questions
- How long should building a primary school timetable take?
- With the inputs collected properly, drafting should take hours, not weeks. The audit and agreement-gathering stage is where the real time goes, usually a few working sessions with leadership. Schools using Bell Path usually finish setup in about half an hour and generate drafts in minutes. The weeks saved come from not rebuilding after a late-discovered constraint.
- Should I timetable planning time or specialists first?
- They are two sides of the same decision: a specialist teaching a class is what releases that class's teacher. Start from planning-time entitlements (what is owed), then check that your specialist program supplies enough release on the right days, and adjust the rotation until both sides balance.
- What is the most common primary timetabling mistake?
- Trusting a timetable that looks complete. The errors that damage staff trust (missed release time, part-timers rostered on days they do not work, silent room clashes) are invisible on a full grid. Checking each teacher's week before publishing is the single most valuable habit.
- Can I build a primary school timetable in Excel?
- Yes, and many schools do. The grid is the easy part. What Excel cannot do is check the result: it will not tell you a teacher is 30 minutes short of release, that a job-share handover left a class uncovered, or that the hall is double-booked on Thursday. If your school has part-timers, job-shares, or a large specialist program, the checking is where spreadsheets break down.
In Bell Path
Bell Path runs this sequence for you
Setup walks through staff, agreements, planning time, specialists, meetings and rooms in this order, then generates a checked timetable. A small school takes about two minutes to generate; a large one takes longer.
See how generation worksKeep reading
Planning time in Australian primary schools: APT, RFF, DOTT, NIT and NCT, explained.
Planning time is the weekly release from face-to-face teaching that every Australian primary teacher is entitled to. Victoria calls it APT, New South Wales RFF, Queensland NCT, Western Australia DOTT and South Australia NIT. The name changes, but the problem is the same everywhere: release time must be delivered to the minute, every week, and someone must teach the class while you do.
The pre-publish timetable checklist: what to check before staff see it.
Before staff see a new timetable, check every per-person promise (planning time to the minute, part-timer days, job-share handovers) and every structural one (rooms, meetings, duty coverage, bell times). Staff judge a timetable by the errors they find, not by the hundreds of sessions that were right. Run this checklist before publishing and the timetable stays out of the staffroom conversation.
How to change a school timetable without rebuilding the whole week.
To change a school timetable mid-year without rebuilding it, keep the published week as your baseline, change the underlying staffing fact rather than the cells, compare how much the new version moves, and publish one clearly current version. A staffing change does not have to mean a fresh timetable and another round of disruption.
School timetable generator
Bell Path builds a primary school timetable from the details you give it: staff, classes, part-time days, planning time, meetings and rooms. It then checks the result and shows you what it could and could not fit.
Primary school timetable software
Bell Path builds and checks the weekly timetable for Australian primary schools. It is for the school leader who builds the timetable, answers the questions about it, and would like fewer rewrites.