The Guest You Should Have Refused

Somebody was let in, or served, when they should not have been. Everybody knew at the time.

The person on the door was not wrong about what they saw. They were unsure whether the venue would back them, and that uncertainty is what made the decision.

What actually stops a refusal

Not judgement. Four specific things:

They do not know the line. ⚠️ "Use your judgement" means every refusal is a personal opinion, which is much harder to hold than a house rule.

They are not sure they will be supported. If a refusal produces an argument and a manager overrules it, nobody will refuse again for months.

It is being made alone. Late, in front of an audience, with the person in front of them.

Nobody has practised it. ⚠️ Knowing you should refuse and knowing what to say are different, and only the second one is available at 01:00.

What has to be decided in advance

The criteria, written plainly. Intoxication, aggression, capacity, condition of entry. In terms a person can apply, not a policy paragraph.

Who decides. ⚠️ Whoever is on the door decides, and is supported — or someone specific is called. Either works. Not deciding does not.

The words. The actual sentence. "Not tonight, sorry" is complete, and a person can say it. A general instruction to be firm is not a sentence.

What happens next. Do they move away, is anyone called, is it recorded. ⚠️ The step nobody plans, and it is where a refusal turns into a scene.

Backing them

The whole thing rests on this.

A refusal stands. ⚠️ Even one you would have judged differently. Overruling it in the moment removes the authority from everyone watching, permanently.

Discuss it afterwards, in private. If the call was wrong, that is a conversation for the next day, not a correction in front of a guest.

Say it out loud. "If you refuse someone, I will back you" — and staff need to have heard it before they need it.

Recording it

Not bureaucracy — three lines, because it matters later.

Who, when, why, who decided. ⚠️ Without it, a repeat visit is a fresh decision made by whoever is on tonight, with none of the history.

And it protects the person who refused. If it is questioned later, there is a record of what happened and why.

The pattern worth watching

Refusals concentrated on one shift or one person. ⚠️ Look at both explanations. It may be who is on the door; it may be which night attracts what.

Zero refusals, ever. ⚠️ Not a good sign. It means either nobody needs refusing — unlikely — or nobody feels able to.

Incidents that followed a non-refusal. The cost side, and it is the argument for making the change.

What it costs to get wrong

Letting someone in who should not be. The evening of everyone else, your staff's safety, and occasionally something much worse.

Refusing someone who was fine. ⚠️ Real and much smaller. A wrongly refused guest is one unhappy person; a wrongly admitted one can cost a whole room — and your team knows this ratio better than any policy document.

Three to hold

Refusals per month. ⚠️ The trend and the distribution, not the number itself.

Incidents where someone said afterwards that they had doubts. Ask. It is the most useful thing you will learn, and nobody volunteers it.

Whether staff can state the criteria. Ask three people separately. Different answers means there is no rule.

Where the record has to sit

A refusal recorded in someone's memory is unavailable to the person on the door next week. It has to sit against the night and, where relevant, against the guest, or every visit starts from nothing.

tasteck keeps notes against guests and shifts, so what happened on a night and what was decided stay attached to it.

They made the call they thought the venue would support. If you want a different call, that is a decision to make in the afternoon, not something to expect from someone standing alone at the door.