Groups

How to organize a potluck sign-up that actually balances the meal

Stop hoping people self-sort into mains, sides, and dessert. Give the sign-up sheet categories instead.

7 min read

Ask AI · in the $19/mo plan

Ask your own records a question. Which groups have stopped growing?” — answered from the records you already keep. It reads your church and no other, and it can't invent a number.

10 questions a month included · no AI add-on to buy

Every church potluck has the same failure mode. Someone puts a sign-up sheet on a table in the lobby, twenty-two people write their names on it, and on the night of the meal there are eleven pans of dessert, four bags of chips, and one crockpot of chili for a room of ninety people. Nobody did anything wrong. They just signed up for whatever felt easy, and dessert is always easy.

The fix is not a better sign-up sheet. It is a sign-up sheet with categories on it, and someone willing to nudge people toward the empty ones. That is the whole method, and it works whether you run it on paper, in a shared spreadsheet, or through whatever your church already uses to list an event.

Why the self-sorting sheet fails

A blank sign-up sheet asks people to make a decision they are not equipped to make: what does this meal need? Most people do not know how many other families are coming, what anyone else has already claimed, or whether the church leans toward big eaters or grazers. So they default to whatever is fastest to make or whatever they already have a good recipe for. For a huge number of home cooks, that default is a dessert or a bag of something from the store. Mains take planning, a bigger pan, and usually a trip to the store for meat. Nobody defaults to a main.

The result is a meal that is technically fully signed up and practically unbalanced. You do not find out until the tables are set, which is the worst possible time to discover you are short on food people can actually make a plate from.

The three-and-a-half category method

Instead of one open sign-up, split it into categories and give each one a target number:

  • Main dishes — casseroles, meat, a big pot of something. This is the category that always runs short and needs the most gentle pushing.
  • Sides — vegetables, salads, rice, potatoes, anything that is not the center of the plate.
  • Desserts — this category fills itself. You will rarely need to ask twice.
  • Bread, drinks, or paper goods — a half-category for the low-effort items that still need to exist: rolls, cups, ice, napkins.

Put a number next to each category on the sign-up — “we need 10 mains, 3 more spots left” — and people will fill the gaps you show them. Show no numbers, and they will fill the gaps they feel like filling.

Figuring out how many of each you need

Start from an honest headcount, not a hopeful one. If 90 people usually show up on a normal Sunday and this is a normal Sunday potluck, plan for 90, not the 140 you would get if every family that ever comes showed up the same week. A workable rough split for a sit-down potluck is one dish per five to six people, distributed as roughly a third mains, a third sides, and a third desserts and extras. For 90 people that lands near 15 dishes total: 5 mains, 5 sides, 5 desserts, with bread and drinks handled by whoever is already bringing the coffee urn.

The math does not need to be precise. It needs to exist. A number on the sheet, even a rough one, turns the sign-up from a guessing game into a checklist.

Building the sign-up itself

The tool matters less than the categories, but a few habits make any tool work better:

  • List the category, then the slot count, then blank lines. “Mains (need 5): 1. ___ 2. ___” reads as a job to finish, not an open invitation.
  • Ask for a rough headcount alongside the dish. “How many will your dish serve?” catches the family who was planning to bring a small bowl of something for four people to a potluck of ninety.
  • Put one person's name on the sheet as the point of contact. Not to police it — just so someone can answer “did we get enough mains yet” without guessing.
  • Close the sign-up a few days early, not the morning of, so there is time to fill a gap by asking a specific person directly.

A paper sheet on a clipboard works for a single event. A shared spreadsheet works better once more than one person needs to see it at the same time. If your church is already planning the event somewhere — a calendar, a bulletin insert, wherever people go to see what is coming up — the sign-up sheet should live next to that, not in a separate group text nobody remembers to check.

The week-before gap check

Every potluck sign-up looks lopsided a week out, because desserts fill first. That is normal and not yet a problem. The actual check happens three to four days before the meal: count what is signed up in each category against the target, and if mains are short, ask two or three specific people rather than posting a general reminder. A general reminder reaches the people who already signed up. A direct ask reaches the people who have not thought about it yet.

This is also the moment to look at who tends to sign up every time and who has not brought anything in months — not to guilt anyone, but because a personal ask lands better than a sheet ever will, and it is easier to make if you actually remember who is who. Keeping that picture current is part of what a weekly admin rhythm is for — a few minutes to notice patterns before they become the same three families doing everything.

Where a lightweight system actually helps

None of this requires software. It requires categories, a target number, and a person willing to ask. Where a system earns its keep is on the headcount side of the equation: if your church already tracks who registered for the gathering, you know the 90 you are planning for is a real number instead of a guess carried over from last time. SundayBridge's event calendar handles that part — you create the gathering, people register, and you can see the count — but it does not run the category sign-up itself. That part still lives on a sheet or a spreadsheet next to it, and that is fine. The sign-up is a five-minute job. The part worth not losing track of is who is actually coming.

The problems that show up every single time

A few things happen at nearly every potluck, and it helps to expect them rather than be surprised:

  • Someone brings three desserts. Kindly redirect them toward a side next time, or just let it be — extra dessert has never ruined a potluck.
  • The main-dish category is always the hardest to fill. Consider asking one or two families ahead of time to anchor it, rather than hoping the sheet fills itself.
  • Dietary needs get missed. Add one line asking contributors to label a dish if it is vegetarian, nut-free, or gluten-free, and set those dishes together with a small card. It is a tiny ask that solves a real problem for a handful of people every time.
  • New families do not know they are welcome to bring anything. A line at the bottom of the sign-up — “new to church? Come as you are, food is optional” — removes the awkwardness of showing up empty-handed to something that looks like a club.

None of this is complicated. It is the difference between hoping a meal balances and building a sheet that makes it balance on its own, one category at a time. After the event, whatever you noticed — the three new families who came, the couple who brought a main for the first time — is worth carrying into what happens after the big Sunday, since a shared meal is often the easiest place a new person actually talks to someone.

Frequently asked questions

How many dishes do we actually need for a church of 150?
A common rule of thumb is one serving-size dish per five to six people, split across categories. For 150 people that is roughly 25 to 30 dishes total — call it 10 mains, 10 sides, 8 desserts, and a couple of drink or bread contributions. Adjust up if your crowd tends to eat light on mains and heavy on dessert, which most crowds do.
What if someone signs up but does not show up with food?
It will happen at every potluck of any size, which is why the categories need a small buffer built in rather than an exact count. Aim for slightly more sign-ups than the math requires in the main and side categories specifically, since a missing dessert is a minor letdown and a missing main is a real gap.
Should we ask people what they are bringing, or just how many people are coming?
Both, and they are two different questions. A headcount tells you how much food you need in total. A category sign-up tells you whether the food you are getting is the food you need. Skipping the category question is exactly how you end up with nine desserts and one pan of chicken.
Is a spreadsheet good enough, or do we need an app?
A shared spreadsheet with three tabs, one per category, works fine for a single event and is often the right amount of tooling. The friction shows up when you are running potlucks every month and re-explaining the categories, chasing the same three families for headcounts, and losing track of who came last time — that is a repetition problem, not a spreadsheet problem.
How do we handle dietary restrictions without singling people out?
Add one line to the sign-up asking contributors to label their dish if it is vegetarian, nut-free, or gluten-free, and place those dishes together on the serving table with a small handwritten card. That solves it for everyone who needs it without requiring anyone to explain their diet out loud to a greeter.