How to handle last-minute changes with tour guides without losing any

Why do last-minute changes go wrong?

A tour operator emails at 21:00 to move tomorrow’s pick-up from 9:00 to 8:30. Someone in the office reads it, messages the guide and goes home. Nobody tells the coach company. At 8:30 the guide is at the hotel and the coach is not.

The change itself was simple. It went wrong for three reasons that appear in almost every incident:

• Several channels: the change came by email, went out on WhatsApp and the spreadsheet still shows the old time.
• Sent was treated as confirmed: a message was delivered, but nobody checked that the guide had seen it and agreed.
• Only part of the chain was told: the guide knew, the driver, the tour leader and the venue did not.

A protocol fixes all three, and it does not depend on people being more careful. It depends on everyone doing the same steps in the same order.

What counts as a last-minute change?

Any change made after the guide has confirmed the service. In practice, these are the ones that come up again and again, and each affects different people:

A protocol for last-minute changes, step by step

Seven steps, in this order. It takes longer to read than to do.

1. Record the change in the service first

   Update the time, meeting point, PAX or status in the service record before telling anyone. That record is the version everybody works from.

   Red flag: If the first place the change appears is a chat, the spreadsheet or system will be wrong within the hour.

2. List who it affects

   Use the table above: guide, driver, tour leader, venues, client. Do not rely on memory at 21:00.

3. Notify through the agreed channel

   The one your agency uses for operations, the same every time, with the full new details, not just what changed.

4. Ask for an explicit confirmation

   A written reply, not a read receipt. Until it arrives, the change is open.

5. Phone whoever has not replied in time

   Set your own threshold, for example any change for the next morning that is still unconfirmed by 22:00.

6. Close the loop with the client

   Tell the tour operator or tour leader that everyone has confirmed, or what is still open.

7. Leave it in the history

   Who changed what, when, and who confirmed. It settles disputes and feeds the monthly review.

How do you know a guide has really seen the change?

You ask. A delivered email or a double tick only tells you the message reached a device. It does not tell you the guide read it properly, noted the new time or is able to make it.

Make confirmation part of the agreement with your guides: every change gets a reply, even if it is just “confirmed”. Most guides prefer it, because it protects them too. With the change and their reply in writing, there is no argument later about what time they were given or where the group was waiting.

The same logic applies to the first assignment. A service is not covered when the message goes out but when the guide accepts. We go into that in tour guide assignment.

What do you do when a guide falls ill on the day?

It will happen, usually on the busiest day of the season. The work is done before that day:

• A backup list per language: two or three guides who know they may be called at short notice, in the order you will call them.
• One person who decides: on duty, with the phone, so the guide who is ill knows who to call and the decision is not made by a group chat.
• A complete hand-over: the replacement gets the full service, the tour leader’s contact, tickets and any notes, not a forwarded chain of messages.
• The client told if needed: if the tour operator was given the guide’s name, tell them about the replacement before the group meets someone unexpected.

Record the replacement in the service. At the end of the month, the guide who did the work is the one who invoices it, and the one who was ill should not find the service on their list.

Who pays when a tour is cancelled at the last minute?

That depends on what you agreed with the client and with the guide, and the two are separate conversations. Many agencies set cancellation terms in their guide rate card, for example a share of the fee if a service is cancelled after a certain point the day before. Whatever you choose, write it down, share it before the season and apply it the same way to everyone. Our guide on how to set tour guide rates covers cancellation terms alongside the rest of the rate card.

In the record, a cancelled service should stay visible as cancelled, not be deleted. Deleted services are the ones that reappear as disputes when the invoices arrive.

What should the guide do when a change arrives?

The protocol works better when guides know their half of it. Share a short version with every guide before the season, ideally on one page:

• Reply to every change, even if it is just to confirm. Silence is treated as not confirmed.
• Say straight away if you cannot make it. A no at 21:00 can be solved; a no at 8:00 often cannot.
• Check the service record, not old messages, before leaving home on the day.
• Report changes you hear about on site, for example a tour leader who moves the lunch stop, so the office can update the record and tell the driver.

How do you stop changes getting lost across channels?

With one rule: the service record is the truth, every other channel is an alert. You can still call a guide or send a quick message when a change is urgent, but the change itself lives in the record, and anyone who wants to check the time looks there.

• One record per service, with time, meeting point, PAX, language, guides and status.
• Conversations attached to the service, not in a group with forty other conversations.
• A duty rota for out-of-hours changes, so the 21:00 email is read by someone with the authority to act.
• A monthly review of the changes: if the same tour operator always changes the PAX the night before, it is a conversation to have with them.

The full method for keeping guides and services in one place, from request to invoice, is in how to manage your agency’s tour guides. And if changes have already led to two services on the same guide, see how to prevent tour guide double booking.

How does Partners handle last-minute changes?

In Partners, each service is a request with its time, meeting point, PAX, language, guides and status. When you change the time, the PAX or the meeting point of a service that was already accepted, the request moves to Modificado (Modified) and the guides involved get an email. The change stays in the service history, and every guide sees their own calendar updated.

The email is not where the change counts as communicated. Every guide affected has to accept the service again in Partners, and that second acceptance is their explicit “OK, I have seen the change”. Until they do, you can see in the request that the change has not been acknowledged; once they accept, it goes back to Aceptado (Accepted). That is the explicit reply from the protocol above, built into the service, so nobody in the office has to chase confirmations on WhatsApp.

Questions about the change go in the chat inside that request, with unread indicators, so the conversation stays with the service rather than in someone’s phone. If you need a replacement, Partners suggests guides by language and availability and flags who already has a service that day. Guides use a free portal on their phone, with nothing to install.

Notifications go by email, so for very short notice changes a phone call is still part of the protocol. Pro costs €79 a month (excl. VAT) for up to 50 guides, and the first 25 agencies pay the founder price of €49 a month, fixed.