Expanding to a Second City: The Operations Checklist Nobody Gives You

Here's the checklist nobody hands you before city number two.

The mistake almost everyone makes first

The trap is treating a second city as 'more of the same.' It isn't. In Vienna you're running on a decade of undocumented knowledge. Which guides are reliable, which meeting points flood when it rains, who can handle a rowdy stag group. In Barcelona you have none of that. All the informal memory that made Vienna feel easy simply doesn't exist yet.

So the real project isn't opening a city. It's discovering how much of your operation lived in your head. And writing it down before you have to run two of them at once.

The people problem: you can't reuse the pool

Your Vienna guides can't lead a Gothic Quarter tour. Obvious, but it has a sharp edge: everything you know about qualifying and trusting a guide has to be rebuilt from zero in a market where you have no reputation and no referrals.

Before your first Barcelona tour goes live, you need answers to:

• Who are the guides, and what can each actually lead. Languages, neighbourhoods, themes (food, history, architecture), group sizes?
• What licences does this city require? Barcelona regulates guiding differently than Vienna, and some sites need certified guides. Get this wrong and you're fined, not just embarrassed.
• Who's genuinely available, versus who said yes to be polite in the first meeting?
• How will you cover a Saturday sickout when you personally know none of the backups?

Capture qualifications on day one, not day ninety

The single highest-leverage thing you can do is record each guide's real capabilities the moment you meet them. The way you never got around to doing in Vienna. Not 'Jordi, good guy.' Instead: Jordi. Catalan, Spanish, English; Gothic Quarter and Gràcia; food and history; up to 25 pax; weekends only. That structured record is what lets you answer 'who can take this?' without having spent three years learning the roster by heart.

The real project isn't opening a city. It's discovering how much of your operation only ever lived in your head. And writing it down before you're running two at once.

The process problem: duplicate the system, not the mess

If Vienna runs on a spreadsheet plus a WhatsApp group plus your memory, expanding means... a second spreadsheet, a second group, and a memory you no longer have. That's not duplication. That's how a good operator becomes a bad operator in two cities simultaneously.

Before you launch, decide what a repeatable 'city in a box' looks like:

1. One place to see every tour, filtered by city. So you're not tab-switching between Vienna and Barcelona at 7am and mixing them up.
2. A guide database per city with the qualification fields above, so a new market inherits your structure even though it needs new people.
3. The same fill process everywhere: post the tour, qualified local guides apply, you approve. Identical muscle memory in both cities.
4. The same cancellation path: a guide drops, the tour returns to the local pool, other qualified guides re-apply. You do not want to be personally phoning Barcelona backups you've never met.

The point of standardising isn't neatness. It's that city three, four, and five become copy-paste instead of a fresh adventure each time.

The you problem: you can't be in two cities

In Vienna you're the safety net. The person who fixes the Saturday mess by knowing everyone. You cannot be that in Barcelona, and you definitely can't be it in both on the same Saturday morning. Expansion forces a change you probably needed anyway: the operation has to run without you standing in the middle of it.

That's uncomfortable, because being the indispensable middle felt like control. But an operation only scales past one city if the system, not the founder, holds it together. If you've been meaning to get out of the middle, a second city will make the decision for you.

A pre-launch checklist you can actually use

• Every local guide's languages, neighbourhoods, themes, group-size limits, and availability. Written down, structured, not in your head.
• Local licensing and certification rules confirmed, per site if needed.
• One calendar covering both cities, filterable by city.
• A defined fill process and a defined cancellation/re-assignment path, identical to city one.
• At least two qualified backups for every recurring tour before it goes on sale.
• A named local point person, so problems don't route through your phone at 2am your time.

What software won't do for you

Software doesn't recruit your Barcelona guides, doesn't know which meeting point floods, and won't win you a reputation in a new market. That's shoe-leather, and it takes months. What it does is stop city two from doubling your admin. When the structure is already built, adding a city is loading a pool and pressing go, not reinventing how you work. That's the whole difference between expanding and just being busier in two places.

If city two is on the whiteboard, the best thing you can do first is get city one out of your head and into a structure you can clone. EasyPlanning was built to make a second (and third) city a matter of loading a new guide pool onto the same calendar and process. Not starting over. Book a demo and we'll map it to your expansion, or start a free trial and set up Barcelona alongside Vienna. If you're not sure city one is ready, start with 5 Signs Your Tour Company Has Outgrown Spreadsheets.