The Night You Turned People Away
Venues count what they sold and never count what they refused. Turn-aways, unanswered enquiries and slots that were full are demand you already paid to attract. How to count them without building anything.
A good Saturday. The room was full, the tables were all sold, the numbers were the best in months.
How many people did you turn away?
Almost nobody can answer this, and it is frequently the largest number in the building.
Why it is never counted
Because a refusal produces no record.
A sale leaves a transaction. A refusal leaves nothing — a phone call that ended, a group that walked, an enquiry nobody replied to. There is no line in any report where it could appear.
So the night reads as a success, which it was. It just may also have been a night where you refused as much again.
The three places it happens
One — the enquiry that was not answered. A message on a Friday afternoon, a call during service, a form submission at 02:00. Most venues have a large pile of these and no idea how large.
Two — the slot that was full. Someone wanted 22:00 on Saturday and 22:00 on Saturday was gone. They did not want 19:00 on Tuesday, so they went elsewhere.
Three — the door. People who arrived, saw the queue or the price, and left. Invisible by construction unless someone is watching for it.
All three are demand you already spent money to create. The advertising worked. The interest was real. It arrived at a closed door.
Counting it without building anything
One week. No system.
Unanswered enquiries: count the ones that got no reply. This is a number you can produce today from whatever channel they arrive on, and it is usually the one that causes the sharpest intake of breath.
Full-slot refusals: whoever takes bookings makes a mark when they say no because it is full, with the time requested. A tally on paper is enough.
Door walk-aways: ask the door team for a rough count on the two busiest nights. Rough is fine — you are looking for whether it is five or fifty.
⚠️ Precision is not the point. The purpose is to find out whether refused demand is a rounding error or a second business.
What the answer changes
Each of the three points somewhere different, which is why counting them separately matters.
Mostly unanswered enquiries? That is not a capacity problem at all. It is a response problem, it is the cheapest of the three to fix, and it usually returns the most.
Mostly full slots at one specific time? You have a pricing and a spreading question. The peak hour is underpriced relative to demand, and the hours either side are not being offered as alternatives.
Mostly door walk-aways? Look at what they saw — the queue length, the entry price, the wait with no information. Frequently a queue that moves is worth more than a queue that is short.
The trap
The instinct is to read refused demand as "we need more capacity."
Sometimes. But capacity is the most expensive answer on the list and often the wrong one. More space on a Saturday is also more space on a Tuesday, and Tuesday is where venues die.
Cheaper answers, tried first: answer the enquiries, price the peak properly, offer the adjacent hour deliberately rather than as a consolation.
The one worth doing regardless
Reply to the unanswered ones.
Not to fill this Saturday — it is full. To fill a Thursday, or next month. A person who wanted to come and got no answer is a warm lead sitting in an inbox, and in most venues there is a pile of them.
⚠️ This is the highest-return hour on the list and it requires nothing but doing it.
Three to hold
Enquiries with no reply, weekly. The cheapest lost revenue you have.
Refusals by requested time slot. Tells you whether it is a capacity problem or a pricing one.
Rough door walk-aways on your two busiest nights. The one you have to ask for, because it will never appear on its own.
Where the record has to sit
If enquiries arrive across several channels and bookings live somewhere else, "who asked and did not get in" is not a question anything can answer. That is why refused demand stays invisible in venues that measure everything else carefully.
tasteck keeps enquiries and bookings on the same record, so the people who wanted to come and could not are a list — one you can work through on a slow Tuesday rather than discover a year later.
You already paid to make them want to come. The expensive part was done.
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