The reflex is to cancel
It is 6:40 and the skipper calls: the starboard engine will not start, and the mechanic cannot come before Thursday. The boat has three departures a day. The fastest thing is to cancel everyone. It is also the most expensive: lost revenue, refunds, bad reviews, and guests who will not rebook.
Most of those departures can still run. They need a different boat, a different time or a merged trip. The hard part is seeing that quickly, under pressure.
The checklist
- List what is affected first. Every departure the boat was on, from now until it is fixed, with the number of guests on each. Do not change anything until you have the list.
- Check which other boat qualifies. It must have what this tour needs: enough seats, the right equipment, the right licence for the area. Write those requirements per tour in advance.
- Move times before cancelling. If the other boat is busy at 9:00, can the trip run at 10:30? Before moving, know how many guests that affects and whether the crew is free at the new time.
- Merge light departures. Two half-empty trips on the same day can become one, if the remaining boat has room for every party.
- Raise capacity where a bigger boat steps in. A larger replacement can take extra bookings.
- Cancel last, with a reason. Write down why, so whoever calls guests can explain, and so you can look back on it.
- Call guests from the list, starting with the next departure.
Options, from least to most disruptive
- Assign another boat that qualifiesAny boat with the capabilities the tour asks for
- Move the timeSee how many guests it affects before you confirm
- Merge light departuresMove bookings only where the whole party fits
- Cancel, with a reasonLast resort; the reason is kept
Four stacked options, least disruptive first. Assign another boat that qualifies. Move the departure's time, seeing how many guests it affects. Merge light departures by moving bookings where there is room for the whole party. Cancel last, with a reason that is kept.
How ItinerWiz helps
ItinerWiz is the operating platform for independent experience businesses. In ItinerWiz:
- Impact before the change. Taking a boat out of commission, or planning maintenance, names the affected departures and their bookings before you confirm. With nothing affected, it applies at once.
- Tours ask for capabilities, not a specific boat. So any boat with those capabilities can be assigned, and a boat out of commission is no longer offered.
- Gaps become problems. A departure missing what it needs appears on the Problems list, saying what is missing, how many bookings it affects, and by when to decide. Each problem leads to its fix, and closes once the gap is filled.
- Time changes say who they move. Changing a departure’s time shows how many bookings and guests move with it, and warns if a crew member is busy at the new time.
- Capacity can be raised on a departure, never below the guests already booked.
- Bookings move only where the whole party fits. Only departures with room for the whole party are offered.
- Run anyway needs a reason, which is kept with who decided and when.
- Cancelling restates what it cancels, such as “2 bookings (5 guests) will be cancelled”, and records your reason. The departure’s crew and boat are free again for that time.
- Back in commission, the boat is offered again.
Taking a boat out of commission
- 1Operator → ItinerWizTake boat out of commission
- 2ItinerWiz → OperatorDepartures and bookings affectedNothing changed yet
- 3Operator → ItinerWizConfirm
- 4ItinerWiz → OperatorProblems: what is missing, by when
The operator starts taking a boat out of commission. ItinerWiz names the departures and bookings affected before anything changes. The operator confirms. The boat stops being offered. A departure left without a boat it needs shows as a problem saying what is missing and by when to decide.
Telling guests, and what no tool can do
Working from the affected bookings, your team decides who moves and who is offered a refund, then texts the guests by SMS from ItinerWiz. Maintenance logs and engine hours stay with your yard. And no tool can promise you will never cancel: some days the weather or the fleet decides.
Where to go next
Before the next breakdown, write down what each tour needs from a boat, so the “which boat qualifies” step is instant. If the breakdown also takes a skipper off the water, read planning crew for peak season. For the vocabulary, see what a departure is. To try it on your own fleet, join as a Founding Operator or see pricing.
Frequently asked questions
Should I cancel all departures when a boat breaks down?
Not by reflex. First list the affected departures and guests, then check whether another boat qualifies, whether times can move, and whether light departures can merge. Cancel what is left, and tell guests why.
Can another boat take a tour it does not usually run?
If it has what the tour needs, such as enough seats, a shade cover or a licence for the area. Decide those requirements per tour in advance, so the question takes seconds on a bad morning.
Can ItinerWiz tell guests about the change?
Yes, by SMS. It shows which departures and bookings are affected, lets your team move or cancel them with the impact restated, and you text the guests from ItinerWiz.
How do I bring the boat back once it is repaired?
Put it back in commission. In ItinerWiz it is then offered again for departures that need a boat like it.