The Weekly Number Your Staff Never See

The team knows whether it felt busy. They do not know what the night made, what it cost, or whether the thing they did differently worked.

So they optimise for what they can see, which is how busy it feels — and that is not the same as what makes money.

What people do when they cannot see the numbers

They fill the gap with assumptions, and the assumptions are consistent:

Busy equals good. A hectic night with poor spend feels like a success and a calm night with high spend feels like a failure. Both are backwards, and nobody has ever been told.

The expensive thing is the one they were told off about. In the absence of figures, cost is learned from anecdote — usually one incident from two years ago.

Their own contribution is invisible. Someone who consistently sells better than everyone else does not know it, so nobody can learn from them.

What is safe and useful to share

The distinction that matters is not "sensitive" versus "not". It is can they act on it.

Take for the night, against the same night last week. Simple, comparative, and it teaches the thing people most need to learn — that busy and profitable are different.

Average spend per guest. The number the floor can actually move, and the one most directly connected to what they do.

The forward view. What next weekend looks like. People plan their own lives around this and appreciate knowing.

Something that improved. If the thing you asked for worked, say so with the number. Otherwise the request will be assumed to have been pointless.

What not to share, and why

⚠️ Individual comparisons on a wall. Ranked lists of people demotivate everyone below the top and encourage the behaviour that games the metric. The information is useful privately and corrosive publicly.

Anything with someone's pay in it. Obvious, and it is worth being explicit that this is why some things stay closed — otherwise the closure reads as general secrecy.

Numbers you are not prepared to explain. ⚠️ A figure shared without context generates worse assumptions than no figure, because it looks like an answer.

The format that survives

Not a meeting. Not a dashboard nobody opens.

One number, said out loud, once a week, at a moment people are already together. Thirty seconds at the start of a shift.

Written up somewhere the team already looks, if you have such a place. If you do not, the spoken version alone is enough — and a printed sheet in a room nobody stands in is not.

What actually changes

Three things, and the third is the one that pays.

Suggestions get better. People who know the average spend suggest things that move it, rather than things that make the night feel smoother.

The good performers become visible to themselves. Frequently they had no idea, and once they know they can articulate what they do — which is the only way it spreads.

Requests get accepted. ⚠️ "We need to push the mid-range bottles" lands completely differently when everyone has seen that the mid-range is where the margin is. Without the number it is an instruction; with it, it is a reason.

The objection worth taking seriously

"They will ask for more money."

Sometimes. But the conversation about pay is happening regardless, and it happens with better information on your side too. A team that understands the numbers understands why the answer is what it is — and the venues that share tend to have that conversation more calmly, not less.

Three to hold

Weeks with the number actually shared. If it is not near everything, the habit has not landed.

Average spend per guest, weekly. The floor's number.

Suggestions received from the team, monthly. ⚠️ Rising is the real signal that the sharing is working — it means people now have something to reason with.

Who says it, and where

Posted on a wall   read once, then invisible
Sent in a group chat  scrolled past
Said at pre-shift   heard, but not retained
Said, then posted   retained

⚠️ The number has to be spoken by someone who can answer a question about it. A posted number with nobody attached to it reads as an instruction from management, not information.

The person who says it matters more than the channel

⇒ If the GM reads it out and cannot explain a movement, the next week nobody listens. Say only numbers you can explain.

---

The week it goes the wrong way

This is the test. Everything works while the number is improving.

Hide it     the whole exercise is revealed as marketing
Show it flat  fine, but says nothing
Show it down  people find out what the number is actually for

⚠️ A bad week shown plainly buys more credibility than ten good ones. The first down week is when staff decide whether this is information or pressure.

What to say in a down week

1. The number
2. One thing that plausibly explains it (not a person)
3. One thing being changed, or "nothing yet, we are watching"

⇒ ⚠️ Point two must not be a person. Once a number is attached to a name in public, it stops being a shared metric and becomes a performance review nobody agreed to.

---

When someone games it

They will. That is not a character problem; it is a design signal.

If one person can move the number alone, it was the wrong number

⚠️ The fix is pairing, not policing. Any single metric can be moved in one shift; two paired metrics cannot.

Faster turn time    →  pair with spend per head
Higher attach rate   →  pair with comp ratio
More repeat bookings  →  pair with no-show rate

---

Cadence

Daily    people stop hearing it
Weekly   the smallest unit that shows a pattern
Monthly  too late to act on

⚠️ Weekly is not a compromise; it is the only cadence that matches how staffing decisions are actually made.

The exception

⇒ During a change you are testing, go daily for two weeks — and say that it is temporary when you start. Otherwise the return to weekly reads as the project being abandoned.

---

What it looks like after three months

Month 1  people ask what the number means
Month 2  people ask why it moved
Month 3  people tell you why it moved before you ask

⚠️ Month three is the whole point. If you are still explaining the definition in month three, the number is too complicated — pick a simpler one and start over.

---

Where the record has to sit

If the weekly number takes an hour to assemble, it will be shared for three weeks and then stop. The constraint is not willingness; it is how long it takes to produce.

tasteck keeps sales, guests, and shifts on the same record, so the weekly figure is a report someone opens rather than a spreadsheet someone rebuilds.

They are already making commercial decisions all night. They are just making them without any of the commercial information.

---

---

Read next

• Nightclub KPI Dashboard: What Belongs On It and What Is Just Noise
• Nightclub KPI Guide: 12 Metrics Every Operator Must Track
• Night Venue Scheduling: Why the Roster Never Matches the Room
• Stage Rotation Is a Scheduling Problem
• Your Pour Cost Is a Schedule Problem
• Why Your Best Staff Leave in Month Four