A working browser demonstration of a structured operational workflow. It is not presented as a deployed casino system.
Product maturity
Interactive workflow demonstrationKnow exactly what this page represents.
A workflow-fit review, customization scope, implementation plan, and a decision on whether the workflow should remain a browser tool or become a controlled production application.
Evidence documentation workflow
Game Protection Evidence Review
Source-linked observations, procedure comparisons, risk significance, alternative hypotheses, evidence limitations, temporary controls, ownership, and cautious game-integrity conclusions.
Workflow demonstrationReview and assessment workspaceReady for workflow-fit reviewHow demonstrations are controlled →
Five connected Surveillance control workflows
Compare Surveillance controls →Surveillance Review, Protection & Coverage Control Suite
Current Surveillance control workflow: Game Protection Evidence Review · Game-protection evidence review
Incident context
A baccarat table shows repeated late chip movement during high-value play
Over two evening shifts, supervisors report several occasions when chips appeared to move near the betting cut-off at a high-limit baccarat table. The table has fast play, guest hand-squeeze procedures, frequent supervisor interaction, and one camera angle that compresses the betting area. Drop and win are unusual for the period, but the sample is small and no single transaction has yet been verified as past-posting or collusion. Management needs a game-protection review that tests procedure performance and alternative explanations rather than beginning with a misconduct conclusion.
A pattern concern has been raised from operating observations and results, but the available information mixes verified events, impressions, statistical noise, camera limitations, and assumptions about intent. Surveillance must compare actual sequences with approved controls, preserve relevant evidence, and identify proportionate safeguards while review continues.
Which events are directly observable, which approved controls applied at each moment, where did execution differ, what legitimate alternatives could explain the pattern, how significant is the exposure, what evidence supports or weakens each hypothesis, and what temporary or corrective action is justified now?
The workflow produces source-linked observations, procedure comparisons, risk significance, immediate actions, competing hypotheses, supporting and contrary evidence, confidence levels, evidence preservation, limitations, verified facts, open questions, temporary safeguards, assigned follow-up, cautious conclusions, and the exact management support or decision required.
Case evidence
Preserve chronology and source before drafting findings
A defensible record identifies what was observed, where it came from, what remains unavailable, and which statements still require verification.
- 01
Authorized review request or incident reference
- 02
Time-ordered observations and source references
- 03
Evidence availability, restrictions, and known gaps
- 04
Chronology, attributable observations, evidence status, and access restrictions
Case record
What the incident file must distinguish
These fields protect the difference between evidence, interpretation, allegation, decision, and follow-up action.
Review trigger, scope, and approved standard
Records the operational trigger, game, table, review window, lead and independent reviewers, included events, exclusions, and the exact procedure or game-protection standard used for comparison.
Time-sequenced observation and source
Captures each observable action with synchronized time, camera or record reference, verification state, involved role, and enough sequence detail to distinguish before, during, and after the betting cut-off.
Expected control and observed deviation
Links the event to the required dealer, supervisor, layout, chip, card, or communication control and states whether execution met, partially met, or differed from the approved standard.
Risk significance and immediate safeguard
Grades the plausible financial, integrity, safety, or procedural exposure without equating significance with guilt and records any temporary table, staffing, monitoring, or procedural safeguard.
Competing hypothesis and confidence
Tests suspected and legitimate explanations using supporting evidence, evidence against, missing sources, alternative causes, confidence level, next test, and an owner for further examination.
Conclusion, action, and management authority
Separates verified findings from unresolved questions, records limitations, corrective actions, decision support required, classification, next update, and the authority permitted to make operational or personnel decisions.
Three apparent late-bet movements do not support one simple conclusion
- Review identifies three hands where a guest's fingers contact chips after the dealer begins the no-more-bets call, but only one angle clearly shows whether the wager position changed.
- In the clearest event, the chips move approximately two centimeters within the same betting box while the supervisor is answering another guest and the dealer continues without a visible lock or verbal correction.
- The second and third events are partly obscured by hand-squeeze activity and camera compression; table records show no corresponding payout anomaly, and the unusual two-shift hold is not treated as proof of manipulation.
- The applicable procedure requires an unambiguous betting close and supervisor intervention when chip position changes are observed, so enhanced live monitoring, a dealer reminder, and a temporary supervisor-position adjustment are assigned while a wider sample is reviewed.
The review brief verifies one control-execution gap, records two unresolved observations, identifies camera and sample limitations, compares each sequence with the approved betting-close procedure, tests accidental chip contact, guest habit, weak table control, and deliberate movement as separate hypotheses, and recommends immediate procedure reinforcement plus targeted monitoring rather than an accusation of cheating or collusion.
The Table Games Manager approves the temporary supervisor-position change and dealer procedure briefing. The Surveillance Manager approves a bounded extension of the review sample. No guest exclusion, staff discipline, loss attribution, or integrity finding is authorized unless later evidence reaches the required standard and the responsible management function makes that decision.
Game Protection Evidence Review isolates one specific operating decision
This page is built around the exact failure, evidence standard, approval boundary, and implementation conditions that make Game Protection Evidence Review different from the other workflows in the library.
Where an incident record becomes unreliable
A pattern concern has been raised from operating observations and results, but the available information mixes verified events, impressions, statistical noise, camera limitations, and assumptions about intent. Surveillance must compare actual sequences with approved controls, preserve relevant evidence, and identify proportionate safeguards while review continues.
Why chronology, source, and uncertainty must stay separate
Game-protection work is strongest when it reconstructs observable events, compares them with current controls, tests competing explanations, states evidence limitations, and separates exposure from intent. This workflow helps surveillance identify real procedural weaknesses and proportionate safeguards while preventing financial results, player skill, supervisor suspicion, or incomplete footage from becoming an unsupported misconduct conclusion.
The review or escalation decision this record supports
Which events are directly observable, which approved controls applied at each moment, where did execution differ, what legitimate alternatives could explain the pattern, how significant is the exposure, what evidence supports or weakens each hypothesis, and what temporary or corrective action is justified now?
The workflow produces source-linked observations, procedure comparisons, risk significance, immediate actions, competing hypotheses, supporting and contrary evidence, confidence levels, evidence preservation, limitations, verified facts, open questions, temporary safeguards, assigned follow-up, cautious conclusions, and the exact management support or decision required.What must remain attributable and verifiable
- Review trigger, scope, and approved standard
- Records the operational trigger, game, table, review window, lead and independent reviewers, included events, exclusions, and the exact procedure or game-protection standard used for comparison.
- Time-sequenced observation and source
- Captures each observable action with synchronized time, camera or record reference, verification state, involved role, and enough sequence detail to distinguish before, during, and after the betting cut-off.
- Expected control and observed deviation
- Links the event to the required dealer, supervisor, layout, chip, card, or communication control and states whether execution met, partially met, or differed from the approved standard.
- Risk significance and immediate safeguard
- Grades the plausible financial, integrity, safety, or procedural exposure without equating significance with guilt and records any temporary table, staffing, monitoring, or procedural safeguard.
What must be defined before the workflow handles real incidents
- Map each supported game and rule setting to the current approved procedures, table controls, camera objectives, system records, and responsible operational reviewers.
- Define observation categories, verification states, risk significance, confidence levels, hypothesis dispositions, evidence standards, and wording prohibited without formal authority.
- Require synchronized source references and event sequencing so reviewers can distinguish chip contact, wager movement, betting closure, dealer response, supervisor position, result, and payout handling.
What management must decide for this workflow
Only the controls that are specific to this application are shown here. The shared portfolio standard is documented once in the methodology.
Approved data, accountable review, management authority, and evidence-based claims apply across the portfolio.
How demonstrations are controlled →- Responsible reviewer
- Surveillance Manager or authorized management recipient
- Decision before use
- Surveillance Manager or authorized management recipient approves the prepared review Notes and assigns any follow-up before it is shared or used.
- Not for
- Do not use this to conclude cheating, collusion, or intent from patterns alone or bypass approved game-protection procedures.
- Application-specific limits
- It does not determine intent, guilt, disciplinary action, or a final incident conclusion.
6 workflow-specific risks to review
These are practical failure risks for this workflow, not repeated portfolio-wide disclaimers.
- Starting with a named suspect or preferred theory can cause reviewers to select confirming clips while ignoring contrary events, ordinary play, or control weaknesses.
- Using table hold or short-period financial performance as direct evidence of manipulation can confuse statistical variation with observable game-protection facts.
- Comparing conduct with an outdated, informal, or incorrectly configured procedure can label permitted game practice as a control breach.
- Recording only evidence that supports the concern can hide alternative explanations, camera limitations, supervisor workload, guest habits, or inconsistent procedure execution.
- Applying an intrusive temporary control without a stated objective, owner, review point, and proportionality assessment can create guest-service or privacy harm without improving protection.
- Allowing a cautious review conclusion to be rewritten as cheating, collusion, theft, or dishonesty in downstream personnel or exclusion records can exceed the evidence and review authority.
Who compiles the factual record
- Surveillance supervisor or assigned reviewer
- Authorized incident or evidence custodian
The preparer should separate direct observation, recorded evidence, statements, assumptions, missing coverage, and later management conclusions.
Who determines the authorized disposition
Surveillance Manager or authorized management recipient
Final approval requirements are consolidated in the Operational boundaries section below.
A management-ready output—not just a completed form
The working app organizes the result so management can understand the position, verify the evidence, choose an action, record approval, and assign the next review without rewriting the workflow from scratch.
What the completed workflow should make clear
Review Notes prepared from approved inputs, with source references, open questions, named ownership, limitations, and a visible management review point.
Review Notes
The decision management must make
Which events are directly observable, which approved controls applied at each moment, where did execution differ, what legitimate alternatives could explain the pattern, how significant is the exposure, what evidence supports or weakens each hypothesis, and what temporary or corrective action is justified now?
The app prepares the decision; it does not approve or execute it.Records that should support the recommendation
- Authorized review request or incident reference
- Time-ordered observations and source references
- Evidence availability, restrictions, and known gaps
- Chronology, attributable observations, evidence status, and access restrictions
What management still needs to question
- Starting with a named suspect or preferred theory can cause reviewers to select confirming clips while ignoring contrary events, ordinary play, or control weaknesses.
- Using table hold or short-period financial performance as direct evidence of manipulation can confuse statistical variation with observable game-protection facts.
- Comparing conduct with an outdated, informal, or incorrectly configured procedure can label permitted game practice as a control breach.
Surveillance Manager or authorized management recipient
This reviewer confirms the decision record. The complete approval gate is stated once in Operational boundaries.
Close the action with ownership and a checkpoint
Prepared by: Surveillance supervisor or assigned reviewer · Authorized incident or evidence custodian
Next checkpoint: The reviewer sets the follow-up date, confirms the responsible person, and records whether the matter is closed, monitored, returned for correction, or escalated.
What should remain after the meeting
- Operating position
- The review brief verifies one control-execution gap, records two unresolved observations, identifies camera and sample limitations, compares each sequence with the approved betting-close procedure, tests accidental chip contact, guest habit, weak table control, and deliberate movement as separate hypotheses, and recommends immediate procedure reinforcement plus targeted monitoring rather than an accusation of cheating or collusion.
- Decision owner
- Surveillance Manager or authorized management recipient
- Status
- Draft, reviewed, approved, returned for correction, monitored, or closed
- Required record
- Evidence references, approved action, responsible person, approval status, follow-up date, and remaining uncertainty
Case purpose
The event this record helps document without overclaiming
Assess game-protection observations against procedures, evidence, alternative hypotheses, risk significance, and temporary controls.
Source-linked observations, procedure comparisons, risk significance, alternative hypotheses, evidence limitations, temporary controls, ownership, and cautious game-integrity conclusions.
Define evidence handling and escalation before use
- Map each supported game and rule setting to the current approved procedures, table controls, camera objectives, system records, and responsible operational reviewers.
- Define observation categories, verification states, risk significance, confidence levels, hypothesis dispositions, evidence standards, and wording prohibited without formal authority.
- Require synchronized source references and event sequencing so reviewers can distinguish chip contact, wager movement, betting closure, dealer response, supervisor position, result, and payout handling.
- Build independent-review triggers for high-value exposure, repeated patterns, staff or guest allegations, material camera limitations, and conclusions that could affect employment or exclusion decisions.
- Test the workflow with deliberate violations, accidental movement, unclear footage, legitimate advantage play, procedure drift, system-clock mismatch, and unusual but statistically plausible results.
- Agree temporary-control approval, communication, expiry, effectiveness testing, and removal rules with Table Games, Surveillance, Security, Compliance, and guest-service leadership.
How to judge whether case records become more defensible
- Every material observation links to a source, time sequence, verification state, approved control, observed deviation, risk significance, and any immediate action taken.
- Reviewers document evidence supporting and weakening each material hypothesis, and unresolved alternatives remain visible in the management output.
- Financial results and player characteristics provide context but do not substitute for direct evidence of an event, control gap, or supported pattern.
- Temporary safeguards are proportionate, authorized, time-bounded, owned, communicated to necessary roles, and assessed for operational effectiveness and unintended impact.
- Independent reviewers can reproduce the core factual sequence and understand why the stated confidence and conclusion do not exceed the available sources.
- The pilot identifies actionable procedure, supervision, coverage, or training improvements without producing unsupported guest or staff misconduct labels.
Review the evidence workflow
Check what is known, unknown, and authorized before drawing a conclusion.
Assess game-protection observations against procedures, evidence, alternative hypotheses, risk significance, and temporary controls.