ContactBook a call

Industries/ Hospitality/ Group and site dashboards

A restaurant KPI dashboard for every site, ready before the briefing

We pull covers, sales, spend per head, labour, reviews and stock from the systems each site already uses, and define every number the same way everywhere. General managers see their own site, the operations director sees all of them, and nobody spends Monday building a spreadsheet.

The operations director of a small restaurant group, a man in his forties with a shaved head and a white shirt, in a back office reviewing charts on a laptop, menus pinned on the wall.
Used by
General managers, operations directors, finance leads and owners
Takes the place of
Sunday-night spreadsheets and the Tuesday group summary
Connects to
Your tills, rota software, reservations and stock system
Built with
Our live dashboards service

Where it hurts today

A normal week, before it exists

Every Sunday night each general manager fills in a spreadsheet: covers, takings, labour hours, comps and anything that went wrong. Some send it on Monday, some on Tuesday, and one site still uses last year's template with the columns in a different order. On Tuesday afternoon someone at head office stitches the lot into a group summary for a week that ended two days earlier.

The numbers never quite agree, because each site counts differently. One includes service charge in sales and one does not. One counts a child as a cover. Labour at one site includes the agency chef and at another it does not. Half of Wednesday's operations meeting goes on arguing about whether a site really had a bad week, rather than deciding what to do about it.

Meanwhile the things that matter arrive last or not at all. Reviews are read by whoever happens to look. Stock counts come monthly, so a problem with spirits at one bar is found weeks after it started. A site that overstaffs every Monday is noticed when the quarter's figures land, and the owner hears about a bad Saturday from a friend before any report mentions it.

What it does

Group and site dashboards, feature by feature

What the dashboard shows, and the groundwork that makes the numbers worth trusting.

  1. 01

    Daily sales and covers by site, before the briefing

    Covers, sales, spend per head and labour for each site and meal period, loaded overnight and on the manager's phone before the morning briefing. Each figure sits beside the same day last week, the same day last year and the forecast, where you have one.

  2. 02

    One definition for every KPI

    What counts as a cover, whether sales include service charge and tips, what labour includes and when a week starts are each agreed once with your finance lead, written in plain English and used on every screen. Arguments about whose figure is right end at the definition.

  3. 03

    Each manager sees their own site

    A general manager sees their site in full and where it sits in the group. The operations director sees every site side by side, sortable from weakest to strongest. Finance sees everything, and individual pay rates stay out of the dashboard altogether.

  4. 04

    Labour cost against sales and the rota

    Planned hours from the rota, worked hours from clocking in and sales from the till, shown together per shift. Late clock-outs, long breaks and a shift that ran heavy against quiet trade show up the morning after, not at the end of the month.

  5. 05

    Online reviews alongside the numbers

    Ratings and comments from review sites and your own feedback forms, where those services allow access, shown exactly as guests wrote them, sorted by site and tagged by theme, such as speed of service or food temperature, so a run of slow-service comments sits next to the night's labour.

  6. 06

    Stock and wastage variance

    Where your stock system records counts and deliveries, the dashboard compares what the tills say was sold with what was actually used, for high-value lines such as spirits, wine and meat, and flags any site where the gap is widening.

A day with it

How the day runs instead

A normal week for a group of five restaurants with the dashboard running.

  1. 7.50am
    General manager

    Opens the dashboard on a phone before the briefing. Last night's covers beat the forecast, labour came in on plan, and two new reviews both mention a long wait for drinks. That becomes the first point of the briefing.

  2. 9am
    Operations director

    Sorts all sites by labour against sales for the past week. One site has run heavy every Monday for a month. A call to its general manager finds a closing shift nobody remembered to remove from the template rota.

  3. 11am
    Finance lead

    Checks yesterday's sales by site against the card provider's settlement. One site is marked stale because its till did not send last night's data, so the finance lead waits rather than reconciling against an empty panel.

  4. Wednesday
    Head of food

    Looks at stock variance across the sites. Meat usage at one kitchen is higher than its sales suggest for the second week running. A visit with the head chef that week finds a portioning change nobody had written down.

  5. Monday
    Owner

    Reads a one-page email: last week by site, against last year and against plan, with three lines on what changed. Opens the dashboard only to look more closely at the one site that slipped.

What it connects to

Works with what you already run

The dashboard reads from the systems your sites already use. Nobody types numbers into it.

  • Till and point of sale

    Sales, covers, discounts, voids, comps and service charge per site, shift and till, loaded overnight, or more often where the till offers an API that allows it.

  • Rota and time and attendance

    Planned shifts and worked hours by role and site, with an estimated wage cost per shift and no individual pay rates, for example from Planday or Deputy, where they offer reporting or API access.

  • Reservations or property management system

    Bookings, no-shows, walk-ins and party sizes for restaurants, and occupancy, room nights and average rate for hotels, so covers can be read against what was actually booked.

  • Stock and accounting systems

    Counts, deliveries and wastage from your stock or purchasing system, and actual costs from your accounting software, for example Xero, where it offers an API, so the dashboard and the monthly accounts can be reconciled.

The first version

Start small, then grow it

A first version should be useful on day one and small enough to get right. This is where we would usually draw the line, and what tends to follow once people are using it.

In the first version

  • Last night's covers, sales, spend per head and labour for every site
  • Written definitions for each number, agreed with your finance lead
  • Site-level access for managers and a group view for operations
  • A last-updated stamp on every panel, with stale data clearly flagged
  • A weekly summary email for people who will never open a dashboard

Once it is in use

  • Reviews and guest feedback grouped by site and by theme
  • Stock and wastage variance for spirits, wine and other high-value lines
  • Comparison against a covers forecast, once you have one running
  • Hotel measures such as occupancy and average rate beside restaurant figures

Buyer's guide

Before you commission one

Four decisions that shape a group dashboard, best taken before any screens are drawn.

  1. 01

    Till reports, a BI tool or a built dashboard

    For one site, the reports in your till and rota software may be enough. Hospitality analytics products that connect to common tills are worth a look for groups on mainstream systems. If you already pay for a business intelligence tool such as Power BI and your team knows it, build in that rather than add another. Custom work earns its place when systems differ across sites or definitions need care.

  2. 02

    Pick the numbers and check the data

    Write down the decisions made every week, such as whether a site needs another shift or whether a menu change is working, and choose the five or six numbers that answer them. Then ask each system's provider how data can be taken out: through an API, a scheduled report or not at all. Groups that grew by buying sites often run several different tills.

  3. 03

    Name who owns the definitions

    Someone has to have the final word on what a cover is and what counts as sales, usually the finance director, with the operations director owning which numbers appear and who sees them. Each general manager owns the accuracy of their own site's inputs, such as clocking in and stock counts. Without owners, the dashboard becomes the next thing people argue about.

  4. 04

    Know the signs it is working

    Watch whether managers open it before the morning briefing, whether the Tuesday spreadsheet quietly stops, whether meetings start from the same figures on both sides of the table, and whether problems such as a heavy Monday rota are spotted in days rather than at the end of the quarter. Usage by screen shows which views to keep and which to cut.

Terms worth knowing

The words you will meet

Spend per head
Sales divided by covers for a meal period. Agree whether it includes drinks, service charge and tips, because the same evening looks very different depending on what is in the figure, and comparisons between sites only mean something when every site counts it the same way.
Stock variance
The gap between what the tills say should have been used and what the stock count shows was used. Some gap is normal. A gap that keeps growing at one site is worth a visit, because it is often the first sign of over-portioning, waste or stock going missing.
Data warehouse
A single store where data from the tills, rota, bookings and stock is kept in a tidy, consistent shape, so the dashboard reads from one place rather than querying every system each time. It keeps screens fast and lets your history survive a change of till.

Handled with care

The details that matter here

A group dashboard puts every site's performance and labour costs in front of people. These are the details we handle with care.

  • Pay and personal data

    We keep individual pay rates and names out of the dashboard, showing labour cost by shift, role and site instead. We agree with you who sees cost figures at all, and access is set from your staff sign-in, so it ends when someone leaves the business.

  • Tips, service charge and definitions

    We settle service charge, tips, VAT, comps, voids and agency labour with your finance lead before any screen is built. In the UK, the Employment (Allocation of Tips) Act 2023 requires tips to be shared fairly and records kept for three years, so we keep tips out of sales and leave their allocation to the system that records it.

  • Stale and missing data

    Every panel shows when it was last updated. When a site's till fails to send, the dashboard marks that site as stale rather than showing a zero, and the loading job retries and tells a named person if it cannot catch up.

  • Fair comparisons between sites

    A city-centre bar and a village pub do not trade alike, so a simple league table can be unfair to a good manager. We design comparisons against each site's own plan, forecast and last year as well as against each other, and agree with you how rankings are shown.

Guides

Worth reading first

Questions

What buyers ask first

Do we need a dashboard if our POS already has reports?

For one site, the till's reports may be all you need, and we will say so. A group dashboard earns its place when you need several systems in one view: labour against sales, rota against forecast, reviews beside the numbers, or every site counted the same way when they run on different tills or rota tools.

Can we build restaurant dashboards in Power BI?

Yes, and if your team already uses it, that is usually the right choice. We build the group dashboard in Power BI and spend most of our time on the parts underneath: the connections to the tills and rota, the definitions and the data model. Moving you to another tool would add cost and retraining without solving the actual problem.

Should site managers see other sites' numbers?

That is your choice, and we build whichever you decide. Some groups show every manager the full table, some show only their own site and where it ranks, and some keep comparisons for the operations team. We suggest ranking against each site's own plan as well as against each other, so a strong manager at a quieter site is not discouraged.

What happens when a till stops sending data?

The dashboard says so. That site's panels are marked stale with the time of the last good data, the load retries and catches up when the till comes back, and a named person is told if it cannot. A missing site should look missing, not like a terrible night, so nobody makes a decision on a figure that quietly stopped moving.

Can we add a new site to the dashboard ourselves?

Mostly, yes. If the new site uses the same till and rota software as the others, adding it is a setting your team can change, and we show them how at handover. A site on a different till, perhaps one that came with a purchase, needs a new connection built and checked, which is a small piece of development work.

Tell us how Monday's numbers get made

Tell us which tills, rota and booking systems your sites run on. We reply within 48 hours with what a group dashboard could pull from them, and what it could not.

More for hospitality

What else we build for hospitality