TL;DR: For 20–30 people, the workflow is five dated steps. Write the terms. Open one booking page that takes a deposit and the traveler's details in the same step. Size the deposit so that all of them together cover your supplier's deposit. Schedule the balance in automatic installments that finish two to three weeks before the supplier's final payment. Let reminders and card retries run, and export the rooming and passenger lists from the bookings when the supplier asks. The worked example below runs the numbers for 25 people on an $1,800 trip.
The whole workflow for collecting deposits, traveler info and payments from a 20–30 person group is: terms first, then one booking link that collects the deposit and the details together, then installments on a schedule that ends before your supplier's balance is due. Everything else is a consequence of that order. Get it right and your job shrinks to the one or two travelers whose card fails. Get it wrong and you spend the month before departure chasing 25 people for a form and a payment, often while fronting the venue money from your own account.
This guide is the dated version. Every step has a day count, worked for a real group size, and the deposit and schedule numbers come from data on real group trips, not a rule of thumb.
The Workflow on One Timeline
Work backward from the day you leave. The dates below assume a supplier who wants a deposit at contract signing and the balance 60 days before arrival, which is the common shape for venues, tour operators and hotel group blocks. Shift them to your contract.
| When | Step | What happens |
|---|---|---|
| Day −200 | Sign the supplier contract | You owe a deposit now and a balance at day −60. Note both numbers and both dates. |
| Day −195 | Write the terms | Price, what is included, deposit, installment dates, refund and cancellation rules, what happens on a missed payment, minimum group size. One page. |
| Day −190 | Open the booking page | Packages and prices, the deposit, the registration questions and the payment plan are set once. Share one link. |
| Day −190 to −120 | Bookings arrive | Each traveler pays the deposit and fills in their details in one step. The deposits together cover what you paid the supplier. |
| Day −150 to −80 | Installments charge on their dates | Reminders go out before each one. Failed cards get a retry and a notice. You deal only with the exceptions. |
| Day −80 | Last installment due | Twenty days of slack before the supplier's balance for a retry, a reminder and a conversation. |
| Day −60 | Pay the supplier's balance | Every traveler has paid. The money is already in your account. |
| Day −45 | Send the supplier's lists | Rooming list, passenger names, dietary list, all exported from the same bookings. |
| Day −30 | Collect anything time-sensitive | Passport numbers, flight details, arrival times, through the same system. |
Group travelers book early when there is a plan to book onto. Travelers on payment plans book a median of 181 days before departure, against 84 days for travelers who pay in full, so the window from day −190 is realistic, not optimistic.
Step 1: Write the Terms Before Anyone Pays
The terms page is what every later step refers back to, so it comes first. It should answer, in this order:
- Price and what it includes, per package if you offer more than one.
- Deposit, as a dollar amount, and whether it is refundable.
- Installment dates, the actual calendar dates, not "monthly."
- Refund and cancellation schedule, tied to your supplier's. If the venue refunds nothing after day −60, neither can you.
- Missed payment rule. What happens after a failed charge and a retry: a grace period, then the spot is released.
- Minimum group size and what happens if you do not reach it.
Write it before the booking page opens, link it from the page, and make accepting it part of checkout. A traveler who read the terms before paying is a traveler who does not argue about them at day −60. The retreat deposit policy guide has the refund schedules that hold up.
Step 2: Size the Deposit From the Supplier's Deposit
The deposit has one job: cover what you owe the supplier at signing, so you never front it. The math is short.
Worked example. 25 travelers, $1,800 each, a venue that wants $9,000 at signing and the balance at day −60.
- Supplier deposit ÷ travelers = $9,000 ÷ 25 = $360 a person, which is 20% of the price.
- Round to a number that reads clean on the page: $360, or $400 if you want a buffer for one or two people who book late.
- Balance per traveler: $1,800 − $360 = $1,440, collected in installments.
Twenty percent is on the higher side of what organizers actually ask. On the median SquadTrip trip the deposit was about 15% of the price, and the middle half of trips asked 10% to 23%. Lower deposits book more people, so set yours from the supplier math, not from the "25% to 40%" advice that circulates. If your supplier wants less up front, ask for less.
Step 3: Collect Traveler Details at Checkout, Not by Email
One link does both jobs: the traveler pays the deposit and answers the registration questions in the same step. Nobody can pay without giving you their details, and nobody gives details without paying, so the roster and the ledger are the same list.
| Collect at booking | Collect at day −30 | Do not collect |
|---|---|---|
| Legal name as on ID | Passport number and expiry, if a supplier needs it | Card details by email or text, ever |
| Email and phone | Flight numbers and arrival time | Full date of birth, unless an airline or insurer requires it |
| Emergency contact | Anything the supplier asks for late | Information you have no supplier reason to hold |
| Room choice or roommate name | ||
| Dietary and accessibility needs | ||
| Acceptance of the terms, and a waiver if the trip has activities |
Keep the booking form short. Every extra question at checkout costs bookings, and 73% of checkouts happen on a phone. Passport details can wait for the day −30 request through the same system, which keeps them out of email.
Step 4: Schedule the Balance to End Before the Supplier's Balance
The last installment is due two to three weeks before the supplier's final payment date. That gap is the whole reason the workflow runs without you.
Worked example, continued. Balance $1,440, booking opens at day −190, supplier balance due at day −60, last installment at day −80.
| Installment | Due | Amount |
|---|---|---|
| Deposit | At booking | $360 |
| 1 | Day −160 | $288 |
| 2 | Day −140 | $288 |
| 3 | Day −120 | $288 |
| 4 | Day −100 | $288 |
| 5 | Day −80 | $288 |
A traveler who books at day −120 gets the same end date and fewer, larger installments. The schedule is anchored to the supplier, not to the booking date. Six payments in total is also what travelers actually choose: the median payment plan on SquadTrip runs six payments, and 43% of plans run four to six. The payment plan calculator builds the schedule for your own numbers.
Step 5: Let Reminders and Retries Run
Set up well, the installments charge themselves. A reminder goes out before each due date. If a card fails, the system retries, tells the traveler and tells you. What reaches you is the exception list: the one or two people whose card failed twice.
Handle those by the rule you wrote in Step 1, the same way for everyone. A system-sent notice and a written policy keep it administrative. A personal text from the organizer makes it a favor.
Fee math, so you can put it on the terms page. On SquadTrip the platform is free and one 6% fee is added to each payment, paid by the traveler by default. The $1,800 trip costs the traveler $1,908, and you receive $1,800 in your own Stripe account; SquadTrip never holds the money. You can absorb the fee instead, in which case you receive $1,692. A traveler who picks Klarna, Afterpay or Affirm at checkout pays a 4% convenience fee on top. Details on the pricing page.
Step 6: Export the Lists From the Bookings
The rooming list, the passenger name list and the dietary list are the same bookings sorted three ways. Export them when the supplier asks, and if two travelers swap rooms the week before, export again. A spreadsheet rebuilt from emails is wrong the day after you build it.
When a Spreadsheet, a Form and Venmo Are Enough
For fewer than ten people who pay in full, a Google Form, a Stripe payment link and a spreadsheet work, and there is no reason to pay for more. The setup breaks at 20–30 people on payment plans for one reason: nothing charges a card on a due date. Every installment depends on the traveler remembering, the form and the payments and the roster live in three places, and the organizer becomes the reminder system. 57% of group trip bookings use a payment plan, so at this size the plan is the normal case, not the exception.
A booking platform built for groups does the five steps as one setup. On SquadTrip, the packages, deposit, registration questions, terms acceptance and installment schedule are set when you create the trip, each traveler books through one link, the dashboard shows who has paid what, and the lists export from the bookings. The full guide to collecting money for a group trip compares the other tools organizers use, and how to book group travel covers the supplier side: group airfares, room blocks and attrition dates.
The One-Page Terms Template
Copy, fill in, link from your booking page.
[Trip name], [dates] Price: $[1,800] per person, [shared room]. Includes [lodging, breakfasts, two excursions, airport transfers]. Does not include [flights, travel insurance, other meals]. Deposit: $[360] at booking, [non-refundable after 7 days]. Payment plan: balance of $[1,440] in [5] automatic payments of $[288] on [dates]. Cards are charged on each date; you will get a reminder [3] days before. Missed payment: a failed charge is retried [3] days later. If it fails again, you have [7] days to update your card before your spot is released and the deposit is kept. Cancellation: cancel before [date] for a refund of everything except the deposit; before [date] for 50%; after [date] no refund. Travel insurance is recommended. Minimum group: [15] travelers. If we do not reach it by [date], everyone is refunded in full.
