Tour Booking Form Template for Operators — Samba blog

Tour Booking Form Template for Operators

A two-stage booking form template for tour operators: sell the seat at checkout with minimal fields, then collect passports, dietary needs, and waivers after the deposit is in.

By Valentin Fily

10 min read

A practical tour booking form template needs four things to sell a seat: the departure date, the number of travelers, the lead booker's contact details, and a payment choice. Payment belongs in checkout, not in a field where someone types a card number.

The common advice to "put every detail on the form" confuses booking a seat with preparing a trip. A short form captures the booking; a longer set of participant details follows once the seat is held. And neither a Google Form nor a polished PDF will stop a departure from being oversold or the office from chasing balances in a spreadsheet.

That split matters most for owners and office managers who still take bookings through a Google Form, a Word or PDF file, or an email thread, then retype them into a spreadsheet. A guided trip isn't an equipment rental: a food walk, city tour, rafting trip, sailing departure, cycling tour, safari, ski week, trek, or retreat has travelers to brief, payments to track, and a manifest to prepare.

The Minimum Fields a Tour Booking Form Needs

Ask only for what lets a traveler pick a real departure, gives the office one reliable contact, and sends them to checkout. Every extra field is another reason to close the tab, and on a $4,000 trek that closed tab is a large unsold seat.

Minimum fields that confirm a seat

FieldWhen to askWhy it is enough
Departure dateAt bookingTies the reservation to one departure so a 12-seat trip isn't sold twice
Number of travelersAt bookingSets party size, and the price when adults and children are charged differently
Lead booker name, email, and mobileAt bookingOne contact confirms the booking and can be reached the morning of departure
Deposit or full paymentCheckout, not a typed card fieldTakes money when the seat is held, without storing a card number in the form

If the form has to go live today, use trip and departure date, party size, lead booker name, email, phone, and payment choice. Split adults and children only if their prices differ. The payment choice is a decision made at checkout, deposit or full amount, not a card-number field.

Passports, dates of birth, dietary needs, medical notes, and waivers aren't on this first list. Some trips can't run without them, but the lead booker rarely has every companion's details to hand while paying.

Practical rule: Stage A sells the seat. Stage B runs the trip.

Copy the Two-Stage Tour Booking Form Template

Paste the Stage A rows into your booking form. Send the Stage B rows after booking, with one set of answers per participant.

StageFieldAsk it whenNotes
A, at bookingTrip and departure dateAlwaysNames the product and the date the seat is on
A, at bookingParty size, adults and childrenAlways; split ages only if prices differOne party total is enough when everyone pays the same
A, at bookingLead booker name, email, and phoneAlwaysOne contact for the whole party
A, at bookingPromo codeOptionalLeave the field off if you don't run codes
A, at bookingDeposit or full paymentAlways, in checkoutA choice, not a place to type a card number
A, at bookingTerms and cancellation checkboxAlwaysAgreement before the seat is confirmed
B, after bookingFull name as on the passportPer participantMust match travel documents on international trips
B, after bookingPassport number and nationalityMulti-day or international onlySkip on a city walk or half-day tasting
B, after bookingDate of birthPer participantUsed for age rules, insurance, and rooming
B, after bookingDietary needs and allergiesPer participantFor kitchens, tastings, and packed lunches
B, after bookingMedical notesPer participantWhat the guide must know, not a long medical history
B, after bookingEmergency contactPer participantName and phone of someone not on the trip
B, after bookingWaiver signatureBefore the activityEssential for water, adventure, and cycling
B, after bookingActivity-specific detailsWhen the trip needs themShoe size, swim ability, cycling experience, or room-share preference

Stage A is what a lead booker can answer while paying. Stage B is what they often don't have for every companion at that moment: passport numbers, medical notes, dietary requirements. Keep Stage B off the first screen. The booking form's job is to confirm a seat, not to assemble the guide's complete file before checkout. The terms checkbox should point at a written policy; if yours is still a paragraph in an email, start from a tour operator terms and conditions template.

Add activity-specific fields only when the answer changes preparation, safety, or rooming. A cycling trip may need riding experience, a trek a fitness acknowledgment, a water activity swim ability. For private or custom trips, take a request instead of instant checkout while the date or itinerary still needs approval.

The payment row records a choice between a deposit and full payment. It never asks the traveler to type card details into the form. Send Stage B once the deposit or full payment is in.

Fields to Add or Drop by Trip Type

Keep the same Stage A on every product, then add only the Stage B details the trip actually uses. A day tour stays lean. A multi-day departure needs more preparation, but that still doesn't put every detail at checkout.

Trip typeKeep from Stage AAddDrop
Day tour or activityDeparture, party size, lead contact, payment choice, termsPickup or meeting point, mobile for the morning ofPassport, insurance, room share, fitness essay
Multi-day trek or skiSame Stage A, with deposit rather than full paymentPassport and nationality, insurance, room share, fitness acknowledgment, installment datesDay-tour-only shortcuts such as skipping passport or rooming
Water activityStage A plus waiver before launchSwim ability, weight for raft or kayak balancePassport and rooming on a half-day
Private or customPreferred dates, group size, budgetA request instead of instant checkoutA live pay button until the date is confirmed
A chart showing how to customize tour booking forms based on specific trip types like multi-day or private tours.

Day tour or activity. A food walk, city walk, or short boat trip needs the departure, party size, contact details, payment choice, and terms. Add a meeting-point or pickup question if travelers need to know where to go. Drop passport, insurance, room sharing, and the long fitness questionnaire. If children pay a different price, keep the adult-child split even on an otherwise short form.

Multi-day trek or ski trip. Add what travel and room planning depend on: passport details where relevant, insurance confirmation, room-share preference, and a fitness-level acknowledgment. A trip booked months ahead with staged payments also needs a clear installment schedule, with the balance due before departure.

Water activity. For rafting, kayaking, or a small-boat sail, ask about swim ability and collect the waiver before launch. What that document should cover is its own job; see this guide to a rafting waiver. Ask for weight only when the crew uses it to balance a raft or kayak. A half-day trip doesn't need passport and rooming questions just because the same company also runs multi-day trips.

Private or custom trip. Use a request form for preferred dates, group size, and budget. Confirm the date and what you can deliver before sending a payment link; an instant pay button can take money for a trip nobody has agreed to. Pricing and quoting private group tours covers what happens between the request and the payment link.

Custom Questions That Stop Last-Minute Problems

A custom question earns its place only if it prevents a specific snag: a missed pickup, a safety call, a rooming mix-up. Answers that land in a form response without being tied to the booking still leave the office to reconcile and follow up.

A pickup hotel or meeting-point confirmation stops the van and the group waiting in two different places. A mobile number reaches travelers who are already in town and not checking email. For the person back home who should be called if something goes wrong, the emergency contact form article covers which fields matter.

Ask, "Has everyone in your group read the fitness level?" A plain yes-or-no flags a mismatch before a trek or long ride, not on the first climb. For multi-day trips, collect arrival flight times when the airport pickup or the first night depends on them.

Keep checkout short. Ask for pickup and mobile at booking only when the trip is days away or the meeting point changes the price; otherwise collect them after the seat is held. Passports, dietary needs, and emergency contacts can come later too, with a deadline counted back from departure.

Cut questions that won't change a decision. Shirt size for a walking tour, a full medical history, or a second passport copy for a short tasting adds work without helping the guide run that departure.

If the answer won't change a pickup, a safety decision, or a room assignment, leave the question off.

Where Google Forms and PDFs Break After Submit

A form collects a booking; it doesn't manage one. A Google Form, Word file, or PDF doesn't check availability, so a 12-person departure can be sold to 14 people because nothing counts down.

A wooden table with a laptop, tour booking form, and a notebook containing a seat list.

Payment usually sits somewhere else. The office pastes a payment link into an email, tracks deposits and balances by hand, and relies on a spreadsheet someone has to keep current. Participant details end up in one person's inbox, and the manifest gets rebuilt by hand before every departure.

Illustrative arithmetic, not a benchmark: take a fictional 10-person departure with 3 balances still open. At 3 chase emails per balance, that's 9 emails before anyone checks dietary needs or waivers. Or take a full 12-seat day trip where the form accepts two more yeses: now someone has to find a second guide and a bigger vehicle, neither of which appears on demand.

Long lead times make it worse. A fictional multi-day trip booked 90 days out, with a deposit and later installments, gives a spreadsheet three months to drift as payments, rooming details, and participant records change.

Better form fields don't fix this. A standalone form can't close a booking cutoff, enforce a minimum group size, or stop two departures claiming the same boat. It can't tie a payment to a booking or keep the manifest current unless someone reconciles the records by hand.

Participant details need a place to land other than an inbox, one that the pre-departure checklist can be worked from. The fix is to connect the booking questions to live departures and checkout, so the office isn't reconstructing what happened after submit.

Keep Card Numbers Out of the Form

A payment choice is a form question. A card number, expiry date, and security code are not. Don't collect card details in a Google Form, PDF, Word file, or email reply.

A form stores whatever a traveler types. That answer then gets copied into a spreadsheet, forwarded to a colleague, or left sitting in an inbox, and every copy is something the operator now has to protect. The card industry's own rules are blunt about the security code: the PCI Security Standards Council states that card verification codes may not be retained once the transaction has been authorized. A form response keeps it indefinitely. Let a payment provider collect card details in online checkout instead.

The process should be simple: the traveler chooses a deposit, installments, or full payment, then enters card details in checkout. The deposit is taken when the seat is confirmed, and the receipt stays tied to the booking rather than to an email someone has to dig up later.

Stop asking travelers to email card details. Don't read a card number off a PDF over the phone and key it into another system. Those habits create more copies of sensitive data without making the departure any easier to run.

A bank transfer can be recorded as an offline payment against the booking, so the office sees who has paid without bank details ever touching the traveler form. For a private trip, confirm the date first, then send a payment link. The traveler still enters card details in checkout, not in a request form.

Attach the Form to Live Departures and Checkout

The Stage A questions stay the same; what changes is what they're connected to. Instead of typing a preferred date into a blank field, the traveler picks a departure with capacity attached. Seats count down, and the departure closes when it's full.

A five-step infographic showing how a tour booking form integrates with live departures and seat inventory.

A cutoff stops bookings after the office or guide needs the final list. A visible minimum group size tells travelers whether a departure runs with a small party or still needs more bookings. Shared resources count too: a boat, van, or set of bikes can't be on two departures at once.

Before confirming, the traveler should see remaining seats, the cutoff, the minimum group, and the payment options. Checkout takes the deposit, installment, or full amount on the spot, and the confirmation names the departure, so nobody has to match a form response to an email thread.

Not every product should sell this way. The inquiry forms at Count Kálnoky's Estates in Transylvania ask for guest count, preferred dates, and budget before anything is priced, the right shape for a retreat or private event that needs a conversation first. Selling a fixed seat on a published departure is a different job. Once the booking is confirmed, group records and trip prep are the territory of participant management software.

A booking widget on your own website, including a WordPress plugin, or a hosted trip page can run Stage A against live capacity. For private trips, an on-request booking replaces the inquiry-then-email loop without pretending the date is already confirmed. Either way, checkout must never ask for a card number in a custom form field.

Keep These Fields and Drop the Rest

The booking form collects what sells the seat. Everything else comes after booking, when each participant can give their own details. And a tidy form still won't prevent overselling or balance chasing if bookings, departures, and payments live in separate places.

A design guide infographic titled Keep These Fields and Drop the Rest, outlining best practices for travel forms.

Stage A, at booking

  • Departure: a specific trip and date.
  • Party size: adult and child counts only when prices differ.
  • Lead contact: the booker's name, email, and mobile.
  • Payment choice: deposit, installments, or full payment, chosen in checkout.
  • Terms: agreement to the terms and cancellation policy before the seat is confirmed.

Stage B, after booking and per participant

  • Travel identity: passport name, plus passport number and nationality when the trip is international or multi-day.
  • Participant details: date of birth, dietary needs, allergies, and the medical notes the guide needs.
  • Trip readiness: an emergency contact, waiver signature, and only the activity-specific details the trip requires.

Drop passport and insurance questions from a day tour, room sharing from a walking tour, weight unless a raft or kayak needs balancing, and the promo-code field when you don't issue codes. Remove the adult-child split if everyone pays the same. If a lead booker can't answer a question while paying, collect it after the deposit, unless the seat can't be confirmed without it.

Every activity has its own short list of answers that matter. Dive operators are a good example: Kona Honu Divers' guide to another Kona dive company tells divers to ask who is in the water with them and what experience level a dive expects, which is exactly the Stage B detail a dive booking form should collect from each participant.

The form is only the front door. Behind it, the chosen date has to connect to live departures, capacity, cutoffs, minimum group sizes, shared resources, and payment. That's what Samba does: booking widgets on your own site (including a WordPress plugin) and checkout with deposits and installments, all on the free plan, with payments going straight to your own connected Stripe account and cash or bank-transfer bookings you log yourself carrying no fee. After booking, Participants gathers passports, dietary needs, and emergency contacts per traveler, so checkout stays short and the guide still gets a complete file. See the full feature list for how it fits your departures.

Frequently asked questions

What fields does a tour booking form need at minimum?

A tour booking form needs the trip and departure date, party size, the lead booker's name, email, and mobile, a payment choice, and a terms and cancellation checkbox. Split adults and children only when their prices differ, and add a promo code field only if you actually run codes. Everything else can wait until the seat is held.

When should a tour operator collect passport details, dietary needs, and medical notes?

Collect them after booking, one set per participant, once the deposit or full payment is in. The lead booker rarely has every companion's passport number, allergies, or medical notes while paying, so asking at checkout loses bookings. Set a deadline counted back from departure, and ask for passport number and nationality only on international or multi-day trips.

Is it safe to collect credit card numbers in a Google Form or PDF booking form?

No. A form stores whatever the traveler types, and that answer gets copied into spreadsheets, forwarded, and left in inboxes, so every copy becomes something you must protect. The PCI Security Standards Council does not allow card verification codes to be kept after a transaction is authorized. Ask for a payment choice on the form and let a payment provider collect card details in checkout.

Should private or custom tours use instant checkout or a request form?

Use a request form. Ask for preferred dates, group size, and budget, confirm the date and what you can deliver, then send a payment link. An instant pay button on a private trip can take money for a departure nobody has agreed to. The traveler still enters card details in checkout, never in the request form itself.

Why can a Google Form oversell a tour departure?

A Google Form, Word file, or PDF does not check availability, so nothing counts seats down. A 12-person departure can be sold to 14 people, and the office then has to find another guide and a bigger vehicle. A standalone form also cannot close a booking cutoff, enforce a minimum group size, or stop two departures claiming the same boat.

Valentin Fily, Founder and CEO of Samba

Valentin Fily

Founder & CEO

Related posts

Keep the 20–30% you would hand an OTA

Samba gives tour and activity operators direct bookings on their own website, so you stop paying a marketplace 20–30% of every booking.