Gaming Surveillance Incident Report
Report suspected cheating, theft, advantage play, or other irregular activity in a gaming venue with clear footage references, escalation notes, and follow-up ownership.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Casinos · Card Rooms · Sportsbooks · Hospitality And Entertainment
Overview
The Gaming Surveillance Incident Report template captures suspected cheating, advantage play, theft, tampering, or other irregular activity observed on camera or on the floor. It is designed to turn a fast-moving event into a structured record with the incident type, location, people involved, footage references, immediate action, and follow-up ownership.
Use this template when surveillance or security needs to document an event that may require review, escalation, or preservation of evidence. It works well for casino pits, slot banks, card rooms, sportsbooks, cage areas, and other gaming-adjacent spaces where timing and camera references matter. The form is especially useful when multiple teams need the same facts in a consistent format.
Do not use it for routine maintenance issues, ordinary guest service complaints, or general shift notes that do not involve a suspected incident. If the event is still unfolding, use the ongoing activity field to show whether monitoring continues, and keep the description factual rather than speculative. If you do not know the subject’s name, the template still supports a usable report through physical description, camera IDs, and time range. That makes it easier to maintain an audit trail and hand the case to the right reviewer without losing context.
Standards & compliance context
- Use data minimization by collecting only the names, account IDs, and other PII needed to identify the subject and support the investigation.
- If the report is shared with multiple departments, maintain an audit trail that shows who submitted it, who reviewed it, and what action was taken.
- When the report includes personal data, make the disclosure language clear so staff understand why the information is being collected and how it will be used.
- If your venue operates under internal security or gaming-control procedures, align the incident type, escalation path, and retention rules with those policies.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Submission Notice
This section establishes who is reporting the incident, when it was submitted, and the short summary that frames the rest of the record.
- Reporting Unit / Location
- Date and Time Observed
-
What happens after I submit?
The report will be reviewed by surveillance leadership or security management. If needed, footage will be preserved, an audit trail will be created, and follow-up may include internal investigation or escalation.
Incident Overview
This section captures what happened, where it happened, and whether the activity is still in progress so reviewers can triage quickly.
- Incident Type
- Game / Area Observed
-
Incident Description
Describe what was observed, including sequence of events, observable actions, and any immediate outcome. Avoid speculation.
- Is the activity ongoing?
People and Entities Involved
This section identifies the subject using only the details needed to support review, matching the level of certainty you actually have.
- Who was involved?
-
Known Names or Aliases
Enter only if already known from observation or records. Do not collect extra PII.
-
Physical / Role Description
Use observable descriptors such as clothing, position at the table, or role. Avoid sensitive personal attributes unless operationally necessary.
-
Associated Account / Player ID
Use only if needed for internal review.
Evidence and Footage References
This section ties the report to camera IDs, footage windows, and attachments so the event can be verified and retrieved later.
- Camera ID(s)
- Footage Time Range
- Evidence Type
-
Attachments
Upload relevant clips, images, or supporting records.
Impact and Escalation
This section records the severity, immediate response, and any law enforcement contact so the response path is clear.
- Observed Impact
- Immediate Action Taken
- Was law enforcement contacted?
-
Escalation Notes
Include who was notified, when, and any case or reference number if applicable.
Follow-Up and Review
This section assigns ownership, sets the review deadline, and captures next steps so the incident does not stall after submission.
- Recommended Follow-Up
-
Assigned To
Person or team responsible for follow-up.
- Review Deadline
- Additional Notes
How to use this template
- 1. Set up the form fields to match your venue by listing the incident types, area names, camera IDs, and escalation options your surveillance team actually uses.
- 2. Enter the submission notice first with the reporting unit, incident datetime, and a short summary so the reviewer can see what happened at a glance.
- 3. Complete the incident overview with the observed behavior, the game or area involved, and whether the activity is still ongoing.
- 4. Add the people and entities involved using known names, aliases, physical description, or account ID only when those fields are needed to identify the subject.
- 5. Attach the relevant footage references and evidence, then record the immediate action taken, any law enforcement contact, and the assigned follow-up owner with a review deadline.
Best practices
- Use a date-time picker for the incident timestamp so the record is searchable and consistent across shifts.
- Keep the incident description factual and chronological, and separate observed actions from assumptions about intent.
- Use conditional logic to hide identity fields when the subject is unknown, which reduces friction and unnecessary data entry.
- Record exact camera IDs and footage time ranges before the end of the shift so the evidence is still easy to retrieve.
- Mark required fields only where the information is essential to review or escalation, and leave nonessential fields optional.
- Include a clear what-happens-after-I-submit line so staff know who reviews the report and what the next step is.
- Use attachments for stills, exports, or logs rather than pasting long narratives into the description field.
- Assign a review deadline on every report so unresolved incidents do not disappear into the queue.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What incidents should this template be used for?
Use it for suspected cheating, advantage play, theft, collusion, tampering, or other unusual behavior observed by surveillance. It is also useful for documenting repeat patterns that need review by security, compliance, or gaming management. If the event is a routine guest complaint with no surveillance concern, a different intake form may be a better fit.
Who should complete the report?
A surveillance operator, floor supervisor, security lead, or other designated reviewer should complete it as soon as the event is observed or confirmed. The form works best when the person entering it can identify the camera, time range, and immediate action taken. If multiple people saw the event, one person should consolidate the report to avoid duplicate records.
How detailed should the incident description be?
Record only the facts you can observe or verify, such as actions, timing, location, and visible interactions. Avoid speculation about intent unless it is clearly supported by evidence. The goal is to create a usable audit trail that another reviewer can follow without needing to reconstruct the event from memory.
What evidence should be attached?
Attach the relevant footage references, still images, logs, or other supporting materials that help confirm the incident. Include camera IDs and the exact footage time range so the reviewer can find the event quickly. If your process allows it, note whether the evidence is original, exported, or cross-referenced from another system.
Should this form include names or player IDs?
Only collect known names, aliases, or account IDs when they are actually needed to identify the subject or support follow-up. If the person is unknown, use a physical description and location details instead of forcing a guess. This supports data minimization and reduces unnecessary PII in the record.
What happens after the report is submitted?
The report should route to the assigned reviewer, such as surveillance management, security, compliance, or operations, depending on your workflow. The reviewer can then decide whether to preserve footage, escalate internally, contact law enforcement, or close the case. A clear review deadline helps prevent incidents from sitting unresolved.
How does this compare with an ad-hoc email or chat message?
An ad-hoc message is easy to miss, hard to search, and often lacks consistent fields like camera IDs, time ranges, and escalation status. This template creates a structured record with validation-friendly fields and a repeatable review path. That makes it easier to track patterns, hand off cases, and maintain an audit trail.
Can this template be customized for different gaming environments?
Yes. You can tailor the incident types, area names, evidence fields, and escalation options for casinos, card rooms, sportsbooks, or entertainment venues with gaming areas. You can also add conditional logic so only relevant follow-up fields appear for the incident type being reported.
Related templates
Go deeper on the topic
-
A standard operating procedure (SOP) is a documented, step-by-step procedure for a repeatable task — the written version of "how we do this here." Good SOPs...
-
Workforce management (WFM) is the operational discipline of getting the right employees, with the right skills, in the right place, at the right time — and...
-
A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
-
A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
-
MangoApps AI agents now take action across 21 apps—approving leave, advancing candidates, managing schedules—not just surfacing recommendations.
-
Unregulated generative AI exposes companies to data leaks, compliance violations, and productivity blind spots. Learn how to govern AI adoption before...
-
Overcome enterprise-wide AI deployment challenges with scalable GenAI strategies that cut costs, boost adoption, and deliver measurable ROI.
-
Deploy collaboration tools successfully with 5 proven tips to boost adoption, align teams, and improve communication from day one.
Ready to use this template?
Get started with MangoApps and use Gaming Surveillance Incident Report with your team — pricing built for small business.
