Running Two to Six Venues Without the Brand Drifting Apart

A guest books your second location on a Thursday, gets a confirmation email that looks nothing like the one from your first site, arrives to find the no-show policy is different, and asks the host why. The host does not know either.

That is drift. It rarely arrives as one bad decision. It accumulates: a manager tweaks the cancellation window because a supplier let them down, someone rewrites the confirmation text because the old one felt stiff, a menu gets a new allergen note that never makes it back to the other kitchens. Six months later you have four venues that share a logo and almost nothing else.

Making everything identical solves nothing. Venues differ for real reasons, and forcing a coastal site to run the same hours as a city-centre one is how you lose money on purpose. The useful work is deciding, once and explicitly, which column each thing lives in.

The identical column

Four things belong here, and they are the four that guests notice fastest when they disagree.

Booking policy. Cancellation window, deposit rules, how long you hold a late table, what happens to a party that shrinks from six to four. If site A holds tables 15 minutes and site B holds them 30, guests learn the wrong lesson at one and get burned at the other. Write one policy. If a specific site genuinely needs an exception (a 200-cover events venue is not a 30-seat bistro), write the exception into the same document instead of letting it live in a manager's head.

Brand voice and every guest-facing message. Confirmations, reminders, review requests, the sign on the door. These are the highest-volume writing your business does, and they are usually the least supervised. One set of templates, one tone, one signature. Individual venues should be able to swap the address and phone number, and nothing else.

Allergen data. This one is about safety and compliance rather than brand. In the EU, the 14 declarable allergens have to be accurate and available for every dish you serve, and "the other branch's list says something different" is not a defence anyone wants to make. One master dish list, one owner, one update path. When a supplier changes a product, it changes everywhere at once. Check the exact scope of your obligations with your local food safety authority, since enforcement varies by country.

Data and reporting definitions. A no-show at one site has to mean the same thing as a no-show at another, or your group-level numbers are decoration. Same for a covered table, a cancelled booking, a repeat guest. Boring, and it decides whether you can compare your sites at all.

The genuinely different column

Everything above is the spine. This is where local judgement earns its keep.

Pricing. Rent, wages, and what the street will pay all differ. A city-centre site carrying twice the rent of a suburban one cannot run the same price list without one of them being wrong. Guests accept this more readily than operators expect, as long as the prices are published clearly and nobody feels ambushed. What they do not accept is discovering the difference at the table.

Opening hours. Driven by footfall, not by a group standard. An office-district lunch trade and a residential dinner trade want opposite things. Set hours per site from that site's actual demand curve, then publish them everywhere a guest might look, and keep them right on holidays. Wrong holiday hours generate more complaints than almost anything else on this list.

Menu specials and a slice of the core menu. The signature dishes travel. The specials should not. A chef who can run a Tuesday special from whatever the market had that morning is worth more than a chef executing a group-wide plan, and guests in a small group like knowing their local has something the others do not. A useful ratio is a fixed core (the dishes people come to your brand for) plus a local section each kitchen owns outright.

Staffing shape and local partnerships. Team size, shift patterns, which supplier delivers the bread, which nearby hotel you take overflow from. None of this needs to match.

Where the split gets argued about

Two areas sit awkwardly in the middle, and they are worth deciding deliberately rather than defaulting.

Loyalty is one. Points earned at one venue should almost always be spendable at another, because a group-wide programme is one of the few real advantages you have over a single independent. The awkward part is funding it: when a guest earns at your busy site and redeems at your quiet one, the quiet one carries the cost. Sort out the internal accounting before you launch, not after the first manager notices.

Events are the other. A quiz night that works in one neighbourhood can be dead in another. Keep the format library shared, so nobody rebuilds a ticketing flow from scratch, and let each site pick from it.

Make it a routine

Written standards decay quietly. The thing that keeps them alive is a short recurring check rather than an annual audit nobody schedules.

Once a month, pull the same four numbers for every site: no-show rate, cancellation rate, average spend, and repeat-guest share. You are not looking for the best performer. You are looking for one site that has quietly diverged from the others, because that gap is usually a process difference rather than a market difference, and it is fixable. If you want a sense of what the repeat-guest gap is worth in cash before you go chasing it, the repeat guest revenue calculator will size it for you.

Once a quarter, walk one venue that is not your home base and book, eat, and leave as a guest would. Managers know when the owner is watching, and a site visit announced three days out shows you a performance. Booking under a name nobody recognises shows you the actual product.

And when something does change, change it in one place. The most common cause of drift in a small group is that the policy was updated in an email, three managers read the email, two of them acted on it, and nobody could later say which version was current. If the rule lives in one system that every site reads from, that failure mode disappears.

The short version

Identical: booking policy, brand voice and templates, allergen data, and how you define your numbers. Different: pricing, hours, specials, and local staffing. The mistake most small groups make is enforcing the second list while letting the first one drift, usually because pricing and hours feel like control and templates feel like detail. It is the other way round. Guests forgive a menu that changes between your venues. They do not forgive being told two different things about the same booking.