How to Organize a Potluck in 2026: Dish Assignments, Quantity Formulas and a No-Duplicates Signup System

Most potluck advice stops at "give people a specific assignment." That is correct and it is the easy part. The parts that actually break a potluck are the ones nobody publishes: how many slots a table of 30 needs, how you keep the slot list visible so two people do not both bring dessert, who is coming to which part of the day, and what happens when four guests arrive at 6:15 all needing twenty minutes of oven.

This guide gives you the arithmetic. A claimable slot plan for 10, 20, 30 and 50 guests with what each slot has to feed. A per-guest quantity formula in ounces and pans. A dietary labelling system that fits on an index card. A table of which dishes survive a car ride. Fifteen wordings you can paste. And the oven math, because a home oven fits four casseroles and your guests are bringing eleven.

Key takeaways

• Plan 1.25 to 1.5 lb of total food per adult, and size each slot by what it must feed rather than by dish count. One 9x13 pan is 8 to 10 main portions or 12 to 16 side portions.
• A 20-guest potluck needs about 11 food dishes across 15 claimable slots, once you separate hot sides from cold salads from bread and count drinks and supplies as real slots.
• The slot list has to be visible to guests. A list only you can see fails exactly like a group text: whoever missed the message brings a second dessert.
• One potluck is usually more than one function. The day-before prep, the meal and the late dessert round have different guest lists and different headcounts.
• A standard 30-inch oven holds about four 9x13 pans across two racks, and a refrigerated casserole needs 30 to 45 minutes at 350°F. Publish an oven schedule or the meal starts 40 minutes late.
• Label dishes with what they contain, not what they are free from, because a home kitchen cannot promise allergen-free. And follow the USDA two-hour rule: nothing perishable between 40°F and 140°F for more than two hours, one hour above 90°F.

How to Organize a Potluck in 5 Steps

Organizing a potluck is five decisions in a fixed order, because each answer sets the next. Lock the date and headcount, turn the headcount into a slot list, publish that list where guests can see what is claimed, send each guest a specific assignment, then run the oven and the serving line on the day.

1. Set the date, the eating time and an RSVP deadline. The eating time matters as much as the date, because it tells guests whether they are bringing something hot.
2. Turn your headcount into a slot list. Not "mains, sides, dessert." Numbered slots with a serving target: "Main 2, feeds 10 to 12, hot."
3. Publish the slot list so guests can see what is taken. If claims are invisible, duplicates are guaranteed.
4. Confirm each assignment individually. Serving size, serve temperature, oven needs, and any allergen info you need back.
5. Run the day on a schedule. Oven windows, a serving line in the right order, an announced eating time.

The rest of this guide is those five steps with the numbers attached. If your potluck sits inside a bigger event with a run-of-show and a budget, the step-by-step party planning timelinecovers the weeks before. <!-- link to: NEW-US-93-how-to-plan-a-party --> If your list has crossed 40 names, splitting one guest list by functionhas the tracker and the arithmetic. <!-- link to: NEW-AB-13-guest-list-management -->

How Far Ahead to Start: Casual, Large and Holiday Potlucks

Start early enough that guests can plan a real dish. Someone who gets their assignment four days out buys chips. Someone who gets it two weeks out makes the thing they are known for.

Mixily's potluck guide states 1 to 2 weeks for a casual potluck, 3 to 4 weeks for 15 to 30 people and 4 to 6 weeks for a holiday potluck. Those windows are sound. The refinement is that a potluck has two deadlines, not one: the RSVP deadline and the assignment deadline. The gap between them is where hosts lose a week.

Why you split the invitation from the assignment

Send the invitation first and the assignments second, once RSVPs are in. Assign dishes in the invitation and you will hand four slots to people who are not coming, then re-cut the whole list. The exception is a themed potluck, where the theme is the appeal: name it upfront, hold the specific slots until replies land.

Give the deadline a reason, too. "RSVP by the 14th" gets ignored. "RSVP by the 14th, because I am cutting the dish list on the 15th" gets answers. Then nudge only the people who have not replied, because blanket reminders train everyone to ignore you.

Food Categories, Potluck Themes and the Dish Count Formula

Six categories cover every potluck: mains, hot sides, cold salads, bread or starch, desserts, drinks. Most guides run four and merge hot sides with cold salads, which is how you end up with three pasta salads and nothing warm on the table.

Mixily's guide publishes the widely quoted ratios: one main per 8 to 10 guests, one side per 6 to 8, one dessert per 10 to 12, roughly one dish per 2 to 3 guests overall. Useful, but a dish is not a unit. "One side" is either a 9x13 pan of scalloped potatoes or a bowl of cucumbers for four. Size the slot by servings and the ambiguity disappears.

The per-guest quantity formula

Work in servings per guest, then convert to pans. Total food across the table lands around 1.25 to 1.5 lb per adult, which sounds high until you remember people take a spoonful of everything.

Pan yields, so you can size a slot in one line

Now a slot reads "one 9x13, feeds 10 to 12 as a main" and there is nothing left to interpret.

Six potluck themes that double as your slot list

A theme is optional, and its real value is structural: a good theme is already a category list, so your slots write themselves.

The Claimable Slot Plan for 10, 20, 30 and 50 Guests

Here is how many of each slot a given headcount actually needs, and what each slot has to feed. Print it, cross out what does not apply, and you have your signup sheet in five minutes.

Two things to notice. The food-dish count lands close to the familiar "one dish per 2 to 3 guests" rule at every size, so this is that rule made specific. And drinks and supplies are real slots: leave ice, cups and serving spoons off the sheet and you buy all of it yourself at 4 p.m.

Adjustments that matter

• Kids. Two children under 10 count as one adult, and add a plain starch slot. Buttered noodles save the evening.
• Long event. Past three hours, add a dessert and a drink slot rather than more mains. Appetite peaks once.
• A drinking crowd. Add a second bag of ice before a second bottle of anything.
• Leftovers wanted. Add one main slot and tell guests to bring containers.
• No oven. Convert two hot slots to cold and one to a slow-cooker slot.

Build a Signup System Nobody Duplicates

A signup system works when three things are true: the slots are specific, guests can see which ones are claimed, and every claim is attached to a named person. Miss one and you get the classic failure, three people arriving with pasta.

Plenty of RSVP tools handle dish signup alongside the reply. Mixily's summer picnic guide describes exactly that, stating that guests pick their dish when they confirm attendance, all in one step, and it is a good pattern. So the real question is not whether a tool can collect a dish, but whether the answer is visible to the next guest and attached to the right part of your event.

The four ways hosts actually run this, compared

Platform features change, so re-verify anything in the fourth row against the provider's current documentation before relying on it.

Where Lumhe fits, and where it does not

Start with the limits. Lumhe has no dish-claiming checkbox and it does not design your invitation. You write the slot list yourself. What it changes is the two things a flat RSVP cannot do.

The first is per-function tracking. One potluck is one event containing sub-events, and each function carries its own date, time, venue, guest list and RSVP. The meal is a function. So is the 10 a.m. prep session, and so is the 8 p.m. dessert round. You get a separate confirmed number for each, so "how many am I cooking for" and "how many are helping me set up" stop being the same guess.

The second is that the assignment reaches a person. You find guests inside Lumhe by name, phone number or email, connect, and invite them directly, so the slot list lands with the individual instead of scrolling past in a thread. Real-time tracking shows who has not answered, and you nudge only those people.

You upload the invitation you already made: an image from any design tool, a video, a PDF, or typed text. Typed text is the practical one here, because that is where the slot list goes. A template library is coming soon, so for now the design is yours and the coordination is Lumhe's.

Keeping the slot list current without a claim button

One habit does most of the work here. Once a day, at the same time, update the list and repost the short version.

Naming the claimed dishes matters more than listing the open ones. That line stops the second brownie pan, and it quietly tells the guest who has claimed nothing that everyone else has.

Who Brings What to Which Function

A potluck almost never has one guest list, and this is the part no guide writes. There is the meal. There is usually a prep shift the day before or the morning of. There is often a later wave: people who work Saturday, people with a nap schedule, neighbors coming by for dessert. Different rooms, different numbers.

Treat them as one flat RSVP and every number you hold is wrong. You will know 28 people said yes to "the potluck" and not know that only 6 are coming at 10 a.m. to peel potatoes, or that 11 of the 28 are dessert-only and do not belong in the mains math.

What changes when you count them separately

Mains math runs on the meal number, not the total invited. Plates and napkins run on the total across all functions, because the dessert crowd uses plates too. The oven schedule runs on the meal number plus whatever the second sitting needs reheated. And the prep number decides whether you are chopping alone at midnight.

It is also the fairest way to ask for help. "Can everyone come early?" gets four vague maybes. A separate invitation to a 10 a.m. prep function, sent to eight people with its own RSVP, gets a real answer from each and no guilt for the six who cannot come.

The two-sitting holiday potluck

For holiday meals with two waves, hold back one main and one starch from the first sitting, covered, in the reheat queue instead of on the table. Tell second-sitting guests the time they are eating, not the time the event started. Put the dessert slots on the second sitting, so the first wave is not staring at four pies while the mains are still hot.

Stop Saying "Bring Whatever": Assignment Scripts You Can Copy

"Bring whatever" is a question, and the easiest answer to a question is chips. A specific assignment is a favor: it takes a decision out of your guest's week, and most people are relieved to be told what to make. A complete assignment has five parts, and any part you leave out is one the guest fills in with a guess.

The five assignment moves that raise the quality of the table

• Match the dish to the person. The confident cook gets the ambitious slot, the busy person gets the store-bought pie. Both are contributions and nobody feels tested.
• Name a dish you have seen them make. "Would you bring that lemon orzo from June?" gets a yes almost every time, and a dish you know is good.
• Give the amount as a vessel. "A 9x13" is easier to act on than "twelve servings."
• Assign the serve temperature explicitly. This is what protects your oven schedule.
• Never double up a category silently. If you must, say so: "Sam is bringing brownies, so something fruit-based would balance the table."

When someone claims a slot that is taken

Answer fast and offer a real alternative. A day of silence is how you get two of the same dish anyway.

Dietary Restrictions: Collect Them at RSVP, Not on the Day

Ask about dietary needs in the RSVP, design the slot list around the answers, then label every dish. Handle it on the day instead and you get a guest with a serious allergy standing in front of eleven unlabelled pans, asking strangers what is in things. The structured version is two fields and one rule.

The two fields to collect

Field one: "Anything you cannot eat?" as a free-text box. Field two, the one hosts skip: "Is that a preference, an intolerance, or an allergy?" They get treated differently. A preference shapes the menu. An allergy shapes the labels, the serving utensils and where the dish sits in the line.

The rule: label what a dish contains, not what it is free from

A home kitchen cannot promise allergen-free. Shared cutting boards, shared oil, flour in the air, one spoon in two bowls. So the honest label states contents. The FDA recognizes nine major allergens: milk, eggs, fish, crustacean shellfish, tree nuts, peanuts, wheat, soybeans and sesame. If a dish contains one, name it.

The five-tag labelling system

Use a fixed tag set so guests learn to scan for their tag instead of reading every card.

NGI rather than GF is deliberate. "Gluten-free" is a claim about a controlled process. "No gluten ingredients" is a claim about a recipe, and a recipe is the only thing a home cook can vouch for.

The dish card template

One card per dish, written by you from the guest's reply rather than handed out at the door.

Design the slot list for your most restricted guest

Two hard minimums. With vegetarian guests, at least one main and two sides are meat-free and one is substantial enough to be a meal. With a serious allergy in the room, one main is confirmed free of that allergen, gets its own serving spoon, and sits at the front of the line ahead of the dish that contains it. Cross-contact on a buffet happens at the spoon, not in the kitchen.

Then ask that guest what they are comfortable with. Some will want to bring their own main. That is not a hosting failure. Give them a slot for it.

Dishes That Actually Travel, and What Falls Apart in the Car

A potluck dish has to survive a car, a countertop and up to two hours of waiting, which rules out a category of otherwise excellent food. The test: if a dish is only good in the ten minutes after it leaves the oven, it is not a potluck dish.

Three fixes that rescue a fragile dish

• Deconstruct it. Dressing, crisp toppings, herbs and nuts travel in separate bags and go on at the table. A salad assembled in the host's kitchen is a different dish from one that rode in a bowl for 25 minutes.
• Ship it cold, finish it hot. A crumble topping baked separately and spooned on beats one that went soft under foil.
• Use the cooler as a warm box. Fill a hard cooler with hot water, close it ten minutes, dump it, then load foil-wrapped hot dishes. It holds above 140°F for well over an hour.

Food safety, in three numbers

USDA guidance is the whole rule set. Perishable food should not sit between 40°F and 140°F for more than two hours in total, and above 90°F that drops to one hour. Reheat cooked dishes to an internal 165°F. Hold hot food at 140°F or above, cold food at 40°F or below. Put those numbers in your reminder and most day-of food problems disappear.

Day-Of Logistics: Oven Space, Reheating and the Serving Line

Here is the bottleneck every host hits and almost no guide mentions. A standard 30-inch oven has an interior roughly 24 inches wide by 19 inches deep, which fits about two 9x13 pans per rack and four across two racks. Your 20-guest potluck has eleven dishes arriving, and four of the guests bringing them assumed they could have the oven for twenty minutes. Solve that with arithmetic before the day, not improvisation at 6:15.

The oven math

Two adjustments. Both racks loaded adds roughly 25 percent to every time above, because airflow is blocked. And every door opening drops the cavity 25 to 50°F, so a busy oven runs colder than the dial says.

Publish an oven schedule

Three days out, send a schedule of named 20-minute blocks. Two before the eating time and two after is usually enough. The rule that makes it work: a guest who has not booked a block is bringing something room temperature.

The four ways around a full oven

• Slow cookers on the counter. The best answer. A dish that arrives hot in a slow cooker holds above 140°F for hours and never touches your oven.
• The preheated cooler. The warm-box trick above buys an hour of holding with no equipment.
• The stovetop. A pot of soup or beans on low is oven space you did not use. Keep one burner free for it.
• Reassign the slot. If a dish needs 45 minutes and the oven is booked, swap that guest with a cold-slot guest. A week out, not at the door.

Watch the electrical load, not just the counter space

Four slow cookers are fine. An electric griddle plus a roaster oven plus a coffee maker on one circuit is not. Read the wattage on each appliance and do the addition.

A standard US 15-amp, 120-volt circuit delivers about 1,800 watts, with a safe working load near 80 percent of that, or roughly 1,440 watts. Kitchen countertop circuits are commonly 20 amps, about 1,920 watts safe, and most kitchens have two. Practical rule: one appliance over 1,000 watts per circuit, everything else shares. Use a heavy-duty cord rated for the load and never daisy-chain power strips for a heating appliance.

The serving line

Set the table before the first guest arrives, in the order people build a plate: plates, mains, hot sides, salads, bread, condiments, then cutlery and napkins last so hands stay free. Drinks and ice go on a separate surface, because that station gets visited five times as often and it will jam your line.

Two throughput facts. A single-sided line moves about 5 to 8 guests per minute, so pulling the table off the wall to serve from both sides roughly halves the queue, which matters above 25 people. And keep one serving utensil per dish plus three spares, because guests reliably arrive with a dish and no spoon.

Announce the eating time out loud on arrival. "We are eating at 6:30" does more for food temperature than anything else here. Then spend thirty seconds naming a few dishes and who made them.

Splitting the Load: What to Do About Guests Who Cannot Cook

Give non-cooks a real slot, not an apology. The unspoken truth of most potlucks is that the host absorbs everything nobody claimed: the anchor dish, ice, disposables, drinks, foil, coffee. Those are contributions too, and the easiest ones to hand out.

The non-cooking slot list

Put these on the sheet as numbered slots alongside the food. Costs below are rough US grocery estimates for planning only and vary by city and store, so check locally.

The host still makes the anchor dish

Keep this rule however good your sheet is. The host makes at least one substantial main, because someone will cancel at 4 p.m., someone will bring half of what they promised, and one dish will not survive the car. A pan of lasagna or a pot of chili gives the potluck a floor.

Budget for it. At a 20-guest potluck, a host making the anchor main and covering ice, disposables and basic drinks is typically spending somewhere around $60 to $110 before anyone arrives, again a planning estimate rather than a quoted price. The fix is not asking anyone for money. It is putting ice, cups, napkins and drinks on the slot list as claimable items, which cuts the host's share by roughly half.

The guest who brings nothing

Feed them warmly and say nothing. Next time, assign them ice or cups directly rather than on an open list, because open lists get claimed by the people who were always going to claim something.

Potluck Invitation Wording and Signup Requests You Can Paste

Fifteen wordings covering the whole sequence from invite to thank-you: seven invitations and eight follow-up messages. Swap the names, dates and slot lists. Each one pastes as-is into a message, an invitation text field, or the typed-text invitation you upload.

Invitation wordings

1. Casual weeknight potluck, small group

2. Weekend dinner potluck with the slot list in the invitation

3. Large potluck, 30 or more guests

4. Friendsgiving potluck

5. Themed potluck, taco bar

6. Office or team potluck

7. Building or block potluck

Assignment and follow-up messages

8. The specific assignment message

9. Redirecting a duplicate claim

10. The non-cook assignment

11. The oven-time request

12. Collecting dietary information

13. Reminder, three days out

14. Day-of arrival instructions

15. Thank-you the next day

Your Printable Potluck Signup Sheet and Planning Checklist

Both assets in full. Copy the sheet into a document, print it, or paste it into a message.

The printable signup sheet

The potluck planning checklist

After the Potluck: Photos, Leftovers and Thank-Yous

The hour after the meal holds three jobs most hosts do badly or skip.

Leftovers, in the right direction

Send food home. Ask the non-cook slot for a roll of containers, and hand dishes back full rather than washed and empty. Two rules: never send a guest's dish home with a different dish in it, and never keep a serving bowl. Masking tape and a marker on the bottom of every pan at the door, and each one finds the right kitchen.

Photos, in one place instead of eleven camera rolls

A potluck is the most photographed meal there is, because people photograph the thing they made. Then each photo stays on the phone that took it, and the person who made the corn casserole never sees the shot of the full table.

Collect them in one shared timeline. On Lumhe that is Moments: guests upload their own photos, everything gathers in one organised place, and it does not expire. Not a group chat and not a story that disappears in a day, so the dish photos and the table shot are still there next year. Send the link the morning after, while people still have the photos open.

Thank-yous that name the dish

Send them within 48 hours with one specific detail each. "Thank you for coming" is a formality. "Your orzo was the first thing to run out" is a message somebody keeps. Anyone who brought supplies, worked a setup shift or stayed to clean gets an individual note, not a group message.

Two lines for next time

Note what ran out and what came back untouched. "Not enough bread, way too much dessert, need two more serving spoons" makes you a better host next time than trying to remember.

Frequently Asked Questions

How do you organize a potluck signup so nobody brings the same thing?

Write numbered slots with a serving target instead of category names, then publish the claimed list where every guest can see it and refresh it once a day. "Hot side, feeds 10 to 14" is claimable. "Sides" is not. The failure is rarely careless guests, it is a claim the next person could not see.

How many dishes do you need for a potluck?

Plan about 7 food dishes for 10 guests, 11 for 20, 16 for 30 and 23 for 50, roughly one dish per 2 to 3 guests. Split them across mains, hot sides, cold salads, bread and dessert rather than counting undifferentiated dishes, and size each by servings: 5 to 6 oz of main per adult, 4 oz of each side.

How far in advance should I organize a potluck?

Two to three weeks for 10 to 20 guests, four weeks for 20 to 35, five to six weeks for a holiday potluck. Set two deadlines, not one: the RSVP deadline first, assignments a day or two later once you know the real headcount. Reminder three days out, oven schedule four days out.

What should the host bring to a potluck they are hosting?

At least one substantial main, plus the things nobody claims: ice, disposables, serving utensils and coffee. The anchor main is insurance, because someone will cancel late, someone will bring half of what they promised, and one dish will not survive the drive.

How do you handle oven space at a potluck?

Publish a schedule of 20-minute blocks three or four days out, and treat anyone not on it as bringing room-temperature food. A standard 30-inch oven fits about four 9x13 pans across two racks, a refrigerated casserole needs 30 to 45 minutes at 350°F, and both racks loaded adds about 25 percent. Slow cookers, the stovetop and a preheated cooler absorb the overflow.

How do you handle dietary restrictions and allergies at a potluck?

Ask two questions at RSVP: what someone cannot eat, and whether that is a preference, an intolerance or an allergy. Then label every dish with what it contains rather than what it is free from, because a home kitchen cannot promise allergen-free. Confirm one main is safe for your most restricted guest, give it its own spoon, and place it ahead of the allergen-containing dishes in the line.

Can you run a potluck when the guest list has more than one part?

Yes, and it is the more accurate way to run one. The day-before prep, the meal and the late dessert round are separate functions with separate guest lists and separate headcounts. On Lumhe each is a sub-event inside one event with its own date, time, venue, guest list and RSVP, so how many are eating and how many are helping are two real numbers.

What is the best potluck theme?

A taco or bowl bar is the most reliable: it becomes a slot list on its own, and guests building their own plates removes the serving bottleneck. Soup and bread works best in cold months and uses burners instead of oven space. "Dishes from your family" suits a group that does not know each other, as long as guests name the dish when they claim a slot so cuisines do not double up.

Planning a potluck? Upload the invitation you already made to Lumhe, whether it is an image, a video, a PDF or typed text, and put your slot list right in it. Then find and connect with your guests by name, phone number or email inside Lumhe and send it to them directly, so the assignment reaches the person instead of scrolling past in a group thread. Add each function separately, so the day-before prep session and the meal itself have their own guest lists and their own RSVPs, and you always know how many people you are cooking for and how many are helping you set up. Nudge only the guests who have not replied. After the meal, every dish photo and the whole-table shot collect in Moments, a shared timeline that does not expire, so the person who made the corn casserole finally gets to see it. You can also share your invitation link on WhatsApp, iMessage, Instagram or any other platform. Explore Lumhe.

SEO Keyword Map