BOH 112: Incident Reporting

A casino incident report is a controlled factual record of an event that may affect people, money, gaming integrity, property, evidence, compliance, or the casino license. Its purpose is not to make the writer sound authoritative. Its purpose is to allow another qualified person to reconstruct what happened and decide what must happen next.

Incidents can include injuries, threats, disruptive behavior, missing property, payout disputes, suspected cheating, employee conduct, equipment failures, data events, cash exceptions, exclusions, intoxication concerns, or emergency response.

An incident is not the same as an exception

An incident is an event requiring factual documentation and response. An exception is a departure from an expected rule, threshold, process, or result. One event can be both.

A patron fall is an incident. A late safety inspection may be an exception. If the fall occurred in an area where the inspection was missed, the records may connect, but they should not be collapsed into one vague story.

Read Exception Reporting for the broader control process and Security Response Procedure for response coordination.

What the report must establish

A useful report answers:

• Who was involved, present, notified, or responsible?
• What was directly observed or reliably recorded?
• When did each important step occur?
• Where did the event happen?
• How did staff respond?
• What evidence was preserved?
• What decision was made, by whom, and under what authority?
• What remains open and who owns it?

It should distinguish direct observation, system record, video review, witness statement, and inference. “The guest was intoxicated” may be an unsupported conclusion. “The guest had slurred speech, stumbled twice, and was refused further alcohol by the beverage supervisor at 01:14” records observable facts.

Write the timeline before the narrative becomes memory

Casino environments are noisy and fast. Times from surveillance, access control, gaming systems, telephones, radios, and employee recollection may differ. The report should identify the source of each time.

A simple timeline can be more valuable than a long paragraph:

This format makes gaps visible. It also prevents the writer from accidentally changing the sequence while trying to tell a smooth story.

Evidence preservation is not evidence interpretation

Staff may need to preserve:

• surveillance video;
• game or machine logs;
• cage and player-account transactions;
• tickets, chips, cards, or documents;
• photographs;
• access-control records;
• radio or telephone logs;
• witness names and statements;
• damaged equipment;
• digital audit trails.

Preservation should follow policy and law. Employees should not copy sensitive footage to personal devices, conduct unauthorized searches, or alter a live system simply to “see if it works.” Chain of custody and access records matter.

Neutral language protects the investigation

Avoid labels that imply a finding before review:

• “cheater” becomes “patron whose play was referred for review”;
• “fake injury” becomes the observed behavior and medical response;
• “drunk” becomes specific signs and actions;
• “stole” becomes “item was seen being removed” unless the conclusion is established;
• “admitted guilt” becomes the person’s exact relevant statement, accurately quoted or summarized.

Neutral writing is not weak writing. It is disciplined writing.

Notifications should be role-based

Not every incident belongs in a property-wide message. Privacy, investigation integrity, and regulatory confidentiality may restrict access.

The response plan should define when to notify:

• shift or department management;
• security;
• surveillance;
• medical responders;
• compliance or AML;
• human resources;
• legal or risk management;
• information security;
• senior executives;
• law enforcement;
• the gaming regulator or another authority.

Notification does not transfer ownership automatically. The report should state who leads the next step.

Nevada’s current gaming statutes and regulations index illustrates how operational, surveillance, and control obligations sit within a wider regulatory framework. Exact reportable events and deadlines vary by jurisdiction and license condition.

A report should support action, not just storage

After containment, management may need to determine:

1. Was the immediate risk controlled?
2. Did policy work as intended?
3. Did staffing, training, design, or equipment contribute?
4. Is regulatory or insurance reporting required?
5. Is a guest or employee follow-up due?
6. Does the event reveal a repeated pattern?
7. What corrective action is proportionate?
8. How will closure be verified?

A report marked “closed” without a closure reason is not complete. Useful closure codes might distinguish no further action, coaching, repair, policy change, regulatory referral, law-enforcement referral, claim handling, or duplicate report.

Measure timeliness and quality together

A fast report can be incomplete. A perfect report filed days late can be operationally useless. Balanced measures include:

[ \text{Timely filing rate}=\frac{\text{reports filed within standard}}{\text{reports due}} ]

[ \text{First-review acceptance}=\frac{\text{reports accepted without material correction}}{\text{reports reviewed}} ]

[ \text{Open-action aging}=\text{current date}-\text{action assignment date} ]

If 92 of 100 reports were timely but only 54 were accepted without material correction, the system has a quality problem hidden by a good speed metric.

Frequent report failures

• copying conclusions from another employee without attribution;
• changing times to make the sequence look cleaner;
• omitting a manager’s decision;
• recording sensitive personal details unrelated to the event;
• failing to preserve the original evidence;
• using the report to attack an employee or guest;
• leaving the follow-up owner blank;
• treating a verbal handover as closure;
• writing from memory at the end of a long shift.

The best report is neither dramatic nor defensive. It is specific, chronological, attributable, proportionate, and useful to the next person who must make a decision.

Privacy and retention need explicit rules

Incident files may contain health details, identification, employee information, financial transactions, allegations, and video references. The property should define who can view each category, how long records are retained, where attachments are stored, and when legal hold overrides ordinary deletion.

Writers should include what is necessary for the event, not everything known about a person. A guest’s unrelated medical history, nationality, loyalty value, or previous complaints may be inappropriate unless directly relevant and lawfully used.

Templates should prompt facts, not dictate conclusions

A practical form can include:

• event category and location;
• start, discovery, response, and closure times;
• persons involved and contact status;
• observable facts;
• actions taken and authority;
• evidence references;
• notifications;
• immediate outcome;
• follow-up actions, owner, and due date;
• regulatory, insurance, or legal status;
• supervisor quality review.

Dropdowns improve consistency, but the narrative must still explain the event. Selecting “guest misconduct” does not describe what the guest did.

Quality review should sample the underlying evidence

Supervisors should compare selected reports with video, system timestamps, dispatch logs, or transaction records. The review can identify recurring problems: vague descriptions, missing decisions, late entry, incorrect times, or open actions without owners.

A monthly incident count is not enough. Ten reports may indicate ten problems, better reporting, a new classification rule, or one repeated control failure. Trend analysis should use severity, location, shift, event type, cause, and closure quality.

Incident reporting succeeds when the record changes the next decision. If the same hazard, guest-conduct issue, or handover failure repeats without corrective action, the organization is documenting risk rather than managing it.