How to Organize a Potluck Without the Group Chat

It’s Thursday, and the potluck is Saturday. You open the group chat to work out what’s coming and start scrolling. Forty messages. Three people have said hummus. Nobody has said a main. Kim asked two weeks ago whether anything would be gluten-free, and the answer, if there was one, is somewhere above the memes.

So you start a spreadsheet, and now you’re the person messaging everyone one at a time to fill it in.

Nobody did anything wrong. Each guest answered the question they were asked, which was “what are you bringing?”, by announcing a dish. The question nobody was asked is the one that matters: what’s still missing?

Ask for courses, not dishes, on one sheet everyone can see.

A chat is a timeline. A potluck is a table. The thread shows you the latest message, but what you need is the latest state: how many are coming, which courses are covered, and who can’t eat what. Every new message changes all three, and nothing in the thread adds them up.

Ask for gaps, not dishes

“Bring whatever you like” is how you get three hummus. Assigning a dish to each guest is how you spend the week doing it. The middle path is to decide the courses before anyone replies. For twelve people, that might be two mains, three sides, two desserts, and someone on drinks, with an “other” line for ice, plates and a folding chair.

Then guests claim a gap instead of announcing a dish. The person who was going to bring hummus sees that the sides are full and a main is still open, and brings a main. Your own dish goes in last, into whatever is left, which is how the one thing nobody wanted to make gets made.

Size each dish by the headcount

A recipe that “serves eight” serves eight people eating only that dish. At a potluck everyone takes a little of everything, so a main needs to cover the headcount divided by the number of mains, not the whole room. Twelve coming and two mains means each main serves six. Three sides means each side serves four. That’s less than most people make, and it’s why a potluck planned by course sends everyone home with lighter containers.

It only works if the headcount is on the sheet. Ask every reply how many they’re bringing, not just whether they’re coming, and let “maybe” be an answer, so the people who aren’t sure yet don’t go quiet instead.

Write down what people can’t eat, once

A diet mentioned in a message is a diet forgotten by Saturday. Ask for it on the sheet, next to the reply, and then read the sheet by guest rather than by dish. A guest who is vegan and can’t eat gluten needs one dish that is both. A vegan pasta and a gluten-free steak leave them with a plate of salad.

Allergies are different from diets. A diet is something a dish either suits or doesn’t. An allergy is a question about ingredients, and only the person who made the dish knows the answer. So list each allergy for the people cooking (“two guests avoid peanuts”) and let the bringers check their own recipes. A sheet can flag a recipe that mentions peanuts. It can’t promise that a dish doesn’t contain them.

One more thing: those answers are personal. The host needs them. The whole guest list doesn’t.

One link, with mogumogu.ai

This is what the new potluck page in mogumogu.ai does, and the reason it exists. Until now nothing in the app could be shared outside your household, and a potluck is the one meal you plan with other people.

You create the potluck with the occasion, the date and how many of each course you want, and send one link. Nobody needs an account. Whoever opens it replies yes, maybe or no with their headcount, notes their diet and any allergies, and claims a dish in a course that’s still open. The sheet shows each course against what you asked for (“Mains 1 of 2”), each diet on the list with the dishes that suit it or “No dish yet”, and each allergy with how many guests named it.

A dish can be a name (“Kim’s chana masala”) or a recipe picked from the catalogue. A recipe gives the bringer a shopping list scaled to the servings they promised, and lets the sheet warn where its ingredients mention an allergy on the list.

A guest’s diet, allergies and note are seen by the host and that guest only. Everyone else on the link sees counts. If the link gets forwarded further than you meant, make a new one, and the old one stops working.

The potluck then sits on your week plan as its own night, held to its date, and the dish your household claimed goes on the grocery list in the amount you promised. If you’re the guest rather than the host, “Add to my plan” does the same on yours.

Do This Week

If there’s a potluck in your calendar, three steps, with or without the app:

• Decide the courses before you send the invite. How many mains, sides and desserts the headcount needs, plus drinks and an “other” line for ice, plates and chairs. Write those counts at the top of a note everyone can edit.
• Ask every reply for three things. How many are coming, what they can’t eat, and which open slot they’re taking. Claim a gap, not a dish.
• Read the sheet two days out, by guest. Fill an empty course yourself, and check that each person on the list has at least one dish they can eat. If you’d rather not do the reading, send a mogumogu.ai link and let the sheet do it.

Ask for courses, not dishes, on one sheet everyone can see.