What the Door Team Knows
The people at the entrance see the crowd change, the promoters underdeliver, and the trouble start — usually weeks before management does. Why almost none of it reaches anyone, and the two habits that fix it.
Ask a door supervisor who has worked six months what is different about the crowd lately and you will get a specific, accurate answer in about four seconds.
Ask the owner the same question and you will usually get last quarter's numbers.
The information exists. It just has nowhere to go.
What they see that nobody else does
Who is arriving and who has stopped. They recognise faces without knowing names, and they notice absence — which is the thing reports are worst at.
Which promoter actually delivers. They watch the groups arrive and can tell you within a week which name is bringing people and which is bringing a list.
Where the trouble starts. Almost always a specific pattern — an hour, a group size, a combination — visible from the entrance long before it becomes an incident.
Who was turned away, and why. The demand you refused, which appears in no system.
⚠️ All four are leading indicators. Everything management looks at is a lagging one.
Why it does not travel
Three reasons, none of them anyone's fault:
Nobody asks. The role is defined as controlling entry, not as observing. So they observe and say nothing, because saying something is not part of the job.
The shifts do not overlap. Management leaves before the door does, or arrives after. In many venues the owner and the Saturday door team have not had a conversation in months.
It got dismissed once. Someone mentioned something, it went nowhere, and that is the end of the reporting culture for a year.
The two habits that fix it
One — a ninety-second question at the end of the night. Not a form, not a report. One question, asked by whoever is closing:
"Anything different tonight?"
⚠️ The answer is usually "no" and that is fine. The value is entirely in the nights when it is not, and those nights are the ones you currently miss.
Two — write down the answer when it is not "no". One line, same place every time. Without this the habit produces conversations that evaporate.
What to do with a month of one-liners
Look for the repeat, not the incident.
Three mentions of the same hour is a staffing decision. Three mentions of the same promoter is a pricing conversation. Three mentions of the same group profile is a door policy question.
One mention is a Tuesday. Three is a pattern, and the pattern is the thing you could not see from the reports.
The one worth acting on immediately
"We turned people away."
That is refused revenue, it appears in nothing, and the door is the only place it is visible. ⚠️ Even a rough count on the busiest two nights changes what you know about your capacity — and it costs one question.
The mistake to avoid
Turning this into a report.
A form kills it within a month. The door team is working, the closing is busy, and any process with more than one step will lose to the actual job — correctly, because the actual job is more important.
Ninety seconds and one line is the design, not a starting point.
What it changes about the door role
There is a second effect worth naming.
Being asked changes what people notice. A door supervisor who knows they will be asked at the end of the night watches differently for the whole night — and that is free.
⚠️ It also means the question has to be genuine. Asked and then ignored is worse than not asked, because it teaches that observation is not wanted.
Three to hold
Nights with an end-of-night note. If it is not near everything, the habit has not landed.
Repeats in the last month. One mention is noise; three is the finding.
Rough turn-away count on the two busiest nights. The number that exists nowhere else.
Where the record has to sit
A one-line note is worth nothing if it lives in a different place each week. It needs to sit against the night, so that a month later the repeats can be seen next to what the night actually did.
tasteck keeps notes against nights and guests, so an observation on a Saturday is next to that Saturday's numbers when someone looks back.
They already know. Nobody has built the ninety seconds it takes to find out.
Related articles
Your Pour Cost Is a Schedule Problem
Most venues chase pour cost with tighter counts and better jiggers. The variance usually tracks who was behind the bar, not what they were pouring. How to read pour cost by shift, and why the fix is often on the roster.
Your Coat Check Is a Queue Problem
In cold markets the coat check decides how your night starts and how it ends. What the queue costs in unbought first drinks and in clearance time at close, and the three changes that move it without new staff.
Your Best Night Was Not Your Best Night
The night with the highest take is rarely the night that earned the most. What has to be subtracted before a night can be ranked, and why the answer usually reorders the whole week.
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