Church Retreat Registration: Forms, Deposits, and Day-of Check-In

Church retreat registration is different from registering people for a Sunday service event or a one-night dinner. You are collecting information across several categories at once — lodging preferences, transportation, dietary restrictions, medical needs, emergency contacts, and permission forms for minors — and you need all of it before departure day, not the morning the bus leaves.

A Google Form handles the data collection part but falls apart everywhere else: no payment processing, no confirmation emails with QR codes, no capacity limits, no waitlist. A general event registration platform solves most of those problems, but only if you configure it correctly for retreat-specific requirements.

This guide covers how to structure your church retreat registration form, how to handle deposits and balance payments, how to manage capacity, and what day-of check-in looks like at the departure point.

What Makes Retreat Registration Different

Most event registration asks for a name, an email address, and a payment. Retreat registration asks for all of that plus a separate set of logistical questions that affect how you plan and run the event.

Multi-day format changes everything

A multi-day retreat means attendees need to know what to bring, when to arrive, and where they are sleeping. It also means you need to communicate more before the event — packing lists, schedule outlines, travel instructions — and your registration confirmation email needs to contain more than just a QR code.

Lodging preferences and room assignments

Most retreat centers assign rooms by gender, by age group, or by attendee preference. Collecting roommate requests at registration saves you a manual back-and-forth later. Common fields: preferred roommate name, cabin or dorm preference if you offer options, and whether the attendee needs an accessible room.

Transportation and carpooling

If you are chartering a bus, you need a headcount before you book. If attendees drive themselves, you want to know who is offering rides and who needs one. Collecting transportation preference at registration lets you coordinate carpools before the confusion of departure day.

Deposit vs. full payment

Retreat costs are usually higher than a single-event ticket. Many churches collect a deposit at registration to hold a spot and collect the balance four to six weeks before the retreat. This reduces cancellations and helps you confirm the headcount for venue and catering contracts.

Youth vs. adult forms

Youth retreats require parent or guardian information, emergency contacts, medical authorization, and in many states a signed permission slip before the minor leaves the church property. Adult retreats need less of this, but emergency contact collection is still standard practice for any overnight event.

How to Structure the Registration Form

A well-structured form collects everything you need without overwhelming the person filling it out. Group fields logically so the person can move through sections without having to jump back and forth.

Section 1: Personal information. Full name, email address, phone number, date of birth (for age verification if your retreat has age groups). For youth retreats, this section collects child information, not parent information — parent details go in their own section.

Section 2: Emergency contact. Emergency contact name, relationship to attendee, and phone number. Specify that this should be a different person from the registrant. For youth retreats, the parent or guardian is typically the emergency contact and goes here.

Section 3: Lodging preference. Room type if you offer options (single, double, cabin bunk), roommate request (name), accessibility needs, and any other sleeping arrangement notes. A free-text field here catches situations your dropdown options miss.

Section 4: Transportation. Bus seat (yes/no if you are chartering), driving yourself (yes/no), offering rides to others (yes, with available seats count), needs a ride (yes/no), departure location preference if you have multiple pickup points.

Section 5: Dietary restrictions and medical information. Food allergies (dropdown with common allergens plus free-text for other), dietary preference (vegetarian, vegan, kosher, halal), medications being brought to the retreat, medical conditions relevant to staff (asthma, diabetes, seizure history, mobility limitations), and a free-text field for anything not captured by the structured fields.

Section 6: Permissions (youth retreats). Photo and video permission (yes/no), permission to receive first aid and over-the-counter medications, permission to participate in water activities if applicable, and signature acknowledgment that the parent has read the retreat policies. For legally valid permission, most churches require a wet signature on a paper form in addition to digital acknowledgment — check with your church's legal counsel or insurance carrier on what they require.

Section 7: T-shirt size. If your retreat includes a shirt, collect size here rather than in a separate communication. Sizes: youth S/M/L, adult S through 3XL. Add an “I already have a retreat shirt” option if returning attendees can opt out.

Handling Deposits and Balance Payments

The most common retreat payment model is a deposit at registration to hold the spot, with the balance due four to six weeks before the retreat date. This structure reduces last-minute cancellations because attendees have skin in the game early.

Option 1: Two separate ticket tiers

Create a “Deposit” ticket tier priced at your deposit amount (for example, $50). After the deposit window closes, unpublish the Deposit tier and publish a “Balance Due” tier priced at the remaining balance. Email registered attendees with the balance due link and a deadline. This approach is simple and works on any plan.

The downside: you have to manually track who paid the deposit and follow up with those who haven't paid the balance. An export from your registration platform filtered to deposit-only payers gives you the follow-up list.

Option 2: Collect full payment upfront with a refund policy

Some churches skip the two-step approach and collect full payment at registration with a published refund policy (for example, full refund up to 60 days before, 50% refund 30 days before, no refund inside 30 days). This is simpler to manage and eliminates the balance-collection step entirely. The tradeoff is that the upfront cost is higher, which can reduce registrations from families who want to commit but can't pay the full amount immediately.

Option 3: Scholarship and financial assistance tiers

If your church offers financial assistance, create a separate “Scholarship Rate” ticket tier with a lower price and limit it to a set number of spots. Or set the tier price to $0 and collect a note in a custom field explaining the situation — then handle the actual scholarship allocation offline. Keeping scholarship spots off the public form avoids abuse while still giving you a clean way to track who is on assistance.

Managing Capacity

Retreat capacity is usually constrained by the venue — cabin beds, bus seats, or a retreat center's maximum group size. Set a hard registration cap on your event so you don't oversell.

Per-tier capacity

If you are running youth and adult retreats on the same trip with separate lodging, set capacity limits per ticket tier (Youth: 40 spots, Adult: 30 spots). This prevents accidentally selling more youth spots than your youth cabin can hold while adult spots remain open.

Waitlist

Once capacity is reached, new registrants should see a clear message that the retreat is full and an option to join a waitlist. Communicate the waitlist policy upfront: what order waitlisted registrants are moved, by what date you will confirm their spot, and whether they need to pay a deposit to hold their waitlist position.

Communicating closures

When registration closes — either because capacity is full or because the registration deadline has passed — update your event page to say so explicitly. “Registration is closed. Contact the church office to inquire about availability.” is better than leaving a broken or empty form up. If you collect walk-in registrations, note that on the page too.

Day-of Check-In at the Departure Point

Bus departure check-in is more compressed than event-door check-in. You have a fixed departure time, a finite number of seats, and attendees arriving in a rush in the last ten minutes before you need to leave.

QR code scanning

Each registered attendee receives a QR code in their confirmation email. Check-in volunteers scan codes at the bus door — one scan, and the attendee is marked present. No searching a paper list by name, no re-entering information. For youth retreats, scan when the child boards the bus; the parent standing there gets confirmation their child is checked in.

Assign at least two check-in volunteers: one scans, one handles walk-ins, last-minute questions, and attendees who can't find their QR code. The list is cached locally on the scanning device, so parking-lot WiFi issues don't block check-in.

Rooming lists

Print a rooming list from your registration export the night before departure. Sort by assigned room or cabin. Each room leader should have their list before boarding — not when they arrive at the retreat center. Include the lodging preference and roommate request columns in the export so you can finalize assignments during the bus ride if needed.

Bus seat assignment

If you chartered a bus and assigned seats, include the seat number in the confirmation email. Check-in volunteers can call out seat numbers as attendees board to keep the aisle clear. For small groups where assigned seating is overkill, a simple numbered list of who is on the bus is enough to reconcile against your headcount before departure.

Handling no-shows and last-minute additions

Before departure, compare your checked-in count to your registered count. For no-shows, decide your cutoff time: if someone is not there five minutes before departure, their spot on the bus goes to a waitlisted attendee or is forfeited. Communicate this policy in the pre-retreat email so no one is surprised.

Last-minute additions — a friend who shows up with a registered attendee — need a paper form and a seat assessment before they board. Have a blank registration form available. Do not add people without capturing emergency contact and medical information first.

Frequently Asked Questions

Can we use the free plan for a small church retreat?

Yes. CompleteEvent's free plan covers events up to 100 attendees with full custom form support. For a youth retreat or small adult retreat with 25 or fewer attendees, the free plan handles registration, confirmation emails, QR check-in, and export. The 25-spot cap applies per event, not across your account, so you can run multiple retreats per year.

How do we collect a deposit now and the balance later?

The simplest approach is two ticket tiers: a Deposit tier active during early registration, and a Balance Due tier you open later for the same registrants. Export your deposit payers, email them the balance link with a deadline, and unpublish the Deposit tier once the balance window opens. Alternatively, some churches collect full payment upfront with a clear refund policy and skip the two-step process entirely.

How do we handle registration for minors?

Add parent or guardian name and phone number, an emergency contact different from the parent, and a permissions section (photo, first aid, water activities) to your registration form. For legally binding permission, most churches pair digital registration with a paper permission form signed by the parent. Check your church's insurance policy for what they require — some carriers mandate a paper signature for minors traveling overnight.

What does check-in look like at the departure point?

Each registered attendee has a QR code in their confirmation email. Check-in volunteers scan the code on any smartphone — no dedicated hardware, no app download. The attendee is marked present in real time. The full attendee list is cached locally so poor or absent WiFi at the parking lot doesn't block check-in. Print a backup list the night before in case a phone dies or a battery runs out.

What if someone shows up who didn't register?

Have a paper form ready that mirrors your digital registration form. Collect name, emergency contact, medical information, and any required permission before they board. Add a late-registration note and enter their information into your system after the retreat for your records. Do not allow someone to participate in an overnight retreat without capturing emergency contact and medical information first.

Set up your church retreat registration with CompleteEvent — free for small retreats, 20% nonprofit discount on paid plans.