Three weeks before departure, the copying starts
A departure of eighteen passengers staying in four hotels needs four rooming lists. Somebody opens the booking system, copies names into a spreadsheet, works out who is sharing with whom from the booking notes, marks the singles, adds the dietary notes and the ground floor request, and emails it to the first hotel. Then they do the same for the next one, which wants a different layout.
Two days later a couple change from a double to twins. A single traveller who had asked to share is now paying the single supplement. One passenger cancels. Each change is an email to four hotels, and at arrival one of them still has the old list printed at reception.
Why rooming lists go wrong
The information is correct in the booking system, more or less. The problems come from copying it by hand, per hotel, and then keeping four copies in step.
- Sharing arrangements sit in free-text notes, not in a field the list can use.
- Names are spelled differently on the booking and on the passport details.
- Each hotel asks for a different layout, so no template fits all of them.
- Changes after the first list are sent piecemeal and nobody tracks which version each hotel has.
- Requests such as adjoining rooms or a walk-in shower live in a separate notes column.
What a wrong list costs on arrival night
A tired group arrives at 7pm. Two friends who booked twins have been given a double. A passenger's gluten-free note never reached the kitchen. Someone who cancelled is still on the list and the hotel charges the room. The tour leader spends the first evening at reception fixing it, and the passengers' first impression of the trip is the queue.
In the office, the cost is hours spent building lists by hand every week in the busy months, and the worry that one of the dozens sent this month is wrong.
Rooming lists generated from the bookings
We build rooming list generation into your booking workflow, so the list is produced rather than typed.
- Room sharing becomes structured data on the booking: who shares with whom, room type and bed type, rather than a line in the notes. Existing notes are converted once, with a person checking the ones that are unclear.
- Passenger names come from the booking, and the list flags any name that differs from the passport details you hold.
- Each hotel has its own template, set up once: columns, order, language, and whether they want dietary and mobility notes on the same sheet.
- The list for every hotel on a departure is generated in one step, as a spreadsheet or PDF, and sent from your mailbox with a version number.
- When a booking changes, the system works out which hotels are affected and prepares a change notice showing only what moved, with the new version attached.
- The system records which version each hotel has acknowledged, so you can see at a glance who is out of date.
| Change | Old way | New way |
|---|---|---|
| Double to twin | Email each hotel | Change notice generated for affected hotels |
| Passenger cancels | Remember to tell everyone | Removal appears on the next version |
| New sharer matched | Edit four spreadsheets | One booking change, lists regenerated |
| Hotel asks which list is current | Search sent items | Version and acknowledgement shown |
The week before departure, done differently
The operations person opens the departure, checks the sharing summary, and sends all four rooming lists at once. When the double becomes twins, the change notice goes to the three hotels where it matters. The day before arrival, a final version goes out, and the tour leader gets the same list on their phone.
If a hotel has not acknowledged the latest version, it shows on the departure screen, and someone rings them. That is the only manual chasing left.
Is rooming list day a problem in your office?
- Rooming lists are copied by hand from the booking system.
- Sharing arrangements are written in booking notes.
- Each hotel's list is formatted separately.
- Late changes go out as loose emails without version numbers.
- Tour leaders find room mix-ups on arrival.