Potluck Planning Without the Awkward Texts

You decide to throw a potluck because you're broke, busy, or just don't want to cook for fifteen people. Smart move. Then you send the text — "everyone bring something!" — and three things happen.

1. Four people bring chips and salsa.
2. Two people bring nothing because they thought someone else was bringing the same thing.
3. You end up making three extra dishes the morning of because the math didn't work.

This is a coordination problem dressed up as a food problem. The fix is a system, not a better text.

Why "Bring Whatever" Always Fails

People are polite. When you say "bring whatever," they default to the lowest-effort, lowest-risk option — chips, store-bought cookies, a bottle of wine. Nobody wants to be the person who shows up with a labor-intensive dish that nobody touches, so everyone plays it safe. Safe means: no main course shows up.

The fix is to remove the decision burden. Assign a category, and let people pick what they make inside that category. They get creative freedom; you get a balanced meal.

The Dish Board: The Whole System

Make a shared list with five columns: Mains, Sides, Salads, Desserts, Drinks. Set a target number for each column. Let guests claim a slot.

The host fills in two things first: the protein main and ice + cups. Those are the two things you cannot risk being missing.

The Text You Actually Send

Here's a copy-paste version that works. It's friendly, structured, and removes the "what should I bring?" follow-up loop.

Two things this does that "bring something" doesn't:

• It sets the structure ("here's what's missing") so people can fill a real gap, not guess.
• It gives a public claim mechanism, so duplicates resolve themselves.

The Five-Day Nudge

About five days out, look at the list. Send a soft nudge to anyone who hasn't claimed. The trick is to make it about logistics, not pressure.

Notice what's missing: no guilt, no "we're counting on you," no list of what everyone else brought. You're just narrowing the choice from "anything" to "one of two things." It almost always works.

Food Math: How Much Per Person

If everyone brings what they signed up for and you sized the categories right, you're covered. But if you're scaling up:

• Mains: 5–6 oz protein per person. A standard 9x13 dish feeds 8.
• Sides: ½ cup per person, per side dish.
• Salad: 1 cup per person, per salad option.
• Dessert: One slice per person, plus 20% extra (people circle back).
• Drinks: 2 drinks per adult for the first hour, then 1 per hour after.
• Ice: 1 lb per person. Always more than you think.

The Awkward Situations (And How to Handle Them)

"Can I just bring drinks?"

Sure — but cap it. If three people ask, you'll have nine bottles of wine and one salad. Reply: "Drinks are covered, but we still need a dessert or a bread situation if you're up for it."

Someone with a dietary restriction

Have them pick the slot that matches their need. If your friend is vegan, ask them to take a main or a hearty side — that way they know there's something they can eat, and the rest of the table benefits too.

Someone who can't cook

Store-bought is fine. Always. Suggest categories that travel well from a store: a bakery dessert, a Costco rotisserie chicken, a fancy cheese board. The goal is a balanced meal, not a cooking competition.

The serial flake

If you have a friend who claims a dish and never delivers, assign them the lowest-stakes category (chips, ice, plates). The meal isn't ruined if they no-show.

Setup the Day Of

People will arrive holding casserole dishes that need warming, salads that need tossing, and bottles that need opening. Three things to set up before anyone arrives:

1. A dedicated drop zone. One counter, cleared off, with a sign or sticky note for each category. Guests put their dish on the matching spot and walk away.
2. Serving utensils. Have 10+ ready. Nobody brings a serving spoon. You'll be the one digging through your drawer at 6:45 looking for tongs.
3. Oven space + warming plan. Decide what gets reheated and what stays room temp. Set the oven to 200°F as a holding zone. Mains in first.

The best potlucks I've been to all had the same setup move: a labeled spot for every category. People walked in, set down, joined the conversation. The worst ones had hosts running between the kitchen and the door for 45 minutes while a salad sat in someone's car.

The 30-Minute Rule

Tell guests dinner starts at 7pm but ask them to arrive by 6:30. The half-hour buffer absorbs late arrivals, lets the warm dishes get into the oven, and gives you a window to actually arrange the table. Without it, you're plating cold food at 7:45 while three guests are still parking.

How LOMA Helps

The dish board doesn't need to be a spreadsheet. In LOMA, you can spin up a potluck event with the food categories pre-built, share a single link, and let guests claim what they're bringing — no group chat, no "wait, who has dessert?" Everyone sees the same list update in real time. You see your gaps at a glance and send a nudge to one person instead of texting six.

Your future self, standing in the kitchen the morning of, will thank you for not having to scroll through 84 messages to figure out whether anyone is bringing bread.