Casino Suspicious Activity Report Form

This template is used to document suspicious patron activity, related transactions, and observable behaviors in a consistent internal format. It supports compliance review and SAR preparation by capturing facts, timestamps, locations, and evidence notes in one place. It is not the SAR itself; it is the worksheet that helps your team decide what to escalate.

The person who observed the activity should complete the form as soon as practical after the incident. In many casinos, that may be a floor supervisor, surveillance team member, cage staff member, or security officer. The key is to record first-hand observations and avoid speculation or second-hand assumptions.

Use it each time a suspicious event, pattern, or transaction sequence needs internal review. It works for a single incident, repeated activity over a shift, or a series of linked events involving the same patron or associated persons. If your process includes escalation thresholds, this form should be completed whenever those thresholds are met.

Include only the patron details your team actually needs to identify and review the event, such as a known name, player account reference, or internal identifier. Use conditional logic so unknown patrons can be documented without forcing unnecessary fields. Avoid collecting extra PII unless it is required for compliance review and your policy allows it.

No. This template supports internal documentation and review, but it does not replace your SAR filing workflow or legal review process. It should feed the next step in your compliance chain, such as escalation to the AML or compliance owner. The form should also make clear what happens after submission.

Common mistakes include writing vague summaries, mixing opinions with observations, and leaving out exact times, locations, or transaction estimates. Another frequent issue is collecting too many required fields, which slows reporting and reduces accuracy. The best forms keep required fields limited, use clear field types, and separate observed facts from review notes.

Yes. You can tailor the reporting source, evidence fields, and follow-up routing for surveillance, security, cage, slots, table games, or compliance. Conditional logic can hide irrelevant fields so each department sees only what applies. That keeps the form easier to use and improves data quality.

This template can feed case management, incident tracking, document storage, or compliance review workflows. Common integrations include ticketing tools for follow-up, secure file storage for evidence, and notifications to the compliance owner. If you connect it to other systems, keep access controls tight because the form may contain sensitive PII and internal investigative notes.