How much food does one person actually eat at a potluck?

Plan on roughly one pound of food per adult across the whole spread — main dish, side, and dessert combined — and about two-thirds of that for a child. That is a planning number, not a rule; a hall full of teenagers eats more than a hall full of retirees. Use it to set a floor, then adjust for who you know is coming.

What if I don't know how many people are coming?

Start from your average Sunday attendance, not the number of households, since some people come without their whole family and some bring guests. If forty people usually attend, plan food for something close to forty, and add ten to fifteen percent for visitors and last-minute additions rather than trying to guess an exact number.

How many main dishes versus sides should we ask for?

A workable split is roughly one main dish for every eight to ten people, one side for every six to eight, and one dessert for every eight to ten, since desserts tend to be smaller portions and people take less of them. Assigning categories by last name or by table, rather than leaving it open, is what actually produces that ratio.

Should we ask people to sign up or just announce it?

A sign-up, even an informal one on paper in the lobby, beats an announcement alone almost every time. An announcement tells you how many people intend to bring something; a sign-up tells you what they are bringing, which is the number you actually need to know whether the mains, sides, and desserts are covered.

How do we plan for a potluck tied to a bigger event, like a homecoming Sunday?

Treat it as an event with its own headcount, not an extension of a normal Sunday. Attendance on a homecoming or anniversary Sunday can run thirty to fifty percent above a typical week, so use that week's registration or expected-guest count, not the trailing average, as your baseline for food.

How to plan potluck headcount for a church of any size

Every fellowship hall has a potluck story: the year the fried chicken ran out before the second service crowd got through the line, or the year three people brought macaroni and cheese and nobody brought a vegetable. Nobody plans for that. It just happens, because a potluck is one of the few church events where the food supply depends on forty separate decisions made in forty separate kitchens, and no one is coordinating them.

You cannot control what people bring. You can control the number you plan around, and a little rough math goes further than it gets credit for. None of this requires a caterer’s spreadsheet — just a headcount you trust and a few ratios that hold up whether you are feeding forty people or two hundred.

Start with a number you actually trust

The single biggest cause of potluck shortfalls is not stingy cooks. It is a headcount pulled out of thin air. “We usually get a good crowd for this” is a feeling, not a number, and feelings do not tell the kitchen crew how many pans to expect back empty.

Use your actual attendance history as the starting point. If your church runs sixty on a normal Sunday and this potluck follows the second service, sixty is your baseline — not eighty, because you hope for a good turnout, and not forty, because you are worried about scaring the cooks. Churches that keep a clear read on attendance over time have an easier version of this problem: the baseline is sitting right there instead of being reconstructed from memory the Tuesday before.

The per-person math

A workable planning figure is about one pound of food per adult, counting the main dish, one side, and a taste of dessert together, and roughly two-thirds of a pound for a child under twelve. That number is not precise — nothing about a potluck is precise — but it is precise enough to catch the big misses.

A church of 60: plan for roughly 50 to 55 pounds of food total, assuming a mix of adults and kids.
A church of 120: plan for roughly 100 to 110 pounds.
A church of 250: plan for roughly 210 to 230 pounds, and start thinking in terms of assigned categories rather than an open free-for-all, because at that size the law of averages stops saving you.

The math scales. What does not scale on its own is the mix — and that is where most shortfalls actually happen.

Why the shortage is never really about total food

Almost every potluck horror story is a mix problem, not a quantity problem. There was plenty of food in the building; there just wasn't plenty of the right kind. Seven crockpots of baked beans and one green salad is technically enough calories and a genuinely bad meal.

The fix is a simple ratio, applied on purpose rather than left to chance: roughly one main dish for every eight to ten people, one side for every six to eight, and one dessert for every eight to ten. Desserts stretch further because people take smaller portions of them, which is why a potluck can survive being dessert-heavy but rarely survives being side-dish-heavy with no mains.

“Bring a dish to share” from the pulpit produces intentions, not information. A sign-up sheet — even a plain paper one taped to the lobby table — produces the one thing you actually need: who is bringing what.

Split the sheet into three columns: mains, sides, desserts. As people sign up, you can see in real time whether the mains column is filling in or sitting empty while the dessert column overflows. That fifteen-minute glance the Thursday before the potluck is worth more than any formula, because it tells you exactly where to nudge people, and who to ask directly rather than leaving it to chance.

Build in slack for the people you didn't count

Potlucks attract visitors, extended family, and the neighbor someone invited on a whim — people who were never going to show up in your attendance average. Add ten to fifteen percent on top of your baseline headcount to cover them. It is a cheap kind of insurance: a little extra food left over costs nothing but leftovers, while running out at 6:15 costs you the last table's worth of goodwill.

This is also where knowing whether the meal is tied to a bigger event matters. A potluck that follows a normal Sunday behaves like a normal Sunday. A potluck built around a homecoming or a big Sunday behaves like that event — attendance can run well above the trailing average, and the food count should follow the day's expected crowd, not the ordinary week.

Space and tables matter as much as food

A hall that feeds two hundred people also has to seat two hundred people, and that math is less forgiving than the food math. Figure eight to ten square feet per person for round-table seating, plus room for a serving line that does not choke the entrance. If your fellowship hall genuinely cannot hold the crowd you expect, that is worth knowing well before the Thursday sign-up count, not discovered at 5:45 while folding chairs are still in a closet.

Two services and a shared meal in between raise their own version of this problem: the first-service crowd eats before the second-service crowd has even arrived. If your church runs that way, plan the timing of the serving line as carefully as the quantity, or hold back a visible reserve for the later group so the table does not look picked-over to the people walking in last.

After the last plate: turning a good potluck into a next step

A potluck is one of the easiest environments in church life for a guest to feel like they belong, because sitting down over a shared plate does more relational work in twenty minutes than a handshake at the door does in two. That is worth protecting on purpose. If a newer face sat at your table, the same discipline that applies to following up after any big Sunday applies here: write the name down before it slips your mind on the drive home, and give someone the job of reaching out that week.

SundayBridge will not plan your headcount or manage the sign-up sheet — that part stays on paper or in your own lobby table the way it always has. But once you know who showed up, especially anyone new, the follow-up board is a simple place to put a name, an owner, and a date, so the conversation that started over a shared plate does not quietly disappear into someone's memory instead.

A quick reference to keep in your notes

Keep this rough table somewhere you will actually see it again next quarter, rather than reconstructing it from scratch each time:

Food per person: about one pound for an adult, two- thirds of a pound for a child.
Dish mix: one main per 8–10 people, one side per 6–8, one dessert per 8–10.
Buffer: add 10–15 percent above your usual attendance for guests and last-minute additions.
Space: roughly 8–10 square feet per seated person, plus a serving-line lane.

None of this guarantees a perfect potluck. Someone will still bring seven-layer dip to a meal that needed a green vegetable. But a real headcount, a simple dish-category ratio, and a small buffer will keep the hall fed by 6:15 almost every time — which is the actual goal.