Your Dress Code Is a Pricing Decision

A dress code is written as a rule about clothes and works as a rule about people.

That is not a criticism — filtering the room is a legitimate and often necessary thing to do. But it means a dress code is not really a wardrobe policy. It is a positioning decision, enforced at the door, by a staff member, one guest at a time, at speed.

And like every pricing decision, it has a cost that can be counted.

What the code is actually doing

Setting the room's price signal    before anyone sees a menu
Filtering by spend intent          imperfectly, and everyone knows it
Filtering by group composition     which is usually the real purpose
Giving the door a reason to say no that does not require a judgement call

The fourth line is the most valuable and the least discussed. A written code lets a door staff member refuse entry by pointing at a rule rather than at a person. That protects the staff member, and it makes the refusal defensible. A door with no stated code has to improvise a reason every time, and improvised reasons are where trouble starts.

The cost side

Every refusal is a guest who does not spend. That is the obvious cost, and it is not the largest one.

The refused guest             this night's spend, gone
Their group                   often the whole party leaves
The people behind them        a slow door loses the queue
The story afterwards          refusals travel further than admissions

The second line is where the money is. Refusing one person in a party of six usually costs you six covers, not one. Most venues have never counted this, because the log records a refusal and not a party size.

The measurement almost nobody has

Refusals per night, by reason
Party size behind each refusal
Refusals by hour             is the code enforced the same at 11 and at 1?
Refusals by staff member     is it enforced the same by everyone?

The fourth line is uncomfortable and important. If one staff member refuses at several times the rate of another on the same door on the same nights, you do not have a dress code. You have a person's judgement, wearing a code as cover. That is a legal exposure as much as a commercial one.

The third line finds the other common failure: a code that is strict at eleven and abandoned at one. A code that is not enforced consistently through the night is not doing the filtering job you think it is — it just moves the filter to whoever arrives early.

Writing a code that works at the door

Be specific about items, not about styles. "Smart casual" cannot be enforced consistently by anyone. A short list of named items can be.

Publish it where guests see it before they travel. A code discovered at the door is a refusal. A code read at home is a wardrobe choice. This one change reduces refusals without loosening anything.

Make it the same for everyone, and check that it is. Anything applied differently by group is a serious exposure in most jurisdictions, and the door log is where that either does or does not show.

Give the door a script. The refusal is the highest-friction moment in the venue. The words should be decided in advance, in daylight, not invented at the door at midnight.

⚠️ Do not tighten a dress code and raise a cover charge in the same month. Both filter the same room and you will not know which one changed your door.

What the code cannot do

Fix a spend problem            people dressed well can order cheaply
Fix a behaviour problem        clothing is a weak proxy and everyone knows it
Substitute for door training   the code is the tool, not the skill
Create a crowd you do not have if the room is empty, the code is just a smaller room

The last line is the one that costs venues most. Tightening a code in a quiet period feels like protecting the brand. What it actually does is refuse the few guests who came.

Loosening without losing position

If the numbers say the code is costing more than it protects:

Loosen by hour, not by rule. Strict early, relaxed late — or the reverse, if your problem is at closing. This keeps the code intact while recovering the trade.

Loosen by item, publicly. Remove one named item from the list and announce it. A quiet relaxation reads as inconsistency at the door, which is the worst of both worlds.

Replace the filter, do not remove it. If the code was doing real work, a cover charge, a minimum spend or a booking requirement can do the same filtering with less friction and a countable price.

The system we built

tasteck is a booking and analytics system for night venues, built by people who ran them for sixteen years and grew from ¥200 million to ¥1.2 billion a year — six-fold, by attacking the business with systems rather than by pushing harder on sales.

What it does here, honestly: tasteck does not run your door and has no refusals module — that belongs in the door log. What it holds is the other half of the comparison: bookings by hour, party sizes, spend per table, guest history and who was on shift. Put a night's refusals next to what the room actually did that night and the code stops being a matter of taste.

What it does not do: it does not record refusals, does not enforce policy, and does not advise on discrimination law — which governs this area in most countries and should be checked with someone qualified in yours. This guide is not legal advice.

The output no one else produces

tasteck outputs the maximum you can spend on each marketing channel next month, as an amount in your currency.

A dress code and a marketing channel are the same instrument pointed in opposite directions. The channel decides who arrives; the code decides who gets in. Spending to attract guests your door then refuses is the most expensive mistake available in this business, and it is invisible unless both numbers exist in the same place.

The ceiling is computed from the lifetime value of the guests each source actually delivered. Nothing else in the nightlife category produces that figure.

Ask it from ChatGPT

tasteck connects to ChatGPT over MCP: ask your numbers as a question and the answer comes back in the chat — what average party size spent last Saturday, which hours filled, which guests were first-timers.

Multi-language is built in, the operating surface itself, with your language set during onboarding.

From $34 a month for up to two venues. Thirty days free on every plan, cancel any time. → Pricing

Start this week

1. Record refusals with party size. One extra field. It changes the number by several times.
2. Break refusals down by hour and by staff member. Both will surprise you.
3. Put the code where guests read it before they leave home. Cheapest fix available.
4. Replace every style word with a named item. "Smart casual" is unenforceable.
5. Write the refusal script in daylight. Not at the door, not at midnight.

Read next

• Door Staff and the Queue Outside
• The Incident Log You Do Not Keep
• Pricing a Night Out Without Guessing
• The VIP Room That Earns Less Than the Floor
• Nightclub Software

---

On benchmarks. No acceptable refusal rates, target ratios, or code templates appear in this guide. We do not have a dataset broad enough to publish them, and dress codes are bound up with local discrimination law, which varies. One month of your own refusals, recorded with party size and staff member, will tell you what the code costs — and whether it is a code at all.