Twelve emails, three attachments and a phone call
Your tour leader is due to meet a group in Lisbon on Saturday. Over the past fortnight they have received the passenger list, two versions of the rooming list, a spreadsheet of supplier contacts, a PDF of the itinerary, the transfer plan, a note about a passenger's hearing aid, and an email saying the restaurant on day five has changed. On Friday evening the operations manager rings to go through it all and mentions a route diversion from last month's leader report.
On day three, a hotel asks about a passenger's late arrival, and the leader scrolls through their inbox on the coach trying to work out which version of the rooming list is current.
The briefing is scattered because the information is
Each piece of the briefing comes from a different place in the office. Operations holds the itinerary and suppliers, the booking system holds passengers, someone else holds the transfers. Nobody assembles them, so the leader does.
- Every update is a new email, so old versions linger.
- Supplier contacts and confirmation references are in a separate sheet.
- Passenger requirements come in their own message.
- Route and practical notes from previous leaders are not passed on.
- Leaders cannot easily tell what has changed since they last looked.
Leaders work from stale information
A leader working from an old rooming list or an old restaurant booking creates problems on the ground that the office has already solved. Leaders also spend their first evenings on tour re-checking paperwork rather than getting to know the group.
For the office, the Friday phone briefing takes an hour per departure in the busy months, and depends on the operations manager remembering everything that changed.
One briefing pack that updates itself
We build a leader briefing that pulls each part from where it already lives.
- Each departure has a briefing page for its leader, secured by a login, which works on a phone and saves for use without signal.
- The passenger list, rooming by night and requirements come from the booking system and rooming list generator.
- Supplier bookings for each day, with confirmation references and contact numbers, come from the confirmation tracker.
- Transfers, float and planned on-tour payments come from the transfer planner and float log.
- Route and practical notes are attached to the tour, including points raised by earlier leaders, so each leader sees what the last one learned.
- Emergency contacts and your own procedures documents sit in a fixed section.
- Whenever something changes, the leader gets a short notification of what changed, and the page shows the change highlighted until they have seen it.
| Briefing section | Source |
|---|---|
| Passengers and requirements | Booking system |
| Rooming by night | Rooming lists |
| Daily services and contacts | Supplier confirmations |
| Transfers and float | Transfer planner and float log |
| Route notes | Tour notes and previous leader reports |
Briefing a leader in a few minutes
A week before departure, the leader opens their briefing and reads it at their own pace. The Friday call becomes a short conversation about the group and anything unusual, not a read-through of documents. When a restaurant changes during the tour, the leader gets a notification and the new booking is on the page.
When a hotel asks a question on day three, the leader opens the page for that night and has the current rooming list and the booking reference in front of them.
New leaders benefit most. Someone leading a tour for the first time gets the same structured briefing as a veteran, including the practical notes that used to live only in experienced leaders' heads: where the coach can actually stop, which lift is out of order, which restaurant needs the numbers confirmed the morning before.
Are leaders briefed by email?
- Leaders receive their briefing as many separate emails.
- Leaders have worked from old versions of rooming lists or bookings.
- Notes from previous leaders do not reach the next one.
- Briefing calls take a long time and rely on memory.
- Leaders cannot see what has changed since they last looked.