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
Surveillance Review Request Intake
Controlled surveillance intake with authorization, bounded scope, privacy restrictions, source preservation, answerable review questions, deadlines, ownership, and a management-ready assignment brief.
Workflow demonstrationRequest and intake workflowReady 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: Surveillance Review Request Intake · Authorized request intake
Incident context
A broad employee-review request arrives with no bounded time window or decision question
A department manager reports a recurring chip-inventory concern and asks surveillance to review a dealer's activity from the last several weeks. The request includes hearsay from two supervisors, no incident reference, no exact tables or dates, and no explanation of who authorized the personal-data review. Relevant footage has different retention periods, table paperwork may identify the operational window, and an unrestricted search would consume substantial review time while exposing unrelated staff and guests.
Surveillance cannot responsibly start from a vague instruction to watch someone. The request must be converted into an authorized, proportionate, time-bounded review with preserved sources, explicit exclusions, answerable questions, delivery expectations, and privacy restrictions before footage is opened or exported.
Who is authorized to request the review, what operational decision will the result support, which dates, tables, transactions, people, and source types are genuinely relevant, what must be preserved now, what is explicitly out of scope, and how will the authorized result be delivered?
The workflow produces an intake brief containing request authority, purpose, priority, review window, included scope, exclusions, known and unverified information, privacy restrictions, requested sources, preservation status, review questions, expected deliverables, owners, deadlines, notifications, authorized recipients, and an accept, clarify, defer, or decline decision.
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.
Request identity and authorization basis
Captures the request reference, requesting department, named requestor, authorizing manager or function, policy basis, request type, priority, and the operational decision the review is expected to support.
Bounded time, place, and activity scope
Defines the exact review start and end, table or area, transaction or event types, included roles, relevant operational records, and any threshold that limits unnecessary searching.
Explicit exclusions and privacy restrictions
States what surveillance must not review, which unrelated people or activities remain outside scope, what identities require protection, and who may receive or discuss the result.
Known facts and reported information
Separates confirmed source records from allegations, impressions, anonymous reports, supervisor recollections, and assumptions so intake wording does not predetermine the review conclusion.
Source, availability, and preservation register
Lists footage, system logs, table documents, access records, statements, and other requested sources with relevant period, custodian, availability, retention deadline, preservation status, and due action.
Review questions, output, and handoff
Turns the purpose into answerable questions, defines the expected format, authorized recipients, review owner, completion target, update cadence, escalation route, and intake disposition.
A suspected chip discrepancy is narrowed to one baccarat table and twelve minutes
- The original request asks for a review of a dealer's recent shifts, but table inventory records identify one unexplained $5,000 difference at baccarat table B-04 between 23:08 and 23:20 on July 22.
- The Table Games Manager confirms the operational decision is whether the table inventory movement can be reconstructed and whether a procedure follow-up is required, not whether the employee committed misconduct.
- Cameras B04-1 and B04-3, the fill-and-credit log, the table close sheet, and the supervisor shift report are identified as relevant; unrelated break-room, entrance, and previous-shift footage are explicitly excluded.
- The camera sources are preserved before their retention deadline, the result is restricted to the Surveillance Manager and Table Games Manager, and the intake is accepted with two answerable questions and a noon update target.
The generated intake brief replaces the multi-week personal review with a twelve-minute transaction-reconstruction scope. It records authority, the known inventory difference, unverified concerns, precise source list, exclusions, preservation actions, privacy limits, two review questions, assigned reviewer, completion target, authorized delivery format, and the condition under which any scope expansion would require new approval.
The Surveillance Manager accepts the bounded operational review and declines the unrestricted employee-history request. Any later disciplinary inquiry, expanded date range, additional personal-data source, or behavioral assessment requires separate authorization and must be supported by the first review's evidence rather than the original allegation alone.
Surveillance Review Request Intake isolates one specific operating decision
This page is built around the exact failure, evidence standard, approval boundary, and implementation conditions that make Surveillance Review Request Intake different from the other workflows in the library.
Where an incident record becomes unreliable
Surveillance cannot responsibly start from a vague instruction to watch someone. The request must be converted into an authorized, proportionate, time-bounded review with preserved sources, explicit exclusions, answerable questions, delivery expectations, and privacy restrictions before footage is opened or exported.
Why chronology, source, and uncertainty must stay separate
A vague request can waste review capacity, miss retention deadlines, expose unrelated people, invite confirmation bias, and produce an answer that does not support the manager's actual decision. This intake workflow forces authority, purpose, scope, exclusions, source preservation, answerable questions, expected output, and distribution to be agreed before review starts, while still allowing urgent preservation to occur immediately when delay could destroy evidence.
The review or escalation decision this record supports
Who is authorized to request the review, what operational decision will the result support, which dates, tables, transactions, people, and source types are genuinely relevant, what must be preserved now, what is explicitly out of scope, and how will the authorized result be delivered?
The workflow produces an intake brief containing request authority, purpose, priority, review window, included scope, exclusions, known and unverified information, privacy restrictions, requested sources, preservation status, review questions, expected deliverables, owners, deadlines, notifications, authorized recipients, and an accept, clarify, defer, or decline decision.What must remain attributable and verifiable
- Request identity and authorization basis
- Captures the request reference, requesting department, named requestor, authorizing manager or function, policy basis, request type, priority, and the operational decision the review is expected to support.
- Bounded time, place, and activity scope
- Defines the exact review start and end, table or area, transaction or event types, included roles, relevant operational records, and any threshold that limits unnecessary searching.
- Explicit exclusions and privacy restrictions
- States what surveillance must not review, which unrelated people or activities remain outside scope, what identities require protection, and who may receive or discuss the result.
- Known facts and reported information
- Separates confirmed source records from allegations, impressions, anonymous reports, supervisor recollections, and assumptions so intake wording does not predetermine the review conclusion.
What must be defined before the workflow handles real incidents
- Define which departments and roles may request each review type, who authorizes personal-data or restricted-evidence access, and which emergency preservation actions may occur before full intake approval.
- Create mandatory scope fields for time window, location, operational event, relevant roles, included sources, exclusions, purpose, decision required, and maximum permitted expansion.
- Standardize neutral intake language that separates known facts, reported information, allegation, hypothesis, and requested test without importing guilt or intent into the assignment.
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 expand scope beyond authorization, collect unnecessary personal data, or start a review without a valid requester and purpose.
- 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.
- Beginning an unrestricted person-focused review without a defined operational purpose or authority can create disproportionate surveillance and privacy exposure.
- Using an allegation as the review question can bias the search toward confirming wrongdoing rather than testing observable events and alternative explanations.
- Delaying source identification until after clarification can allow relevant footage or logs to expire even when the final review scope is appropriate.
- Omitting explicit exclusions can cause reviewers to expand into unrelated dates, locations, people, or conduct because the request boundary is not visible.
- Accepting a deadline without source availability, workload, urgency, and output complexity can create rushed review, missed evidence, or false expectations for management.
- Delivering results to the original requestor without confirming authorization and distribution restrictions can expose sensitive evidence or personnel information.
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, Intake / Request prepared from approved inputs, with source references, open questions, named ownership, limitations, and a visible management review point.
Review NotesIntake / Request
The decision management must make
Who is authorized to request the review, what operational decision will the result support, which dates, tables, transactions, people, and source types are genuinely relevant, what must be preserved now, what is explicitly out of scope, and how will the authorized result be delivered?
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
- Beginning an unrestricted person-focused review without a defined operational purpose or authority can create disproportionate surveillance and privacy exposure.
- Using an allegation as the review question can bias the search toward confirming wrongdoing rather than testing observable events and alternative explanations.
- Delaying source identification until after clarification can allow relevant footage or logs to expire even when the final review scope is appropriate.
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 generated intake brief replaces the multi-week personal review with a twelve-minute transaction-reconstruction scope. It records authority, the known inventory difference, unverified concerns, precise source list, exclusions, preservation actions, privacy limits, two review questions, assigned reviewer, completion target, authorized delivery format, and the condition under which any scope expansion would require new approval.
- 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
Receive and authorize a bounded surveillance review request with scope, privacy, sources, ownership, and deadline controls.
Controlled surveillance intake with authorization, bounded scope, privacy restrictions, source preservation, answerable review questions, deadlines, ownership, and a management-ready assignment brief.
Define evidence handling and escalation before use
- Define which departments and roles may request each review type, who authorizes personal-data or restricted-evidence access, and which emergency preservation actions may occur before full intake approval.
- Create mandatory scope fields for time window, location, operational event, relevant roles, included sources, exclusions, purpose, decision required, and maximum permitted expansion.
- Standardize neutral intake language that separates known facts, reported information, allegation, hypothesis, and requested test without importing guilt or intent into the assignment.
- Map source custodians, retention periods, preservation methods, access classifications, delivery formats, and notification duties so intake can trigger timely evidence protection.
- Train reviewers to convert broad requests into answerable questions such as whether an event occurred, whether a sequence can be reconstructed, or whether a specified control was followed.
- Pilot urgent, routine, incomplete, unauthorized, overbroad, and privacy-sensitive requests and confirm that the workflow supports accept, clarify, defer, partially accept, and decline outcomes.
How to judge whether case records become more defensible
- Every accepted request has documented authority, operational purpose, bounded scope, explicit exclusions, answerable questions, source register, owner, deadline, and authorized recipients.
- Urgent evidence is preserved before retention expiry without automatically authorizing a broader review than management has approved.
- Reviewers spend less time searching irrelevant footage or clarifying vague assignments, and scope changes are separately recorded and approved.
- Known facts and allegations remain visibly distinct, reducing confirmation bias and preventing intake wording from becoming an unsupported conclusion in later reports.
- Requests that lack authority, proportionality, answerable purpose, or necessary source availability are clarified, narrowed, deferred, or declined with a documented reason.
- Completed outputs answer the agreed questions in the approved format and reach only authorized recipients within the promised update or completion window.
Review the evidence workflow
Check what is known, unknown, and authorized before drawing a conclusion.
Receive and authorize a bounded surveillance review request with scope, privacy, sources, ownership, and deadline controls.