Published: October 9, 2026 / Last updated: October 13, 2026
A stall shift table needs more than a list of who works when. Cooking, cashier and calling out all run in parallel, so you have to set a headcount for each role. And customers are not spread evenly across the day, so if every slot has the same headcount, the peak doesn't get handled and quiet periods have too many people.
Decide roles and headcounts as pairs: 2 cooking, 1 cashier, 1 calling out. If you only list numbers without roles, nobody knows on the day who does what, and that gets argued out on the spot.
Cooking, cashier, calling out, serving, prep, and setup and cleanup are the usual split. It varies with the stall, so write down the jobs your stall actually has and group them into roles. If you split too finely you end up with roles of one person each, so as a rule make only the jobs that run at the same time into separate roles.
Some people can't do certain roles. Someone can't cook, someone is bad at calling out. If you don't ask this when collecting answers, you end up swapping people after the assignment. Jobs with fire or knives may be limited to experienced people or those who were put in charge, so count first how many people can go into them.
First split the opening hours into the peak and the rest. At the peak, put people on cooking, cashier and calling out. When it's quiet, have people cover cooking and cashier together and cut the headcount. If you know how the previous year went, use that. If you don't, put more people right at opening and at lunchtime and adjust on the day.
For example, three on cooking and two on cashier for the two hours around noon, and one each in mid-afternoon. In Shiftto the required headcount can differ per slot and per role, so you can enter that as it is.
Enter the number below which it doesn't work, not the number that would be nice to have. If you enter the ideal, nearly every slot shows as short and you can't tell which ones are truly in danger. If you have room, you can add people by hand on the day.
The time before and after opening is easy to forget. Prep, setup, getting ready to open, and cleanup and dishes after closing can need more hands than the open hours. If you only make slots for the open hours, nobody is there right before opening and cleanup gets pushed onto a few people.
You can also make cleanup something everyone takes part in. If you ask for availability for individual cleanup slots, you may end up with nobody for the last slot. Even then, write the end time in the table.
For long opening hours, put break slots in the table. If breaks are left to each person, someone ends up resting at the peak or nobody gets a break. The same goes for time to see other exhibits: make it a slot, and less resentment is left afterward.
Stagger breaks so that half the people rest at a time. If everyone rests together the stall stops, so make sure someone stays on each role. This is easy to miss by hand, so look at the finished table and check that no role drops to zero during break times.
Ask about conflicts first. People with another exhibit, a performance or a club tournament find it hard to bring it up later.
Leave people time to walk around the festival, too. If some people ran the stall all day and others played all day, resentment stays even when the stall went well.
Imbalance in the number of shifts causes the most complaints. Someone may also be absent on the day, so keep the table editable.
Paper and spreadsheets are the easiest place to start. But copying answers into a table and checking the required headcount become more of a burden as the group grows.
The organizer enters dates, slots, roles and headcounts and shares a URL, and participants answer ○△×. From the collected availability, it builds a table that meets each role's required headcount. No sign-up, free, and the table can be printed or exported as CSV.
Collect availability and build the shifts automatically
No sign-up or login. Free, and ready in 5 minutes.
Create a shift