Running a programme across several cities: what repeats and what does not

23 September 2026

A programme that runs in six cities is not one event repeated six times. It is six productions that have to arrive at the same room, and almost all of the work sits in the distance between those two sentences. Here is what I fix once for a whole tour, what I decide again at every stop, and where the two get confused.

Six stops, six productions

The last programme of this shape I ran moved 260 people through six Italian cities, in six working languages, with three gala dinners along the way. On the approved deck it was one event with one running order. On the ground it was six venues, six load-in windows, six local technical crews and six groups of people who had never worked together before and never would again.

The instinct is to standardize everything, because standardizing is what makes a tour feel like a tour. That instinct is right about the guest experience and wrong about the production. What the audience sees has to be identical at every stop. What produces it cannot be. Pretending otherwise is how a tour opens strong and degrades from the third city onward, with everyone aware that something has slipped and nobody able to point at when.

I would rather run six honest productions that converge on the same room than one plan that six cities are made to accept.

What gets fixed once

The centrally decided list is shorter than most people expect, and it is closed before the first stop opens its doors:

• The running order and its timings. Not approximately the same. The same.
• The content and the language provision. Who is interpreted into what, and at exactly which moment of the programme.
• The elements the audience reads as "the same event". Usually fewer things than the brand book lists, and they need to be the ones that survive a different room.
• The budget per stop, contingency included. Set before the tour starts, not after the first stop has taught everyone what it really costs.
• Who approves a change, and by when.

That last one matters more than any single element on the list. On a tour, requests to vary something arrive at every stop, usually from the local side, usually reasonable and usually small. A room that would work better the other way round. A start pushed by fifteen minutes because of the traffic that evening. Each one is defensible on its own. Granted six times without a rule, they add up to a last stop that no longer resembles the first, and the client notices before anyone in the production does.

What gets decided again at every stop

The build. Load-in windows across that tour ranged from a full day in a purpose-built space to a few hours in a building where the access is what it is and no amount of budget is going to widen a staircase. So the set gets designed for the tightest stop on the tour, not the average one. A build sized for the easiest venue is a build that has to be cut down at speed, in front of a crew seeing it for the first time, at the stop that could least afford the improvisation.

The crew. A different local team at every city is normal here, and it means the same production brief gets six different readings. The document is not what transfers. The walk-through is. I go through it on site, out loud, with each crew, in the room, and I have never once done that without finding at least one thing that had been read the way it was written rather than the way it was meant.

The room. Same menu specification, six kitchens, six sets of service timings to agree against a running order that cannot move. The specification travels. The schedule behind it is rebuilt each time.

The leg that looks shorter than it is

Anyone planning a tour of Italy from a map plans it wrong, and it is one of the few mistakes I can predict before seeing the itinerary. The country has a fast rail backbone, and two cities sitting on it can be closer in practice than two cities that look almost adjacent on the page. Step off that spine, towards the Adriatic side, the deep south or anywhere with a mountain in the way, and the same distance costs a different afternoon. Tours get built on the assumption that distance and time are the same measurement, then lose a stop's worth of energy to a transfer that everyone had priced at half of what it took.

On that programme we moved people by private transfer rather than as one coach group. It costs more per head, and it buys back the only currency a tour actually runs on, which is the schedule. Two hundred and sixty people arriving in workable groups is a gala dinner that starts when it says it will. The same 260 arriving as one convoy is a room held for forty minutes and a kitchen deciding on its own what to do about it.

Where a tour is actually run from

What makes the sixth stop look like the first is not the deck. It is that someone who was in the room at stop one is in the room at stop six, carrying across the corrections rather than the file.

So I debrief after every stop, not only at the end of the tour. Twenty minutes, the same three questions, written down while the room is still being struck and everyone still remembers the thing that nearly went wrong. By the third city the list of what to watch for has stopped being generic and become specific to this programme, these speakers, this way of getting 260 people seated. That is the whole compounding effect of a tour, and it only exists if somebody is collecting it. I have written about how I run that conversation in the debrief almost nobody does.

The rest is the same discipline any single event needs, applied six times without letting the sixth one get the tired version of it: the reconfirmations, the phone calls, the triple check. On a tour those do not happen once. They happen per stop, on a rhythm, which is why I plan the tour's calendar around the checking and not the other way round. That part I have covered in the last weeks are not for building, they are for checking.

For the stages a single stop goes through, start with how to organize a corporate event in Italy. On the file that holds a multi-stop programme together, see the document that keeps a project on course. Running the days themselves is part of the on-site coordination service.