There are two failed potlucks, and I've hosted both. The first is the anarchy potluck: "bring anything!" produces nine desserts, four bags of chips, and a single tray of deviled eggs that gets stripped like a car in a bad neighborhood. The second failure is rarer but worse: the controlled potluck, where the host assigns specific recipes to specific people — and the group chat goes quiet, two people suddenly "might have a thing that day," and somebody's aunt is still mad about being assigned "store-bought rolls" in 2019. I am not exaggerating about the aunt.
Between anarchy and tyranny there's a band of structure where potlucks actually work, and after a decade of church potlucks, office spreads, block parties, and book clubs, I can tell you the band is wider than the anarchy people think and narrower than the spreadsheet people (me, formerly) want it to be. The trick is matching the format to the group — because the same structure that saves a 20-person block party insults a 6-person book club.
The four formats
Format 1: No assignments (the true potluck). Everyone brings whatever. This works — genuinely — in exactly one situation: a recurring group with more than a dozen members and its own food culture. A monthly church potluck self-balances over time because Doris always brings the broccoli casserole and everyone knows it. History is the coordinator. If your event is a one-off, you don't have history, and anarchy gives you the nine-dessert table.
Format 2: Category claims. The host posts a menu of categories — mains, starches, vegetables, desserts, drinks — sized to the guest count, and people claim a slot and cook whatever they want inside it. This is the workhorse. It's the same engine as my Friendsgiving assignments method, minus the turkey politics, and it fits almost every one-off gathering of 8 to 30 people. The host's authority stops at the category line, which is exactly where resentment starts.
Format 3: The theme. "Everything has to be a dip." "Dishes from a place you've lived." "State-fair food." A theme replaces assignments entirely — duplication stops mattering (a table of eight competing chilis is a cook-off, not a failure) and the theme does the marketing for you; people show up curious. Best for groups that like each other but don't cook seriously, because a theme lowers the stakes of any single dish.
Format 4: Host-cooks-the-anchor. The host makes the main — a couple of pork shoulders, a giant pot of gumbo — and the potluck fills in around it. This is the most reliable format per dollar of host money and my pick for anything important enough that failure stings. The anchor guarantees dinner exists; everything guests bring is upside. It's also the only format where the host spends real money, so here's what mine costs:
Anchor Math — Pulled Pork for 24
- Pork shoulder, 2 x 8 lb bone-in @ ~$2.50/lb$40.00
- Rub, mustard, foil (pantry-adjacent)$4.50
- Buns, 4 dozen$14.00
- Sauce, 2 bottles + 1 doctored$9.00
- Slaw mix + dressing (the one side I guarantee)$11.00
- Plates, napkins, serving spoons for the whole table$12.00
- Host total$90.50
Under $4 a head to anchor a 24-person dinner, priced from Texas grocery ads this summer — shoulder floats $1.79–2.99/lb, so watch the weekly flyer. Guests cover everything else.
Sizing the board (the math hosts skip)
Category claims fail when the board itself is wrong — twelve slots for twelve guests sounds fair and produces a wall of food nobody can finish. Potluck dishes arrive in batch sizes (a casserole feeds 8–10 regardless of who carries it), so the board needs far fewer slots than guests. My ratios, tuned against the leftover bags I've sent home for years:
| Guest count | Mains/anchors | Starches | Veg/salads | Desserts | Non-cooking slots |
|---|---|---|---|---|---|
| 8–12 | 1 | 1 | 2 | 1 | 2–3 (drinks, ice, bread) |
| 13–20 | 2 | 2 | 3 | 2 | 3–4 |
| 21–30 | 3 | 3 | 4 | 2–3 | 4–5 |
Two design notes. First, desserts are capped on purpose — dessert is the category people over-volunteer for, and an uncapped board drifts sweet. When someone asks for a dessert slot that's full, the line is "dessert's covered — can I put you down for a veg side? You'd be saving the whole table." (They always say yes. Being needed beats being third brownie.) Second, the non-cooking slots aren't charity; drinks, ice, cups, and bread are real jobs that cost real money, and they're where the friend who "doesn't cook" gets to contribute without a panic-bought veggie tray. Someone claiming drinks can cover the whole table with $9-a-bottle wine that tastes like more and look like a hero.
Portion logic for whoever's cooking: potluck plates follow the buffet rules from my quantity cheat sheet — guests take a spoonful of many things rather than a serving of each, so a dish that "serves 8" at dinner serves 12–14 at a potluck. Tell your cooks that. It's the difference between them spending $18 and $35.
The tyranny line: language that works
Every potluck instruction lives on one side of a line. On the safe side, you're defining the shape of the meal; on the tyrant side, you're auditing someone's cooking. The same request, phrased across the line:
- Safe: "Can you claim a vegetable side?" Tyrant: "Can you make roasted brussels sprouts, the crispy kind, not the soggy kind?"
- Safe: "We're set on desserts, could you cover bread?" Tyrant: "Actually, could someone else do dessert this year?" (Everyone knows who that's about. Including her.)
- Safe: "Heads up, oven's full 3–6 pm, so slow-cooker or room-temp dishes travel best." Tyrant: "No dishes that need my oven."
The last pair matters most, because logistics is the one place hosts should be bossy and usually aren't. Say the oven constraint, the counter-space situation, and the label request ("tape your name on your dish and spoon") in the invitation, cheerfully, once. Food-safety logistics too: dishes should travel hot in insulated bags or cold in coolers, and anything perishable follows the two-hour room-temperature limit — at a long potluck I put out half of each big dish and hold the rest in the fridge, which keeps hour-three food as safe as hour-one food and looks more abundant anyway.
Arrival hour, choreographed
The first fifteen minutes decide whether the table works, and they're pure logistics. Clear the landing zone before anyone arrives: an empty counter by the door where dishes get dropped, uncovered, and triaged — hot things to the slow-cooker power strip (one $10 strip ends the outlet scavenger hunt forever), cold things to the fridge shelf you emptied yesterday, room-temp things straight to the table. Put serving spoons, trivets, and a roll of masking tape with a marker at the landing zone so unlabeled dishes get named on arrival. And stage the table in meal order — plates, mains, sides, bread, then desserts on a separate surface, because dessert on the main table gets grazed at 6 p.m. and the board's careful balance dies in front of you. Fifteen minutes of choreography converts twelve people's trunks into one coherent dinner.
The claim board itself
Where the board lives determines whether it fills. A shared doc dies; a group-chat message thrives, because claiming publicly is mildly fun and visibly finite. Post the categories with a few slots pre-filled ("I've got the pork and slaw; Mia's on mac") — a partially claimed board fills dramatically faster than an empty one, the same scarcity psychology that fills the Friendsgiving board. Close it 48 hours out with a summary message so everyone can see the whole menu, which quietly triggers the last unclaimed slot to fill and lets people plan around each other. That summary message is the control. You never assigned anyone anything, and yet: two mains, balanced sides, capped desserts, ice that actually shows up. The aunt brings whatever she wants inside her category, feels entirely unmanaged, and tells people it was a lovely party — which, thanks to a board she never noticed was load-bearing, it was.