Behaviour Report
The Casino Behaviour Report compares dealers and tables against their peers, and normalises for how busy each was.
What it does
Raw totals track activity. A dealer who worked more hands will have more of everything, which tells you nothing.
The report is built to surface rates that differ from colleagues' — which is what "unusual" has to mean before it means anything at all.
Running one
Choose the period and the population. A meaningful comparison needs:
- Enough time. A shift is noise; a month gives rates worth reading.
- A comparable group. Compare blackjack dealers with blackjack dealers.
- Enough activity per person. Somebody who worked two shifts has no rate.
Reading it
Look for people or tables that stand out on several measures rather than one. A single high measure has ordinary explanations — a new dealer, a difficult table, a period with an unusual crowd. A consistent pattern across measures does not.
The report identifies figures that differ from their peers'. It does not establish why, and difference is not misconduct.
Take an outlier to the video and the underlying ratings before forming any view. Used properly, the report clears people at least as often as it flags them — an anomaly with an obvious innocent explanation, established quickly, is a good outcome.
From the report to the evidence
Drill into a person or table to see the activity behind the figures, then the ratings or rounds, then the footage. The report tells you where to look; the recording tells you what happened.
Doing it fairly
- Apply the same period and population to everybody. Comparing one person's worst month against everyone else's year manufactures an outlier.
- Record what you concluded, including when the conclusion was that there was nothing in it — on a Workspace node or in a case.
Elsewhere
The Point of Sale module has its own Behaviour Report, applying the same idea to register staff.
What is recorded
Generating the report is audited — Behavior Report (type 101), written server-side. See the Audit Catalog.