Munich was booked a month ahead. Riyadh was booked a day and a half ahead.
Same desk. Same customer base. Same agencies placing the bookings. The only thing that changed was the destination, and the booking window moved by a factor of twenty. The full ranking is in Finding 02 of the Gulf Outbound Hotel Index, built on more than 25,900 confirmed bookings.
| Booked earliest | Median days ahead |
|---|---|
| Munich | about 31 |
| Singapore | about 26 |
| Paris | about 26 |
| Kuala Lumpur | about 25 |
| Milan | about 25 |
| Booked latest | Median days ahead |
|---|---|
| Riyadh | under 2 |
| Kuwait City | about 2 |
| Amman | about 2 |
| Manama | about 2 |
| Cairo | about 2 |
Why this is the most useful table in the file
Because it removes the customer as an explanation.
If lead time were a cultural habit, it would be roughly constant across a single customer base. It is not. The same people who book Riyadh the day before book Munich a month out. Whatever is producing the difference is sitting in the destination, not in the person.
Look at what separates the two lists and it is not mysterious:
- The late list is short-haul, visa-light, and repeat. Riyadh, Kuwait City, Amman, Manama, Cairo. Flights are frequent, the trip is familiar, and there is nothing to arrange. There is no reason to book early because booking early buys you nothing.
- The early list is long-haul, visa-bearing, and structural. Munich, Singapore, Paris, Kuala Lumpur, Milan. A visa appointment, a long flight with fewer daily options, and a trip with enough moving parts that the hotel is one decision among several.
Lead time is a measure of how many dependencies stand between deciding and travelling. That is it.
Three operational consequences
Your cancellation exposure is already implied by this table. The destinations booked a month out are the ones that cancel at close to 40%; the ones booked two days out cancel at under 14%. A month of elapsed time is a month in which a visa can be refused or a plan can change. If you know the window, you can predict the risk without modelling anything.
Your desk needs two speeds, not one. A same-week Gulf request and a month-out European request are different products. One is won on being the first complete answer that exists. The other is won on structure, options and follow-up. Running both through one process means being mediocre at both.
Your allotment and payment terms should not be uniform. Committing early on a destination whose customers decide two days out is committing against a curve you can see in advance.
How to build this for your own book
You do not need a data team. You need three columns: destination, date the booking was created, date of travel. Subtract, take the median per destination — not the mean, which one advance group booking will drag out of shape — and drop any destination with too few bookings to be meaningful.
That gives you a tiering. Three tiers is enough: booked-late, booked-mid, booked-early. Then set staffing attention, cancellation assumptions and payment terms by tier instead of by instinct.
It is an afternoon of work. Most desks have never done it, and then treat a month-out Munich booking and a tomorrow-night Riyadh booking as the same transaction.
They were never the same transaction.
Source: the Gulf Outbound Hotel Index, version 1.0 — more than 36,100 B2B wholesale hotel bookings from one Gulf desk. Findings and full tables · Methodology · CC BY 4.0 · 10.5281/zenodo.21796038