Skip to main content
All guides

Guide

The yard duty roster: fair, covered, and out of the staffroom conversation.

Nobody notices a good duty roster. Everybody notices an unfair one. This guide covers coverage, fairness accounting, part-timer loading, and the wet-day plan — the four things that decide whether your roster survives the term.

Updated 8 July 20269 min read

Key takeaways

  • A duty roster has two jobs: every zone covered every break (safety), and the load spread fairly across the term (trust). Most rosters fail the second job.
  • Fairness must be measured across the whole term, not eyeballed week by week — and it must count duties actually done, including swaps and cover.
  • Part-timers need pro-rata duty loads on their actual days; fixed recurring duties and role-based exemptions need explicit rules, not folklore.
  • The wet day plan is part of the roster, not a separate document — outdoor zones must map to indoor supervision before the rain arrives.

What a duty roster is actually for

Yard duty — playground duty in NSW — is a child-safety system first and a workload-distribution system second. The first job is absolute: every zone covered, every break, every day, including the oval nobody can see from the office and the ten minutes before the first bell. The second job is what determines whether the roster generates grievances: staff notice unfairness with forensic precision.

Design for both from the start. A roster that achieves coverage by quietly overloading the same six agreeable people is not a roster — it is a slow leak in staff goodwill that presents, months later, as "morale".

Map the zones and breaks before the names

Start from supervision requirements, not staff availability: which areas need eyes during which windows, at what ratio, given your grounds and your students. Before-school, recess, lunch (often split into eating and play), after-school, and bus duty each have their own shape. Some zones need two adults; some need an adult with specific first-aid or fixed-equipment knowledge.

Write the zone map down formally. When a duty is missed, "I did not know the far oval was mine" is a systems failure, not a person failure — and it is preventable with an unambiguous map, clear handover times, and duties printed on each teacher's own timetable rather than on a laminated sheet in the staffroom.

Fairness is arithmetic, not perception

The only defensible fairness measure is a running count per person across the term: duties assigned, duties actually done, duties absorbed from other people's absences. Week-by-week eyeballing systematically hides imbalance, because the person who "just this once" covered a Friday lunch duty four separate times looks fine on any single week's view.

Set the loading rules explicitly and publish them: how full-time load is calculated, how part-time load is pro-rated, which roles carry reduced or zero load (principal class, staff with negotiated arrangements), and how time-of-week desirability is balanced — Friday afternoon duty and Monday-before-school duty are not the same duty, and staff know it.

Then track against the rules. When someone claims the roster is unfair, the answer should be a ledger you can show, whichever way the conversation is about to go.

Part-timers, fixed duties, and the exemption folklore

Part-time staff take pro-rata duty on the days they actually attend — which sounds obvious until the roster generator (human or software) spreads duties evenly across a week that includes their days off. Their available days then carry proportionally more duty, which is correct, and worth explaining before someone reads their Tuesday as punishment.

Fixed recurring duties — the teacher who always takes the bus gate because they park there, the assistant principal who covers the front office window — are fine, but they need to be recorded as fixed and counted in that person's load. The same goes for exemptions. Every school has exemption folklore; the roster only stays defensible when the folklore is converted into written rules that a new daily organiser can apply without a séance.

The wet day plan is part of the roster

Rain converts an outdoor supervision problem into an indoor one with completely different geometry: classrooms and corridors instead of zones, different ratios, different sight-lines. If the wet-day version of the roster is improvised at 12:40 under a grey sky, the same reliable people get grabbed every time — unfairness again, now with added chaos.

Build the wet-day mapping in advance: each outdoor duty converts to a defined indoor supervision post, and the conversion is one decision ("wet day timetable is on"), not forty. The fairness ledger should keep counting through wet days — indoor duty is still duty.

Absences: the roster's daily stress test

Every staff absence potentially breaks the duty roster, and this is where rosters quietly rot: the absent teacher's duty gets handed to whoever is standing nearest, the swap is never recorded, and by week eight the official roster and reality have diverged.

Duty reallocation belongs inside the same morning workflow as class cover, not as an afterthought. When cover is arranged for an absent teacher, their duties should surface in the same view, get reassigned deliberately — ideally to whoever is furthest under their fair-share line — and get recorded so the ledger stays true.

How Bell Path handles it

Bell Path generates yard duty rosters from your real zone map and bell times, with a year-to-date fairness ledger per staff member, pro-rata handling for part-timers, explicit fixed-duty and exemption rules, and lunchtime club commitments respected. Wet day plans convert outdoor posts to indoor supervision in the same screen, and daily cover reallocates an absent teacher's duties alongside their classes — so the roster on the wall and the roster in reality stay the same document.

Common questions

How do you make a yard duty roster fair?
Define the loading rules explicitly (full-time load, pro-rata for part-timers, role-based reductions), balance desirable and undesirable slots, and keep a running per-person count across the term of duties assigned and actually done — including swaps and absence cover. Fairness that is not counted is not fairness; it is luck.
Should part-time teachers do yard duty?
Yes, pro-rata, on the days they attend. The subtlety is that their duty concentrates on fewer days, so their rostered days can look heavier than a full-timer's — that is correct and worth explaining proactively.
What happens to yard duty when a teacher is absent?
Their duties need explicit reassignment as part of the same morning process that arranges class cover — recorded, and ideally directed to staff furthest under their fair-share line. Informal "can you just grab the oval" handoffs are how rosters and reality diverge.
Is a yard duty roster template enough?
A template solves week one. It does not track fairness across a term, absorb absences, handle part-timer pro-rata, or convert to a wet-day plan. Schools with simple grounds and stable staffing can run on a template; schools with real complexity end up wanting the roster connected to the timetable and daily cover.

Free resources

From the Bell Path workspace

A duty roster with a memory

Bell Path rosters yard duty with a year-to-date fairness ledger, wet-day conversion, and absence handling built into the same morning workflow as daily cover.

See yard duty rostering

Keep reading

Yard Duty Rosters That Staff Trust: A Planning Guide | Bell Path