Meal sign-ups: potlucks, meal trains, and snack schedules

Potlucks, meal trains, and snack schedules are all “food sign-ups,” and people build them the same way, which is why potlucks get nine desserts, meal trains get three lasagnas on Tuesday and nothing Thursday, and the snack schedule collapses in week four. They are three different shapes. This guide builds each one in MojoSignUp and explains why the shape is different.

The potluck: one date, dish categories with capacity

A potluck is a single event where the variety of food matters more than the count of people. The failure mode is everyone bringing the easy thing. The fix is to make the categories explicit and cap them.

Build it as one sign-up with one instance for the date. On that instance, add slots for the categories, not for individual dishes: “Main dish · 8,” “Side or salad · 8,” “Bread or rolls · 3,” “Dessert · 6,” “Drinks · 3,” “Plates, cups, napkins · 2.” The numbers are capacities. When six people have claimed dessert, dessert disappears from the chooser and the seventh person brings a salad. That is the entire mechanism, and it is the one thing a group chat cannot do.

Size the categories to the crowd. For forty people, eight mains and eight sides is generous. For fifteen, four and four. If you want people to say what they are bringing, ask for it in the registration form so “Main dish” is not eight mystery casseroles, but keep the categories as the slots. Do not make a slot per specific dish. Nobody signs up for “Aunt Linda’s green bean casserole” except Aunt Linda, and when she does not come, the slot sits there.

Put the practical facts in the description: whether there is an oven or a fridge, whether to bring a serving spoon, when to arrive with hot food. Leave public listing off unless the event is genuinely open to strangers. The 40-person potluck worked example walks through exact numbers.

The meal train: one meal per day, capacity 1

A meal train is the opposite shape. It is one dish per day, for a family that just had a baby or a surgery or a loss, over two or three weeks. The failure mode is clumping: everyone picks the first few days, the family freezes lasagna, and week two is empty.

Build it as one sign-up and one instance per delivery day, each with capacity 1. Use recurrence to generate the dates: daily or every other day for the span you agreed with the family, then delete the days they said they do not want. Every other day is usually right. Families receiving meals are also receiving leftovers, and a meal every day for three weeks is more food than most households can eat.

Capacity 1 on each instance does the anti-clumping for you. Once Tuesday is taken, the next person sees Wednesday. The dates that are still open are visible to everyone, so the gap in week two is obvious to the person deciding when to cook, which is exactly what you want. If you have more volunteers than days, add days or tell the extras they are the backup for cancellations. There is no waitlist; when someone unregisters, the day reopens for whoever looks next. How to schedule repeating dates covers generating and pruning the series.

Privacy matters more here than for any other food sign-up. Do not put the family’s address, phone number, or the reason for the train on the page. The page is visible to anyone with the link, and links get forwarded. Put “delivery details will be sent to you after you sign up” in the description, then send the address directly to each person on the roster. The organizer can see every registrant’s email. Use it. Dietary restrictions go in the description because everyone cooking needs them, but keep it to the food: “no nuts, no shellfish, one adult is vegetarian.”

The snack schedule: weekly recurrence, small capacity

A team snack schedule or a classroom snack rotation is a series of identical small jobs: someone brings snacks this week. The failure mode is the schedule that is fully claimed in September and half abandoned by November, because people signed up for a date in the abstract and forgot.

Build it as one sign-up with a weekly recurrence for the season, capacity 1 or 2 per date depending on whether you want a backup. Do not add slots. Snack is snack. If there are two kinds of job, like “snack” and “drinks,” those are two slots per instance, but resist the urge to add “napkins” as a third. Whoever brings snack brings napkins. Say so in the description.

Generate the season, then delete the bye weeks and holidays right away. A phantom snack date on a week with no game is how someone shows up to an empty field with orange slices. Put the opponent or the occasion in the instance title if it helps people match the sign-up to the calendar they already have.

Ask people to sign up for at most two dates in the first round. If everyone claims their preferred date on day one, the season fills unevenly and the family that travels in October is stuck with October. Two passes, a week apart, fills a season more fairly than one free-for-all. The sports teams guide covers the rest of the season logistics.

Reminders, and what they do not do

Organizers can turn on an SMS reminder that fires 30 minutes before the instance start. For a potluck, that is useful: it is the “leave now with the hot dish” nudge. For a meal train, a 30-minute warning is too late to cook, so send a message the day before yourself. For a snack schedule, the reminder helps the person who forgot it was their week, as long as the instance start time is the game time and not midnight.

The confirmation email people receive when they register is the reminder they will actually look for. It has the date, the sign-up name, and the unregister link. Tell people to keep it.

Allergies and dietary needs

There are two kinds of allergy information, and they go in different places. The needs of the people eating go in the description, because everyone cooking has to see them. “Two kids with nut allergies, please no nuts in anything” is a public fact about the event, stated without names.

The details of what each person is bringing, and any ingredient list, go in the registration form where organizers can read them and choose what to relay. Do not echo a family’s medical information back onto the public page. If you need to publish a label at the table, do that on paper at the event, not on the sign-up.

When someone drops out

In all three shapes, the person who cannot make it should use the unregister link in their confirmation email. The spot reopens immediately. If they message you instead, remove them from the roster so the open spot is visible to the next person who looks, then post in the chat that Thursday is open again. Two lines in the chat plus an accurate page beats a private scramble. How attendees unregister has the details.

Building each one, in order

1. Potluck. One sign-up, one instance for the date, slots per food category with capacities sized to the crowd. Ask what they are bringing on the form.
2. Meal train. One sign-up, recurrence every other day for the agreed span, capacity 1 per instance, delete unwanted days. Address goes to registrants directly, never on the page.
3. Snack schedule. One sign-up, weekly recurrence for the season, capacity 1 or 2, no slots. Delete bye weeks now. Two sign-up rounds, a week apart.

For every one of these, register yourself once in a private browser window before you send the link, confirm the email arrives, and unregister. The first-event tutorial is the same check in more detail.