How to Make a Camp Duty Roster That Is Actually Fair
August 20, 2026
A duty roster is fair when two things are true: everyone does roughly the same number of jobs, and everyone can see the count. Rotate the six standard jobs — head cook, assistant cook, kitchen clean-up, campsite clean-up, fire, water — so that nobody draws the same job twice before the whole group has drawn it once, and post the finished grid where people can read it. Fairness that only exists in the organiser’s head is not fairness; it is a claim.
What actually causes the argument
Almost nobody at camp is trying to dodge work. The resentment comes from a different place: people can see their own jobs and cannot see anyone else’s.
If you washed up on Friday night and again on Saturday night, you know that. You do not know that the person who looks idle did the water run twice while you were in your tent. So the felt experience is “I did all the dishes” and it is sincere and it is usually wrong.
That is why the fix is arithmetic and publication rather than good intentions. A visible count converts a feeling into a fact that anyone can check in four seconds.
The six jobs, and why that set
The Scouting convention has settled on roughly the same six for decades, and it holds up outside Scouting too because it maps to the actual work of feeding a group outdoors:
| Job | What it really is | Time cost |
|---|---|---|
| Head cook | Owns the meal, decides when it is done | 45–60 min |
| Assistant cook | Chopping, fetching, watching the second pot | 30–45 min |
| Kitchen clean-up | Dishes, pots, food storage | 30–40 min |
| Campsite clean-up | Eating area, litter, tidy before dark | 15–20 min |
| Fire / stove | Fuel, lighting, keeping it going, putting it out | Spread across the day |
| Water | Hauling, filling jugs, water for washing | 20–30 min, twice |
Notice the time column. Two of these jobs are twice the work of two others. Any roster that treats “one job” as one unit is already slightly unfair, and it is fine — as long as the heavy jobs rotate too. The failure mode is when the same reliable person gets head cook every time because they are good at it.
The pairing that saves the most trouble
Put kitchen clean-up on people who did not cook that meal. It sounds obvious and it is skipped constantly, because it is easier to write “Patrol A does dinner” and let them sort it out — which in practice means the cooks stand around while one person washes forty items.
Building the rotation
The naive method is to write names down the side, meals across the top, and fill in whatever comes to mind. It produces repeats within about four cells.
The method that works is a stride offset. Order your people, order your jobs, and step through both lists at a rate that is not a multiple of either. In plain terms: instead of always moving down one person for the next job, move down by a number that does not divide evenly into your crew size. The effect is that a person’s second turn lands on a different job than their first.
If you are doing it by hand, the practical version is:
- Write the jobs across the top of the grid, one column per job.
- Write the meal slots down the side (Fri dinner, Sat breakfast, Sat lunch, Sat dinner, Sun breakfast).
- Fill the first row with names in your list order.
- For each following row, shift the whole row along by one plus one extra place.
- At the bottom, count how many times each name appears. If the gap between the busiest and the quietest person is more than one, patch it by hand.
Step 5 is the one people skip and it is the one that matters. The count is the deliverable, not the grid.
How big should the group be
Six to eight people is the number the roster wants. Below about five, the rotation runs out and people repeat jobs before the weekend is over. Above about twelve, half the group has no meaningful job on any given meal, because one stove only supports so many hands.
If you have thirty people, you do not build a thirty-person roster. You build three or four rosters, one per cooking group, and that is a large part of why the split into groups exists at all — there is more on that here.
The three rules that settle most disputes
Nobody has two jobs in the same meal slot. If a person is head cook, they are not also on water. This is the rule that gets broken when a roster is patched at the last minute after a dropout.
Everybody appears at least once by the second day. A person with no job on a weekend camp is not being spared, they are being excluded. It reads as favouritism from the outside even when it is an oversight.
The busiest and the quietest differ by at most one. Not zero — with five meals and seven people you cannot hit zero. But two or more is visible and people notice.
Handling the things that break rosters
Someone drops out on Thursday. Do not shuffle the whole grid. Reassign only that person’s cells to whoever currently has the lowest count, then re-check the totals. A full rebuild irritates everyone who had already memorised their slots.
Someone cannot do a specific job. Dietary or medical reasons for not cooking, a fear of fire, an injury. Take them out of that column entirely rather than swapping them out case by case, and let the count absorb the difference elsewhere.
Young and older members mixed. Pair rather than exempt. A twelve-year-old on assistant cook with an adult on head cook is a real job. A twelve-year-old with no jobs is the origin of a habit.
The willing volunteer. The person who offers to cook every meal is doing you a favour and undermining the roster. Let them cook twice, then hand them the water run.
Paper, spreadsheet or a tool
| Handwritten grid | Spreadsheet | A planner that counts | |
|---|---|---|---|
| Takes minutes to build | 15–20 | 30+ first time | Under a minute |
| Guarantees no repeat jobs | Only if you check | If you build formulas | Yes |
| Shows jobs-per-person totals | Count by hand | Yes | Yes, always visible |
| Survives a late dropout | Rewrite | Fiddle with ranges | Recalculates |
| Readable at camp with no signal | Yes | Print it first | Print or open offline |
The honest summary: a handwritten roster is perfectly good for one weekend with eight people. It stops being good the third time you rebuild it after a change, and it stops being good immediately at thirty people across four groups.
Frequently asked questions
How many jobs should each person get on a weekend camp? Two or three across five meal slots is normal for a group of seven or eight. What matters is not the absolute number but that the spread between the busiest and quietest person is at most one.
Should adults be on the duty roster? On a Scout camp, no — the youth run the patrol duties, and adults who take over the washing-up are removing the point of the exercise. On a family or club camp, yes, and the adults should be on it first.
What jobs go on a camp duty roster? Head cook, assistant cook, kitchen clean-up, campsite clean-up, fire or stove, and water. Some troops add a latrine or a quartermaster role. Six is enough for most weekends.
How do you stop the same person always cooking? Rotate by position rather than by volunteering. If you ask “who wants to cook”, you will get the same two hands every time, and by Sunday the other six will have learned nothing and done less.
Should the duty roster be posted at camp? Yes, on paper, at the kitchen area. A roster that lives on the organiser’s phone is a roster people have to ask about, and asking is exactly the friction that makes them stop bothering.
What do you do if someone refuses their job? Do not renegotiate the grid on the spot. Note it, let them swap with a specific named person for that slot only, and keep the totals equal. A swap is fine; a deletion is what breeds the next refusal.
The short version
Fair means counted, and counted means published. Six jobs, rotate with an offset so nobody repeats, keep the per-person totals within one of each other, and print it.
If you would rather not do the arithmetic, the free Camping Meal Planner & Grocery List builds the rotation for you — it fills the grid without repeat jobs and shows a jobs-per-person count next to every name, so the fairness is visible rather than asserted. It also scales the menu to your headcount and merges the shopping list. No account, runs in the browser.
For a whole camp with several groups, forms, gear and budget in one place, our premium apps go further.