Surveillance performance metrics measure whether the casino surveillance function is available, accurate, timely, useful, and properly documented. Good metrics include review turnaround time, camera availability, report correction rate, escalation accuracy, unresolved review rate, and request volume by department. Bad metrics reward noise, suspicion, or “catch counts” without context.
Quick Facts
- Surveillance should not be judged only by how many incidents it finds.
- A useful metric improves control decisions; a vanity metric only fills a dashboard.
- Camera availability matters more than camera count.
- Review speed must be balanced against accuracy.
- Report quality is a measurable control issue.
- Escalation accuracy helps separate useful alerts from room chatter.
- Metrics should support independence, not pressure operators into false certainty.
Plain Talk
Surveillance is hard to measure because much of the value is prevention, verification, and quiet support.
A table dispute resolved correctly may save trust. A camera issue fixed before a major incident may prevent a disaster. A clean report may protect the property months later. None of that looks like a dramatic “catch.”
That is why surveillance metrics must be chosen carefully. The wrong numbers create bad behavior.
If management rewards only the number of suspicious reports, operators may start seeing suspicion everywhere. If management rewards only fast review time, operators may rush unclear conclusions. If management counts cameras but not working priority views, the property may feel covered while important areas are weak.
This page focuses on practical manager-level metrics. For department structure, read Surveillance Department Overview. For the leadership role, read Surveillance Manager Role.
How It Works
Surveillance metrics should answer five management questions.
| Management question | Useful metric | Bad version of the metric | Better interpretation |
|---|---|---|---|
| Can we see what we must see? | Priority camera availability | Total camera count | Coverage quality matters more than quantity |
| Are reviews handled in time? | Review turnaround time | Fastest single review | Use median or category-based time |
| Are reports usable? | Report correction rate | Number of reports written | More reports do not mean better control |
| Are alerts meaningful? | Escalation accuracy | Number of escalations | False alarms waste attention |
| Are requests balanced? | Requests by department | Total requests only | Shows who relies on surveillance and why |
Metrics should be discussed with examples. A number without context can punish the wrong person.
A slow review may be slow because the request was vague. A low incident count may mean prevention is working. A high report count may mean the floor is sloppy, not that surveillance is excellent.
Back of House Example
A casino notices that surveillance review requests from table games have doubled during weekends.
A lazy interpretation says: “Surveillance is getting slower.”
A better review asks:
- Are the requests coming from one pit or all pits?
- Are they tied to disputes, late bets, fills, dealer errors, or player complaints?
- Are supervisors asking for review because they lack confidence?
- Are camera angles creating unclear answers?
- Are new dealers assigned to high-pressure tables?
The metric points to the question. It does not answer it alone.
After review, management finds that a new floor supervisor is sending every minor complaint to surveillance instead of making routine floor decisions. The fix is coaching, not buying more cameras.
From the Casino Side:
The casino wants surveillance to support control without becoming a statistics theater.
A dashboard can be useful. It can also become nonsense.
If the surveillance manager is pressured to show “more results,” the department may overreport weak signals. If the department is punished for unclear reviews, operators may pretend certainty. If camera downtime is hidden because nobody wants a maintenance discussion, the casino discovers the problem only after a dispute.
Regulatory standards remind management that surveillance is part of required control, not a decorative system. Nevada’s surveillance standards list required coverage areas and record expectations. Nevada’s Minimum Internal Control Standards show the broader control environment. Federal tribal gaming rules in 25 CFR Part 542 include definitions and control concepts relevant to surveillance operations.
Common Mistakes
- Measuring catches instead of control value.
- Counting all cameras as if every view has equal importance.
- Treating a fast but weak review as good performance.
- Ignoring report corrections because they are embarrassing.
- Letting department politics influence escalation statistics.
- Comparing shifts without accounting for volume, staffing, and floor activity.
- Building a dashboard nobody uses to improve decisions.
Hard Truth
If surveillance metrics make operators chase numbers instead of facts, the dashboard has become part of the risk.
FAQ
What are casino surveillance performance metrics?
They are measurements used to evaluate surveillance workload, coverage, review timeliness, report quality, escalation usefulness, and system reliability.
Should surveillance be measured by how many cheaters it catches?
No. That is too narrow and can distort behavior. Surveillance also prevents errors, verifies disputes, supports compliance, protects staff, and documents incidents.
What is camera availability rate?
It is the percentage of required or priority camera views that are working and usable during a measured period.
What is review turnaround time?
It measures how long surveillance takes to complete review requests. It should be interpreted by request type, not as one blended number.
What is report correction rate?
It is the share of surveillance reports returned for revision because they were incomplete, unclear, opinion-heavy, or missing key details.
Can surveillance metrics hurt independence?
Yes. If metrics pressure operators to confirm suspicions or avoid unclear answers, they damage independence and accuracy.
Who should review surveillance metrics?
The surveillance manager should review them first. Senior management, compliance, audit, or risk leadership may review higher-level summaries depending on property structure.
Deeper Insight
Surveillance metrics should be built around behavior you want more of.
You want operators to be accurate, observant, calm, timely, discreet, and honest about uncertainty. You want reports that can be read months later. You want required views working before a big dispute happens. You want escalation to be meaningful.
You do not want operators competing to create suspicion. You do not want every unclear review turned into a confident story. You do not want floor supervisors dumping their judgment onto surveillance because “the camera will decide.”
A useful surveillance dashboard might include:
| Metric | Formula | What it tells management | What to watch out for |
|---|---|---|---|
| Review Load | Review Requests / Surveillance Hours | Demand placed on the room | High load may reflect floor weakness |
| Median Review Time | Middle review completion time | Typical response speed | Average can be distorted by long cases |
| Report Correction Rate | Corrected Reports / Reports Submitted | Writing quality | Low rate may mean poor review, not perfect reports |
| Priority Camera Availability | Working Priority Views / Required Priority Views | Usable coverage | Do not hide chronic weak angles |
| Escalation Accuracy | Valid Escalations / Total Escalations | Signal quality | Some valid concerns will remain inconclusive |
| Unclear Review Rate | Unclear Reviews / Total Reviews | Limits in coverage or request quality | High rate needs root-cause review |
Metrics are not a substitute for leadership. They are a way to make leadership less blind.
Formula / Calculation
Review Load = Review Requests / Surveillance Hours
Priority Camera Availability = Working Priority Camera Views / Required Priority Camera Views
Report Correction Rate = Reports Returned for Correction / Reports Submitted
Escalation Accuracy = Valid Escalations / Total Escalations
Formula Explanation in Plain English
Review load shows whether the room is being asked to do too much for the hours staffed. Priority camera availability tells whether key views are actually usable. Report correction rate shows whether reports need better writing or review. Escalation accuracy shows whether the department is raising useful alarms instead of creating noise.
The formulas are simple. The interpretation is where the manager earns the paycheck.
Related Reading
Start from Back of House and Surveillance Department Overview, then continue to Surveillance Manager Role and Surveillance Report Writing. Metrics also connect to Exception Reporting, Incident Reporting, and Internal Audits in Casinos. Useful glossary pages include surveillance, drop, fill, and player rating. For player-facing context, read How do surveillance teams work?. Game examples are strongest in Blackjack, Baccarat, Craps, and Slots.