How to change a school timetable without rebuilding the whole week.

A teacher changes days, goes on leave, takes a new role, or is replaced mid-year. The visible problem might be one empty class or one specialist rotation, but the timetable around it is already doing hundreds of useful things. Staff know their release times, teams have settled into meeting windows, and families may have organised around part-time patterns. Treat that working week as an asset.

Write down the new fact precisely before moving anything. Which person changed? From what date? Which days, sessions, classes, duties, meetings, or rooms are affected? A clear change statement keeps one staffing event from becoming an accidental redesign of the whole school week.

Do not edit the only published copy. Save the current timetable as a named version and create the replacement beside it. That gives you a reliable before-and-after comparison, a way back if the new arrangement is rejected, and a clear record of what staff were following on any date.

This matters most when the change is urgent. Under pressure, it is tempting to fix the visible cells in the PDF or spreadsheet and keep going. The result is usually two partly current versions and no trustworthy answer when somebody asks which one applies on Monday.

Update the source facts first: availability, employment fraction, role, class allocation, specialist load, fixed meetings, and any negotiated arrangement. Then regenerate or make a targeted repair from those facts. If you only drag sessions away from the obvious clash, the timetable may look fixed while its underlying model still says the old staffing arrangement is true.

Keep the smallest possible scope. A Thursday-only availability change should not quietly reopen Monday to Wednesday. Lock or preserve the parts of the week that still work, then let the affected area move enough to become valid again.

A technically valid timetable can still be the wrong mid-year answer if it moves half the school. Compare the candidate against the published baseline: how many teachers, classes, specialist sessions, planning-time blocks, rooms, and duties changed? The count makes disruption visible before staff experience it.

Prefer the valid version that protects the most settled patterns, even if a completely fresh solve looks tidier. Mid-year, familiarity has operational value. A marginally neater grid is rarely worth dozens of changed routines.

A local staffing change can create distant consequences. Recheck every teacher's planning-time delivery, part-timer days, job-share handovers, specialist coverage, meetings, rooms, and duties before publishing. Do not assume that an untouched-looking row is unaffected.

Give the candidate a second pair of eyes. The person who made the change knows what they intended and is therefore the least likely to notice an assumption that remained wrong. A short review of the affected teacher and class views is cheaper than a correction after staff have started following the new week.

Name the new version, give it an effective date, and make the previous version visibly superseded. Tell the directly affected people what changed and why, then point everyone to the same current source. If printed packs are part of school life, replace them deliberately rather than hoping the old copy disappears from the staffroom wall.

The message should be specific enough to act on: which version applies, from which date, who is affected, and where the current teacher, class, room, and duty views live. Staff do not need the whole solving history, but they do need certainty about Monday morning.

If only one person knows why the timetable works, every staffing change is also a key-person risk. Keep the constraints, versions, decisions, and trade-offs with the timetable rather than across one person's memory, inbox, and private spreadsheet. The goal is not documentation for its own sake. It is that another leader can make the next change without reconstructing the school from hallway conversations.

A durable record also makes staff conversations fairer. When somebody asks why their release moved, the answer can point to the changed staffing fact and the alternatives considered, not to a vague memory of what seemed possible at the time.

In Bell Path, the planner updates the relevant staff or class detail, runs Final Check, and generates a new version while asking the solver to stay close to the accepted timetable. The previous version remains intact for comparison. Before the replacement goes live, the planner can inspect the changed teacher, class, room, planning-time, and duty views, then publish one new current version for staff.