Potluck Signup Form Template

Every potluck faces the same statistical destiny: left uncoordinated, the table converges on five potato salads, three bags of chips, and one heroic casserole. Dessert overflows, mains run out by seven, and the one vegan guest eats bread. This template is the coordination layer — a signup that claims courses, names dishes, counts servings, and tags allergens before a single oven preheats.

Why these fields. The opening question splits three ways because potlucks have three honest states: bringing a dish, bringing only an appetite, and not coming — and the form branches on the answer. Dish-bringers get the full signup: a course claim (the field that prevents the potato-salad singularity), the dish's name (labels with names and cooks credited make the table a story, and "Grandma's mac & cheese" recruits its own fans), a serves estimate that lets you sanity-check total food against total guests, and dietary tags that spare the vegetarian guest a buffet interrogation. Appetite-only guests skip everything and land on an ending that genuinely welcomes them — a good potluck needs eaters as much as cooks, and guilt is bad seasoning. Decliners exit warm in two questions. Three paths, three endings, each one honest about its answer.

What we left out. Assigned-dish signup grids ("we need three salads, sign here") — they solve balance by killing the joy, and the course-claim field achieves ninety percent of the balance with none of the homework energy. Recipe collection, which is a lovely follow-up email and a terrible pre-event required field. And exact timing questions, because potluck dishes arrive when they arrive.

Who uses this. Neighborhood block parties and building potlucks, church and community-group suppers, office lunch clubs, Friendsgiving hosts, and teams whose "bring something" email thread has failed them three years running.

Make it yours. Watch the Summary view as claims arrive — when mains run thin and desserts stack up, one message in the group chat steers the next signups. Export the CSV before the day and post the menu where guests can see it: dishes, cooks, serving counts, and tags are already in columns. Set the close date a couple of days ahead so cooks can shop, and rename the courses to fit your table — brunch potlucks swap in "egg dishes" and "pastries" beautifully.

Balance without bossiness. Nobody is assigned anything; everyone sees their claim count. That light touch is why this form fills a table evenly while the sign-up-sheet approach fills it with resentment. And if your potluck is a recurring institution — monthly suppers, annual block parties — keep the link alive between events: the dish history in your responses view becomes the group's unofficial cookbook index, and returning cooks already know the drill.