Yoga Retreat Registration Form: Template and Field Guide

Say a retreat fills fourteen spots. Nine deposits have landed in Stripe; of the other five, two guests plan to pay on arrival and three have gone quiet. Eleven waivers are signed and three are not, and nobody can confirm whether those three are also the unpaid ones. Departure is close enough that the inbox is now the only record that matters.

Why One Registration Page Is Doing Three Jobs

Most hosts run registration out of three places: a payment link pasted into an email, a waiver saved in a separate folder, and a spreadsheet reconciled by hand. Take a retreat at $2,400 a head for 14 guests, booked months out. One missing balance in that group is $1,800 or more, and nobody sees it coming when payments, waivers, and health notes sit in different tools. If you are still planning the retreat itself, settle the registration flow at the same time as the venue and the schedule.

Guests increasingly find and book retreats online, and market trackers such as DataIntelo's yoga retreat market report now break reservations down by booking channel. In practice, the first screen a guest sees has to work on a phone.

That screen is doing three jobs at once:

• Commit. Name, email, date, and a payment that holds the place.
• Collect. Health notes, diet, emergency contact, and a signed waiver.
• Get paid before arrival. Balance, installments, and cancellation terms the guest already accepted.

The fix is timing, not fewer fields. Committing takes two minutes and a card, so give it the whole page and let it close fast. Collecting and getting paid can wait until the booking exists: a waiver reminder sent next week still lands, while a deposit that stalls at checkout is gone.

Each job fails when it shares a page with the other two.

Field-by-Field Registration Template

Read the table as a stage map. Booking rows gate the deposit. Pre-arrival rows feed the manifest and the lead teacher. Required means the booking cannot close, or the retreat cannot run safely, without the answer. Optional means you ask only when the retreat offers that choice.

Beyond name, email, and the deposit, three answers are required: an emergency contact, an injury or condition note relevant to practice, and a signed waiver. Dietary questions appear only when meals are included. Transfer questions appear only when you offer transfers. Passport fields appear only for international guests.

The yoga-specific rows cover experience and style, an injury question that accepts none, a neutral optional pregnancy question with a speak-to-us route, mobility, preferred intensity, hearing or vision needs, and a roommate request. Turn each row into one field or one task so nothing is asked twice.

Yoga retreat registration fields by stage

Practical rule: If a field does not change the booking, the teaching, the kitchen, or an emergency response, it does not belong on the form.

Splitting Booking From Pre-Arrival Tasks

Stage 1 holds the spot. Collect name, email, phone only if you need it that day, retreat date, room or occupancy preference if you offer it, and the deposit, installment, or full payment choice. Every extra field sits between interest and a deposit. If an answer does not stop the booking from closing, it moves to stage 2.

Stage 2 opens as soon as the booking exists, with deadlines counted back from the departure date. Health and injury notes, dietary needs, the emergency contact, passport details, experience level, the waiver, and arrival details all belong here. Only the details you need to confirm the place stay at checkout.

A 60-day lead time

1. Day 0. The guest books and pays the deposit. The spot is held.
2. Within the first week. Pre-arrival tasks appear. Balance reminders follow the schedule you set.
3. About 30 days out. Health, dietary, and waiver tasks are due.
4. 7 to 14 days before arrival. Guests correct allergies, injuries, emergency contacts, or arrival plans.

Put a due date on each pre-arrival task before the retreat page goes live. For a day-long workshop or a weekend, skip the 60-day arc: collapse stage 2 into one task due seven days out, with the waiver inside it.

A long checkout does not make a safer retreat. It just delays the deposit.

Health and Injury Questions Without a Medical History

Ask one open question: "Anything in your body we should know about for practice, such as injuries, surgeries, or pregnancy?"

That question gives the teacher what they need to adapt the practice before day one. A full medical history gets skipped or answered carelessly, and it rarely changes the class. None is a valid answer.

What to ask next

Keep the follow-ups short, each with a one-line purpose:

• Mobility or sensory needs. So the room, mat, and instruction fit the guest.
• Conditions that affect the planned practices. So modifications are ready before the first session.
• Medication details relevant to an emergency. So the person on site knows what matters if something goes wrong.
• A private word with the teacher. Optional, for guests who will not put it in writing.

All of this lands after the deposit, so the health questions never hold up the booking.

Decide who sees what. The lead teacher sees health notes and emergency contacts, kitchen staff see dietary needs only, and office staff see what their role requires; role-based team access is what keeps that split from depending on who forwards which email. Passports, dietary needs, and emergency contacts are collected after booking and stay on the participant record. Attach a dedicated emergency contact form to that same record so the details a responder needs are current and findable. Put one name and one date in your process: the retreat manager deletes every health note once the retreat ends. Guests update their own answers through the traveler portal, and a reminder in the final stretch before arrival lets them correct an injury, a medication, or a contact that changed since they booked.

This is not legal or medical advice. Have the waiver and health wording reviewed by a local lawyer, and follow the privacy rules where you and your guests are based.

Waivers and Payment Terms Shown Before Checkout

In plain terms, a waiver says the guest knows the retreat is physical, accepts that participation carries some risk, and confirms the health answers are accurate. Get it signed before arrival, not on a clipboard at check-in, where nobody has time to read it, nobody can act on a flagged answer, and the queue backs up at the door.

Track unsigned waivers on one status list. Send reminders about 14 days out, then check daily who is still outstanding. Keep marketing consent as a separate box, unticked by default. The signed waiver should sit on the booking itself, the way online waiver software attaches it to the guest, instead of living in a file nobody can match to a payment.

Money the guest sees before paying

Offer a deposit or full payment, and add installments when the ticket sits above roughly $2,000. Installment payment software sets the schedule once at checkout instead of leaving you to invoice each payment. Show cancellation and refund terms before the payment button. Use promo codes for early-bird or returning guests. Let travelers submit cancellation or refund requests in writing, decide each one yourself, and keep every request in one place.

One published yoga retreat registration and waiver form shows what clear terms look like. A $1,000 non-refundable deposit secures the spot and counts toward the balance. The rest is split into two 50% payments with firm calendar deadlines. Cancel within 7 days of booking and you get a full refund; cancel later but more than 90 days out and you get everything back except the deposit; inside 90 days, no refunds unless a replacement guest pays in full. Record your own version of each number on the booking: the deposit, the balance deadlines, the cancellation windows, and the guest's acceptance.

State your non-refundable portion and your final no-refund window the same way, in amounts and days rather than "subject to our policy." And say what happens if you cancel the retreat: refund every fee.

The figures below are illustrative only, for a $2,400 retreat and 14 guests, with a $600 deposit and two $900 installments.

Illustrative payment arithmetic for a $2,400 retreat with 14 guests

Layout and Confirmation Rules That Get Forms Finished

Build the page for a phone first. The rules below are practical habits, not measured completion rates, so test the page with two or three past guests before you launch.

• One column. Stack every field so a thumb can scroll without zooming.
• Price above the first question. Show the price, what is included, and the deposit amount before anyone types a name.
• Progress steps. On a multi-part form, label booking, then travel details, then health and waiver.
• Optional questions later. Guests can skip them without losing what they already entered. Allow save-and-resume.
• Autofill and inline errors. Each mistake sits beside the field it belongs to.
• Phone stays optional. Require it only for day-of coordination, and show a one-line reason if you do.
• Conditional questions only. Diet, transfers, and passport fields appear when that booking needs them.

The confirmation email states the amount paid, the balance and its due date, the next task with a link, the waiver deadline, and what happens if the guest does not finish.

Move Registration Into One Participant Manifest

The manifest is what registration produces. It shows each guest's name and passport status, dietary needs grouped for the kitchen with allergies flagged, emergency contacts for the lead teacher, waiver status as signed or outstanding, balance status as paid, due, or overdue, room preferences for whoever assigns rooms, and arrival details for pickup. A printable copy goes to whoever meets the group. The manifest fills in as travelers add passports, dietary needs, and emergency contacts, which is the point of treating participant manifests as the booking record rather than a weekend spreadsheet.

Many retreat guests book straight through the host's own website rather than an online travel agency; wellness-retreat industry roundups track that direct-versus-OTA split. Direct bookings only help if the site that took the money also holds the rest of the record.

Start by listing every place guest data lives today. Move booking and payment onto one trip page. Turn pre-arrival questions into tasks counted back from departure, so the health and waiver work lands after the deposit instead of in front of it.

Checkout should take a deposit, an installment plan, or full payment, and on-request bookings cover private retreats. Embed a booking button, a departures list, or a calendar widget on your own site. Set capacity and booking cutoffs per departure to close last-minute joins and hold the smallest viable group. Guests pay balances and finish tasks in a self-service traveler portal, with automatic reminders until everything clears.

Samba keeps the deposit, the balance, and the pre-arrival tasks on the same booking, so a yoga retreat registration form no longer lives across a form tool, a payment link, and a spreadsheet. The three jobs stay split by timing: the guest commits and pays, the safety information arrives on a schedule, and the balance clears before arrival. Capacity, waivers, dietary needs, and who still owes money sit on one manifest before you leave for the venue. Cash and bank-transfer bookings you log for the record carry no fee; bookings through Samba's checkout carry a flat 2% per booking. See how that works for yoga and wellness retreat hosts.