How to Set Up a Duty Rota: Rotating Cleaning, Daily Duties and Roles Fairly

Duties cause arguments through opacity, not unfairness

Complaints about duties come less from the actual count than from the feeling that “I’m always the one doing it”. Even if it’s actually even, there’s no way to check without a record. On the other hand, people accept a slight imbalance if they can see how it came about.

• No record of who did it when, so nobody can count turns
• Swaps and substitutions are agreed verbally, and nobody keeps track
• Duties differ a lot in workload but each counts as one turn
• Nothing is decided about absences, so turns are just skipped
• Only a few people decided how it works

The fix is simple. Decide the order once, in front of everyone, put the result in a table and share it. Then rotate exactly as the table says. That alone removes almost all the back-and-forth over duties.

Fixed rotation versus drawing each time

As a rule, recurring duties suit a fixed rotation. If you draw every time, chance will inevitably make the same person come up several times in a row, and each time you’ll need to explain. The practical approach is to use a draw only to decide the starting order.

Deciding the first order and turning it into a rota

The only thing inside a rotation is the order. As long as that order is decided in a way everyone accepts, the rest can run mechanically.

1. 1

   Decide the unit and frequency

   Weekly or daily? One person or two? Decide this unit first. Once it’s set, the number of slots you need is fixed.

2. 2

   Line up the order as slots first

   In the Team Splitter, choose “Arrange slots yourself” and list numbered slots 1, 2, 3… for the number of people. The “Nos. 1–6 (order)” button creates the numbered list in one go.

3. 3

   Paste in the names

   Paste them in a non-arbitrary order such as alphabetical or class register order. If people can choose the order themselves, that becomes the point of contention.

4. 4

   Run it where everyone can see

   Share the screen, read out the statement and produce the result in one go. The result changes every time you run it, so nobody can engineer a particular order. If you want people to see the drawing itself, you can build amidakuji in the same order (numbers at the bottom, names at the top).

5. 5

   Turn it into a rota and share it

   Once you save the result to the log, the “Log & duty roster” tab can map that order onto dates. Set the start date, the interval (Daily, Weekdays only, Weekly, Every other week or Monthly) and how many people per turn, and you get a table of dates, weekdays, who’s on duty and which round it is. Only at this point is it something people can check later.

What to put on the rota

• Dates and names. A calendar layout shows the schedule well ahead
• What the task involves. Spell out what has to be done for it to count as finished
• Roughly how long it takes. Duties heavier than expected show up at this point
• A column for swaps. Note who swapped with whom
• Where each round ends. Knowing how many turns make a full cycle makes checking for imbalance easier (6 people one at a time is 6 turns; two at a time is 3)

Spelling out the task is especially effective. A duty that just says “cleaning” means different things to different people, and the more conscientious you are, the more you lose out. Write down whether it includes changing the bin bags and whether mopping the floor once a week is enough.

Decide rules for swaps and absences in advance

Rotas stop working when exceptions come up. Discussing them after they happen leads to arguments every time, so decide in advance how each likely exception will be handled.

The key is not to skip missed turns. If you skip them, the more someone is absent, the fewer duties they do. Only swap the order, and make sure every turn comes back round.

Tips for keeping it going

• Put the rota where everyone can see it. A shared file or a notice board both work
• Send a reminder the day before. Forgetting is the most common reason a turn gets missed
• Review it after each full round. You’ll find duties that are too heavy or tasks that aren’t needed
• Tick it off when done. That leaves a record of who did it
• When complaints come up, review the tasks, not the order. Usually the cause isn’t the number of turns but the difference in workload

When a rota stops working, the cause is usually on the task side. A duty anyone can finish in 15 minutes doesn’t cause arguments, but one that takes some people an hour will, however fairly you set the order. After one full round, review the tasks themselves.

FAQ

Should duties be drawn each time or follow a fixed rotation?

Recurring duties suit a fixed rotation. Drawing each time means chance will make the same person come up several times in a row, and you’ll need to explain every time. It’s practical to use a draw only for the starting order and then follow that order.

How should I handle someone who misses their turn?

The basic approach is for the next person in line to cover that turn and for the absent person to take the next one. Simply skipping the missed turn means the more someone is absent, the fewer duties they do. Only swap the order, and make sure every turn comes back round.

How do I make duties with different workloads fair?

Don’t count them as one turn each. You can count a duty that’s twice the work as two turns, or run heavy duties on a separate rotation. Writing the task and a rough time on the rota also aligns what counts as finished, which shrinks the difference in workload between people.

How should the order be decided so people accept it?

The reliable method is to draw once where everyone can see and share the result as a table. With an amidakuji maker you can line up the order (the outcome) first and add the names afterwards, so nobody can suspect you of adjusting while watching the result. Not allowing individual swaps afterwards matters just as much.