• Home»
  • Blog»
  • Group Supplier Contracts, Allotments and Confirmations

How Tour Operators Manage Group Supplier Contracts, Allotments and Confirmations

Published On: 

October 28, 2026

Last Updated: 

October 28, 2026
How Tour Operators Manage Group Supplier Contracts, Allotments and Confirmations

The hotel invoices you for 45 rooms. You believe you contracted 40 with an option on five more, and that you released the five in March. The email that settles it is somewhere in an inbox, possibly one belonging to someone who left last year.

You'll probably pay. Not because you were wrong, but because proving you were right costs more than the five rooms.

Most tour operators keep supplier records. The problem is that what was agreed, what space you still hold and what each supplier has confirmed are spread across PDFs, email threads and people's memories. Below: where that goes wrong, how to manage contracts, allotments and confirmations properly, and how to run all three from one system.

Where Group Supplier Management Goes Wrong

Four problems account for most supplier disputes and missed dates.

  • The contract isn't the agreement. The signed PDF holds the original rates and room counts. Everything agreed afterwards (extra rooms, a later release date, a free place agreed by phone) sits in email threads, or nowhere.
  • Quotes and commitments get confused. A rate that was only quoted ends up in the costing as if it were contracted, while a supplier's informal "I'll hold 20 rooms until April" is never written down, so nobody knows whether you're liable for it.
  • Nobody tracks the allotment position. Operators know what they contracted, but not at a glance what's been used, released and left, so release dates and attrition limits get read when the invoice arrives.
  • Requests are sent, but confirmations aren't recorded. Final numbers, manifests and dietary lists go out. Whether each supplier accepted them, and which version, isn't logged anywhere you can find.

The information usually exists. It just can't be assembled in time, and often only one person knows where it is.

How to Manage Group Supplier Contracts

Get the terms that cost money written into the contract. Before signing, check that it states rates by room type and date, contracted capacity, the release schedule with quantities at each stage, attrition terms, deposit amounts and dates, the final payment date, cancellation terms by date band, and what happens to unreleased space. The release schedule and cancellation bands are the two most often left vague, and the two that cost the most.

Keep one live contract record per supplier, per group. It shows those terms as they stand today, not as they were signed. The signed PDF is attached to the record, not a substitute for it.

Record every amendment as a change to that record, dated, with who agreed it on each side. When something is agreed by phone, send a short written summary and ask the supplier to confirm it in a line. That line is your evidence. Suppliers rarely object, because a misremembered conversation exposes them as much as you.

Mark each term as quoted or contracted. A rate stays "quoted" until the supplier commits to it in writing. Costing only from contracted terms closes the gap between the price you sold and the price you're invoiced.

Capture Attrition and Minimum-Number Clauses

These clauses decide what you owe when a group shrinks, and they're the ones most often agreed loosely and read too late.

Hotel attrition. Hotel group contracts usually set a cut-off date, after which unreserved rooms return to the hotel, and an attrition clause, which says how far you can reduce the block without paying for the rooms you drop. One published hotel group agreement, for example, lets the group reduce its block by 10% without penalty up to the cut-off date, and charges for the remainder below that. The percentage, the dates and how "room nights" are counted vary by hotel.

Air minimums. Group air contracts can set a minimum share of the block that must be ticketed. Cathay Pacific's South Africa group terms, for instance, set a minimum of 80% at ticketing. What happens below that line is set in the contract.

Minimum numbers on your own side. Supplier minimums only protect you if your traveller terms carry a matching minimum-numbers condition, with a go/no-go date before your largest supplier commitments; see when to lock the group price with travellers.

For each supplier, record three numbers against the group: the minimum you've committed to, the date it's measured, and what falling short costs.

How to Manage Allotments

An allotment is only useful if you know its current position. For each supplier, per night and room type (or per seat, for coaches and air), track:

  • Contracted: what the supplier is holding for you
  • Allocated: what's assigned to registered travellers
  • Released: what you've handed back, with the date and the supplier's acknowledgement
  • Remaining: what you can still sell

Put each release date and attrition measuring date on the allotment itself, with a named owner, and decide each release against the current headcount before the date passes. How much to keep is a forecast in its own right (how to work out true remaining capacity across suppliers), and the dates belong in one deadline calendar with named owners.

The position should move whenever a traveller registers, cancels or changes room. If it's updated by hand once a week, the number you act on at a release date is already out of date.

How to Manage Supplier Confirmations

Treat every request to a supplier as open until it's confirmed. A valid confirmation names what was agreed, comes from a named person, and carries a date and, ideally, a reference.

  • Log each request: what was sent, to whom, when, and which version.
  • Ask for written confirmation explicitly. "Let me know if there's a problem" produces silence, and silence looks the same as an email that never arrived.
  • Save the reply against the group and supplier, not in an inbox.
  • Chase anything unconfirmed before the date it matters.
  • Reconfirm against the final numbers. When the final rooming list, manifests and dietary lists go out, every supplier gets one last request, and every one has to come back acknowledged before departure. Silence at this stage counts as unconfirmed, not as agreement.

Hotels need one extra step, because rooming lists change many times before arrival: tie each confirmation to the exact version sent, as covered in why rooming lists need version-linked confirmations.

What a Supplier Record Should Hold

Per supplier, per group:

  • Contracted terms: rates, capacity, deposit schedule, release dates, cancellation conditions
  • Attrition and minimums: the committed minimum, when it's measured, and the cost of falling short
  • Every amendment since, dated, with who agreed it on both sides
  • Current allotment position: contracted, allocated, released, remaining
  • Every request sent, with date, recipient and version
  • Every confirmation received, with date and reference
  • Payment status against the contracted schedule
  • Notes from verbal agreements, with the supplier's written confirmation attached

The test is whether a colleague picking up the file can answer "where are we with this hotel?" without calling the person who negotiated it.

Managing Contracts, Allotments and Confirmations in One System

With a few groups a year and a stable set of suppliers, a well-kept folder and a disciplined confirmation habit can work. It breaks when several groups run at once, each with a dozen suppliers and more than one person handling them. The record still exists, but nobody can assemble it when it matters.

A group travel management system keeps all three against each group, in one place:

  • Contracts: current terms per supplier, every amendment dated, quoted and contracted terms marked, and attrition and minimum clauses stored as numbers rather than paragraphs in a PDF.
  • Allotments: the contracted, allocated, released and remaining position updated automatically as travellers register and cancel, with an alert before each release or attrition date showing the current headcount.
  • Confirmations: every request logged with its status, so an unconfirmed supplier shows up on a list instead of at check-in. Here's how one operator tracked every manifest it sent to acknowledgement, supplier by supplier.

For an established operator, this doesn't mean replacing the booking platform. The group layer can be built into the platform you already run, so supplier terms, allotments and confirmations sit next to the travellers and bookings they apply to.

Frequently Asked Questions

Produce the release: the email, the date, the recipient and, ideally, their acknowledgement. Then check it against the contract: whether the release fell inside the release schedule and the attrition allowance, and whether the disputed rooms were an option or part of the contracted block. If your own record is thin, ask the hotel for its pick-up report for the block, which shows rooms held and used by date. If you still can’t show it, you’ll generally pay, because the dispute costs more than the amount. That’s exactly what recording releases and confirmations protects against.

One named person per supplier per group, usually in operations rather than whoever negotiated the deal. The negotiator’s job ends with getting every agreed term into the record, including anything agreed by phone. The owner keeps the allotment position, release decisions and confirmations current from then on. If the owner changes, the record moves with the group, not with the person.

Yes, if the system can hold terms against each group and allotment, not just against the supplier. Most booking systems store supplier details and bookings, but not the contracted block, its amendments, its release schedule and the confirmations behind it. That’s the part a group layer adds.

Read more on:

Industries



      +  47  =  51

    Ravi Makhija

    Ravi Makhija is the Founder and CEO of Guru TechnoLabs, an IT services and platform engineering company specializing in Web, Mobile, Cloud, and AI automation software systems. The company focuses on building scalable platforms, complex system architectures, and multi-system integrations for growing businesses. Guru TechnoLabs has developed strong expertise in travel technology, helping travel companies modernize booking platforms and operational systems. With over a decade of experience, Ravi leads the team in delivering automation-driven digital solutions that improve efficiency and scalability.

    linkedin-icon twitter-cion
    Ravi Makhija
    Why Group Tour Availability Becomes Hard to Track When Every Supplier Has a Different Capacity Why Group Tour Availability Becomes Hard to Track When Every Supplier Has a Different Capacity