Do we need a form at all, or can people just tell us at the door?

For anything with a headcount that matters — a meal, childcare, seating, supplies bought per person — you need a number before the day arrives, which means you need a form. For a come-as-you-are event with no capacity limit, a sign-up sheet in the lobby is honestly fine. Save the form for events where the number changes what you do to prepare.

Should we ask for a phone number or an email address?

Ask for whichever one you will actually use to reach people, and only that one. If your reminders go out by text, take the phone number and skip email. If you send a printed itinerary by email, take the email and skip the phone number. Asking for both because you might need one someday is how a two-field form becomes a four-field form.

What about dietary restrictions and allergies?

Ask only if you are serving food you control the menu for — a sit-down dinner, a retreat with catered meals. For a potluck or a cookout where people bring their own plate, the field collects information you cannot act on, which makes it noise. If you do ask, one open text field beats a checklist of nine allergens; people will tell you what matters in their own words.

Is it okay to require a name and nothing else for a low-stakes event?

Yes, and for a lot of church events that is the right call. A trunk-or-treat, a movie night, a park cleanup — these do not need contact information at all if you are not sending a confirmation or a reminder. A single name field that tells you roughly how many are coming is enough. Add fields only when a specific downstream task needs them.

How long should we keep registration data after the event is over?

Long enough to do the follow-up you intend to do, and not much longer. If a guest signed up for a fall festival and you want to invite them back for Easter, keep the name and how you reached them. Drop the rest — the allergy note, the T-shirt size, the emergency contact — once the event that needed it has passed.

Setting up a simple registration process for a church event

Somewhere in most churches there is a registration form with fourteen fields on it for a chili cook-off. Name, phone, email, emergency contact, dietary restrictions, T-shirt size, how did you hear about us, do you need childcare, do you need a ride, any accessibility needs, are you bringing a dish, which dish, spouse’s name, spouse’s dietary restrictions. Nobody set out to build that form on purpose. It grew, one well-meaning field at a time, because somebody once needed to know a T-shirt size and nobody ever took the field back out.

The fix is not a better form builder. It is a different question asked before you build the form at all: what will we actually do with each piece of information we collect? If there is no clear answer, the field does not belong on the form. This is not about being minimalist for its own sake — it is about the plain fact that every field you add costs you signups, and most churches are trying to get more people to show up, not fewer.

Start from the task, not the template

Before you open a form builder, write down what you need to do before the event happens. Not what would be nice to know — what you will act on. A meal needs a headcount three days out so the kitchen can shop. A retreat with bunk assignments needs to know who is coming with whom. A kids’ event needs an adult name attached to each child. Everything else is curiosity dressed up as a form field.

This matters because the person filling out the form is doing math in their head, even if they do not realize it: how long will this take, and is it worth it. A three-field form gets filled out standing in the church lobby with one thumb. A twelve-field form gets bookmarked for later, and later rarely comes. If you are planning the event itself, decide what the form needs to accomplish at the same time you decide what the event needs to accomplish — they are the same conversation, not two separate ones.

The fields that almost always earn their place

Name. Not negotiable. You need to know who is coming, even for a headcount-only event.
One way to reach them — phone or email, not both. Pick whichever channel you will actually use for the reminder or the confirmation, and ask for that one. Two contact fields is almost always redundancy, not resilience.
A number, if the number changes anything. “How many in your group” matters for a meal or a seating chart. It does not matter for a park cleanup where everyone just shows up.
Age or grade, only if it changes logistics. A children’s event needs to know who is a toddler and who is old enough for the craft with scissors. An adult small-group kickoff does not need anyone’s age at all.

Four fields, and for a large share of church events, that is the entire form. It is not incomplete. It is complete for what the event actually requires.

The fields that usually do not earn their place

Every one of these shows up on real church forms, and every one of them can be justified in isolation. The problem is that isolation is not how forms get built — they get built by stacking isolated justifications until the form is exhausting.

Emergency contact, for events with no elevated physical risk. Save it for the ropes course, not the potluck.
Dietary restrictions, for a potluck or a bring-your-own-plate cookout where you have no control over what is served anyway.
“How did you hear about us,” asked of people who are already members and already on your list. It is a marketing question wearing a registration costume.
Address, unless you are mailing something physical, which almost nobody is anymore.
A comments box, left open and unlabeled “in case people want to add anything.” It rarely gets used, and when it does, it is usually a question better answered by a person than a text field.

None of these are wrong to ask, ever. They are wrong to ask by default. Ask them when the specific event needs the specific answer, and leave them off the rest of the time.

Guests are not members, and their form should not pretend otherwise

A first-time guest signing up for a Saturday workday does not need to be asked their household size or whether they are interested in a small group. That is a second conversation, not a first-form field. Registration is not the moment to build out someone’s full profile — it is the moment to get their name down and get them in the door. What happens after they show up is a separate, slower path that starts with a real conversation, not a checkbox they ticked before they ever met anyone.

This is also why the registration form and the follow-up plan should be designed together but kept operationally distinct. The form’s job is capacity planning: who is coming, how many, any logistics that change what you prepare. The follow-up’s job is relationship: who showed up, who to call, who noticed them. In SundayBridge, a name from an event registration can become a follow-up with an owner and a date if that guest is new — but the registration form itself should stay narrow, and the follow-up decision should happen after the event, by a person looking at who actually walked in.

Match the form’s weight to the event’s weight

A Wednesday night trivia game and a weekend retreat with an overnight stay are not the same kind of event, and their forms should not look alike. The retreat genuinely needs an emergency contact and a room preference and maybe a medical note. The trivia night needs a name and a rough headcount for how many tables to set up. Copying the retreat form’s rigor onto the trivia night’s signup is how low-stakes events end up with high-stakes paperwork, and it is a quiet way to talk people out of coming to something that was supposed to be easy.

A useful gut check: if a field would embarrass you to ask about a hot dog cookout, it does not belong on the form for the hot dog cookout, no matter how useful it might theoretically be.

What to do with the list once the event is over

The registration list is not the end of the story — it is the start of one, and then it should mostly be let go. Keep what you will use again: a name, and the channel you reached them through, if you plan to invite the same people to something similar later. Drop what was single-purpose: the dietary note for that one dinner, the room assignment for that one retreat, the T-shirt size for that one 5K. Carrying every event’s full form forward indefinitely is how a person record ends up cluttered with details nobody will ever look at again, which makes the details that actually matter harder to find when you need them.

If the event revealed something worth remembering about a person — a first-timer who came back for the second cookout in a row, a family that clearly needs childcare at everything you run — that belongs in their ongoing record, not just in the spreadsheet for last month’s event. That is a judgment call made by a person after the fact, not a field on the original form.

A short form is not a lazy form

There is a temptation to treat a long form as thorough and a short one as careless. In practice it runs the other way. A long form is usually a sign that nobody stopped to ask what each field was for — it is the paperwork equivalent of clutter. A short form that asks exactly what the event needs and nothing else takes more thought to build, not less. It means somebody sat down before the event and decided, deliberately, what mattered.

That discipline pays off twice: more people finish the form because it took thirty seconds, and the person reviewing signups afterward gets a clean list instead of nine columns of half-answered questions. Fewer fields, chosen on purpose, beats more fields, added out of habit, almost every time.