Potluck Sign Up Sheets for Large Groups of 50+

A potluck for eight sorts itself out. A potluck for 60 does not. Without structure you get 14 bags of chips, three pans of the same baked ziti, and nothing to drink. The fix is not asking people to "just bring something." It is building a sign up sheet that steers contributions before anyone commits.

Here is the actual workflow for setting one up, in the order you would do it.

Count heads first, then do the math

Start with a real number. If you are expecting 50 to 60 people, assume most eat a full plate and some eat two. A useful rule of thumb for a crowd that size: plan one serving dish for roughly every eight to ten guests per category. So for 60 people you want about six to seven mains, six to seven sides, four to five desserts, and enough drinks and supplies to cover everyone.

Write those target counts down before you touch any software. They become your slot caps later. If you skip this step, you will either over-order (a table of untouched food) or under-order (a line that runs out at plate 40).

Don't forget the boring categories. Ice, cups, serving spoons, napkins, and trash bags are the things nobody volunteers for and everybody needs. At 60 people you will go through more of all of it than you expect.

Build the categories as separate signup options

Once you have your targets, create the form. The fastest path is to describe the event in plain language and let the AI-powered signup forms build the structure for you. Type something like "Office potluck for 60 people, need 7 mains, 7 sides, 5 desserts, drinks, ice, and serving utensils," and you get a draft with the categories already laid out. Then you edit.

The key move for a large group is making each category its own set of slots with a cap, not one open text box. If you give people a single blank field, you lose all control over balance. Instead, structure it like this:

• Main dishes with 7 slots
• Sides and salads with 7 slots
• Desserts with 5 slots
• Drinks (non-alcoholic) with 4 slots
• Supplies: ice, cups, utensils, napkins with 4 slots

Each person picks a slot and writes what they are bringing in a short description field. That way you can see at a glance that you have six mains filled and one open, instead of scrolling a flat list trying to count casseroles.

You can set this up from scratch or start from one of the ready-made signup form templates and adjust the numbers. Either way, the goal is the same: the sheet reflects the math you already did.

Set quantity caps so the categories fill and lock

This is the step that separates a 60-person potluck from a 60-person pile of desserts. On a potluck signup form, you set a maximum number of slots per category. When the dessert slots hit five, the option fills and locks. The next person who opens the form sees desserts are full and picks a main or a side instead.

You are not policing anyone. The form does it. Caps turn "please don't all bring cookies" into something the sheet enforces on its own. If you have ever had to text someone back and ask them to switch their dish, you know why this matters at scale.

For anyone who shows up after every slot is taken, turn on a waitlist. People can still add themselves, and you will have backups if someone drops out the morning of. Automatic alerts when a spot opens are part of the Boost plan, but the waitlist itself keeps a running list of extras either way.

If you want more detail on preventing the all-dessert problem specifically, that is its own topic worth reading up on when you plan the categories.

Share the link and let people sign up in seconds

For a group of 50-plus, how you distribute the link matters as much as the form. Paste it into the group email, the team chat, the class thread, whatever channel people already check. No one signing up needs an account; they open the link, pick a slot, type their dish, and they are done. The form works in any phone browser, so the mobile-friendly signups handle the half of your group who will respond from their phone on a lunch break.

If part of the group is together in person, generate a QR code and post it, or print the form for the folks who prefer paper. For a recurring event, like a monthly department lunch or a seasonal gathering, save the form as a template so you are not rebuilding categories every time.

Watch the sheet and nudge the gaps

After the link goes out, check the form once a day. You are looking for one thing: which categories are lagging. If mains are full but you have only one drink and no ice signed up with three days left, send a short reminder that points at the open slots. People respond better to "we still need drinks and ice" than to a generic "don't forget to sign up."

Turn on automatic email reminders before the event so you are not chasing everyone by hand. A reminder a day or two out cuts no-shows and empty slots. On the free plan you can view up to 30 responses per form on the site, and every response is always stored; if you expect well over 30 contributors and want to see them all at once, the paid plan unlocks the full list and CSV export.

The pattern scales beyond food. The same category-plus-cap structure runs a church potluck signup for a 200-person fellowship meal or a classroom team snacks rotation. Count heads, build capped categories, share the link, watch the gaps. Do those four things and a 60-person potluck feeds everyone with food left to spare, not a table of chips.