A weather problem quickly becomes a communication problem when guests, guides and booking partners receive different answers. “We are watching it” may be true, but it leaves travelers wondering whether to eat breakfast, leave the hotel or cancel their transport. The operator needs a clear decision process and messages that translate uncertainty into practical next steps.
This playbook is an operating framework, not a set of weather thresholds. Decisions about vessels, trails, vehicles and activities belong to the responsible qualified people and relevant authorities. Product conditions and booking-channel rules also matter. Prepare the communication before conditions deteriorate, while checking the actual requirements for your business and departure.
Write the decision chain before the first disruption
Identify who monitors conditions, who assesses the activity and who has authority to cancel or change it. A booking assistant may gather information without being the person who decides whether a boat sails. Name a backup for each essential role so the procedure still works when the usual owner is unavailable.
The decision record needs the affected product and departure, assessment time, source information, responsible person and next review point. Include relevant authority or site notices where applicable. Do not reduce the record to “bad weather” if the actual problem is a specific closure, inaccessible meeting point or unavailable resource.
Decide who communicates the result to guests, guides, drivers, sales channels and other suppliers. One coordinator should keep those updates aligned. A guide's operational decision and an office's guest message should describe the same outcome, even when they are sent by different people.
Use relevant official information without treating it as the whole decision
Choose sources appropriate to the location and activity. For Thai marine operations, the Thai Meteorological Department publishes a shipping forecast and separate warning information. Those are primary resources for the assessment; a general phone weather icon is not a substitute for the relevant forecast and operational advice.
Check the issue time and geographic coverage. A screenshot from an earlier bulletin can circulate long after a newer assessment exists. Save the source link and timestamp in the internal decision record so a colleague can see what was considered. Do not present an old warning as a current condition.
Official information does not remove the need to assess the actual route, site and service. Equally, sunshine at the office does not disprove poor conditions elsewhere. Keep the guest explanation factual and proportionate. It should identify the consequence for their booking without turning the message into a speculative forecast or a technical debate about safety.
Define three operational states
Use “monitoring” when a decision remains pending, “confirmed change” when an approved alternative arrangement exists and “canceled” when the booked departure will not operate. Each state should trigger a different message and a different set of internal tasks. Avoid calling everything a delay.
Monitoring requires a next update time and clear guest instructions in the meantime. A confirmed change requires a precise description of what differs, what remains included and any decision the guest must make under the applicable process. Cancellation requires stopping the original plan and initiating the relevant booking follow-up.
Set review points that fit the preparation and travel needed. A departure with a long pickup route may need an earlier decision than a short local activity. Do not copy a review deadline from another product simply because its start time is similar. Work backward from when guests and suppliers need actionable information.
Send a useful monitoring message
Use this original starting template: “We are reviewing conditions for booking [reference], [activity], [date]. The departure is not yet canceled. Please [specific instruction] while we confirm the plan. We will update you by [time and time zone] through [channel]. Contact [monitored route] if you need help before then.”
The bracketed instruction is essential. Tell the guest whether to remain at the accommodation, continue to the meeting point or wait for further confirmation, according to the actual operational decision. Do not leave that action implied by a reassuring sentence about monitoring.
Avoid promising that conditions will improve or that a decision will be favorable. If you cannot meet the stated update time, send an interim update with a new review time and the reason for the delay. A short honest message is more useful than silence while staff search for certainty they do not yet have.
Explain a changed itinerary as a real product decision
When a change is proposed, specify the original element, the replacement and the practical effect on the day. A different island, shorter walk or altered transfer can matter even if the duration and price remain similar. Do not describe an alternative as equivalent solely because it is convenient for the operator.
Confirm that the alternative is actually available before offering it. Check resources, access, inclusions, pickup and timing again. If a guest response is required, state the deadline and what happens if they cannot be reached. Follow the booking channel's relevant process rather than privately changing the service while leaving the original record untouched.
A useful template is: “The planned [element] cannot take place because [verified reason]. We can offer [specific alternative], which changes [material details]. Please review [relevant terms or process] and reply by [time] with [required decision]. We will confirm the resulting arrangement in writing.” This is a communication pattern, not a statement of universal guest rights.
Cancel the departure through every affected part of the operation
Once cancellation is decided, identify all affected bookings, including phone, hotel, agent and direct sales. Check the product, option, date and departure before taking a batch action. A broad date filter can include another tour that remains unaffected. Have a second person review the selection when the scale or consequences justify it.
GetYourGuide's supplier cancellation guide documents its own single and batch workflows and associated notifications. If you sell there, follow the current procedure. Other channels can work differently, so do not assume a cancellation entered in one place updates every separate booking source.
Close affected availability as required and notify the guide, driver and relevant suppliers. A guest message alone does not stop a pickup vehicle leaving the depot. Record who acknowledged the cancellation and what remains to be done. If the business uses Tripnatic, use its current booking and communication controls without assuming automatic updates to unrelated systems.
Use the correct reason and a clear guest message
Distinguish operator cancellation from a customer choosing not to travel. The reason affects the accuracy of the record and can affect the channel's handling. GetYourGuide's cancellation-reason guidance explicitly separates operational issues, force majeure and customer requests. Apply the actual categories of the channel you are using.
Do not ask the guest to cancel simply to make an operator-led cancellation appear customer-led. If an offered alternative is declined, record what actually happened. Keep the evidence and explanation factual; avoid exaggerating a forecast or labeling an ordinary resource problem as weather.
An original cancellation template is: “We have canceled [activity and departure] for booking [reference] because [verified reason]. Please do not travel to [meeting point] for this departure. Your next step is [specific rebooking or cancellation process]. [Named team or channel] will handle [action], and we will update you by [time].” Only promise a refund amount or processing step once the applicable decision is confirmed.
Track rebooking and payment actions separately
A guest accepting another date needs a fresh availability check, updated pickup arrangements and a revised confirmation. Record what happens to the original booking and any price difference under the applicable process. Do not simply move a name on a guide list while leaving the commercial record on the canceled departure.
For a refund, distinguish approved, requested from the provider, processing and completed. Stripe's refund documentation explains that refunds can have pending or failed outcomes and may require follow-up. This is an example from a separate payment provider, not a claim of a Tripnatic integration or a universal processing time.
Tell guests what has actually happened: “The refund request was submitted on [date] under reference [reference]” is different from “The money is in your bank.” Give the provider's current timing information where relevant and say who will investigate if the expected progress does not occur. Keep sensitive payment information out of general operational messages.
Run a short disruption register until every booking is resolved
Create one row per affected booking with the decision, guest contact status, selected option, channel action, payment action, owner and next review. A departure-level note saying “all canceled” cannot show which guest has not received an update or which refund needs investigation.
Prioritize guests whose immediate movements are affected, such as those about to leave accommodation for pickup. Then work through the remaining records methodically. Use the original booking channel where required and an appropriate operational contact route when timing is urgent. Record attempts without repeatedly sending conflicting messages from different staff phones.
For group bookings, establish whether the lead contact is responsible for briefing everyone. Separate accommodations or independently arriving travelers may need distinct instructions. A single acknowledged message does not establish that every party member has stopped traveling to the meeting point. Keep the distribution plan tied to how the group is actually organized.
If a disruption occurs after pickup or after part of an activity, establish a separate case with the actual service delivered and the responsible operational decision. Do not use a pre-departure cancellation template that incorrectly says the guest should stay at the hotel. The immediate message should explain the current arrangement, such as where the group will go next and who is coordinating its return, using only confirmed facts.
The commercial follow-up may require a separate review of the booking terms and the circumstances. Keep that review distinct from directing the guest's immediate movements. Record the actual timeline and relevant changes while they are fresh, then give the guest a named contact and a realistic response deadline. Avoid debating compensation in a group chat while staff are still coordinating transport. A factual record helps the appropriate person assess the case later without asking every guest to reconstruct the whole day.
Review the incident and improve one part of the playbook
After the immediate workload has settled, compare the decision time, first guest update, supplier acknowledgements and completion of follow-up. Ask where uncertainty remained unnecessarily. The issue may be a missing contact number, an unclear alternative or a channel action that only one person knew how to complete.
Rehearse the playbook with a hypothetical cancellation affecting both online and manual bookings. Have a colleague take over halfway through using only the disruption register. They should identify who has been contacted, whether sales are closed and which actions remain pending. Correct the procedure before relying on it during a real interruption.
Keep approved templates together with their owner and review date. Review them when booking terms, pickup arrangements or channel procedures change. Templates should speed accurate communication, not preserve an obsolete promise. Avoid copying a platform's current refund wording into a universal template for all your customers.
A practical readiness check covers five questions: who decides, which evidence is reviewed, when guests hear next, which systems and suppliers need action and who closes each booking's follow-up. Keep the answers short enough to use during a busy morning. If the process requires the owner to remember several unwritten exceptions, document those before adding more automation.
The customer-service template guide can help standardize the wording, while Tripnatic for operators explains the current operator workflow. The most useful weather plan gives people a clear action while respecting the limits of what is known. It remains useful even when the final outcome changes.
