The Report You Open Every Monday

Monday morning. Someone opens the weekly report. Revenue, covers, average spend, labour percentage, a chart of the last eight weeks.

Everyone nods. Nothing changes.

That is the normal outcome, and it is not because the numbers are wrong. It is because most of them cannot change a decision you are about to make.

The test

One question separates a metric from decoration:

If this number came back different, what would I do differently this week?

If the answer is "nothing", or "I'd think about it", it belongs in a monthly review, not on a Monday dashboard.

Run that test on your current report. In most venues, two or three of a dozen survive.

What survives

Different rooms differ, but the ones that usually pass the test share a shape: they are early, they are specific to a decision, and they point at something you control this week.

Bookings on the books for the coming weekend, versus the same point last week. Changes staffing, and you can still act. Last weekend's covers cannot be staffed retroactively.

Labour as a share of revenue, by shift, not by week. The weekly figure hides the problem — one over-staffed Tuesday and a short Saturday average out to "fine". The shift-level number tells you which rota to change.

Something falling off. Guests who came regularly and have not been in; a cast or server whose bookings have dropped; a section whose take has slid three weeks running. These are the ones you can still intervene on. A total tells you where you ended up; a trend tells you where you are going.

What is usually theatre

Total revenue, on its own. It moves for a dozen reasons and points at none of them. It is a scoreboard, not an instrument.

Averages across the whole venue. Average spend across a room with a £15 table and a £900 table describes nobody.

Anything only available after the fact. A perfect breakdown of last month is history. Useful for planning the quarter, useless on a Monday.

Anything nobody owns. A number with no name attached to it does not get acted on. It gets read out.

The trap in the middle

The most dangerous report is the one that is accurate, detailed, and not connected to any lever.

Because it looks like management. It is discussed, it is circulated, and it produces the feeling of having addressed the problem. Whereas a rough number attached to a decision — "we are three staff heavy on Wednesdays" — produces a changed rota.

Precision is not the same as usefulness. A number good to ±20% that changes a rota beats one good to the penny that changes nothing.

Building the short version

Take your current report and split every line into two piles.

Pile one: this changes something this week. Keep it. This is your Monday page.

Pile two: everything else. Do not delete it — move it to a monthly or quarterly review where the longer view is genuinely the right lens.

⚠️ The second pile is usually the larger one, and that is fine. The problem was never that those numbers existed. It was that they sat next to the ones that mattered and diluted them.

The number of numbers

Five is about the ceiling for a page that gets acted on. Past that, attention spreads and nothing is followed up.

If you cannot get to five, the honest move is not to pad it — it is to accept that four things need attention this week and do them.

Who reads it changes what belongs on it

A manager running the floor, an owner with two venues, and a head of a department need different pages.

The owner's page is comparative — this venue against the other, this month against the same month last year. The manager's page is operational — this week's rota, this week's bookings, who has stopped coming in.

Putting both on one page produces a report that serves neither. Two short pages beat one long one.

Three to hold

Forward bookings versus the same point last week. The only one that lets you still change staffing.

Labour share by shift. Where the rota is actually wrong.

The falling-off list. Guests, staff, or sections trending down while there is still time to intervene.

Where the record has to sit

None of the three can be assembled if bookings live in one place, the rota in another, and guest history in a third. That is why the Monday report ends up being whatever was easiest to export — usually revenue.

tasteck keeps bookings, shifts, and guest history on one record, so the forward view and the falling-off list are queries rather than a spreadsheet somebody rebuilds each week.

A report that changes nothing is not a small problem. It is the appearance of having looked.