Nine booked, minimum twelve, and the hotel wants an answer
It is a Tuesday in March. Your October walking tour in Andalucia has nine passengers against a minimum of twelve. The hotel in Ronda has emailed to say the allocation releases on Friday unless you confirm. The guide wants to know whether to keep the dates free. The director says leave it another week, it usually picks up. Nobody is quite sure whether the brochure promised a decision date to passengers, or what it was.
Multiply that by every departure in the programme. Some dates are comfortably over minimum, some are hopeless, and the awkward middle band is where the time goes. Each one is judged separately, from a spreadsheet that shows passenger counts but not the dates that matter.
The numbers live in one place and the deadlines live everywhere else
Passenger numbers usually sit in the reservations system or a bookings sheet. The dates that force a decision sit elsewhere: hotel release dates in contracts and emails, guide confirmation dates in someone's diary, the date you told passengers you would confirm by in the booking terms. Nothing brings them together per departure.
- Minimum numbers are set per tour, but some departures quietly have a different one.
- Release dates differ by hotel, so one departure can have four of them.
- Guides and tour leaders are held on a promise rather than a booked date.
- The decision deadline you gave customers is written in the terms, not in the system.
- Nobody owns the weekly review, so it happens when someone remembers.
The result is that the go or cancel decision is made by feel, and usually late. What your terms say about cancelling a departure, and what you owe passengers if you do, is for your own terms and your adviser. We deal with getting the facts in front of you in time.
A late call is expensive both ways
Cancelling late upsets passengers who have booked flights and time off, and it burns the goodwill of the hotels who held rooms for you. Running a departure that should have been cancelled means operating at a loss, because the coach, guide and fixed costs are the same for nine as for sixteen. Letting an allocation release by accident, when the departure was going to run, means scrambling for rooms at a worse rate or in a worse hotel.
There is also the hidden cost of the review itself. Someone spends a morning each week pulling numbers, opening contracts and chasing opinions, and the answer is still a judgement made under pressure.
A departure board built around the decision
We build a departure view that reads bookings from your reservations system and holds the decision dates alongside them.
- Each departure pulls its live passenger count and the rooms already taken from your booking system, through its API or a scheduled export.
- The minimum and the target numbers are set per tour, with an override per departure where you need one.
- Supplier dates are entered once per departure: hotel release dates, guide confirmation dates, coach and restaurant deadlines. We can read them from the contract schedule if it is a consistent spreadsheet.
- The earliest date that forces a decision is calculated for each departure, and the board sorts by it, so the next decision is always at the top.
- A simple costing shows the break-even passenger number from your own fixed and per-head costs, so you can see how far below it the departure is.
- A weekly summary goes to whoever makes the call, listing departures that need a decision in the next few weeks, with the numbers and the dates.
- When you record the decision, the system creates the follow-on tasks: confirm the allocation, release the rooms, tell the guide, and send passengers the right message from a template you approve.
| Departure status | What the board shows | What happens next |
|---|---|---|
| Over minimum | Green, with the next supplier date | Confirm allocations and guide |
| Close to minimum | Amber, with days until the deciding date | Weekly decision on the list |
| Well under, deadline near | Red, top of the list | Decide: run, merge or cancel |
| Decided to cancel | Tasks for suppliers and passengers | Templates sent, rooms released |
| Decided to run under minimum | Flag kept on the departure | Watch costs and extras |
What the weekly review looks like afterwards
On Monday morning the director opens one screen. Three departures need a decision in the next fortnight. One is at eleven with a minimum of twelve and two weeks to the first release date, so it can wait. One is at six with the hotel release on Thursday, so it gets decided today. The third has had four bookings in a week and has moved to green on its own.
Once the call is made, the follow-up does not depend on someone remembering. The hotel email is drafted, the guide is told, and passengers on a cancelled departure get the message you wrote in advance, with alternative dates listed from the same board.
Merging two thin departures becomes easier too, because you can see which nearby dates have room and whether the hotels there could take the extra passengers.
Signs your go or cancel decisions come too late
- You have let a hotel allocation release on a departure that then ran.
- Departures are cancelled after passengers have booked their flights.
- The decision date promised to customers is not recorded anywhere the office can see.
- The weekly numbers review depends on one person pulling a spreadsheet together.
- You are not sure what break-even looks like for each tour.