The term planner: a whole term on one page, and how to keep it true.

A term planner answers one question at a glance: what is this term's shape? Which weeks are heavy, which are clear, when the fixed events land, and where the collisions are. It spreads load and sets expectations, for the leadership team first, then for staff, and often for families.

It is not a calendar. The calendar carries times, rooms, notes and same-morning changes. The planner carries the week-by-week shape. Schools that ask one document to do both jobs end up with a planner too dense to read and a calendar too vague to run. Keep the two deliberately separate.

Before anything optional goes on the planner, place the points you cannot move: public holidays and curriculum days, reporting and assessment windows, camps already booked, swimming programs with paid bookings, transition and orientation days, whole-school events with outside parties (photo day, performances), and any system-level testing windows.

These fixed points immediately show the term's real shape: usually two or three weeks that are already heavy before a single optional event is added. Everything else gets planned around them, which is why they go on first.

The planner mistake that causes the most pain is treating events as single cells. A Year 4 camp is not three days in week 6. It is three days of camp staff missing from yard duty, specialist sessions for those classes cancelled (and the release time those sessions gave their teachers, gone), and a heavier cover load for everyone left behind.

Before placing an optional event, work out what it disturbs: who disappears, which duties and sessions collapse, what release time is lost and must be made up. Two such events in the same week is usually one too many. This is also the honest argument for keeping the planner near the timetable: the knock-on effects are invisible on a standalone document and obvious in a system that knows the week.

Some collisions are famous (assessment week landing on camp week), but most overload is quieter: three "small" events in one week, each reasonable alone, together using up every scrap of goodwill and cover capacity. The planner is where that gets caught, while whole weeks can still be compared.

Spacing rules that hold up: keep the week before reports open as clear as you can; do not put a whole-school event in the same week as a year-level camp; protect week 1 (routines) and the last week (energy) from anything optional; and leave at least one genuinely clear week per term as slack, because the term will spend it for you whether you plan it or not.

The classic failure is not a bad planner. It is four copies of a good one: the staffroom wall, the office spreadsheet, the newsletter extract, and a photo on someone's phone. They agree in week 1 and drift apart by week 4, and from then on every reader is gambling on which version they found.

Fix it with structure, not discipline: one owner who makes changes, one place staff know to check, and every other copy clearly downstream (dated printouts, newsletter extracts labelled with their week). If a change does not reach the main copy, it did not happen.

Bell Path's operations calendar holds the term's events beside the timetable they disturb, so a camp shows its knock-on effects (cover, duty, specialist sessions and release) in the same place where those get fixed. Staff see what affects them in the staff portal, and the calendar can be shared so families read the same term the office does. The printable term planner template below is the paper version of the same habit: fixed dates first, knock-on effects considered, one copy true.