Back to blog
Guide

The Report You Should Read Every Monday

Most venue reporting is either a wall of numbers nobody opens or a revenue figure that says nothing. Seven numbers, five minutes, once a week — and the rule that decides whether a number earns its place on the page.

There are two kinds of venue reporting, and both fail.

The first is a dashboard with forty numbers. It gets opened twice and then never again, because reading it takes twenty minutes and produces no decision.

The second is a revenue figure in a message. It gets read every day and produces no decision either, because a total cannot tell you what to do.

What works is smaller than the first and more than the second. Seven numbers, once a week, five minutes.

The rule for what goes on the page

A number earns its place if a plausible value would change what you do this week.

Apply it honestly and most numbers fail. Total revenue fails — whether it is up or down, you do not know what to do differently on Monday. Revenue per head against its median passes — if it fell while heads rose, you have a capacity decision.

Run every candidate through it. The page gets short fast.

The seven

1  Revenue per head, vs trailing 8-week median for each weekday
2  Heads, vs the same median
3  No-show rate, this week
4  Shift-weighted retention, rolling 30 days
5  Availability trend, anyone down more than a third
6  Returning guest share, this week
7  Channel ceiling vs current spend, per channel

Why each is here:

1 and 2 together, never separately. Revenue alone cannot distinguish "busier and poorer" from "smaller and better." These two split it in one line.

3 tells you what is booked but not arriving, which is the difference between a demand problem and a confirmation problem.

4 is the slowest-moving number on the page and the most expensive to ignore. Weighted by shifts, not headcount — otherwise a core person leaving looks the same as a casual.

5 is the only forward-looking number here. Everything else describes last week. Availability narrowing predicts a resignation two to four weeks out.

6 tells you whether you are building or churning. A room with rising revenue and falling returning share is renting its growth from marketing.

7 is the one that connects operations to spend. If a channel is under its ceiling, you are leaving volume on the table. Over it, you are buying guests worth less than they cost.

What is deliberately not here

Total revenue. Fails the rule.

Profit. Not available weekly with any accuracy, and a wrong number weekly is worse than a right one monthly.

Anything you cannot act on before next Monday. A quarterly trend belongs in a quarterly review. Putting it on a weekly page trains people to skim.

Anything with no comparison. A number without a baseline is a number nobody can read. Every line above has "vs" in it, explicitly or implicitly.

The five-minute discipline

Same time every week. Monday morning, before the week starts.

Same seven numbers, same order. The order matters more than it sounds — you learn the shape of a normal week, and an abnormal one becomes visible without reading carefully.

One decision, written down. Not seven. One. If nothing changed enough to warrant a decision, write "no change" and stop. A week with no decision is a fine week; a week with seven is a week where nothing was really decided.

Who reads it

Everyone who can act on a line.

The floor manager cannot do anything about the channel ceiling. They can do something about no-show rate and availability trend. Give them those two, and give them their own numbers, not the aggregate.

A number shown only to the owner changes only the owner's behaviour. Most of these have someone closer to them who could act sooner.

The failure mode

The page grows. Someone asks for one more number, it is a reasonable request, and it goes on. A year later there are twenty-two lines and nobody reads it.

Fix it with a hard cap. Seven lines. To add one, remove one. The argument about which to remove is more valuable than the number being added, because it forces the rule to be applied again.

The system we built

tasteck is a booking and analytics system for night venues, built by people who ran them for sixteen years and grew from ¥200 million to ¥1.2 billion a year — six-fold. The weekly page was the habit underneath it, and it stayed at seven lines for most of that time.

What it does here: revenue and guest counts per night with weekday comparison. Guest records that persist across visits, so returning share is computable. Shift submission and history, so retention can be weighted by shifts and availability trends are visible. Bookings with status, so no-show rate is a query. Analytics across accounting, staff performance and guest segmentation.

What it does not do: it does not assemble the weekly page for you or send it Monday morning. The habit is yours. What the product supplies is that all seven are queryable from one place rather than assembled from four.

The output no one else produces

tasteck outputs the maximum you can spend on each marketing channel next month, as an amount in your currency.

That is line 7, and it is the one no other product in this category can put on the page. Lifetime value of the guests each source delivered, times your target margin, minus a reinvestment reserve — as an amount, per channel, per month.

Every other line describes what happened. This one tells you what to do next.

Ask it from ChatGPT

tasteck connects to ChatGPT over MCP: ask for the seven and they come back in the chat — no dashboard to open, no report to find. Which is the difference between a habit that survives a busy week and one that does not.

Measured against every vendor listed on Japan's principal nightlife-industry directory, this is the first implementation of it in the category, and the same interface is callable from anywhere rather than being tied to one assistant.

Multi-language is built in, the operating surface itself, with your language set put in place during onboarding.

From $34 a month for up to two venues. Thirty days free on every plan, cancel any time.Pricing

Start next Monday

  1. Write the seven on one page. Nothing else, however tempting.
  2. Put a "vs" on every line. A number without a baseline cannot be read.
  3. Cap it at seven. To add one, remove one.
  4. Give each line to whoever can act on it. Not everything to the owner.
  5. Write one decision. "No change" is a valid decision and should be written too.

Read next


On benchmarks. No target values for any of the seven appear in this guide. We do not have a dataset broad enough to publish them, and they vary enormously by format, city, and price point. Every line above compares you to your own trailing median, which is the only benchmark that describes your room.

Free, no signup, ~5 minutes

Map out your operations in 5 minutes

Eight questions cover reservations, customer management, shifts, and settlement. Results shown instantly with industry benchmark. Sales emails only if you request them.

Your answers are not stored. The assessment runs entirely in your browser.

Try tasteck free for 30 days

No credit card required. Full access to reservations, cast shifts, dispatch, and analytics.

  • No card required
  • Free data migration support
  • All features unlocked for 30 days