To be 86’d—pronounced “eighty-sixed”—is informal casino slang for being refused service, removed from the property, or told not to return. The problem with the term is that it is imprecise. Two employees can say “he was 86’d” while describing completely different legal and operational actions.
For casino records, the slang should never replace the actual status.
A patron might have been:
- asked to leave for the rest of the evening;
- refused alcohol service but allowed to remain elsewhere;
- backed off from a particular game;
- issued a formal property trespass warning;
- enrolled in self-exclusion;
- listed on a regulator’s exclusion list;
- arrested or removed by law enforcement;
- restricted by management pending review.
Those actions are not interchangeable. The word “86’d” is useful in conversation only if everyone then records what really happened.
The first question is: 86’d from what?
A casino resort can contain gaming areas, hotel space, restaurants, bars, entertainment venues, retail areas, parking, and leased businesses. A restriction may apply to one activity, one venue, all gaming, or the entire property.
For example, “no more blackjack tonight” is not the same instruction as “leave the premises and do not return.” A security report should identify the exact scope rather than rely on slang.
The same principle applies to time. A cooling-off removal for the evening is different from an indefinite property trespass. If a restriction has a review date or reinstatement process, that should be captured.
Backoff, removal, trespass, and exclusion are different tools
| Action | Typical meaning | What staff need to record |
|---|---|---|
| Backoff | Stop a patron from playing a game or using a particular betting approach | Game/activity restricted, time, decision-maker, instructions |
| Removal | Patron must leave now | Reason, scope, escort, condition for return if known |
| Trespass warning | Patron is formally told not to enter or remain on defined property | Exact notice, property scope, date/time, issuing authority, acknowledgement/refusal |
| Self-exclusion | Patron voluntarily enters a formal exclusion program | Program status, effective period, required system actions |
| Regulator exclusion | Government gaming authority places person on an official exclusion list | Jurisdiction, effective status, regulator record, required response |
The glossary pages for Trespass, Trespass Warning, Back-Off, and Self-Exclusion explain those statuses individually.
Why precise language matters after the incident
A shift may understand what happened while the event is fresh. The next shift will only know what the record says.
“86’d for causing trouble” creates immediate questions:
- What behavior occurred?
- Who made the decision?
- Was the patron told to leave gaming only or the entire property?
- Was a formal no-return notice given?
- Was law enforcement involved?
- Is there an expiration or review condition?
- Were surveillance and player-account systems updated?
- Is the person subject to a separate regulatory or self-exclusion status?
A report that answers those questions is operationally useful. Slang is not.
A clean incident record separates fact from interpretation
Suppose a patron argues with a dealer after a disputed hand, raises his voice, refuses a supervisor’s instruction to step away from the table, and is escorted to the exit.
A weak report says:
Patron became aggressive and was 86’d.
A stronger record states the observable sequence: what was said or done, which instruction was given, whether the patron complied, who authorized removal, what notice was communicated, and where the escort ended.
The second version reduces later disagreement because it records actions rather than labels. It also allows management to decide whether the response was proportionate and whether any follow-up is required.
Property action is not the same as a regulator exclusion
Casinos sometimes use “86’d” as though it means a person has been placed in an official government exclusion book. That is inaccurate.
A property can make its own management or trespass decision under applicable law and policy. A regulator exclusion is a separate governmental status created under that jurisdiction’s legal process. Nevada, for example, maintains a formal regulator exclusion process through the Gaming Control Board.
A person barred by one casino is therefore not automatically on a regulator’s exclusion list, and a regulator-excluded person is not merely the subject of an ordinary customer-service decision.
The Excluded Person entry covers that distinction in more detail.
Self-exclusion requires its own handling
Self-exclusion is also not just another form of “86.” It is normally a formal responsible-gambling process with defined enrollment, duration, reinstatement, account, marketing, and entry consequences under the applicable program.
If a self-excluded patron is identified, employees should follow the approved self-exclusion procedure rather than improvising a normal trespass response. The two statuses can overlap in some circumstances, but one does not erase the requirements of the other.
This is why databases should use explicit status fields rather than one broad “banned” checkbox whenever the operating model supports more than one restriction type.
Temporary removal should not silently become permanent
A supervisor may decide that an intoxicated, disruptive, or highly emotional patron should leave for the night. If the intention is temporary, the record should not accidentally turn that event into an indefinite no-return instruction.
The opposite problem also occurs: staff give a clear permanent property instruction, but the report is written as though the person was merely escorted out after a disagreement.
Both errors create problems at the next encounter. Security may either admit someone who should not return or confront someone whose prior removal was never meant to be permanent.
A useful status therefore needs at least:
Scope + Authority + Effective time + Duration/review + Notice givenIdentity quality matters
A restriction is only as useful as the identity attached to it. Similar names, spelling variations, nicknames, old addresses, and missing dates of birth can create false matches or missed matches.
Casinos should follow their approved privacy, security, and identification procedures when recording restriction data. The objective is not to collect unlimited personal information. It is to make the record accurate enough for the authorized purpose and to protect it appropriately.
When staff are uncertain whether a returning person matches a prior record, escalation is safer than pretending certainty from a resemblance or partial name match.
Communication across departments prevents mixed messages
An 86-related decision can involve security, surveillance, table games, slots, cage, hotel, hosts, legal, compliance, and IT. The necessary distribution depends on the scope of the restriction.
A high-value patron creates a common test. Commercial importance does not make an active safety, trespass, self-exclusion, or regulatory status disappear. Hosts need enough information to avoid inviting or comping a person whose current status prevents the activity.
At the same time, restriction information should not be broadcast casually. Access should match operational need and privacy requirements.
Reinstatement needs an owner
Some restrictions are reviewable. If a patron can request reinstatement, the casino should know who can approve it and how the decision is documented.
A frontline dealer, host, or cashier should not be expected to reverse a prior formal status because the patron says “management already cleared me.” The system should show the current status or provide a clear escalation route to someone with authority.
This also protects the patron. A documented reinstatement avoids repeated confrontations caused by stale records.
A regulator list is a separate official status
For a concrete jurisdictional example, the Nevada Gaming Control Board publishes an official Excluded Persons and Most Wanted area. That type of regulator-maintained status is different from a casino manager deciding that a patron should leave one property. Staff should follow the legal and operational process attached to the status that actually applies.
What staff should say instead of “86’d” in a formal record
Use the exact action:
- “Removed from the gaming floor for the remainder of the day.”
- “Management backoff from blackjack; other gaming not addressed.”
- “Issued property trespass notice covering the casino and hotel.”
- “Self-exclusion status confirmed; approved procedure followed.”
- “Regulator exclusion match escalated and confirmed.”
The wording should reflect what actually occurred, not a template selected because it sounds official.
The operational test
When a supervisor reads the incident tomorrow, can they answer these questions without calling the original shift?
- Who was involved?
- What observable behavior or triggering status mattered?
- What exact restriction was imposed?
- Who had authority to impose it?
- What notice was given?
- What departments or systems were updated?
- What happens if the person returns?
- Is there a review or reinstatement route?
If the record answers those questions, the casino no longer depends on the slang.
“86’d” remains part of casino language, but operationally the safest meaning is: stop using the shorthand and identify the actual status. For decision-making detail, continue with Patron Trespass and Backoff Decisions and the dedicated trespass and exclusion glossary entries.