Run kitchen duty as rotating teams of 4-6 people, each led by a head cook who knows the recipes, with children over 12 helping on prep and washing. With 50-60 working adults and teams of that size, each adult’s turn comes round every 8-15 days; the parent’s target of once every 7-10 days needs teams of about 5-8, so the cycle length and team size must be set together.
A kitchen rotation system is the schedule by which a community’s adults take turns in teams on cooking, prep, serving and washing duty, together with the habits that keep the arrangement fair.
The Parent’s Numbers Do Not Quite Fit Together
The parent guide gives kitchen duty for a community of 100 as 4-6 people a day (2 cooks, 2 prep and wash, 1-2 servers), with each adult serving once every 7-10 days, teams rotating rather than individuals, one head cook per team, and children over 12 helping on prep and washing. Its demographic breakdown for 100 people includes 50-60 working adults (Caloric Budget for a Community).
Worked Example: Cycle Length
If every working adult takes duty and teams rotate, the cycle in days equals the number of adults divided by the team size.
- 50 adults ÷ 6 per team = 8.3 days; 60 ÷ 6 = 10 days.
- 50 ÷ 5 = 10 days; 60 ÷ 5 = 12 days.
- 50 ÷ 4 = 12.5 days; 60 ÷ 4 = 15 days.
- So teams of 4-6 give a cycle of 8.3-15 days, roughly 8 to 15. The parent’s 7-10 days is met only at the large end (6 per team with 50-60 adults gives 8.3-10).
- To get a 7-day cycle from 50-60 adults you would need 50 ÷ 7 = 7.1 to 60 ÷ 7 = 8.6 people a team; to get 10 days you need 5-6.
- Children over 12 who help with prep and washing reduce the adult load; the parent gives no count of them, so they are left out here. Sickness, pregnancy and the heavy-labour season will remove other adults from the pool and lengthen the real cycle (Seasonal Labor Calorie Spikes).
The practical result is that the cycle length is a decision, not a given: more people per team shortens the wait but crowds the kitchen.
What You Need
- A roster that names teams, not individuals, and is posted where everyone sees it
- A head cook for each team who knows the recipes and the safety rules
- A rule for swaps and absences, including illness
- A feedback route for complaints about food or fairness that does not depend on the cooks themselves
- A link to the community’s labour plan (Labor Rotation, Surge Labor)
Method: Build The Rotation
Step 1: Count the pool of working adults available in the current season.
Step 2: Choose a team size that the kitchen can hold, then compute the cycle (adults ÷ team size).
Step 3: Rotate teams. The parent says teams, not individuals, because cohesion improves meal quality.
Step 4: Mix skills. Put at least one experienced cook, and one person trained in the hygiene rules, in each team.
Step 5: Review at the busiest season. At planting and harvest the kitchen competes with the fields for the same adults (Harvest Labor Calendar); either lengthen the cycle or draw on older children and the elderly for light jobs.
Common Mistakes
- Rotating individuals. A new face every day means no one learns the stove.
- Leaving the head cook’s authority vague. A team without a clear lead drifts into arguments over seasoning and portions.
- Excusing some people permanently. Exemptions that look like privilege undermine the whole scheme.
- Never asking diners. Complaints that have no route become gossip.
Safety
Tired and rushed cooks are the accident risk
A short-staffed team doing a long shift, or a new cook alone at a 57 kg pot of boiling food, is how scalds and boil-overs happen. Keep every team to its full size at the stoves, put children and the inexperienced on prep and washing rather than at the pot, and keep the cooks’ hygiene rules as strict as the diners’ (Hygiene & Food Safety).
What’s Next
- Learn next: Hybrid: Communal Staples, Family Finishing — the model the rotation serves
- Combine with: Labor Allocation — fitting kitchen duty into the community’s workload