How to Run a Potluck Without Ending Up With Seven Salads

Every potluck fails in one of two ways. Either nobody coordinates and eighteen people show up carrying seven variations of pasta salad, one lonely dessert, and no bread. Or somebody tries to coordinate and does it by sending "bring whatever you want!" in a group text, which produces the same seven salads plus resentment.

The fix isn't a personality change. It's category balancing, a little bit of volume math, and a sign-up mechanism that people actually look at before they leave the house. Get those three right and a twenty-person potluck runs itself. Get them wrong and the host ends up making an emergency Costco run at 5:45 while guests wander around holding foil trays.

This is a working guide, not a philosophy. If you're hosting anything from a housewarming to a Friendsgiving to a work potluck to a block party, the same rules apply.

The two failure modes, named plainly

The first failure mode is no coordination at all. The host says "just bring something!" because they don't want to be bossy. What happens: everyone independently decides that a big salad or a bag of chips is the safest low-effort choice. You get salads, chips, and one person who read the room and brought a whole brisket that becomes the meal by default. The host provides the mains that were supposed to be optional because otherwise there's no dinner.

The second failure mode is coordination without structure. Someone starts a group chat. First person says "I'll bring mac and cheese." Second person says "ooh great idea, I'll bring mac and cheese too." Now there's a running list of overlapping dishes that nobody edits, three "sorry I'll bring pretzels last minute" additions, and the host doesn't know until the day of that no one signed up for anything hot besides mac and cheese.

Both failures come from the same missing piece: categories with target counts. Once you say "we need two mains, three sides, one bread, one dessert," people fill in the slots on purpose instead of independently reinventing the same dish.

The seven-category rule

For any potluck bigger than about six people, split the meal into seven categories:

• Appetizer — something to graze on when guests first arrive
• Main — the anchor protein or carb of the meal
• Side — hot vegetables, grains, roasted things
• Salad — cold vegetable dish (this is the category that runs away with itself)
• Bread — rolls, cornbread, focaccia, garlic bread
• Dessert — the second category that runs away with itself
• Drink — non-alcoholic, alcoholic, or specifically "the ice" (which someone always has to bring)

The target is roughly one dish per category per four guests. Twenty guests? Aim for five mains, five sides, five salads, and so on — but nobody actually needs five bread dishes, so cap the volume categories (bread, dessert, drink) at two or three, and let the substantial categories (main, side, salad) scale with headcount. A working formula for twenty guests:

• Appetizer: 2
• Main: 4
• Side: 4
• Salad: 3
• Bread: 2
• Dessert: 3
• Drink: 2

That's twenty dishes for twenty guests, which sounds like a lot until you remember that everyone eats a little of everything. A potluck is a tasting menu, not seven individual dinners stacked on the same table.

For ten guests, roughly halve those numbers. For forty, roughly double, and start considering two dessert slots specifically for "one chocolate, one fruit" so you don't end up with four flourless chocolate cakes.

Volume math: how many servings is "a casserole"

The single most useful number in potluck planning: one standard 9x13 casserole feeds six to eight adults as a shared dish. Not as a main course — as a shared dish where people take a scoop alongside other things.

Working from that:

• Casserole (9x13): 6-8 shared servings
• Full sheet pan: 12-15 shared servings
• Half sheet pan: 6-8 shared servings
• Bag salad, dressed: 4-6 shared servings
• Family-size bag of chips: 8-10 servings
• Loaf of bread: 8-10 slices
• Pie: 8 slices
• 9x13 sheet cake: 12-15 slices
• Bottle of wine: 5 pours
• Standard soda bottle (2L): 8 servings

For a twenty-guest potluck this means you actually need something like three casseroles' worth of main-ish food across your four main slots, three or four sides worth of vegetable across your side slots, and three desserts is exactly right for twenty people (twenty-four to thirty-six slices, of which people will eat two apiece with abandon).

The classic under-catering mistake is treating "I'll bring a dish" as automatically portioned for the room. A single lasagna at a party of twenty is not a main course — it's one component of a main course. This is what the category counts are correcting for.

Sign-up systems that actually work

There are exactly three sign-up systems that survive contact with real guests. Everything else is a variation of one of these.

The shared spreadsheet

A Google Sheet with columns for name, dish, category, serves, and contains (for allergens). Row per person. Everyone edits their own row. The host pre-fills the target counts per category at the top of the sheet so people can see at a glance what's already full.

Pros: real-time, everyone sees everything, edits are visible.

Cons: some guests will not open a Google Sheet no matter how you frame it. Assume 25% of your invitees will need to be personally texted with "I signed you up for a bread — is a baguette ok?"

The physical clipboard at the last event

If the potluck is a recurring thing — book club, D&D group, monthly Friendsgiving — pass around a clipboard at this month's potluck with the categories for next month's. People sign up in person while they're already thinking about food. This has the highest completion rate of any method (nobody wants to be the one leaving a slot blank while the group watches), but obviously only works if you already have the group together.

A structured sign-up generator

For a one-off potluck with people who aren't all in the same group chat, use the potluck assignment generator. You enter the guest list and it distributes assignments across the seven categories with the right per-guest counts. Guests get a specific "you're on sides" or "you're on dessert" answer instead of a blank prompt to invent one. This is the difference between "bring what you want" (seven salads) and "bring a side dish that serves 6" (an actual side dish that serves six).

The pattern to avoid: a group text where signups happen in the chat scroll. Third person up can't see what first person committed to, tenth person up definitely can't, and by the eighteenth person there's a running joke about how many salads there are going to be, and then eighteen people show up with salads.

Diet and allergen safety: the label rule

The single hosting rule that changes a potluck from stressful to easy for people with allergies or restrictions: every dish gets a card that lists what it contains.

Not "gluten free" (nobody trusts that from a stranger's kitchen). Instead, the honest positive form:

> Pesto pasta salad — contains: wheat, dairy, pine nuts, garlic

Guests with restrictions read the ingredient list and decide for themselves. It takes fifteen seconds to write and means the person with a dairy allergy doesn't have to interrogate every dish or, worse, skip half the meal.

Ask contributors to write their own card when they arrive (have index cards and a Sharpie on the table). If you're pre-printing labels from the sign-up sheet, the sign-up sheet's contains column feeds directly into them.

The five biggest allergens to always label if present are dairy, gluten (wheat), eggs, nuts (specify tree nuts vs peanuts), and shellfish. Sesame is now considered a major allergen too in the US. Soy is worth calling out. And if a dish is vegan or vegetarian by design, say so on the same card — vegetarian guests do the same math from the other direction.

Note that "contains" is honest in a way "gluten-free" isn't. A home kitchen almost certainly can't guarantee no cross-contact with wheat if there's any wheat in the house. Saying "no wheat ingredients" is accurate. "Gluten-free" implies a controlled kitchen you don't have.

The bringing rules (how to be a good guest)

If you're not hosting, you're bringing. There are five rules that make you the kind of guest the host wants back:

1. Bring it in a container you don't need back. The most durable friction at any potluck is Tupperware retrieval three weeks later. Foil pans, disposable trays, and thrift-store platters solve this. If you must bring the good ceramic, put your name on the bottom with masking tape and take it home with you before you leave.

2. Label your dish and your container. Your name, your dish name, ingredients (see above). A piece of masking tape on the bottom of the dish saves the host from playing "whose is this" during cleanup.

3. Carpool the hot food. If you're bringing something that needs to be served warm and you live twenty minutes away, coordinate with someone closer to the host, or bring it cold with reheating instructions ("400 for 15 min, then broil 2 min for the top"). Nobody's oven is available at 6:30 for a stranger's casserole; the ovens are all full of the host's food.

4. Bring your own serving utensil. Even if the host is providing utensils, they're providing one per position on the table, and if you're arriving with something new they can't magic another spoon into existence. Slip a serving spoon into your bag.

5. Show up with the thing you signed up for. Not something adjacent. If you signed up for a salad and you decide en route to bring pretzels instead, you have destabilized someone else's plan for the meal. If you genuinely can't do the thing, text the host as far in advance as you can and let them re-slot.

Use the generator: the actual assignment step

Once you have a guest list and a headcount, the mechanical work of distributing assignments across categories is exactly the kind of thing worth automating. The potluck assignment generator takes a list of names, applies the seven-category rule with the right per-guest counts, and gives you a copy-paste sign-up sheet where every guest has a specific category (not a specific dish — that they still get to pick, within their category).

Use it once to seed the plan, then either drop the output into a shared sheet for people to edit, or send individual "you're on desserts" messages. The generator handles the ratios; you handle the humans.

If your potluck doubles as another kind of coordinated event — say, a housemate holiday dinner with rotating cooking duties beyond that one meal — the duty roster generator covers the recurring-chores side of the same problem (who's on cleanup, who's on drinks, who's setting up). For a gift exchange after dinner, the random gift picker does the Secret Santa draw. And if the group needs help getting a conversation going at the table, the random conversation starter has prompts that work better than "so, how's work."

FAQ

What if I'm hosting and I want to make one big thing myself?

Do it, and remove that category from the sign-up. If you're making the mains — a ham, a big pot of chili, a paella — tell guests "I've got the main covered, please sign up for sides, salads, breads, and desserts." This is actually the easiest hosting mode: you cook the anchor, guests fill in around it. It also means nobody has to negotiate about who's bringing the "real" food.

How much lead time do I need to send the sign-up?

Two weeks for a big potluck (fifteen or more people), one week for a smaller one. Less than five days and you'll get a lot of "I'll bring chips" because that's what people can get on the way. If you're sending less than five days out, pre-assign categories rather than asking people to pick — they're more likely to actually cook something specific if you told them "we need a hot side" than if you asked them to browse the categories.

Can I really tell people what category to bring? Isn't that pushy?

It's less pushy than the alternative, which is a meal that doesn't work and a host who's stressed. Frame it plainly: "To keep us from ending up with all salads, I'm splitting the meal into categories. You're on desserts — bring whatever dessert you like." Almost everyone prefers a constraint. The "bring whatever" prompt is the actual burden.

What about drinks — how much alcohol is the right amount?

The bar-industry rule of thumb is two drinks per adult for the first hour, one per hour after that, and about 40% of pours will be non-alcoholic if you provide non-alcoholic options that aren't just "water." A four-hour potluck for twenty adults with alcohol as an option is roughly 60-70 drinks total, split between wine, beer, and non-alcoholic. Nobody has to bring all of it — spread it across three or four drink-category slots.

Someone dropped out and their category is empty — do I stress?

No. If a main dropped out, ask two side people to double their portions, or reheat something from the host's freezer, or order a pizza when guests are already there and lean into it. Missing one dish out of twenty doesn't break a potluck. Missing four does. The category system is exactly what tells you which situation you're in.

Do I clean up as I go or wait?

Clear used serving dishes as they empty, but leave the food out for a full second pass. Most potluck attendees eat twice — once when they arrive and again forty-five minutes in when they've talked to a few people. Pulling the food after the first wave is the fastest way to make people leave.

The rest is cooking. Get the categories right, get the numbers right, get the labels on the table, and a room full of people eating each other's food takes care of itself.