Someone always ends up taking the 8am Monday slot, the thankless note-taking, or the holiday on-call. Usually it is whoever volunteers first or complains least. A rota built on rotation โ or on chance โ removes the resentment and spreads the load evenly.
Rotation versus random
- Rotation is predictable: A, then B, then C, repeat. Best for recurring duties like standup facilitation or note-taking, because everyone can see their turn coming.
- Random selection is unpredictable and unbiased, good for one-off slots or when a strict order would feel mechanical. It also stops anyone gaming the sequence.
- A hybrid works well: rotate for the core schedule, and use a random picker to break ties or fill last-minute gaps.
A simple method
- List everyone who shares the duty.
- List the slots that need filling (days, times, or tasks).
- Assign by rotation or generate a random order.
- Publish the rota where everyone can see it.
- Re-generate or advance the rotation each cycle so it stays even.
Keeping it fair over time
Fairness is about the long run, not any single week. Track who has taken the bad slots and make sure the undesirable ones โ early mornings, weekends, holidays โ rotate too, rather than silently sticking to the same person. A visible rota makes imbalance obvious before it becomes a grievance.
Handle the human bits explicitly
- Let people swap directly, as long as the swap is recorded.
- Exclude anyone on leave before generating.
- Cap how often one person can be picked in a row.
- Give notice โ nobody likes discovering they are on-call the night before.
Where this applies beyond work
The same logic covers household chores, sports-team captaincy, volunteer shifts, and carpool schedules โ anywhere a shared, unpopular duty needs to be distributed without an argument.