A private group of thirty-two, and a spreadsheet from the organiser
The secretary of a local history society books a private five-day tour of the Rhineland for thirty-two members. The deposit is agreed, the hotels are held and the coach is booked. Then the names start arriving. First a spreadsheet with twenty names and "more to follow". Then an email saying two couples are now sharing twins, not doubles. Then a phone message about a member who uses a walking frame. Then a revised spreadsheet with twenty-eight names in a different order and three spellings changed.
Your office copies each version into the booking system and tries to work out what changed. Meanwhile the hotels want rooming lists, and the organiser asks, reasonably, what you still need from her.
The organiser is the bottleneck, but not by choice
Group organisers are usually volunteers collecting information from members who reply slowly. They send what they have when they have it. The operator's process assumes a single complete list, so every partial list becomes rework.
- Names arrive as spreadsheets, emails and phone messages, in different formats.
- Each new version has to be compared by eye with the last one.
- Room sharing and requirements come separately from the names.
- The organiser cannot see what the operator already holds, so they resend everything.
- Deadlines for names are in the booking terms, not in anyone's diary.
Payment terms between you and the group, and who is responsible for what, are set by your own contract. We deal with the information flow.
Rework, errors and a nervous organiser
Every re-sent list costs staff time and brings a chance of copying something wrong. Passport name spellings matter for flights and some hotels. Room sharing mistakes show up on arrival night. Special requirements that arrived by phone never reach the rooming list.
The organiser also bears a cost. They are the face of the trip to their members, and a messy process makes them look disorganised. Organisers who find it hard to work with you are less likely to bring the society back next year.
An organiser portal that holds the group's own list
We build a group booking area where the organiser manages their traveller details and you see them live.
- When a group booking is confirmed, the organiser gets a secure login to their group page, showing the tour, dates, the room allocation held and the deadlines for names and details.
- The organiser adds travellers one by one or uploads their own spreadsheet. The upload is matched to the existing list, and additions, removals and spelling changes are shown for them to confirm.
- Room sharing is chosen from the rooms held for the group: who shares with whom, twin or double, and single rooms if allowed.
- Each traveller can have requirements recorded (dietary, mobility, room location), or the organiser can send members a link to fill in their own details.
- A completeness panel shows the organiser and your office exactly what is missing: names, sharing, passport details or requirements, against each deadline.
- Changes flow into your booking system through its API or a structured import, so nobody retypes them, and your team gets a summary of what changed each day.
| Information | How it arrives now | How it arrives with the portal |
|---|---|---|
| Traveller names | Several spreadsheets | Maintained by the organiser, one list |
| Room sharing | Separate email | Chosen against the rooms held |
| Requirements | Phone messages | Recorded per traveller |
| What is still missing | Your office works it out | Completeness panel for both sides |
Running a group booking with the portal
The organiser logs in when members reply, adds them, and sees their progress against the names deadline. Your office stops copying lists and starts reviewing a daily change summary. Two weeks before the deadline, a reminder goes to the organiser listing the six members with no room sharing chosen.
When the hotels need rooming lists, the data is already structured. When the coach operator asks about wheelchair access, the requirement is already recorded against the traveller.
Organisers who run a trip every year can copy last year's traveller list as a starting point, which saves them the first round of emails altogether.
Does this sound like your group bookings?
- Group organisers send names in several spreadsheets.
- Your staff compare list versions by eye.
- Room sharing and requirements arrive separately from names.
- Organisers ask what you still need because they cannot see it.
- Group name deadlines are tracked from memory.