Inside a forty-city routing.

How a tour goes from a promoter’s spreadsheet to forty confirmed cities, and where the work actually hides.

Fig. 01The hotel directory, searching around Cumberland Arena. Fictional data.

Every tour starts as somebody else’s spreadsheet. Forty rows: a date, a city, a venue, a capacity. Nobody on that sheet has thought about where forty-two people sleep, how they get from the airport, or what happens when the show in Denver moves to a Thursday.

That is the advance. It is the least glamorous part of touring and the part that decides whether the run feels effortless or falls apart in week three.

Not every stop is the same stop.

The first thing worth knowing about a routing is which stops linger and which don’t. A two-night run in one city, or a show with a day off next to it, behaves like a group stay: more rooms, longer holds, a block worth negotiating. An isolated one-nighter is closer to transient business. Treat them the same and you either over-hold rooms you will release, or scramble for rooms you should have blocked.

A tour is only as good as its advance. The bus will roll on time; the question is whether everyone knows where it is going.

So the routing comes in, and each date becomes a stop with its own city and venue. Hotels are searched by distance from the venue, not the city centre. Rate requests go to every sensible property at once, and the answers come back side by side instead of in eleven email threads.

Where the work actually hides.

It hides in the changes. A date moves; three bookings and two flights move with it. A promoter adds a market; the forecast for that city changes. The point of putting the whole tour on one page is not that it looks tidy. It is that when something moves, you can see everything it touches.

Keep readingMore dispatches