How to set up church event registration (and when an RSVP is enough)

Most church events start the same way. Someone announces it on Sunday, puts a clipboard in the lobby, and a week later there are three lists: the clipboard, a Google Form someone made for the people who were away, and a reply-all email thread. Nobody trusts the headcount, and the caterer needs a number by Friday.

Event registration fixes that by giving every event one list and one way onto it. This guide covers when a simple RSVP is enough, what to ask on a registration form, how to handle sign-up sheets and payments, and how to get from "we're going" to an accurate headcount on the day.

What is church event registration?

Church event registration is the step where people tell you they are coming and give you the details you need to run the event. It can be as small as a yes or no for a fellowship lunch, or as full as a camp form with each child's age, allergies, an emergency contact, a signed waiver and a deposit.

Whatever the size, good registration does three things:

• It gives you one list. Every way someone can say yes ends up in the same place.
• It asks only what you will use. Every extra question is a reason for someone to give up halfway.
• It closes on purpose. You choose when the list is final, and you tell people that date.

Is an RSVP enough, or do you need a registration form?

Many church events only need an RSVP. Use this as a rule of thumb:

If you are unsure, start with an RSVP. You can always ask the people who said yes for more detail later. You cannot easily get back the people who gave up on a long form.

What should the registration form ask?

Write down every decision the event depends on, then ask only the questions that feed those decisions. For most church events that is a short list:

• Name of each person attending, not just the person filling in the form. "Smith family, 4" is hard to check in.
• A way to reach them: an email address or a mobile number, so you can send a reminder or tell them about a change.
• How many are coming, with adults and children counted separately if it matters for food or staffing.
• Dietary needs and allergies when there is food. Put a free-text box, not only tick boxes; allergies do not fit neatly in a list.
• For children: age or school year, allergies and medical notes, an emergency contact, and who is allowed to collect them. Our guide to a children's ministry registration form covers this part in detail.
• Anything the event depends on: a shirt size for camp, whether someone needs a lift, which sessions of a multi-day event they will attend.

Leave out anything nobody will read. Home address, date of birth for adults and "how did you hear about us" belong on a guest card or in your church directory, not on an event form.

How do you handle sign-up sheets for the things people bring?

Many events need more than a headcount. Someone has to bring salads, set out chairs at nine and drive the minibus. That is a sign-up sheet, and it is a different list from registration: registration is "who is coming", a sign-up sheet is "who is doing what".

A sign-up sheet works when each slot has a clear name and a number:

• Salads: 6 needed. Not "bring something to share".
• Set-up crew, 9am: 6 needed. With the time, so people know what they are agreeing to.
• Ice and coolers: 2 needed. The small jobs are the ones that get missed.

Show how many are still needed, so people pick the gaps instead of adding a seventh dessert. When a slot is full, close it. If some slots should only go to one group, such as the welcome team or the parents of the children's choir, say so on the sheet.

The same idea runs a church meal train and a serving rotation: named slots, a visible count and a reminder to the person who claimed each one.

Should you take payment at registration?

Take payment at registration when the church pays a real cost for each person, such as a venue, catering, accommodation or transport. Collecting it as people sign up saves the treasurer from chasing envelopes in the car park afterwards.

A few things make paid registration fair and easy to reconcile:

• Use a deposit for big events. A retreat or camp can take a deposit when people register and the balance later. A deposit also reduces the number of people who sign up and do not come.
• Price by ticket type when it costs different amounts: adult, child, family, or a room type at a retreat.
• Keep cash and bank transfers on the same list. Some people will always pay by cheque or at the door. Mark them as paid against their registration so there is one list of who has paid, not two.
• Make it easy to come if money is tight. Offer a reduced or free place that someone can request quietly, with a named person to contact, and never ask a family to explain in public.
• Put any waiver on the form, so it is agreed at the moment of registering instead of signed on a clipboard at the door.

Collect payments into an account the church owns, with the treasurer able to see it. Avoid a volunteer's personal payment app, even for small amounts; the church's own budget approval process should cover where event money goes.

How do you get people to register who do not read church email?

The people you most want at an event are often the ones who do not read church email: newer members, young adults, visitors and families from the community. Use more than one channel, but send everyone to the same registration link:

1. Announce it on Sunday with the date and the link on the screen and in the bulletin.
2. Email it, with the registration link as the first thing in the message, not the last.
3. Post it where people already talk, such as the church app, a group chat or a small group's thread.
4. Ask people personally. For outreach events in particular, "Would your family like to come? I'll send you the link" works better than any announcement.
5. Let guests register without an account. A login screen stops the visitor you were trying to reach.

Our guide to choosing between email, text, chat and the app goes into which channel suits which message.

When should registration close, and what happens on the day?

Close registration on a date you choose, and say that date in every announcement. The right date is usually the day before someone needs your final number: the caterer, the venue, the bus company, or the children's team who need to know how many leaders to schedule.

After it closes:

• Send a reminder a day or two before, with the time, the place, what to bring and who to contact. Most no-shows forget; they did not change their minds.
• Print or open the list on a phone for whoever is welcoming people, so they can tick names off at the door.
• Have a plan for walk-ins. For a picnic, welcome them. For a kids event, have a short paper form ready so every child is still registered with an emergency contact.
• Count who came. Compare it with who registered. Next year's planning starts with that number.

Who should run registration?

One named person per event, with access to that event's list and nothing else. The volunteer running the youth retreat needs the registrants, the payments and a way to message everyone who signed up. They do not need the church's giving records or the whole directory.

If your current tool can only give that volunteer full admin access, either keep the list yourself and share a copy, or look for a tool that can grant access to one event. Handing out church-wide access to run one picnic is how private information ends up in the wrong place.

When does a form and a spreadsheet stop being enough?

A free online form and a spreadsheet are a good start for a church that runs a few events a year. It gets harder when you run several events a month, when payments and deposits come in through different routes, when sign-up sheets live in a separate document, and when every new event means building the form again from scratch.

Churchory Events is church online event registration software built for that point. Members RSVP yes, maybe or no by email and add the event to their calendar, and guests register on a public page without an account. It has sign-up sheets with live counts, room booking so two ministries do not claim the same hall, and paid events through your church's own Stripe account, with ticket types, deposits, discount codes and an optional waiver. You can name a volunteer as the organizer of one event without giving them anything church-wide. See how Churchory Events works, step by step. For retreats and camps, Retreat Builder adds rooms, rides and the budget.

Events is $25 a month or $250 a year with unlimited events and registrants, on top of the free Core plan, and Stripe's standard fees apply to paid events. If your church runs one picnic a year, keep the clipboard; it is free, and it works.