When comparing venues stops being guesswork

The third venue changes the problem

Going from one location to two is a workload problem. You do more of what you were already doing, and it is exhausting but familiar.

Going to three is a different kind of problem. The thing that made the first venue work was that somebody knew it completely. They knew the regulars, the weak shift, the bartender who needed watching, and the week the walk-in gets ordered wrong. That knowledge does not scale, and worse, it does not announce its own absence. The group keeps running on the assumption that somebody still has that picture, long after nobody does.

What replaces it, by default, is a monthly P&L per venue and a ranking. And a ranking is where most groups start making bad decisions.

This is the point at which groups start shopping for hospitality operations software, and usually buy the wrong thing. Most restaurant operations management software is built to standardise a single venue's workflow, which is a genuinely different problem from comparing five venues honestly. Rolling up five well-run single-venue systems does not produce a portfolio view. It produces five reports.

Why venue rankings mislead

Put five venues in a table sorted by revenue and you will draw the wrong conclusion almost every time. The top venue may simply have the better address. The bottom one may be executing beautifully in a location that will never do those numbers.

If you promote the manager of the best-located venue and put the manager of the hardest one on a performance plan, you have rewarded a lease and punished a good operator. Groups do this constantly, and it is one of the more expensive mistakes available, because the person you just discouraged was your actual talent.

The useful comparison is not venue against venue on absolute numbers. It is each venue against its own realistic ceiling, and then execution quality compared across the group on the dimensions that genuinely transfer.

What actually transfers between venues

• Pour variance. A well-run bar controls its pour regardless of neighborhood. This is close to a pure execution signal.
• Void and comp discipline. Location does not explain why one venue's comp rate is three times another's.
• Labor efficiency against actual demand. Not labor percentage, which is mostly a function of average check. Whether staffing matched the curve.
• Turnover. The most portable signal of all, and usually the most expensive one nobody has priced.

Those four are comparable across a hotel bar and a neighborhood bar. Revenue per square foot is not, and treating it as though it were is how groups end up standardizing the wrong things.

The normalization problem, said plainly

Most groups that grew by acquisition are running several POS configurations, and every one of them has its own idea of what a category is. One venue books a bottled beer under Beer. Another books it under Package. A third has it under a category somebody created in 2019 and never explained.

Roll that up without normalizing and the portfolio view is confidently wrong, which is worse than having no portfolio view, because people act on it. Getting to shared definitions is unglamorous work and it is most of what makes cross-venue comparison trustworthy. It is part of the engagement rather than something you are expected to have solved before you start.

Finding what works and moving it

The real return on a portfolio view is not the dashboard. It is that your best operator's habits stop being local knowledge.

Somewhere in the group, one venue has a closing procedure that keeps variance low. One has a manager who schedules against the demand curve rather than against last week's schedule. One has a training rhythm that is quietly why their turnover is half the group's. In most groups those practices never leave the building they were invented in, because nobody knew they were unusual.

That is the multi-location argument in one line. Not central control. Finding the thing that already works and giving the rest of the group access to it.

How access is scoped

A general manager sees their venue. A regional sees their group. Ownership sees the portfolio. This is partly a permissions question and partly a practical one: showing a GM the whole group's numbers does not help them run their room, and it tends to produce defensiveness rather than action. People act on numbers they can actually affect.

Where to go next

CoreTAP is the platform underneath this and the right page for feature detail. Restaurant analytics covers the analytical approach at the category level. Case studies has the outcomes, including revenue and turnover.