The church potluck

The sheet on the bulletin board

Every church potluck has one, and everyone knows its failure mode: the sheet lives at church, and the deciding happens at home. Somebody means to sign up after the service, gets caught in a conversation in the narthex, and remembers on Tuesday — when the sheet is forty minutes away. So the organizer spends the week fielding texts, calls, and hallway promises, and stitching them together from memory.

The fix is not an app. It is moving the sheet to where the deciding happens: one link, opened in any phone’s browser — nothing to download, no account to create, and nothing that requires being on Facebook, which matters in a congregation where half the people are not.

And the old way still works alongside it. Anyone who would rather sign up with a phone call, can — they tell the organizer, who writes them in, and their name shows on the sheet like everyone else’s. If they open the link later themselves, they can claim their own entry and change it. The technology adapts to the congregation, never the other way around.

The numbers, at church scale

Buffet portions overlap — people take a spoonful of many dishes — so sides run about one per 3–4 people and desserts about one per 6. At church headcounts that produces numbers that look enormous and are not:

Seventeen sides for sixty people sounds like an impossible ask until you remember the covered-dish arithmetic: most households bring one dish, so the dish count is roughly the attendance list. The food takes care of itself. What does not take care of itself is the distribution — sixty people left alone produce eleven desserts and three sides — and that is the organizer’s whole job: post the categories, make the thin ones visible, and let the table balance itself.

Past the same eight cooks

Every congregation has them: the people whose casseroles the whole church knows by name, who cook for every funeral, every welcome dinner, every supper. They are the backbone of the thing — and a sign-up sheet that only lists courses quietly assigns them the entire meal, again.

Put the non-cooking jobs on the sheet as claimable items: ice, cups, plates, napkins, drinks, and the setup and cleanup shifts if your hall runs them. They are genuinely needed — for 60 people, figure about 9 ten-pound bags of ice and 90 cups — and they give the new family, the college kid, and the member who does not cook a real way to contribute that costs a fraction of a casserole. A potluck runs on more jobs than cooking, and a sheet that says so out loud spreads the load without anyone having to ask.

And when two people bring the same thing? Let them. Nobody at a covered-dish supper has ever complained about two pans of macaroni and cheese, and turning somebody’s dish away costs far more than the duplicate ever could. Abundance is not a planning failure here — it is the tradition working.

The fellowship hall, honestly

The hall gives you what no house has — long tables, a big kitchen, room for a hundred — and it hides one constraint: the oven is for holding, not cooking. On its lowest setting it keeps casseroles warm, but it fits four pans and twelve will arrive. The workhorses are slow cookers set to low: they hold themselves at a safe temperature for hours, they travel, and every congregation collectively owns about forty of them.

The food-safety line to plan around: hot food should be held at 140°F or above. Ask for a majority of dishes that are safe at room temperature — salads, breads, sliced ham, deviled eggs, most desserts — and reserve the warming capacity for the few that genuinely need it. Put the hot dishes out last, right before the blessing, not when they arrive.

Two serving-line details that matter more than they should: plates at the front, drinks at the far end, so the line does not stall where people stop to pour — and above about sixty people, run the line down both sides of the table. One-sided service is the difference between a twenty-minute line and a ten-minute one.

Three generations, one table

A church potluck is the rare party where a ninety-year-old and a nine-year-old eat the same meal, and that shapes two things worth planning for.

Label what a dish contains, not what it is free of. A small card by each pan — “contains walnuts,” “made with real bacon” — does more good than any signup field, and it fails safely: “contains nuts” is something the cook actually knows, while “nut-free” is a promise about a kitchen nobody else stood in. For the allergies that are medical rather than preference, collect them privately and pass them to the people cooking — nobody should have to announce a health condition to the whole congregation.

And count the kids as half portions when you are estimating — a table of ten under-twelves eats like five adults, which is why the supper always seems to produce leftovers. It is supposed to. Sending food home in foil is part of the liturgy.

The organizer’s calendar

Where these numbers come from

Sides run about one dish per 3–4 people because buffet portions overlap; desserts come from roughly 1½ pieces a person. Ice runs 1–1½ pounds per head and cups 1½ per person — people set a cup down at a long table and take a fresh one — rounded up to what stores actually sell. The 140°F holding line is the USDA’s. Every number on this page is generated from the same table Dinner Caddy uses to build a real shopping list, so the guide and the app cannot drift apart.