How to Plan a Church Potluck That Feeds Everyone

Picture 80 people in the fellowship hall after the second service. Fourteen of them brought brownies. Nobody brought a main dish. Two people are diabetic, one child has a peanut allergy, and the coffee ran out at 12:15. This is what an uncoordinated potluck looks like, and it happens because nobody decided in advance who brings what.

Here is how to run one that works, in the order you actually do it.

Lock the headcount before you plan a single dish

Everything downstream depends on the number. Guessing high wastes food and money; guessing low leaves people staring at empty trays.

Start with a rough estimate from your last comparable event, then confirm it with a real count. Ask people to RSVP and note how many are in their party, including kids. A simple RSVP form shared in the bulletin and the church email list will pull in far more accurate numbers than counting heads on Sunday.

Once you have a headcount, translate it into servings. A useful rule for a full-meal potluck: plan for each attendee to eat roughly one and a half servings across all dishes, because people go back for seconds. For 80 people, that is about 120 total servings to cover. Split those across categories so you are not left with 40 desserts and no protein.

Divide the meal into categories with real quantities

Do not just ask for "a dish." Tell people exactly what slot you need filled and how much. A category breakdown for a 80-person church potluck might look like this:

Main dishes (proteins): 10 to 12 dishes, each serving 8 to 10. Think casseroles, baked chicken, pulled pork, a vegetarian lasagna.
Sides and vegetables: 12 to 15 dishes. Green beans, mac and cheese, roasted potatoes, rice.
Salads and cold dishes: 6 to 8. These fill plates and travel well.
Breads and rolls: enough for one to two pieces per person.
Desserts: cap this. Six to eight is plenty. Everyone wants to bring dessert, so this is the category you limit first.
Drinks, ice, cups, plates, napkins: assign these to specific people. They are the things everyone assumes someone else is bringing.

When you set slot limits on each category, spots fill and lock as people claim them. That is how you avoid the fourteen-brownie problem. An online signup sheet with a maximum on each option does this automatically, so the dessert slot closes once it is full and the next person is nudged toward the empty main-dish slots.

Handle dietary restrictions out in the open

A church crowd spans every age and health situation. You will have people managing diabetes, gluten sensitivity, nut allergies, and vegetarian diets, plus small children who need something plain.

Do two things. First, ask a short question on the signup: does your dish contain nuts, gluten, dairy, or pork, and is it vegetarian? That information lets you label dishes on the serving table so a parent with an allergic kid can scan the labels in ten seconds instead of interrogating a stranger.

Second, guarantee coverage of the safe categories. Reserve at least two clearly vegetarian main dishes and one gluten-free option, and assign them to volunteers you trust to follow through. Do not leave dietary coverage to chance and hope it works out. When you build your church potluck signup form, add those reserved slots as named requirements so someone owns each one.

A public response summary helps here too. If everyone can see what has already been claimed, a member who was going to bring another pan of brownies can see the dessert slots are full and pivot to the salad category that still has openings.

Set up the signup so people commit in seconds

The goal is that a member reads the announcement, taps a link, picks a slot, and is done before the sermon starts. No account, no login, no app to install.

Describe your event in plain language and let the AI-powered signup forms build the structure for you. Type something like "Sunday church potluck for 80 people, need 12 mains, 15 sides, 6 desserts, drinks, and setup and cleanup help," and you get a working form with the categories and limits already laid out. Edit anything that is off, then share it.

Share it three ways so you catch everyone:

Email and text blast to the congregation with the direct link.
A QR code printed in the bulletin and posted on the fellowship hall door, so people can sign up on their phones on the way out.
The church website, where you can embed the form so it lives next to your other announcements.

Because the form is mobile friendly, an older member can fill it out on their phone in the parking lot without pinching and zooming. That single detail decides whether half your congregation participates or gives up.

Cover the parts of a potluck that are not food

A meal for 80 needs hands, not just casseroles. Someone has to arrange tables at 9 a.m., someone has to make coffee, and three or four people have to stay to wash serving dishes and stack chairs.

Add setup, serving, and cleanup slots to the same form or run a companion church volunteer signup so the labor is claimed the same way the food is. Send an automatic email reminder two days before, and the volunteers who forgot they signed up will show up anyway. Reminders are the difference between a full cleanup crew and you doing dishes alone at 2 p.m.

If your church runs these regularly, save the finished form as a reusable template. Next month you duplicate it, change the date, and reopen the slots. The planning work you did once carries forward.

Start the food coordination first, because it is the piece that breaks most often. Build your potluck signup with hard limits on every category, reserve the dietary-safe dishes, and share the link this Sunday. The fourteen brownies problem solves itself the moment the dessert slot can fill up and close.