How to Collect Potluck RSVPs and Dishes in One Link

You texted the group chat asking who is coming. Then you started a second thread asking who brings what. Now you have two incomplete lists, three people who said "maybe," and no idea whether you will end up with six desserts and zero main dishes. That split is the whole problem. Headcount and dishes are the same decision, and they belong on the same link.

Here is how to build one sheet that captures both, so a 30-person Thanksgiving potluck ends up with the right number of turkeys and enough sides to go around.

Decide your categories before you build anything

Start with portions, not politeness. A single open text box that says "what are you bringing" gives you a pile of brownies and no green beans. Instead, split the meal into categories with target counts.

For 30 people, a workable split looks like this: 2 main dishes, 6 sides, 3 salads, 4 desserts, 2 bread or rolls, and 3 people on drinks and ice. Add one slot for plates, cups, and utensils, because someone always forgets that until the morning of.

Write those numbers down first. They become the capacity limits you set on each option, and they are what stop the sheet from filling with nine desserts. If you want the reasoning behind quota splits in more detail, the related breakdown on balancing a menu with category quotas covers it.

Build the sheet so both answers come from one form

Open a blank potluck signup and treat each dish category as an option with a slot limit. Set the main dishes to a maximum of 2, sides to 6, desserts to 4, and so on. When a category fills, it locks automatically, so the seventh person who wanted to bring brownies sees it is full and picks bread instead. That single behavior is what keeps the menu balanced without you policing it.

Now add the RSVP piece to the same form. Include a short field for number of guests, so one person bringing a partner and two kids counts as four heads, not one. That turns your dish sheet into a live headcount at the same time. No second thread.

If you would rather not build the fields by hand, describe the event in plain language and let the AI-powered signup forms draft the structure in seconds. Type something like "Thanksgiving potluck for 30, categories for mains, sides, salads, desserts, bread, drinks, and supplies, plus a guest count." You edit from there. Forms stay editable after creation, so adjusting a slot limit the night before is one click.

Everything runs on a free potluck sign up sheet online with no ads and no login required to build it. People who sign up never make an account either. They open the link, pick a slot, and type their name.

Add the two fields that actually prevent chaos

Two small additions do most of the work on the day.

First, add an allergy or ingredient note field to each dish entry. A person bringing a casserole can flag that it has nuts, which matters if a kid at the table is allergic. This is the difference between a buffet people trust and one where half the guests quietly skip three dishes.

Second, turn on the public response summary so everyone can see what is already claimed. When a guest opens the link and sees four desserts are taken but mains are still open, they self-correct. The summary also doubles as the running menu, so nobody has to ask you "what should I bring" on the phone.

If you expect more offers than slots, a waitlist catches the overflow instead of turning people away. Someone who wanted a main-dish slot gets added, and if a cook drops out, the spot is there.

Share the link where people already are

Drop the link in the group chat, the email invite, or the class newsletter. On a phone it opens in the browser with nothing to download, because these are mobile-friendly signups by default. If you are collecting RSVPs at a church lobby or a school pickup line, print the QR code and tape it to a sign so people can scan and sign up on the spot.

Then let the automatic emails do the follow-up. You get a notification each time someone signs up, so the list builds while you do other things. Set an automatic email reminder a day or two before the event, which cuts the number of people who forget their dish. On the Boost plan you can also send SMS reminders, though those are US only and email covers everyone.

Read the sheet to plan portions, not guess them

Two days out, open the form and read it like an inventory sheet. Add up the guest-count field for your real headcount. Then scan the categories against your targets.

Short on mains with 28 people coming? Message the three people on drinks and ask one to add a protein, or buy a tray yourself. Six desserts and only two sides? Nudge a couple of the dessert folks toward vegetables. Because the RSVP numbers and the dish list live in the same place, you are making one adjustment instead of reconciling two spreadsheets.

On the free plan you can view up to 30 responses per form on the site, which covers most potlucks outright. If you run a larger church gathering, a church potluck signup scaled past that is where viewing all responses and CSV export on the paid plan start to pay off.

After the event, save the form as a reusable template. Next holiday you duplicate it, reset the dates, and send the same tested online signup sheet in under a minute. The hard part, deciding the categories and limits, is already done.

Start your potluck sheet now, set the slot limits to match your headcount, and send one link instead of two threads.