Illustrative training scenario. Names, cities, experience and figures in this story illustrate the method. This is not a verified case study or a confirmed result of an XO network member.

A group trip rarely breaks down because of one big decision. Usually, problems accumulate from dozens of little things: the age of a child is incorrect, two friends were counting on separate beds, one participant arrives later, and no one considers the payment for a shared transfer to be theirs. While the group discusses everything in one chat, the agreements quickly turn into different versions of the same trip.

The task of a travel agent is not to become a round-the-clock secretary for each participant, but to create a unified order: who makes decisions, where the current composition is stored, when changes are frozen and what is confirmed by the supplier. Below is a system for trips of friends, families, small teams and thematic groups.

Why is a group application more complicated than several ordinary ones?

  • One decision affects several rooms, tickets, transfers and payments at once.
  • Participants have different understandings of the words “together”, “nearby”, “common budget” and “same conditions”.
  • Information comes through different people and quickly becomes outdated.
  • Suppliers set separate deadlines for guest lists, deposits and free changes.
  • Not all wishes can be guaranteed, even if the hotel is ready to accommodate the group.

Andrey’s educational example: 18 people and three room-allocation versions

Consider this illustrative training scenario: Andrey, a travel advisor from Odessa, has been organizing family vacations and complex routes for nine years. One day a company of 18 people approached him: three families with children, two couples and three friends. They wanted to fly to Crete on the same flight and live nearby. In the first two days, Andrey received three tables, dozens of voice messages and conflicting requests for beds.

When the hotel confirmed the rooms, it turned out that one child was booked as an adult, one couple was expecting a sea view that was not available in the selected category, and three friends thought that the cost of single occupancy was shared among the entire group. Andrey stopped new calculations, appointed one coordinator and compiled a single trip map with a version number.

I stopped editing individual posts and started managing changes. Once the group had one source of truth, there were fewer discussions and faster decisions.

Andrey — character in the illustrative training scenario

Step 1: Designate a coordinator and the boundaries of their role

The coordinator communicates the agreed decisions of the group, collects data and confirms changes. He does not sign documents and does not accept financial obligations in place of other adult tourists, unless this is done separately. The agent must maintain the ability to directly confirm personal information, terms and payment with each payer.

  • Last name and first name of the coordinator, convenient channel and backup contact.
  • What decisions does the coordinator have the right to agree on for the group?
  • Which questions each tourist confirms personally.
  • Who collects passport data and in what secure way.
  • Who pays the overall bill or how payments are divided.
  • Who receives emergency updates while traveling.

In order not to lose details, send all changes in travelling party, rooms and services in one message through the coordinator. Each adult participant confirms personal data and agreement with the terms separately.

Message to the group at the beginning of work

Step 2: Create a master trip map

  • Destination, dates, departure city and flight, permissible flexibility.
  • Total number of adults and children with age on dates of travel.
  • Room categories, bed types, meals and special requests.
  • Transfers, luggage, insurance, excursions and other general services.
  • Total budget, currency, who pays and what expenses are considered personal.
  • Deadlines: option, deposit, full payment, tourist data, free changes.
  • Current status of the supplier and date of last confirmation.

The master card describes the entire trip and does not replace contracts and tourist profiles. Its task is to show the consequences of any change. If a member leaves the group, the agent immediately sees whether the price of the room, transfer, group rate or single occupancy supplement changes.

Step 3. Collect the rooming list without ambiguity

A rooming list records accommodation room by room. Each row corresponds to one room, not one traveller. Use a unique internal room ID in the table, even though the actual hotel room number may only be known at check-in.

  • Internal room ID and confirmed category.
  • The names of the guests are exactly as in the documents, but without sending passport copies to the general chat.
  • Date of birth or age of the child on dates of residence.
  • Type of beds: one double, two single, extra bed, crib.
  • Meals, arrival and departure dates if they differ from the main group.
  • Special requests and note: is this guaranteed or only transferred to the hotel.
  • Payer and payment status by room.

Guarantee, category and wish - three different things

  • Category - what is indicated in the confirmation: for example, family room or standard.
  • A guaranteed feature is a condition that the supplier has included in the booking in writing.
  • Request - a request such as neighboring rooms, a high floor or a quiet building; the hotel will try to take it into account, but is not obligated to do so.

The hotel confirmed the Family Room category. A request for three families to be placed side by side has been submitted, but room numbers are assigned by the hotel and are not guaranteed. I will request the location again seven days before arrival.

How to set expectations

Step 4: Enter versions and changelog

Name the first approved file or card version 1.0 and indicate the date. Any change in composition, placement, dates or paid services creates a new version. Do not delete the old one: mark it as irrelevant. In the journal, it is enough to record who requested the change, what has changed, how it affects the price, and who confirmed it.

  1. Receive the change in one message and repeat it in your own words.
  2. Check price, availability, penalties and impact on other participants.
  3. Obtain written consent from affected payers.
  4. Send the change to the supplier and wait for a new confirmation.
  5. Update master card, rooming list, amount and version number.
  6. Report only the confirmed result to the group, not the intermediate promise.

Step 5. Separate general and personal money

Before the first payment, determine what happens if the participant refuses. The group must understand that the refund to a specific person depends not only on his rate, but also on whether the price of the room or shared transfer is the same for others. Do not promise internal redistribution of money until the supplier has recalculated the application.

  • Who receives the invoice and who actually transfers the money.
  • Are there separate payments for rooms or a single payment?
  • What amount is non-refundable at each stage.
  • Who covers the change in total cost when a participant leaves.
  • How are supplements for single occupancy, baggage and personal services determined?
  • How receipt of each payment and balance is confirmed.

Checkpoint calendar

  1. Before booking: line-up, categories, budget and change rules are agreed upon.
  2. On the day of the option: the group knows the exact time when the reservation will no longer be held.
  3. Before the deposit: each payer received the terms and confirmed his part.
  4. Before data transfer: names are checked against documents, children's ages are recalculated based on travel dates.
  5. 14-7 days in advance: The supplier has reconfirmed rooms, meals, transfers and special requests.
  6. 72–24 hours in advance: flight, meeting, coordinator contacts and procedure for delays have been checked.
  7. Upon return: general expenses are closed, feedback is collected and lessons are recorded.

One channel for decisions, another for emotions

General chat is good for atmosphere, questions and reminders, but it doesn't store final decisions well. After the discussion, send a separate brief summary: version of what is confirmed, what is expected, who is responding and by when. If the decision is not on the summary or card, it is not considered accepted.

Outcome in the illustrative scenario for Andrey

After switching to the master card, Andrey, together with the coordinator, agreed on eight rooms in one evening. One participant chose a separate room and accepted the additional payment himself, two families changed categories without affecting the overall budget, and the request to live nearby remained an honestly stated wish. The final version of the rooming list was sent to the hotel ten days before arrival and re-confirmed.

On the trip, one family arrived late due to a flight change. Since the card had separate dates and a backup contact, the transfer was recalculated only for this family, without delaying the rest. Andrey did not promise the impossible - he quickly found the right line and applied a pre-agreed rule.

Group application quality metrics

  • Number of changes after the composition was frozen.
  • Proportion of rooms confirmed without corrections to names, ages and categories.
  • Number of discrepancies between the master card, contract and supplier confirmation.
  • The percentage of payments received before the agreed due date.
  • The number of wishes that the group incorrectly considered to be a guarantee.
  • Time to process one change and the number of participants affected by it.

Take the nearest group request and create three things: one coordinator, a rooming list with one line per room, and a version log. This alone will remove most of the hidden contradictions.

Practice for today