A number without a next action is still reporting
Operators already have numbers. A weekly file is still reporting until someone can release a named action that changes the floor.
The weekly file arrives. Food cost is up. Labour is up. Covers on Tuesday lunch are down. The file is complete. The floor is unchanged.
That is reporting. Reporting is not the same as a recommended action someone can release.
We already wrote that a dashboard is not a decision. This is the next cut. You can track the right numbers and still only be reporting. The missing piece is the rule that turns a moved number into a named action: this item, this shift, this dish off tonight, released by a person, then measured.
The catalogue is not the job
The German hospitality press is full of KPI lists. BarBrain draws a useful line and then publishes twelve metrics. Heptic says the same thing another way: the data already sits in the sales export, the delivery notes and the time clock, and the monthly accountant file is often four weeks late. Their answer is a shorter list, reviewed weekly.
A shorter list is still a list. Twelve tiles or seven tiles does not change tonight’s prep. The test is the same one we use on the homepage. If this number moved, what would you do differently? If the answer is “look at it again next month,” you are reporting.
What an action rule looks like
An action rule is boring on purpose. Before the number is read, you have already said: if this metric moves past this point, this role releases this measure.
Not “we should watch food cost.” A named measure: pull this item, change this prep, move this shift. Simulated against stock and staffing if the knock-on matters. Released. Written back only after that release. Held against the expectation the week after.
Without that rule, the weekly meeting becomes a reading of the file. Everyone agrees the number moved. Nobody owns the sentence that follows.
Why the file stays a file
Because the number lives in one system and the action lives in another. Sales knows covers. Stock knows the crate. The roster knows the shift. The accountant knows the invoice. The monthly file joins them after the week is over.
Because the person who can join them in the week is not always in the room. Experience does not scale to the second site. When they leave, the file stays. The rule does not.
Hospitality is where this shows first. Demand moves by the hour. Capacity does not. Labour and material are committed before the guest arrives. That is why hospitality is the beachhead. It is not the size of the market. The same pattern is a warehouse, a line, a care home.
What follows the number
Spectacle sits above the systems you already run. It does not replace them. It does not add a thirteenth tile. It proposes a named measure, ranked by expected contribution in euro, computed before it runs. You decide, per measure type, what is automatic, what needs a role, and what stays manual. A legally sealed system is never written to.
The loop is detect, recommend, simulate, release, execute, measure. The measurement goes back into the model. A report ends at the observation.
If the object model already exists in your trade, twenty minutes is enough to see whether an action rule is worth building. If the data cannot answer the question, we say so.
FAQ
How is this different from “a dashboard is not a decision”? That piece is about the screen. This one is about the file you already trust. You can have the right numbers and still only be reporting.
Is the answer fewer metrics? Fewer metrics help you read. They do not release an action. The job is the rule after the number, not a shorter catalogue.
Does this replace the accountant’s file? No. The monthly file is a record. Operational intelligence is a recommended action you can release in the week, then measure.
Why start with hospitality? Because the week is short and the systems sit apart. Hospitality is the beachhead, not the whole market.
Where should I start? Spectacle. The Insights series is how we write about the operation.