Events

Church event registration: how to run sign-ups for a potluck, retreat, VBS or paid event

What to ask on the form, when to close it, how to handle money and waitlists, and a six-week timeline you can copy.

By Steven Chen · November 9, 2026 · 11 min read

What does registration need to do for your event?

Start from the decision the registration has to feed. Every event has at least one number or fact that someone has to know before the day:

• Potluck: roughly how many are coming, and whether you have six desserts and no main dish.
• Retreat: who has paid a deposit, who needs a ride, who is sharing a room, and which dietary needs the venue has to hear about.
• VBS: each child's name, grade, allergies, who may pick them up, and a parent you can reach at 10:15 on a Tuesday.
• Paid dinner: an exact count for the caterer, seating, and who has paid.

Write that decision down first. It tells you what the form asks, when the deadline falls, and what "full" means. If the answer is "I just need a rough headcount," you want an RSVP, not a registration form. The churchory.com guide to church event registration covers that choice in depth; this article is about running the thing.

What should a church event registration form collect?

Ask for what you will use, and nothing else. Every field you add is a reason to put it off and never come back. A good test: for each field, name the person who will read the answer and what they will do with it. If you can't, delete it.

Fields for every event

• Full name of the person registering
• Email address
• Mobile phone (for day-of changes)
• How many people they are registering, with names if you need name tags or seating
• One optional "anything we should know?" box

Fields by event type

Two things people forget. Ask for the mobile number, not "phone," because you will text people on the day. And for anything with kids, collect the information once and keep it: a family that filled in allergies for VBS should not do it again for the fall festival. The children's ministry registration form guide on churchory.com lists what a kids form needs in detail.

How do you set a registration deadline that holds?

Tie the deadline to a real decision, and say so. "Register by Sunday the 14th so we can give the caterer a count on Monday" is a deadline people respect. "Please register soon" is not. Work backwards:

1. Find the latest date you can change the number: the caterer's count, the venue's rooming list, the T-shirt order.
2. Subtract two or three days to chase stragglers and tidy the list. That is your published deadline.
3. Decide now what happens after the deadline (no more sign-ups, a late fee, or "come, but we can't promise food") and put it on the form.

Expect a rush in the last 48 hours. That is normal. For a potluck, a soft deadline is fine: say "let us know by Thursday" and accept walk-ins. For a retreat, make the deposit deadline firm. A deposit is the only thing that turns "I'm interested" into a number you can book rooms against.

How do you handle capacity and a waitlist?

Set the capacity before you open registration. The number comes from the room, the venue's bed count, your adult volunteers for a kids event, or the seats in the vans. Write it on the form: "Space for 40." When you hit it, close sign-ups and open a waitlist:

• Record when each person joined, and offer spots in that order.
• When a spot opens, give the next person 24 hours to confirm. If you don't hear back, move on and tell them you did.
• Tell people where they stand. "You're third on the list" is kinder than silence.
• Close the waitlist a few days before the event, or when it is longer than the cancellations you can realistically expect.

For a retreat, one more rule: a spot is not confirmed until the deposit is paid. Say that on the form, so moving an unpaid name to the back of the list never feels personal.

How should a small church run a paid event?

If the event has a real cost per person, take the money at registration. Chasing checks afterwards eats more volunteer hours than any other part of a retreat, and a person who has paid is a person who is coming.

Deposits, balances and scholarships

For anything that costs more than a dinner, offer a deposit and a balance date. The deposit should cover what you lose if the person cancels (the venue's per-bed charge, for instance). Set the balance due a week before you have to pay the venue, not the day of.

Always have a quiet way to ask for help. A line on the form that says "If cost is a barrier, email the pastor and we'll work it out" takes the hardest conversation out of the lobby.

Refunds

Write a refund policy before the first person pays, and print it on the form. A common pattern: full refund until the deposit deadline, deposit kept after that, no refund inside the final two weeks unless the church cancels. Apply it the same way to everyone. Exceptions become the rule within a year.

Taking the payment

Use an online payment processor connected to the church's own bank account, so the money lands where your treasurer can see it. Processors charge a fee per transaction; allow for it in the price. Ask your treasurer or accountant how to record paid events, and keep them separate from giving: registration fees are not donations and should not appear on a year-end giving statement.

For a retreat, this is where registration and planning meet: who has paid decides who gets a bed, and who gets a bed decides what the weekend costs. Tools built for that, such as Churchory's Retreat Builder, keep the room list and the budget next to the registration list.

What reminders should you send, and when?

Three messages carry most events. Send more and people stop reading.

1. One week before the deadline. "Registration for the retreat closes Sunday. We have 12 spots left." Scarcity that is true is the most honest motivator you have.
2. The day before the deadline. Short. Link, deadline, one sentence.
3. Two days before the event, to registered people only. Time, address, what to bring, where to park, who to text if they are running late. Do not send this one to the whole church.

Use the channel your church already reads: for most small churches, the weekly email plus an announcement from the front. If you are still working out which channel reaches whom, our church communication plan article covers it. Send the event-day details from an address people can reply to. Half the replies will be "can I still bring my cousin," and you want those before the day, not at the door.

How do you check people in at the door?

A check-in table welcomes people, confirms who came, catches payments and walk-ups, and keeps the event lead from standing at the door all night.

The night before

• Print the registration list sorted by last name, with the columns the door needs: name, party size, paid or owing, dish or meal choice, and any note.
• Print a second copy. One gets coffee on it.
• Add ten blank lines at the bottom for walk-ups.
• Pre-print name tags in alphabetical order, with blanks for walk-ups.
• Pack a way for walk-ups to pay: a card reader, a QR code for your online form, or a cash envelope and receipt book. Decide the walk-up price.

At the table

Two people is the right number for anything over 30 guests: one to find names and tick them off, one to handle payments, questions and name tags. Recruit them the way you recruit any Sunday role (our church volunteer schedule article covers it), and train them on three sentences: "Welcome, what's your last name?", "You're all set, food is through there," and "No problem, let me add you." Let them say yes to walk-ups, so nobody has to find the pastor.

Tick off attendance as people arrive. The list of who registered and did not come is the most useful list you will have afterwards. For a kids event, the door is also where allergy notes and pickup rules get checked, which is a different process; see our guide to a church check-in kiosk for that.

How do you follow up after the event?

Do this within three days, while everyone still remembers.

1. Thank everyone who came, by email or text, with one photo and one sentence about what comes next.
2. Write a different note to the people who registered and did not come. "We missed you Saturday, hope everything is ok." No guilt. Some had a sick kid; a couple are drifting, and this is how you notice.
3. Ask one question, not a survey. "What is one thing we should do differently next time?" Reply-by-email gets more answers than a form.
4. Record the attendance and the money while it is fresh: registered, came, walk-ups, total paid, refunds, and the one thing to change. Next year's planner (probably you) will thank you.
5. Follow up with first-timers. A guest who came to the chili cook-off because a member invited them has made a first visit, and it deserves the same follow-up as a Sunday. Our first-time guest follow-up article has a plan for it.

If you took registrations for VBS or a retreat, you also have updated family information. Put it into your main member list rather than leaving it in the event form.

A registration timeline, from six weeks out to the week after

This is for a retreat or a paid dinner. For a potluck, compress it: open three weeks out, one reminder, print the list.

One person should own all of this, named out loud, and ideally not the pastor. That person should be able to open the form, see the list and issue a refund without asking anyone.

When is a form and a spreadsheet enough?

For most of what a small church does, a free online form feeding a spreadsheet is enough, and you should not feel behind for using one. It is enough when one person runs a handful of events a year, nobody pays (or payment is a check in a basket), capacity is not a real constraint, and the reminder is an email you were sending anyway.

A potluck, a Christmas Eve headcount, a church workday: form plus spreadsheet, every time. The potluck sign-up template on churchory.com is a good start.

When does event software help?

The spreadsheet starts to hurt when several of these are true at once:

• Money is involved and someone matches payments to names by hand.
• More than one person runs events, each with their own form, their own list and their own version of the family's phone number.
• The same families register for VBS, the fall festival and the Christmas program, and retype their kids' allergies every time.
• Two ministries keep booking the fellowship hall for the same Saturday.
• The retreat has rooms, rides, a budget and a deposit schedule, and you are tracking them across four tabs.

What changes with software is not a prettier form. Registration connects to the people already in your church directory, so a family's details are entered once; payment and registration are one record, so "who has paid?" is a glance; and the event lead can be given the event without the whole system. If you are weighing that step, our buyer's guide to choosing church management software for a small church covers what to look for.

Core is free forever, every product has a 45-day trial with no card, and you can start at app.churchory.com/signup. Or start with the form and the spreadsheet this Sunday, and come back when the retreat gets complicated.

Common questions

What is the difference between a church RSVP and event registration?

An RSVP is a yes, maybe or no with a headcount. Registration collects details you have to act on, such as a dish, a room preference, a child's allergy or a payment. Use an RSVP when a count is all you need, and a registration form when you need to know who is coming and what they need.

How far in advance should a church open event registration?

Four to six weeks before the event for most things, and eight to ten weeks for a retreat or anything with a deposit. Open it when you can announce it from the front, and close it when your last real decision (food, seats, T-shirts) has to be made.

Should a small church charge for events online?

If the event has a real cost per person, such as a retreat or a catered dinner, taking payment at registration saves chasing checks and tells you who is serious. Use a payment processor connected to the church's own bank account, publish a refund policy up front, and check the setup with your treasurer or accountant.

What should a church event registration form ask?

Only what you will use: name, email and phone for everyone, then event-specific fields such as the dish they are bringing, dietary needs, number of children and their ages, an emergency contact, or a room preference. Every extra field costs you sign-ups.

How do you handle a waitlist for a church event?

Set your capacity before you open registration, close sign-ups at that number, and keep a dated waitlist. When someone cancels, offer the spot to the next person with a 24-hour deadline to confirm, then move on.

How do you get church members to actually register?

Announce from the front, put the link in the bulletin and the weekly email, and have a greeter with a tablet or paper list in the lobby for two Sundays. Then send one reminder a week before the deadline and one the day before.

Small Church Admin is written by the team behind Churchory. Choosing software? Read how a small church should choose church management software.