Reporting is where most independents either drown or fly blind. The drowning version comes from software that offers a hundred reports and forty dashboards, so much that you glance at it once, feel vaguely guilty, and never open it again. The blind version is the opposite: no real reporting at all, the business run on gut feel and the vague sense that last weekend felt busy. Both fail for the same reason. The point of reporting is not to have numbers. It is to make decisions, and neither too many numbers nor too few helps you decide anything.
This is a guide to the numbers that actually run a venue: which ones matter, how to read them, and how to set up reporting you will genuinely use. I have both ignored my numbers and buried myself in them, and the useful place is a narrow band in between.
The two ways reporting fails
It is worth naming both failure modes clearly, because avoiding them is most of the battle.
Too much is the more seductive failure, because it looks thorough. A reporting suite with endless breakdowns feels like diligence, but volume is not insight. If you cannot say, for each report, what decision it would change, the report is noise wearing the costume of rigour. The result of too much is always the same: you stop looking, because looking is overwhelming and unrewarding, and you end up no better informed than if you had nothing.
Too little is the more honest failure, and the more common one in small venues. You run on feel, because pulling numbers is a faff and there is always a service to run. Feel is not nothing, a good operator's instinct is real, but it is blind to slow trends and quietly wrong about things that feel true. The Tuesday that feels dead might be quietly profitable. The dish that feels popular might be losing you money. Feel cannot see those, and only numbers can.
The target is between the two: a few numbers, clearly presented, each tied to a decision, looked at on a regular rhythm. That is reporting that works.
The numbers that actually matter
Here is the short list that runs a venue. Not everything you could measure, just the things worth acting on.
Sales and covers over time. The most basic picture: what you took and how many people you served, tracked across days, weeks and seasons. This tells you the shape of your trade, where it is growing or shrinking, and which periods carry the business.
Average spend per head. Sales divided by covers, watched over time. This is one of the most revealing single numbers, because it tells you whether people are spending more or less when they come, which menu changes and service habits move it, and how your busy and quiet periods differ in value, not just volume.
What your menu is actually selling, and at what margin. Not just what is popular, but what is popular and profitable, which are not the same. The dish everyone orders that barely makes money and the quiet dish with a strong margin both matter, and you cannot see either without looking. This is where a lot of hidden profit lives.
Your busy and quiet periods. The real shape of your week and your day, so you can roster to it, fill the quiet parts deliberately, and stop guessing about demand. Most operators think they know this and are partly wrong, because feel rounds off the edges that data shows sharply.
Who your guests are, by value and frequency. This is the number most reporting ignores and the one that arguably matters most. Who are your real regulars, by what they are worth? Who is returning, who is new, who has drifted away? Sales reports tell you what happened. Guest numbers tell you why, and what to do next, because a venue lives or dies on whether people come back.
That is the list. Five things. A venue that genuinely watches those, and acts on them, is well run on the numbers. Everything beyond them is optional, and much of it is distraction.
Sales reporting versus guest reporting
There is a distinction worth drawing out, because it is where most reporting is weakest. Most reporting is sales reporting: it tells you what was sold. That is necessary and it is not enough, because it is all in the past tense and all anonymous. It tells you Saturday took a certain amount and a dish sold a certain number. It does not tell you who, or whether they will come back, or who you are quietly losing.
Guest reporting answers the forward-looking questions. It connects sales to people, so you can see value by guest, retention, and churn. It is the difference between knowing your takings and understanding your business, because a venue's future is mostly determined by its guests' behaviour, and you cannot see that behaviour in a sales report alone. The catch is that guest reporting is only possible if your systems hold a guest record, which is why this connects back to everything else: reporting is only as good as whether your data knows who your guests are.
How to read the numbers without a finance background
You do not need to be an accountant to use these well. A few habits do most of the work.
Read trends, not single figures. One week's number means little. The direction over several weeks means a lot. Always ask "compared to what?", last week, last month, this time last year, because a number with no comparison is just a number.
Ask what each figure would make you do. If average spend per head fell this month, what changed, and what will you try? If a profitable dish is barely selling, should it move on the menu? The number is the start of a question, not the end of one.
And do not chase noise. Daily figures bounce around for reasons that do not matter, weather, a one-off party, a quiet Monday. Looking too closely invites you to react to randomness. A weekly rhythm smooths that out into something you can actually act on.
Setting up reporting you will use
The best reporting is the reporting that happens, and the enemy of that is manual effort. If using your numbers means exporting from three systems and assembling a spreadsheet, it will not happen, because there is always a service to run. Reporting built into your systems, drawing on live data automatically, is the difference between reporting you mean to do and reporting you do.
Keep the rhythm simple. A short weekly check of your key numbers, ten minutes, and a deeper monthly look. Daily is too noisy, yearly is too late. The exact cadence matters less than keeping it, and you will only keep it if the numbers are in front of you without work.
Where Grace fits
Grace's reporting is built around the guest, not just the till, which is the part most reporting misses. Because the platform holds one record per guest, it can show you not only sales and covers and menu performance, but value by guest, retention and who is drifting, the forward-looking numbers that actually shape a venue's future. It draws on live data across bookings, the till and the guest record, so the numbers are there without you assembling anything, and it aims to show you the few that matter rather than burying you in dashboards. You can see the Analytics module for how it works.
It is built this way because I have made both reporting mistakes, ignored my numbers and drowned in them, and the lesson was the same each time: the goal was never more data. It was a few numbers I would actually use.
The short version
Reporting fails by giving you too much, so you read nothing, or too little, so you run blind. Aim for the narrow useful band between: a few numbers, clearly shown, each tied to a decision, on a regular rhythm. The five that run a venue are sales and covers over time, average spend per head, menu performance by margin, your busy and quiet periods, and who your guests are by value and frequency. Read trends not single figures, always ask "compared to what?", and act on what you see. And insist that reporting connects to your guests, because sales tell you what happened while guests tell you what is going to.
---
More in this series
Placeholder block. Link each as it publishes, per the editorial calendar.
FAQ
What reports does a restaurant actually need?
A small number that drive decisions: sales and covers over time, average spend per head, what your menu is actually selling and at what margin, your busiest and quietest periods, and who your guests are by value and frequency. Most other reports are interesting at best and a distraction at worst. - q: "Why is most restaurant reporting unhelpful?" a: >- Because it fails in one of two directions. Either it buries you in dashboards and figures you never act on, so you stop looking, or it gives you almost nothing, so you run on gut feel. Useful reporting sits between: a few numbers, clearly shown, that you actually use. - q: "What is the most important number for a venue?" a: >- There is no single one, but if pushed, the numbers tied to your guests, who is valuable, who is returning, who is drifting, matter most, because they drive the retention that quietly determines whether a venue thrives. Sales tell you what happened; guest numbers tell you why and what to do next. - q: "Do I need reporting software or is a spreadsheet enough?" a: >- A spreadsheet can work, but it relies on you exporting and assembling data by hand, which is slow and tends not to happen. Reporting built into your systems, drawing on live data including the guest record, gives you the numbers without the manual work, which is the difference between reporting you do and reporting you mean to do. - q: "How often should I look at my numbers?" a: >- A short weekly check of a few key numbers, plus a deeper look monthly, suits most independents. Daily is usually too noisy to act on and yearly is too late to change anything. The rhythm matters less than actually keeping it.