A hen party of twelve books a pottery class. One person made the booking. She is paying for eight of the places, three friends are paying for themselves, and someone in the group has a nut allergy that nobody has mentioned yet. Most booking systems store all of that as a single record: one name, quantity twelve, one payment expected.
Everything that goes wrong with group bookings starts in that one record. With schools in England breaking up in late July, tour operators, activity centres and class-based businesses are heading into the weeks when group bookings dominate, and the gap between what the booking tool stores and what is actually happening gets expensive.
The three assumptions that break
Generic booking tools are built around a solo model: one booking is one person, paid for in one transaction, with nothing worth knowing about them beyond a name and an email address. Groups break all three assumptions at once.
The booker is not the group. The person who fills in the form is an organiser. The other eleven people never touch your system, so you have no names, no contact details, and no way to reach them when the start time moves.
One booking is not one payment. Group money is messy by design. An organiser pays a deposit to hold the date, some attendees settle their own share, a company pays for six places on invoice. A tool that expects a single card payment at checkout forces you to take the whole amount from one person and let them sort it out, which organisers hate, or to take nothing and chase the money by email.
The count is not enough. For a restaurant table, quantity twelve might be fine. For a kayaking trip you need per-person waivers. For a catered workshop you need dietary requirements. For a climbing session you need ages and consent forms. “Qty: 12” tells you none of it.
The workaround tax
When the tool cannot model the group, the business becomes the workaround. The pattern is always the same: the booking system holds a headline record, and the real data lives in a spreadsheet per event plus an email thread per group.
For a business running a handful of departures a week, that is easily five or more hours of unpaid admin: building attendee lists, chasing balance payments, forwarding the same joining instructions eleven times, and re-counting capacity because a booking for ten just became a booking for seven. We wrote about the moment this stops being tolerable in signs your business has outgrown its software, and group-heavy businesses hit that wall earlier than most.
The failure that stings most is capacity. If your system counts bookings rather than places, a trip with a hard limit of 30 can quietly oversell the moment two organisers each book “about ten” and both come back with twelve.
What a group booking system actually needs
Here is the capability list worth testing any tool against, off the shelf or custom.
| Capability | What it means in practice |
|---|---|
| Organiser and attendee roles | The booker holds places; each attendee becomes a real record, not a number in a quantity field |
| Attendee self-registration | The organiser gets a link to share; attendees add their own names, contact details and requirements |
| Split and staged payments | Organiser deposit to hold places, per-head balances, or one invoice to a company account |
| Live place counting | Capacity is counted in people, held atomically, released when someone drops out |
| Per-attendee information | Waivers, dietary needs, sizes, ages, collected before the day, not on a clipboard at the door |
| Group communications | Message every registered attendee about changes, not just the organiser |
| Partial changes | One person cancels without collapsing the whole group booking |
The self-registration link is the piece that changes the economics. Instead of the organiser dictating eleven sets of details over email and your staff retyping them, each attendee fills in their own record. The admin cost of a group falls to roughly the admin cost of a solo booking.
One note on the attendee data itself. Dietary requirements and medical details can be special category data under UK GDPR, so collect only what you genuinely need to run the session, tell people why you are asking, and delete it on a schedule. The ICO’s UK GDPR guidance ↗ is the reference here, and a system that collects attendee details properly should make this easy rather than something you bolt on.
Money is where group tools really get tested
Deposits deserve their own mention because groups multiply every payment problem a solo booking has. The organiser wants to commit without fronting the full amount. You want enough money down that a twelve-place hold is real. Attendees want to pay their own share without a bank transfer to someone’s personal account.
The pattern that works: organiser pays a per-head deposit to hold the places, each registered attendee gets a payment link for their balance, and unpaid places release automatically at a deadline you set. We covered the behavioural case for deposits in our guide to online booking systems with deposits; for groups, the deadline-and-release step is the part that protects your capacity.
Corporate groups add one more shape: the booker is a company, nobody pays by card, and the whole thing settles on invoice with a PO number. If you take training or team-day bookings, a system that cannot produce an invoice-backed booking will push those customers, usually your most valuable ones, back to email.
Off the shelf or custom
Plenty of vertical tools handle groups adequately: tour operator platforms do manifests well, class management tools do rosters well. The test is not the feature list, it is your messiest real booking from the last month. Take that exact scenario, the corporate group with two payers and a latecomer, and try to enter it in the trial account. Most tools fail in the first five minutes.
If your groups are standard shapes, a vertical tool is the right answer and cheaper than building. If your group logic is the business, mixed payer types, resource limits across rooms and kit and staff, attendee data feeding your operations, then you are in the territory we mapped in bespoke booking system vs off the shelf, where group and multi-person handling sits in the advanced build tier. Our guide to whether you need a custom booking system has the fuller decision framework.
Frequently asked questions
What is a group booking system?
A booking system designed for bookings where one person books on behalf of several attendees. It tracks the organiser and each attendee as separate records, supports split or staged payments, counts capacity in people rather than bookings, and collects per-attendee information such as waivers or dietary needs.
Can ordinary booking tools handle group bookings?
Usually only as a quantity field: one name, one payment, a headcount. That works for simple cases like a restaurant table, but it fails when attendees pay separately, when you need details for each person, or when part of a group cancels. The gap gets filled with spreadsheets and email.
How should payments work for a group booking?
Organiser pays a deposit to hold the places, attendees pay their own balances through individual payment links, and unpaid places are released automatically at a deadline. Corporate groups should be able to settle the whole booking on invoice instead.
What does a custom group booking system cost?
Group handling sits in the advanced tier of booking builds, typically £15,000 to £30,000 or more depending on payment complexity and integrations, plus a monthly fee for hosting and upkeep. A vertical off-the-shelf tool at £50 to £200 a month is the better answer when your groups follow standard shapes.
What attendee information should I collect?
Only what you need to deliver the session safely: names, contact details, and any waivers, dietary or medical information the activity genuinely requires. Health-related details carry extra obligations under UK GDPR, so ask deliberately and delete on a schedule.
The test worth running this week
Count the email threads attached to your current group bookings. If every group generates a thread of ten or more messages about names, money and joining instructions, the booking system is not doing the booking, your inbox is.
At Forgd, we build and manage bespoke booking systems for UK small businesses, including the organiser-and-attendee model, split payments and capacity logic described above, with hosting, monitoring and updates covered by one flat monthly fee. Get in touch and describe your messiest group booking. If an off-the-shelf tool would handle it, we will say so and point you at the category.