10 group travel management mistakes that eat into your agency's margin

In group travel, selling more seats doesn't always mean earning more. If every new participant adds emails, checks, spreadsheets and manual follow-ups, part of the margin ends up consumed by the management itself.

The challenge is that a group trip combines two realities. On one side, there is a shared programme: dates, itinerary, transport, accommodation, suppliers, prices and seats. On the other, each participant can have different details, payments, documents, needs and services.

On top of that come the changes. Someone joins late, someone else cancels, a family asks to split the payment, a flight is rescheduled, a room type changes or an activity is no longer available. The hard part is not making the adjustment once, but making sure it is reflected everywhere it matters.

Most problems don't come from a lack of travel expertise. They appear when the process can no longer absorb the volume and the exceptions. These are the mistakes that can cost an agency the most time, control and margin.

How operational mistakes affect your margin

Some mistakes have a visible cost: a seat that doesn't sell, a service booked in excess, a supplement that isn't charged or a duplicate booking. Others erode the margin more quietly.

Every hour spent checking bank transfers, tracking down a piece of information, correcting a document or answering a repeated question increases the operating cost of the trip. The same happens when sales and operations need several meetings to reconstruct what was agreed, or when a change forces someone to update several files by hand.

That's why, to know the real profitability of a group, it isn't enough to subtract supplier costs from the amount sold. You also need to account for how much time the team needs to take the trip from the first request to completion.

Mistake 1: spreading information across emails, spreadsheets and chats

It's common for the initial request to sit in an email, the participant list in Excel, the proposal in a PDF, the payments in online banking and the latest changes in WhatsApp.

Each tool may do its job, but none of them on its own gives a complete view of the trip. The team ends up relying on certain people's memory to know where each piece of information is and which version is correct.

This fragmentation leads to:

• Data entered several times.
• Lists updated at different paces.
• Doubts about what has been confirmed.
• Dependence on specific people.
• More difficulty bringing another team member on board.
• More time spent searching than managing.

The solution isn't just to keep all the files in the same folder. Contacts, proposals, trips, bookings and activity need to be connected.

The MOGU CRM for travel agencies connects contacts, opportunities, proposals and trips. That way, sales, operations and customer service can see the same context without rebuilding the history every time they step in.

Mistake 2: not distinguishing between group, booking, buyer and traveller

One of the most common mistakes is using "participant", "customer" and "payer" as if they were always the same person.

On a school trip, for example, the school may be the agency's point of contact, a parent makes the booking and the payment, and the student is the traveller. On a trip organised by an association, there may be a coordinator, even though each member manages and pays for their own seat.

If the system doesn't distinguish these roles, problems appear such as:

• Payments that are hard to allocate.
• Buyer details mixed up with traveller details.
• Communications sent to the wrong person.
• Doubts about who accepted the terms.
• Lack of clarity about which services belong to each participant.

Before opening bookings, it's worth defining:

1. Who acts as the group's general point of contact.
2. Who makes each booking.
3. Who makes the payment.
4. Who is going to travel.
5. What information must be collected from each of them.
6. What communications each profile will receive.

MOGU lets you request buyer and traveller information separately within the booking process. The form can be set up per booking or per traveller, depending on how the group operates.

Mistake 3: an incomplete handover between sales and operations

When the group confirms the proposal, sales may consider their job done. For operations, however, a phase begins in which they need to know exactly what was sold, what terms were agreed and what is still pending.

If the handover happens through a PDF and an email thread, operations has to reconstruct the trip:

• Which version the customer accepted.
• Which services are included.
• Which changes were negotiated.
• Which seats or categories were offered.
• What amounts have been paid.
• What commitments were made to the group.

This gap between selling and managing creates rework and increases the risk that what is delivered doesn't match what was promised.

To avoid it, each group should move forward with a shared context. The accepted proposal, bookings, travellers, payments and operational information must stay connected. It also helps to make clear who is responsible for validating each phase and at what point internal ownership of the trip changes.

Mistake 4: collecting data and documents manually

Asking each participant for their details by email usually seems simple until you have to handle several dozen replies.

Some travellers send all the information. Others leave fields blank. Some reply to an earlier email and others send their details over WhatsApp. Then someone has to copy each reply into the master list and check what's missing.

On school trips, this step requires even more care. When working with minors, the agency must define what information it really needs, for what purpose it is requested and how the relevant consents will be handled. It's best not to ask for more data than necessary or to use generic forms without reviewing how the information is processed.

A more orderly process should:

• Request only the data that is needed.
• Separate buyer information from traveller information.
• Use consistent fields for all participants.
• Clearly indicate which information is mandatory.
• Show which bookings are complete.
• Avoid asking again for data already provided.

The MOGU booking module lets you create custom forms, save them to the library and reuse them on future trips. The information stays linked to the booking and can be exported when the team needs to work with it or share certain details with a supplier.

The agency remains responsible for defining what it requests, reviewing the information and establishing the appropriate legal and operational procedures.

Mistake 5: handling changes by creating a new version of every document

In group travel, changes are part of operations. The problem isn't that they happen, but how they are passed on.

Imagine the outbound flight time changes. That change can affect the transfer, the hotel arrival time, the first activity, the information sent to the group and the guide's work. If only the itinerary is corrected but the related elements aren't reviewed, the issue will surface later.

Before closing a change, it's worth checking:

• Whether it affects the price.
• Whether it modifies a booking or an allocation.
• Whether it changes any contracted service.
• Whether it requires adjusting a payment.
• Whether it must be communicated to the whole group or only to some people.
• Whether it alters the information the traveller will see.

Working with a web proposal avoids generating a new PDF every time the programme changes. With the MOGU proposal builder, the team can update the trip and keep the current version accessible through the same link.

Once confirmed, changes made in the dashboard can also be reflected in the traveller portal. This reduces the risk of someone checking an old document saved in their inbox.

Mistake 6: not controlling seats by package, category or service

Knowing that there are ten seats left on a trip isn't always enough. The hotel may have general availability but no single rooms left. Or an activity may have a lower limit than the group size. There may also be categories, supplements or optional services with their own allocations.

When everything is tracked manually, each new booking means checking several numbers. And a cancellation or category change can leave the count out of date.

A group booking system should let you define:

• An overall seat limit.
• Allocation per category or package.
• Room or cabin types.
• Single supplements.
• Mandatory and optional services.
• Minimum or maximum number per booking.
• Availability of activities or extras.

MOGU lets you set up packages with different prices, limited allocations and additional services. Seats are deducted as bookings come in, which helps prevent overbooking and makes both private groups and seat-by-seat sales easier.

This is especially useful for school and university trips, associations, tours and cruises, where a single proposal can include a common structure and different individual choices.

Mistake 7: chasing every payment manually

Group payments are rarely a single transfer. There may be an initial deposit, several instalments, supplements, optional activities or additional amounts resulting from changes.

When tracking is done in a spreadsheet, the team has to check the bank account, identify the payment, update its status and manually chase overdue instalments.

On a school trip, for example, there may be forty families paying on different dates. The group may be confirmed overall, but the agency needs to know which booking is up to date, which has an instalment pending and which participant hasn't yet completed the process.

With the MOGU online payments and bookings module, the agency can create payment links, set up full or instalment payments and link each transaction to its booking. It can also generate additional charges when a supplement or a new service comes up.

Automating the payment schedule reduces administrative chasing, but the agency must still clearly define the amounts, due dates, cancellation terms and the consequences of non-payment.

Mistake 8: communicating every change by email or WhatsApp

When information travels through different channels, the agency loses control over what each person has received. A schedule may be shared in a WhatsApp group, while the updated voucher is sent by email and the meeting point stays in an older PDF.

Besides, not every communication is relevant to everyone.

On a school trip, at least four audiences can coexist:

• The school or the coordinator.
• Teachers and chaperones.
• Families.
• Students.

Each needs a different part of the information. The school may need the overall view of the group; families, the deadlines and practical details; chaperones, the day-to-day operations; and travellers, the itinerary and the documents they will use during the trip.

The MOGU traveller portal and app bring together the itinerary, bookings, maps, documents and notifications in one space branded with the agency's identity. The information can be viewed in the browser and, through the app, offline too.

This doesn't remove the need to communicate with the customer. What changes is that the agency has a reference point where the up-to-date version of the trip lives.

Mistake 9: building every proposal and every checkout from scratch

Even if two groups aren't identical, they often share destinations, hotels, activities, payment structures, forms or services.

Rebuilding everything from scratch increases response time and encourages inconsistencies. An agent may use an old description, forget a condition or set up a service the agency sells frequently in a different way.

A content library lets you reuse:

• Complete itineraries.
• Days or extensions.
• Accommodation and activities.
• Texts and information blocks.
• Booking forms.
• Pricing structures.
• Optional services.

MOGU lets you save these elements and adapt them for each new group. In addition, MOGU AI can turn a request into a first proposal, prepare itineraries, adapt messages and generate payment steps within the platform.

The key is that the AI works inside the workflow and with the available context, but it doesn't replace professional review. The team checks prices, availability, terms and the suitability of the programme before sharing it.

Mistake 10: measuring sales but not the group's operating cost

An agency may know its revenue and supplier costs without knowing how much internal work the trip required.

If a group generates a good commercial margin but demands weeks of emails, changes, checks and payment reminders, its real profitability may be much lower than expected.

Some useful indicators are:

• Average response time to a request.
• Time needed to prepare a proposal.
• Number of changes made before confirmation.
• Hours spent updating information.
• Percentage of seats filled.
• Bookings with missing data.
• Payments completed on time.
• Time spent chasing payments.
• Incidents caused by outdated information.
• Repetitive traveller enquiries.
• Operating cost and final margin per group.

You don't need to measure everything from day one. Start with the points that generate the most workload and compare the results before and after changing the process.

How MOGU helps you manage group trips with more control

MOGU connects the sales, booking and traveller experience phases in a platform designed for travel professionals:

• CRM: links contacts, opportunities, proposals and trips.
• Proposals: lets you create visual, reusable and updatable itineraries.
• MOGU AI: prepares proposals, messages and payment steps within the context of the trip.
• Booking: collects bookings and buyer and traveller details.
• Payments: lets you set up deposits, instalments and additional charges.
• Allocations and options: controls seats, categories, supplements and services.
• Portal and app: keeps itineraries, documents and notifications accessible.

The goal isn't to remove the agent's judgement or necessarily replace the company's GDS, ERP or back office. It's to stop the group's journey from depending on repetitive tasks, disconnected files and knowledge that only lives in certain people's heads.

A group trip will always have changes and exceptions. The difference is whether each change triggers a chain of emails and checks or can be handled within a connected process.

Book a MOGU demo and see how it would work with one of the groups that currently takes up the most of your agency's time.