The complete guide to event travel reconciliation

Every event lives or dies on a simple question: is everyone actually going to be there, in the right place, at the right time? Answering it means making four lists that never talk to each other — registration, flights, hotels, and transfers — agree. This guide is the complete method for doing that: why the lists drift apart, how to cross-check them, when to run the checks, and what to watch for. Every step works in a plain spreadsheet; GroupGrid just runs the tedious parts for you.

Why event travel reconciliation matters

The mistakes rarely look expensive in the moment. A room booked for the wrong night. A flight that lands after check-in. A name that doesn’t match. Individually small — but multiplied across an event, they quietly become the biggest line item nobody planned for.

And they’re common. In a Corporate Traveler survey of 255 business decision-makers, 55% admitted to costly travel-booking mistakes made in-house — going over budget, booking too late, or choosing the wrong services. Coordinating one trip, the odds are manageable. Coordinating a hundred attendees across separate registration, flight, hotel, and car files, they compound. Reconciliation is how you get ahead of that number instead of paying for it.

The four lists — and why they disagree

The truth about any group trip is spread across files that were never designed to line up:

• Registration — who said they’re coming, their dates, and their requests.
• Flight manifest — who’s actually ticketed, in a different format with different spelling.
• Hotel rooming list — who has a room, for which nights.
• Ground transfers — who has a car, and when.

They disagree because they’re maintained by different people, at different times, in different systems. The eye can’t reliably hold four lists in its head, and the one thing you need to notice — an absence, a mismatch, a duplicate — is exactly what scanning rows tends to skip. Two setup habits fix most of it: put all four in one workbook, and match on email, not name (names get misspelled and reordered; email is unique and stable).

The cross-check method

Cross-checking means comparing the lists against each other and letting the mismatches surface, instead of reading each one on its own. Four questions catch the overwhelming majority of costly problems.

1. Registered, but nothing booked

On the registration tab, look each person up in the manifest and roster by email:
=IF(ISNA(XLOOKUP(email, Flights!Email, Flights!Email)), "⚑ No flight", "ok")
Filter to the flags — that’s your call sheet of people who still need a booking.

2. Booked, but never registered

Run the lookup the other direction. A flight or room with no matching registration is a drop, a duplicate, or a ghost — confirm it or release it while a refund is still possible.

3. Dates that don’t line up

Put arrival next to check-in and let math notice: =hotel_checkin - flight_arrival. Anything that isn’t 0 (or your expected offset) is a mismatch — a flight landing after check-in, a departure before check-out, a transfer on the wrong day. Conditional formatting turns the exceptions red.

4. Wrong airport or outside the window

Filter the arrival-airport column to anything that isn’t your event airport, and dates to anything outside your approved window. Two filters, two short lists to confirm.

With GroupGrid, all four questions answer themselves the moment you upload the files — every gap flagged, with the exact mismatch. For the deeper version of this, see Case closed: playing detective with your travel data.

The pre-event timeline

A cross-check you run once feels like admin. A cross-check you run on a rhythm is what keeps an event from unraveling. Three checkpoints do most of the work:

• T‑6 to T‑4 weeks: your first full reconcile, while the block is open and fares are still sane. This is where the real money is saved.
• Weekly: a quick re-run to catch late registrations, drops, and swaps before they compound.
• T‑1 week: the final pass, so nothing reaches the front desk as a surprise.

Airfare and hotel rates climb sharply in the last couple of weeks, which is exactly why the early checkpoint matters most. The full lifecycle version lives in The event travel playbook.

Red flags to watch

Once you’re cross-checking regularly, the same warning signs come up again and again:

• A registrant with no flight and no room a few weeks out — the classic “I thought that was booked”.
• Two rooms or two flights for one person — a duplicate quietly burning budget.
• Arrival after check-in, or departure before check-out — a guest who technically has both bookings but can’t actually use them.
• Nights outside the block, or the wrong airport — usually an honest self-booking mistake, cheap to fix early.
• A name on the manifest that isn’t on the registration — a drop that never got released.

More on each in Red flags in event travel bookings.

VIPs and the last mile

Some travelers you simply cannot afford to strand. Keep a short VIP watch list — executives, speakers, key customers — and hand-verify their whole journey end to end: flight, transfer timing, room, checkout. The one guest you can’t afford to strand is the one to check twice.

And remember the last mile. The flights and rooms can be flawless and the event can still start badly if getting from the airport to the venue falls apart. Pre-book transfers instead of leaving guests to a rideshare app, cross-check the transfer file against arrival times so no one lands to no ride, and keep a little buffer and a Plan B for the inevitable delay.

Your reusable checklist

Set this up once and run it for every event:

• Collect full legal name, email, arrival/departure dates, and “need travel booked?” at registration.
• Put registration, flights, hotel, and transfers in one workbook; de-dupe by email first.
• Run the four cross-check questions: unbooked, unregistered, mismatched dates, wrong place.
• Reconcile at T‑6/‑4 weeks, weekly, and T‑1 week.
• Keep a running “needs attention” list — it’s your status report and your paper trail.
• Hand-verify every VIP end to end, and confirm the last mile.

Do it once and it feels like admin. Do it every event and it’s the difference between a budget that holds and one that quietly bleeds — and an arrival day that runs itself.