How to Plan a Church Potluck (Without Chasing Anyone)

Church potlucks run on the most reliable supply chain ever invented — casserole-bearing volunteers — and yet the same three failures repeat in every fellowship hall: the sign-up clipboard that never made it past the third pew, six desserts and no vegetables, and one exhausted coordinator who personally phoned forty families. Here's how the churches that run smooth potlucks actually do it.

Start with the number, not the menu

Fellowship meals have famously fuzzy attendance — “everyone's invited” means somewhere between 30 and 130. Get a real count first: announce the meal 3–4 weeks out and ask households to RSVP at one link (bulletin QR code, weekly email, and the church Facebook group all pointing at the same page). Rule of thumb for planning: confirmed yeses + half the maybes + 10% for the folks who decide Sunday morning. A headcount also tells the kitchen team how many tables, chairs, and coffee urns — not just how much food.

The sign-up sheet that fills itself

The clipboard's fatal flaw isn't paper — it's that only one person can see it, once, on Sunday. Put the sheet online where the whole congregation can see what's still needed all week, and it fills without a single phone call. Structure beats openness: specific slots with counts, not “bring a dish.”

Slot template for ~60 people (scale up or down)

• Main dishes / casseroles ×6 (each feeds ~10)
• Vegetable sides ×6 · Starch sides ×4 · Salads ×3
• Bread/rolls ×2 · Desserts ×5
• Drinks (lemonade/tea jugs) ×4 · Ice ×2
• Paper goods (plates, cutlery, napkins, cups) ×2
• Setup crew (45 min early) ×4 · Kitchen/serving ×3 · Cleanup ×4

Two notes from hard experience: list the serving jobs ON the sheet (unassigned jobs default to the same three saints every time), and let people write what they're bringing (“Main — chicken tetrazzini”) so you don't get six of anything.

Quantity math for fellowship meals

Potlucks self-balance if the slots are right — each main feeding ~10 and one side per 10 attendees covers a 60-person meal with the template above. The kitchen team only has to backstop three things:

• Drinks & ice — 2 cups per person; a 60-person meal needs ~8 gallons of drink and 50 lbs of ice.
• Coffee — after-service meals run on it: 1 urn per 40 adults.
• A quiet reserve — one tray of something simple (pasta, rice) held back in the kitchen, in case attendance beats the count. If it isn't needed, it's next week's youth group dinner.

Kitchen & hall logistics

• Label everything: dish name, who brought it, and allergy flags (nuts, dairy, gluten). Collect allergy notes on the RSVP so you know which flags matter before Sunday.
• Two-sided serving line with plates at the start and drinks at a separate table — a 60-person line clears in 15 minutes instead of 35.
• Food safety: hot dishes into warmers or served within the hour; mayo-based salads on ice trays. Assign one kitchen volunteer as the timekeeper.
• Dish return table: a labeled table by the exit for empty dishes, with painter's tape and a marker so unlabeled pans can be claimed — solves the six-week casserole-dish mystery.

For the serial coordinator

If you run this monthly or seasonally, don't rebuild the sheet each time: duplicate last meal's event — slots and all — change the date, and share the same style of link in the bulletin. Your sign-up history also quietly teaches you your congregation's real ratios (maybe your church brings desserts unprompted but never enough vegetables — adjust the slots, not the people).

The general mechanics of sheets that fill are in the online sign-up sheet guide, wording you can paste into the bulletin or reminder emails is in RSVP wording examples, and the big-event version of all this is the family reunion planning checklist.