Who Can Say Stop

At 1am a host asks the floor manager to waive a table minimum for a guest who is "a regular of the owner's."

The floor manager does not know whether that is true. The owner is asleep. The guest is standing there. The table is waiting.

⚠️ There is only one thing that can happen next, and it is yes. Not because the floor manager decided yes, but because the person who could say no was not available and the situation would not wait.

The short version

• A rule with no reachable stop is a rule that always resolves to yes
• The question is not "who decides" but "who can say stop at 1am"
• Escalation that depends on somebody answering a phone is not a control
• Give the person on the floor a small, real authority instead of a large, absent one
• Write down the stop that was used, not just the ones that were not

Where the stop goes missing

What the policy says	What happens at 1am
"Requires owner approval"	Owner is asleep. It gets approved by default.
"Manager discretion"	Manager is on the door. Whoever is nearest decides.
"Escalate to the duty manager"	Duty manager is the person asking.

⚠️ None of these are ignored rules. They are followed exactly as written — and the writing does not survive contact with 1am.

One: the stop must live where the decision happens

A control only works if the person who can pull it is in the room.

Owner approval     - works during the day, fails at 1am
Manager approval   - works if the manager is not the one asking
Floor authority    - works, if you have set a limit they can hold

⇒ The last one feels like giving away control. It is the opposite: a small limit that actually holds beats a large one that cannot be reached.

What a small, real authority looks like

"You may waive up to X per night, total, without asking.
 Above that, it waits for me - and the guest waits too."

⚠️ "And the guest waits too" is the part that makes it work. If the alternative to your approval is "the guest walks out," the pressure will always break the rule. If the alternative is "they wait until morning," the rule can hold.

Two: the difference between a delay and a stop

Many venues have a delay where they think they have a stop.

Stop   nothing happens until somebody says yes
Delay  it happens, and somebody reviews it later

⚠️ A review after the fact is not a control on the night. It is a record. Records are valuable, but they do not prevent anything.

When a delay is the right answer

Delays are right when the cost of stopping is higher than the cost of a mistake.

Stop is right   letting somebody in, waiving a large amount, a barred guest
Delay is right  a small comp, a drink remake, a taxi fare

⇒ Trying to make everything a stop produces a venue where nothing moves and the rules get bypassed. Pick the three things that must stop, and let the rest be recorded.

Three: the escalation that nobody can use

Test any escalation path with one question.

"If this happens at 1am on a Saturday, what exactly does the person do?"

If the answer involves ringing somebody who may not answer, you do not have an escalation path. You have a hope.

Make the fallback explicit

One   Try the named person
Two   If no answer within five minutes, the answer is [X]
Three Write down that it happened and which step was used

⚠️ Step two is the one almost nobody writes. Without it, "no answer" becomes whatever the person under pressure decides, which is usually yes.

⇒ The same shape appears in message channels with no owner: the enquiry nobody knows you missed.

Four: the stop that only the builder can pull

This one appears whenever something runs automatically.

A process runs on a schedule — a reminder goes out, a charge is taken, a report is sent. Somebody realises it should not run tonight.

Who can stop it?
  Only the person who set it up
  And they are not here

⚠️ We hit exactly this in our own operation this month. We had an automated step that would run at a fixed time, and the plan for stopping it was "somebody sends a message to the person who built it, and they stop it."

That plan quietly assumed the builder would be awake and reading messages in the right thirty-minute window.

What we changed
  The stop became a file anybody on the team could create
  The automated step checks for it before doing anything
  Present  - it does nothing, and says why
  Absent   - it runs as planned

⇒ The important part is not the file. It is that the stop moved from a person to a thing, and from one person to anybody.

The question to ask about anything automatic

"If this should not run tomorrow, who stops it and how -
 without needing me?"

⚠️ If the honest answer is "they ask you," you have a stop that works only while you are available.

Five: a stop that leaves no trace is not a stop

If somebody halts something and nobody can see that they did, you lose two things: the ability to review it, and the protection for the person who did it.

Good  a mark, a note, a file, a line in the book - visible afterwards
Bad   a verbal "I told them no" - unprovable in either direction

⚠️ The person who says stop is the one taking the risk. If it goes badly, they need to be able to point at something. Otherwise the rational move is to say yes and let it be somebody else's problem.

The three lines that protect them

What was asked
What was decided
Who decided it, and at what time

⇒ Three lines, thirty seconds. That is the difference between a decision and an argument three weeks later.

Six: the person who is always the exception

Every venue has one relationship where the rules bend: the owner's friend, the promoter who brings numbers, the long-standing regular.

The rule    applies to everyone
In practice applies to everyone except that person

⚠️ Staff learn the exception faster than they learn the rule. Once they know a rule has a person-shaped hole in it, they stop treating it as a rule at all.

What to do about it

You do not have to remove the exception. You have to name it.

"X is an exception. It is my decision and I own it.
 Everybody else is the rule."

⇒ A named exception leaves the rule standing. An unnamed one dissolves it.

Seven: what to put in writing

Keep it to one page, and make it about people and hours, not principles.

For each thing that can be stopped:
  Who can stop it on the floor, tonight
  What their limit is
  What happens if they cannot reach the next person
  Where they write down that they used it

⚠️ Do not write "at management discretion." That phrase moves the decision to whoever is standing closest, and it will not be the same person twice.

⇒ On checks that exist on paper but stopped happening in practice: the check that quietly stopped.

The shift where nobody holds it

Watch for shifts where the person with authority is also the busiest person in the room.

Friday door   the floor manager is on the door, not the floor
Close         the manager is counting, not watching
Staff shortage everyone is covering, nobody is deciding

⚠️ These are the shifts where the limit quietly becomes whatever the moment allows. They are also, reliably, your highest-volume shifts.

Numbers worth keeping

One   How many times the floor authority was used (per week)
Two   How many times it was exceeded and escalated
Three How many escalations got no answer
Four  How many "exceptions" happened, and for whom

⚠️ Three is the number that tells you if your escalation is real. If escalations regularly get no answer, the limit is not being held by you — it is being held by whoever was on the floor.

Why the count matters more than the policy

A policy tells you what should happen. These four numbers tell you what does.

⇒ If the floor authority is used forty times a week and escalation never once, your real limit is the floor limit — and it should be set deliberately rather than by accident. On keeping numbers the team can actually see: the weekly number your staff never see.

The card for the office

────────────────────────
  Stopping something tonight

  1. Can the person on the floor stop it, right now?
  2. If not, who - and will they actually answer?
  3. If nobody answers in five minutes, the answer is: ______
  4. Write three lines: asked / decided / who and when

  If the stop needs one specific person,
  it only works while that person is awake.
────────────────────────

Common objections

"My staff would ring me"

⇒ They would try. The question is what happens in the minutes after you do not pick up, with a guest waiting. That is the actual policy, whether or not it is written anywhere.

"I don't want them giving things away"

⚠️ They already are, whenever you are unreachable — just without a limit. A stated limit gives away less than an absent owner.

"We've never had a problem with this"

⇒ You would not see most of it. A waived minimum at 1am and a correctly-charged table look identical on the sheet unless somebody writes down which happened and why.

"The system enforces it, so we're fine"

⚠️ A system enforces what it was configured to enforce. It will also cheerfully report success while doing nothing — the shape covered in the edit that said saved. Check the outcome, not the confirmation.

"Writing it down slows everyone down"

⇒ Three lines. The version that slows people down is the argument three weeks later about what was agreed.

What to do this week

One   List the three things that genuinely must stop.
Two   For each, name who can stop it at 1am on a Saturday.
Three If that name is only you, set a floor limit instead.
Four  Write the "no answer in five minutes" fallback.
Five  For anything automatic, ask who stops it without you.

Summary

• A stop that needs one specific person works only while that person is awake
• "Requires approval" with nobody reachable resolves to yes, every time
• A small real authority beats a large absent one
• Escalation needs an explicit "if no answer, then" line
• Stops that leave no trace protect nobody and get abandoned
• Name your exceptions — an unnamed one dissolves the rule

The rule that decides your 1am is not the one on the wall. It is whatever happens when the person who could say no does not pick up.