Every duty schedule looks solid on the spreadsheet in August: recess, hallway, bus loop, cafeteria, all covered, every teacher's name in a slot. Then someone's out sick on a Tuesday, two people quietly swap without telling anyone, and by November the schedule taped in the staff lounge doesn't match who's actually standing outside at recess. Kids notice the gap before any adult does.
A duty schedule that survives the year needs a coverage plan built in, not just a list of names and time slots.
Build the swap system before you need it
Most duty schedules fail at the same point: someone's absent, and there's no clear process for who covers, so it either doesn't get covered or two well-meaning teachers both show up while a third spot sits empty.
- Assign each duty slot a *first backup* by name, decided in August, not scrambled in the moment.
- Post the swap rule once, clearly: who initiates a swap, how it gets confirmed, and where it gets logged so the office knows who's actually where.
- Build in an "if nobody's available" fallback — even something as simple as which administrator gets a text when a slot is genuinely uncovered.
The goal isn't a schedule with zero gaps ever. It's a schedule where a gap has an obvious, pre-agreed next step instead of a group text scramble five minutes before the bell.
Building the actual schedule without a full afternoon in a spreadsheet
Once you know your staff list, your duty slots, and any constraints (contract limits, part-time schedules, who can't do a second-floor duty), building a fair rotation by hand is tedious and easy to get subtly wrong.
Try this:
- "Here's my staff list with their contract duty minutes and any constraints: [paste it]. Here are my duty slots for the week: [list them]. Build a fair rotation that distributes duties evenly and respects the constraints."
- "Generate a one-page version of this schedule formatted for the staff lounge wall, plus a version with backup names listed next to each primary duty."
Our [classroom management tool](/classroom-management) can help you draft the specific expectations for each duty post — what "covering the bus loop" actually means moment to moment — so a new or substitute staff member covering a duty they've never done isn't guessing. And if you're training new staff on duty procedures as part of a broader onboarding packet, our [training manual tool](/training-manual) turns the whole set of procedures into one document you only have to write once.
What still needs your judgment
- Fairness over time, not just on paper. A rotation that looks even in August can feel uneven by spring if the same few duties always land on the same people during hard weeks — check in with your staff, not just the schedule.
- What actually counts as an emergency swap. Decide in advance what's worth pulling an administrator in for versus what two teachers can handle between themselves.
- Updating the posted copy. A schedule that changes but never gets reprinted is worse than no schedule — build in a habit of refreshing the wall copy whenever a swap becomes permanent.
