Running Multiple Locations Without Losing Your Edge

At 21:15 on the opening night of the second restaurant, the owner-chef is still standing in the dining room of the original site when the new manager calls. A walk-in queue is forming. A 14-top is arriving 40 minutes late. The head chef is in a car between venues and can't approve a comp check. At the same time, nobody is certain who owns the reorder for tomorrow's delivery.

Nothing has exploded yet. That's the dangerous part. The business has crossed from one restaurant into multiple locations, but the operating system is still built around one person's memory, phone, and physical presence.

Table of Contents

• The Night the Second Restaurant Opens
• What Multi-Location Management Really Means
  • Three workable structures
• Writing SOPs That Save Hours Every Week
  • Document the decisions that repeat
  • Standardize control, not hospitality
• Centralized Reservations and Floor Control
  • Keep the guest record and rules together
  • Avoid the predictable failure modes
• Staffing Models That Fit a Growing Group
  • Make the roster portable
• Comparing Reservation Platforms by Pricing Model
• KPI Tracking Across Multiple Locations
  • The seven numbers worth pulling
  • Use variance to find the leak
  • A 90-day rollout
  • Belgian GKS compliance belongs in the rollout

The Night the Second Restaurant Opens

The first location can survive informal decisions because the owner is close enough to catch problems. A supplier asks a question, the owner answers. A guest requests a special arrangement, the owner approves it. A manager needs to move a table, the owner walks over and decides. The second site turns every one of those habits into a delay.

The new manager doesn't need another motivational speech. The manager needs to know whether a late large party should be seated immediately, paced through the kitchen, or moved to a later slot. The host needs a single view of reservations and walk-ins. The chef needs a clear comp limit. The purchasing lead needs an assigned reorder owner and a documented cutoff.

Practical rule: If a decision affects tonight's service, the person on site must know the rule before the doors open.

The quiet failures multiply quickly:

• Approval lines cross cities. A manager waits for a reply while the dining room absorbs the consequences.
• Guest information fragments. A regular's allergy note sits at one venue, while another host treats the guest as new.
• Inventory ownership disappears. Everyone assumes someone else checked the critical items.
• The founder becomes the workflow. Every exception travels back to the owner-chef, even when the answer should be routine.

Multi-unit restaurant management means overseeing the operations, financials, and performance of two or more restaurant locations, not owning several leases or copying a menu across sites. Sage defines multi-unit restaurant management in those operational terms, and that distinction matters. The group needs shared controls, but each dining room still requires local judgment.

By the morning after the opening, the owner should have three things in place: documented decision rights, one reservation layer across the group, and a weekly review cadence that doesn't depend on the founder being present. The United States franchise market shows why this discipline matters. FRANdata reports 43,212 multi-unit operators controlling more than 223,213 franchised units, about 54% of all franchised units, while a 2024 industry summary estimated 241,380 units and 56% of franchised units under multi-unit operators. The underlying multi-location data points to a system that has been scaling and concentrating, not a niche ownership pattern.

What Multi-Location Management Really Means

A second venue changes the management job. One restaurant can rely on the owner's memory and presence. A group needs shared controls, clear decision rights, and room for each dining room to respond to its own guests, team, and neighborhood.

A multi-location restaurant group usually shares its brand, back office, suppliers, reporting, and sometimes staff, while each venue runs its own service. That differs from a franchise system, where control is distributed through a franchise agreement, and from a single kitchen with satellite counters, where production and service remain largely unified.

The right structure depends on distance, menu complexity, and manager capability. The wrong structure keeps every exception inside the owner's head.

Three workable structures

Owner-operator across both rooms is the leanest option. It can work while the sites are close, menus remain manageable, and the owner can inspect service personally. It breaks down once combined revenue reaches roughly €700,000, because payroll, purchasing, guest recovery, and staffing escalations arrive at the same time.

A general manager per site with an operations director above them creates stronger accountability. Each GM owns the room. The operations director owns standards, cross-site staffing, reporting, and corrective action. One operations director can cover three to five sites within a 90-minute travel range when GMs have genuine authority.

A flatter model suits smaller independent groups. Head chefs lead their rooms, while a part-time finance lead handles reporting, payroll checks, and supplier controls. It reduces management overhead, but only if written rules are precise.

Centralize brand standards, reporting definitions, reservation visibility, payroll approvals, and supplier controls. Keep local decisions such as daily floor adjustments, service recovery within limits, and neighborhood-specific scheduling with the site manager.

Transfer these approvals out of the owner's inbox:

• Payroll approvals
• Supplier orders above a defined threshold
• Guest compensation above €200

Write the threshold, backup approver, and response time into the approval matrix. If nobody can answer “who decides this tonight?”, the group is already relying on informal management.

A reservation platform such as the 10seat restaurant group solution fits groups that need shared visibility without making every floor operate identically. Staff movement creates a similar control problem, so operators should compare multi-location leave solutions before leave requests and cross-site coverage become administrative blind spots.

The operating rule is simple: centralize what must stay consistent, and leave local managers authority over decisions that depend on the room in front of them. That boundary belongs in every SOP, schedule, dashboard, and reservation rule.

Writing SOPs That Save Hours Every Week

An SOP isn't bureaucracy when it replaces a decision the owner is currently making from memory five nights a week. It turns an expensive interruption into a repeatable action that a trained manager can complete without a phone call.

The useful test is simple: could a competent manager follow the document during a busy service without asking what the author meant? If not, the document records intentions rather than procedures. Guidance on how to build SOPs that stick is useful, but restaurant groups should keep each procedure shorter and more operational than a corporate manual.

Document the decisions that repeat

The first SOP should cover opening, starting 90 minutes before service. It should state who checks the room, refrigeration, tills, reservations, staffing gaps, allergens, and 86'd items, and where each exception is recorded.

The closing SOP should connect the physical close to the financial close:

1. Confirm every table is closed correctly.
2. Review voids, comps, discounts, and deposits.
3. Reconcile cash and card totals.
4. Record unresolved guest or maintenance issues.
5. Assign the next action to a named person.

A weekly stock SOP should count the top 20 SKUs, compare actual use with purchasing records, and identify unusual movement before the next order. It doesn't need to prescribe every item in the kitchen. It needs to protect the ingredients that create the largest operational risk.

The reservation SOP must define overbooking, no-show tolerance, confirmation timing, deposit handling, and the hard limit beyond which the host can't add another booking. The comp and void SOP must specify monetary thresholds and required sign-off. The allergen SOP must track the chain from pass to table, including who confirms the instruction and how the server communicates it.

Standardize control, not hospitality

Plating details can remain flexible where the chef's judgment improves the dish. Wine pairings should reflect the local list and the guest conversation. Local menu items can respond to regional suppliers and neighborhood demand. The central document should define the outcome and safety requirement, not dictate every gesture.

A practical opening SOP with 12 lines reused across four rooms can save roughly six hours of manager time per week, according to the operating example specified here. That is a clear cost argument for a partner or finance lead because it connects documentation to recovered management capacity.

An SOP that takes more than 15 minutes to read has already failed. Split it into a short action sheet and a separate reference document.

Every SOP needs an owner, a review date, and a trigger for revision. If a manager bypasses the same step repeatedly, the procedure may be badly designed. The answer isn't always more enforcement. Often, the answer is a shorter sequence, a clearer decision limit, or a better place to record the result.

Centralized Reservations and Floor Control

Reservation management should have one central data layer and several local operating layers. That distinction prevents the common mistake of either giving every host a separate book or forcing every location to use the same floor decisions.

Keep the guest record and rules together

The central system should hold:

• One guest profile, including preferences, allergies, and relevant visit history
• Shared VIP and service notes, with permission controls for sensitive information
• Booking rules, including deposits, cancellation settings, confirmation messages, and party-size limits
• Group-level visibility, so management can identify demand across venues
• Portable waitlists, allowing a guest to move from one suitable location to another when capacity changes

A single guest database helps a regular remain recognized when visiting another site. It also prevents loyalty, allergy, and special-occasion information from being stranded in one venue's reservation book.

The local team should control the live floor map. The host knows which table is available, which section is delayed, whether a large party should be split, and whether the kitchen can absorb another seating wave. Those decisions depend on the night's staffing, the menu, the room's physical layout, and the service pace.

A 10seat-style platform can sit on that boundary for Benelux independent groups operating two to five sites. It can provide real-time floor plans, portable waitlists, and a guest profile that travels with the diner, while the venue retains control over pacing and table allocation. Operators assessing the operational side should also review table management software with attention to floor-level decisions, not just booking intake.

Avoid the predictable failure modes

Two hosts operating separate screens can create double bookings. Separate guest books can leave a returning diner invisible at the second site. Inconsistent deposit handling creates arguments at the door and makes group reporting unreliable.

The correct decision rule is direct:

Centralize the data layer and booking rules. Decentralize the floor map and pacing decisions.

That rule also applies to group bookings. The central layer can route a request by capacity and concept, while the local manager decides whether the room can deliver the experience on that date. A 14-person booking at a quiet neighborhood site isn't operationally identical to the same booking in a compact tasting-room layout.

Central control should make local judgment faster, not remove it. If the host still needs permission to turn two four-tops into one table, the system is over-centralized. If the head office can't see deposits, guest notes, or booking demand across sites, it is under-controlled.

Staffing Models That Fit a Growing Group

Groups with two to five venues generally settle into one of three staffing shapes. The right answer depends less on ambition than on travel time, manager capability, service complexity, and whether the sites share a labor pool.

A single floating GM can cover more than one room when the venues are close and the assistant managers are strong. The trade-off is visible: the model can save roughly €45,000 to €70,000 per year compared with a second dedicated GM, but the floating manager loses 8 to 12 hours of floor presence each week. The multi-location staffing data should be read as a planning input, not a promise of savings.

A dedicated GM per location with a lean operations director above them costs more, but it protects service consistency when the rooms have different demand curves or labor markets. A fully shared back-of-house and front-of-house roster creates flexibility, though it can weaken belonging if employees never know where they belong.

That table should be turned into a decision, not left as a discussion. A group with weak shift leaders shouldn't choose the floating model because the payroll looks attractive. A group with stable neighboring demand shouldn't hire a full hierarchy before testing cross-trained coverage.

Make the roster portable

A unified scheduling tool gives the operations lead one view of vacancies, overtime risk, skills, and availability. Cross-trained servers can move to a busy night, but only if their training records and travel expectations are clear. A shared onboarding document should aim to make a new hire service-ready in five shifts rather than 12, using the specified operating benchmark.

Belgian and Dutch labor rules need to sit inside the staffing design. In Belgium, the 38-hour average is a relevant planning constraint. In the Netherlands, part-time scheduling must follow the applicable CAO rules. The group should verify the current sector agreement, rest requirements, notice rules, and travel treatment before rotating employees between locations.

Local hiring still has a place. A venue with a distinct wine program, language mix, or neighborhood rhythm needs people who understand that room. Centralize training standards and employment records, but don't pretend every shift can be staffed from one interchangeable pool.

Comparing Reservation Platforms by Pricing Model

Restaurant groups should compare reservation platforms by annual cost per venue, not by the comfort of a familiar brand name. TheFork, OpenTable, Zenchef, and Formitable can use different commercial arrangements, so the relevant question is whether the pricing model matches the site's booking volume and average spend.

For a venue taking 220 covers per day at a €52 average ticket, a commission of €1.50 to €2.50 per cover produces a stated annual platform cost of roughly €33,000 to €55,000 per site under the scenario specified here. A flat fee of €100 to €200 per month produces €1,200 to €2,400 per year. The calculation is useful because the difference comes from volume, not from whether the platform has a polished sales presentation.

The named platforms should be compared on the signed commercial terms, not assumptions about their pricing. A tasting menu venue with fewer than 60 covers per night may tolerate commission when average spend is high and booking volume is limited. A busy neighborhood restaurant faces a much harsher equation because every additional booked cover creates another fee.

The sales call also won't always foreground paid placement in TheFork's ranking, no-show deposit leakage, or the practical question of whether the restaurant can export its guest data when it changes provider. Those aren't reasons to dismiss a platform. They're reasons to read the contract and calculate the cost at each location.

The operating rule is clear: once one site clears roughly 8,000 booked covers per year, the operator should test whether commission still makes economic sense. A flat-fee option such as 10seat keeps the comparison focused on predictable venue cost, but the decision still depends on booking quality, controls, integrations, and the group's need for shared reporting.

KPI Tracking Across Multiple Locations

Monday morning is the right time for the weekly KPI review, before payroll questions, supplier calls, and maintenance problems fill the schedule. A restaurant group does not need a quarterly presentation to discover that one site is losing covers, using too much labor, or attracting fewer returning guests. It needs a short, consistent set of numbers, with one person assigned to investigate every exception.

Set the review around weekly unit-level KPIs. Flag a location down more than 8% week over week, or more than 10% versus the prior year for two consecutive weeks. Escalate a unit running five or more percentage points above its prime-cost target for more than two weeks. The KPI dashboard workflow recommends viewing net sales, average check, orders, and sales per labor hour together, then comparing like-for-like venues by concept or region.

The seven numbers worth pulling

Keep covers, average ticket, and no-shows at site level first. Local demand, room capacity, neighborhood habits, and booking rules shape those results. Roll up labor cost percentage and repeat guest share for the group view, then drill back into each location before changing policy.

Centralize the definitions, calculations, and reporting deadline. Keep decisions about pacing, deposits, promotions, and staffing adjustments with the local operator when those decisions depend on the room, neighborhood, or service style. A shared dashboard should create a common language, not force every venue into identical targets.

Compare venues only when they are alike. A high-volume brasserie should not use the same target as a small tasting-menu room. Group-wide averages also hide outliers. Best-practice reporting guidance highlights location-level measures including same-store sales growth, food cost, labor cost, average ticket, voids, comps, and customer review average.

Use variance to find the leak

Location A may hold steady on covers while its average ticket falls. Location B may keep its ticket size stable while no-shows rise. A single group average can make both sites look healthy. Side-by-side reporting gives the operations director two different actions: inspect menu mix and selling behavior at A, then review confirmations and deposits at B.

Apply the same discipline to costs. External guidance commonly places restaurant COGS around 25% to 35% of sales and healthy prime cost under 55% to 60%, with the right range changing by service style and labor market. The 2024 multi-unit restaurant report describes tight economics, including an average profit margin of 9.2%, staff turnover of 34%, menu price increases at 65% of operators, and an average increase of 17% among those operators. Weekly review gives managers time to respond instead of relying on annual results.

A flat-fee reservation platform can keep venue data exportable and reduce the time spent reconciling commission statements. The review may take 20 minutes rather than an afternoon, provided the export includes guest, booking, revenue, and cancellation fields. Confirm those fields before signing. “Exportable” has no practical value if the file cannot support the weekly review. Guidance on restaurant data analytics can help define the reporting layer before the group chooses a platform.

A 90-day rollout

Days 1 to 30: Document the three SOPs that usually fail first, opening, reservations, and closing. Choose the staffing model from the available structures. Name the person responsible for each decision limit.

Days 31 to 60: Move reservations onto one platform and lock the central-versus-local decision matrix. Run one parallel week with the old and new systems side by side. Check table inventory, deposits, guest notes, and cancellation handling.

Days 61 to 90: Cut over fully and start the Monday KPI review. Benchmark every venue against its own pre-rollout baseline, then compare like-for-like locations to identify outliers. Centralize reporting while allowing each floor to control pacing within the agreed limits.

Belgian GKS compliance belongs in the rollout

Belgian operators cannot treat the second site as an administrative copy of the first. The GKS, or Geregistreerd Kassasysteem, requirement mandates a certified cash register system with a black box module. The same registered system must be used at every location covered by VAT unit rules. The Belgian GKS requirements summarize the operating guidance, but each group should confirm its VAT structure and compliance position with a qualified Belgian adviser.

Review the GKS setup before the second site starts trading. Check the cash-register configuration, VAT treatment, and responsibility assigned to each location. Fixing those items after opening creates avoidable administrative and compliance risk.

10seat gives restaurant groups a shared reservation and table-management layer, multi-location visibility, guest profiles that can travel between venues, and location-level reporting while each floor keeps control of pacing. Visit 10Seat to assess whether its commission-free model fits the group's booking volume and operating boundaries.