The Sunday dinner had sixty people and eleven desserts. Two green bean dishes, one of them a casserole. Nobody planned it that way. The sheet said "bring a dish to share," and everyone brought the dish they like to make.
A potluck sheet is a menu with names next to it. Get the categories and the counts right and the food takes care of itself. Here is how to build one, whether it is the church fellowship hall, the family Christmas party, a pool party or the teacher inservice breakfast.
Categories with counts, not an open list
The open list is the problem. "What are you bringing?" with a blank line under it produces dessert. Decide the shape of the menu first, then let people fill it in:
- Main dish (serves 12): 6 people
- Side dish or salad (serves 12): 8 people
- Bread or rolls: 3
- Dessert: 5
- Drinks (lemonade, tea, water): 3
- Plates, cups, napkins, forks: 1
That is for about sixty people. When "dessert" fills at five, the sixth person sees only what is still open and brings a salad. That is the whole trick. Counts do the work you would otherwise do by phone.
More sides than mains is deliberate. People eat a little of everything at a potluck, and sides are what runs out.
How much food
Ask every dish to serve twelve. For a group of sixty, plan about twenty dishes across mains, sides and desserts, plus bread and drinks. It sounds like too little and it is not; people take smaller portions when there are twenty things to try.
For a smaller gathering, scale the counts, not the serving size. A family Christmas with 25 people is two mains, four sides, two desserts, one bread, one drinks. The pool party for fifteen is one main (someone is doing burgers), three sides, two desserts, chips, drinks and ice. Ice is its own row. Someone always forgets ice.
Ask what they're bringing
Add one text question at signup: "What are you bringing?" You will see the actual menu before the day, and if four people wrote "deviled eggs" you can gently ask one to switch. Without it, you know you have eight sides and nothing else.
Two more rows worth adding near the top, guaranteed rather than hoped for: a vegetarian main and a gluten-free side. And ask bringers to put an ingredient card next to their dish. It takes a minute and someone will be grateful.
The rows everyone forgets
Food is the part people volunteer for. The rest is the part that falls on whoever booked the room.
- Setup, 45 minutes before: 2 people. Tables, chairs, the coffee pot, the serving line in a sensible order (plates first, dessert last).
- Cleanup and dishes: 3 people. Wash the serving dishes, take out the trash, wipe the tables, get the leftovers to whoever wants them.
Put those rows on the same page as the food. On a separate sheet they never get filled. On the page, right under "dessert", a few people take them, especially when the description says how long it actually takes ("about 30 minutes after the last plate").
One tip for the cleanup crew: ask everyone to bring their dish in a container with a serving spoon and their name on tape underneath. The dishes get home.
The teacher breakfast is a potluck too
A teacher inservice breakfast or an appreciation lunch is the same sheet with a different menu. Break the meal into components with counts: breakfast casserole for 40 (2 people), fruit (2), muffins or pastries (2), juice (1), coffee and cups (1), paper goods (1), setup at 7:15 (2), cleanup at 9:00 (2). A row that just says "breakfast" never tells you what is missing. Component rows do.
The same goes for a taco lunch: meat for 40, cheese, tortillas, salsa and chips, drinks, each its own row with a count. When every row fills, the lunch is covered.
Timing
Post the sheet two to three weeks out. Long enough for people to plan a grocery trip, short enough that it is not forgotten. Send it once to everyone. A week before, send a second note to whoever has not signed up, listing only the open rows: "we still need two sides and someone on drinks." Short lists get filled.
The day before, everyone who signed up should get a reminder that says what they are bringing. That is the difference between a dish that was signed up for and a dish that shows up.
The mistakes
One line that says "dish to share." You get dessert.
Collecting names on paper in the hallway. The sheet is in the church office by Wednesday, and the people who would sign up on Thursday never see it. Online, one link in the bulletin or the family group chat, and it fills from wherever people are.
Signing up through the group chat. Fourteen messages that say "I'll bring rolls" scroll away. Nobody knows what is covered.
Forgetting the drinks and the paper goods. Someone has to bring cups. Make it a row.
No reminder. The signup was three weeks ago. Life happened in between.
On JustSignup
The potluck signup page starts with the rows above: mains, sides, bread, dessert, drinks, paper goods, setup and cleanup, each with a count you can change. Add the "what are you bringing?" question, put the date and the room at the top, and share one link. People tap a row, enter a name and email, say what they are bringing, and they are done. No account.
Everyone gets a confirmation with a link to change their dish or drop out, and a reminder the day before. When "sides" fills, the next person sees only what is open. If you are short a week out, the dashboard copies a message that lists only the empty rows.
One live page is free, with up to 30 volunteers and no ads, which covers most potlucks. If you run the church dinner every month and want several pages live at once, Pro is $9 a month or $79 a year.
Start the page at justsignup.io/new, pick the potluck template, and put counts on it. Eleven desserts is a sheet problem, not a people problem.