Restaurant reporting: six reports, no more

Restaurant reporting has a way of growing until nobody reads it. A venue starts with a daily sales summary, then adds a weekly labour report, a food cost sheet, a covers report, a menu report, a reviews summary, a marketing report and a few spreadsheets someone built once and still updates. Every report seemed useful when it was created. Together, they take hours to produce, land in inboxes that are already full, and rarely change what anyone does.

The test of a report is simple: does it change a decision? A report that leads the chef to adjust an order, the manager to change a rota, or the owner to revisit a price is earning its keep. A report that is read, nodded at and filed is not. Most venues need far fewer reports than they produce, and far more attention on the few that matter.

This guide sets out six reports for restaurant reporting, no more: the daily report, the weekly prime cost, the weekly covers and bookings report, the weekly kitchen report, the monthly menu report and the monthly profit and loss. For each, it explains what it shows, who should read it, when, and what decision it informs. It also lists twelve reports you can stop producing, covers restaurant KPIs, the weekly review and the restaurant dashboard, and how to keep reporting from growing back.

Reporting exists to help people make better decisions, sooner. In a restaurant, the decisions are practical: how much to order, how many people to roster, which dishes to change, which nights to promote, whether a cost is under control. A good report puts the right numbers in front of the right person at the moment they make that decision.

That means each report needs a reader, a timing and a purpose. A report without a named reader is read by nobody. A report that arrives after the decision has been made is too late. A report without a purpose is noise.

The general idea of business intelligence, turning data into decisions, applies to a single venue as much as to a large company. The difference is scale: a venue needs a handful of clear reports, not a data warehouse.

The daily report summarises yesterday: sales, covers, spend per cover, by service, compared with the same day last week and last year. It may include a note of anything unusual: a large party, a quiet night because of weather, a kitchen problem. It is short enough to read in a minute.

Who reads it: the general manager, and the owner if they are not in the venue every day. When: first thing each morning. What it decides: whether yesterday was normal, and whether anything needs attention today, such as a service that fell well short or a cost that spiked.

Our guide to the covers report, read on a Monday morning covers the covers side in detail.

The weekly prime cost report shows food and drink cost and labour cost for the week, as a share of sales, with the combined figure. It is the single most useful weekly financial report for most venues, because it captures most of what decides whether the week made money.

Who reads it: the chef, for the food side, the manager, for the labour side, and the owner. When: early each week, for the week just ended. What it decides: whether purchasing, waste and the rota are under control, and which half needs attention.

Our guide to prime cost, the one number to watch weekly covers the calculation.

The weekly covers and bookings report shows covers by service, source and party size for the week just ended, alongside the bookings already in for the week ahead. It includes no-show and cancellation rates, and how much notice guests gave.

Who reads it: the manager and whoever writes the rota and the forecast. When: at the end of each week. What it decides: next week's forecast, rota and purchasing, and whether no-shows or cancellations need attention.

Our guide to sales forecasting for next week in twenty minutes covers how it feeds the forecast.

The weekly kitchen report shows how the kitchen performed: ticket times by station and by hour, the slowest tickets, the share of tickets on time, remakes and waste. It shows where and when the kitchen fell behind.

Who reads it: the head chef and the manager. When: weekly, before planning the next week. What it decides: whether the kitchen needs more hands at a particular station or hour, whether a dish is slowing service, and whether the dining room's pacing needs changing.

Our guide to ticket times covers how to read the kitchen's numbers.

The monthly menu report shows each dish's sales, share of its section and gross profit per plate, with the categories' share of revenue. It is the basis for menu engineering: which dishes to protect, re-cost, reposition or replace.

Who reads it: the head chef and the owner or manager. When: monthly, and before any menu change. What it decides: menu changes, pricing and which dishes to promote.

Our guide to menu engineering covers how to act on it.

The monthly profit and loss shows sales, every cost and the profit for the month, ideally with each line as a percentage of sales and compared with the same month last year and the budget. It is the complete financial picture.

Who reads it: the owner and the general manager, and the chef for the lines they control. When: monthly, as soon as the accountant produces it. What it decides: whether the business is on track, which costs are drifting, and where to focus next.

Our guide to a restaurant profit and loss you can read walks through it line by line.

Six reports cover the decisions most venues make: today's attention, the week's costs, next week's plan, the kitchen's performance, the menu and the month's result. Each has a clear reader and purpose. Together, they take far less time to produce and read than a dozen overlapping reports, and they are more likely to be acted on.

Some venues need a seventh for a particular reason: a marketing report while running a major campaign, or a guest feedback summary during a period of change. Add it deliberately, with a reader and a purpose, and remove it when the reason has passed.

Many venues produce reports that rarely change a decision. Twelve common ones are:

Before stopping a report, ask its reader whether it changes a decision. If not, stop it. If they are unsure, stop it for a month and see whether anyone misses it.

Restaurant KPIs, key performance indicators, are the handful of numbers that best show how the venue is doing. Within the six reports, the most useful KPIs are sales, covers, spend per cover, prime cost, food cost percentage, labour cost percentage, no-show rate, ticket times and profit per cover.

Choose a small set and watch them consistently. Our guide to restaurant KPIs worth tracking every week covers eight numbers and what each is for. More KPIs do not mean better management; the right few, watched every week, do.

The six reports come together in a weekly review: a short meeting, often thirty minutes, where the manager, the chef and sometimes the owner look at the week's numbers and agree what to change. The daily report, the weekly prime cost, the covers and bookings report and the kitchen report are its main inputs.

Keep the agenda fixed: what happened last week, what is coming next week, what we will change. End with a short list of actions and owners. Our guide to a weekly review that takes thirty minutes sets out the agenda.

A restaurant dashboard is a single screen showing the most important numbers at a glance, usually updated automatically. It suits the daily report well: sales, covers, spend per cover and a few other measures, compared with the same day last week. A good dashboard replaces several emailed reports with one place to look.

Keep it small. A dashboard with thirty charts is as hard to read as thirty reports. Our guide to a restaurant dashboard you look at daily covers how to design one that people actually use. The general idea of a dashboard, a single view of key information, works best when it is ruthlessly selective.

Every report should be readable in a minute or two. Put the most important number first. Compare it with something meaningful: the same period last week or last year, the budget or the target. Use percentages where they help, and show trends rather than single numbers where possible.

Avoid cluttering reports with every available figure. If a number does not support the report's decision, leave it out. A short report that is read is worth more than a complete one that is not.

Not every report is for managers. The floor team benefits from a few simple numbers too: how many covers are expected tonight, whether yesterday's feedback mentioned anything, which dishes are being promoted, how the last week's no-shows looked. Shared at the pre-service briefing, these turn reporting into something the whole team uses.

Keep it short and practical. Servers do not need the profit and loss; they need to know what tonight looks like and what guests said about last night. A team that sees the numbers understands why the rota, the menu and the booking rules change.

Reports are only as good as the data behind them. Sales that are rung in under the wrong category, covers that are not recorded for walk-ins, stock counts that are skipped, hours that are not recorded accurately: each makes a report less trustworthy. Once a report is wrong a few times, people stop reading it.

Check the data regularly. Make sure sales are rung in correctly, every service's covers are recorded, stock is counted the same way each time and timesheets reflect actual hours. When a report looks odd, check the data before acting on it.

The point of a report is to act on it. When a report shows a problem, a cost that has jumped, a service that fell short, a dish that is losing money, decide what to do, who will do it and when you will check again. Write it down in the weekly review's action list.

Not every unusual number is a problem. A single quiet night may be weather; a single high food cost week may be a stock count. Look for patterns over several weeks before making large changes, and investigate single surprises rather than reacting to them.

A menu change is a moment when the reports matter most. Before the change, the menu report shows which dishes to keep, change or remove. After it, the daily and weekly reports show whether covers, spend per cover and the kitchen's speed have changed, and the menu report shows how the new dishes are selling.

Plan to look closely at the reports for the first few weeks after any menu change, so problems are caught early and the chef can adjust before the new menu settles.

Give each report an owner: the person who produces it, checks it and makes sure it reaches its reader on time. Often the general manager owns the daily report, the weekly prime cost and the weekly review; the head chef owns the kitchen report and contributes to the menu report; the owner or accountant owns the profit and loss.

Ownership keeps reports accurate and timely. A report that everyone produces is a report nobody checks.

Groups with several venues need the same six reports for each venue, plus a short group summary that shows each venue side by side. Comparing venues on the same measures, prepared the same way, shows which are doing well and which need help.

Keep the group summary as lean as the venue reports. The head of a group needs to see which venues need attention, not every detail of every venue.

Reporting tends to grow again, one report at a time. Each new question produces a new report, which keeps being produced long after the question is answered. Review the list of reports every six months. For each, ask who reads it, what decision it supports and when it was last acted on. Stop the ones that fail.

When someone asks for a new report, ask what decision it will support and for how long. Often a one-off analysis answers the question without creating a permanent report.

Here is an illustrative venue that cut its reports. The details are examples.

In servearound, Analytics reads the service itself, on the venue's own clock, across reservations, orders, payments, tables, the kitchen, the menu, guests and campaigns. Reservation analytics shows covers by day, meal period, source and party size, no-show and cancellation rates and how much notice guests give. Kitchen analytics shows ticket times, on-time and remake rates and the slowest tickets. The menu report shows each dish's units, revenue and margin once its cost is set, and payment analytics shows takings by day and hour, discounts, voids and comps.

The dashboard shows the venue's key figures at a glance, such as spend per cover. Food and drink cost and labour come from your own stock counts and payroll, so prime cost is calculated alongside. See Analytics, or get in touch.

For most venues, six: daily, weekly prime cost, weekly covers and bookings, weekly kitchen, monthly menu and monthly profit and loss.

For daily attention, the daily report; for weekly control, prime cost.

Match the timing to the decision: daily for today's attention, weekly for costs and planning, monthly for the menu and the full picture.

Ask each report's reader what decision it supports. If none, stop it.

A small dashboard is a good home for the daily report. Keep it to a handful of measures.

The owner and general manager, and the chef for the lines they control.

The simple, practical parts, yes: tonight's expected covers, feedback themes and the dishes to promote. The financial detail is for managers.

Once set up, the six reports should take no more than an hour or two a week to produce, and much less if the figures come straight from the venue's systems.

Offer it on request, as a one-off analysis, rather than as another regular report. Most detailed questions are answered once and do not need repeating every week, and a regular report created for a passing question soon becomes noise. Ask what decision the extra detail would change, and start there.

Restaurant reporting works best with six reports: the daily report, weekly prime cost, the weekly covers and bookings report, the weekly kitchen report, the monthly menu report and the monthly profit and loss. Each has a reader, a timing and a decision it supports. Stop the reports that do not change a decision; twelve common ones are listed above.

Choose a small set of restaurant KPIs, bring the weekly reports together in a thirty-minute weekly review, use a lean restaurant dashboard for the daily view, give every report an owner, and review the list every six months so reporting does not grow back.