Last year's document with this year's dates, mostly
Six weeks before each departure, someone opens the final documents from the same tour last season. They change the dates, swap one hotel that changed, update the tour leader's name and mobile number, and check the meeting point. Then they personalise it for each booking, adding flight details or the pre-tour night for those who booked one.
Most of the time it works. Occasionally a passenger arrives at last year's meeting point, or a document lists a hotel you stopped using. Once, a tour leader's old mobile number went out to a whole group.
Word documents carry old facts forward
The problem is that each departure's documents are a copy of a copy. The tour itself has a stable core (the route, the daily pattern, what to pack) and a set of details that change per departure. When both are mixed in one Word file, the changing details are edited by hand and some are missed.
- Day-by-day dates are typed rather than calculated from the start date.
- Hotel names and addresses are pasted in, not drawn from the allocation.
- Emergency and tour leader contacts are copied from old files.
- Passenger extras (pre-night, transfers, room upgrades) are added by hand per booking.
- Nobody checks the finished pack against the booking system before it goes.
One wrong detail travels to every passenger
A wrong meeting time or place can leave passengers stranded at the start of a tour, which is the worst place to lose goodwill. Wrong contacts mean the one number a passenger needs in trouble is out of date. Even small mistakes, like a hotel name spelled differently from the one on the booking confirmation, generate phone calls from worried travellers.
The time cost is steady and large in peak months: producing documents for a week of departures can occupy someone for days.
Documents generated from a template and the departure
We separate the parts that stay the same from the parts that change, and then join them automatically.
- Each tour gets a master template: route, daily narrative, what is included, what to bring, activity notes. Your team edits it in a simple editor, and changes apply to all future departures.
- Each departure supplies its own data from your booking and allocation records: start date, hotels per night with addresses, meeting point and time, tour leader and emergency contacts.
- Day numbers become real dates automatically, and each night's hotel is pulled from the allocation, so a hotel change updates the document.
- Each passenger's pack adds their own details: names, room type, pre and post nights, transfers, optional excursions booked, from their booking.
- Before release, a check compares every pack with the booking system and lists anything missing or inconsistent, such as a passenger with no transfer time or a hotel with no address.
- Packs are sent by email or made available in a passenger area, with a log of who received and opened them. A print version is produced for passengers who want paper.
| Part of the document | Where it comes from |
|---|---|
| Daily route and narrative | Tour template, edited centrally |
| Dates for each day | Calculated from the departure start date |
| Hotels and addresses | Allocation records for that departure |
| Tour leader and emergency numbers | Guide schedule and office settings |
| Transfers and extras | The passenger's own booking |
What changes on the operations desk
Producing a departure's documents becomes a review rather than a rewrite. The operations person opens the departure, reads the pre-release check, fixes the two things it flags in the booking system (one missing flight time, one hotel phone number), and releases the packs.
When a hotel changes a fortnight before departure, the affected passengers get an updated document, not an email saying "please note". When the tour leader changes, their number changes everywhere at once.
The master templates also become the single place to improve the text. A better packing list written once reaches every future departure.
Does document season feel like this?
- Final documents start from last year's Word files.
- Passengers have been sent old meeting points or contacts.
- Each passenger's extras are added to documents by hand.
- Hotel changes near departure mean rewriting documents.
- Nobody checks packs against bookings before they go.