Casino Suspicious Activity Report Form

This template is used to document suspicious patron behavior, related transactions, and the observations that support internal review and possible Title 31 SAR filing. It gives compliance, security, and surveillance teams a consistent record of what was seen, where it happened, and what action was taken. It is not the SAR itself, but the worksheet that helps prepare one.

It is usually completed by the employee who observed the activity, such as a floor supervisor, cage team member, security officer, or surveillance analyst. The key is that the reporter can describe the event firsthand and provide enough detail for follow-up. If multiple people observed the same event, one person should submit the report and reference the others in the notes.

Use it each time a suspicious event meets your property’s escalation threshold, rather than waiting to batch incidents later. Prompt completion preserves details, supports an audit trail, and reduces memory gaps in the narrative. If the same patron triggers multiple observations, create separate entries or linked reports according to your internal procedure.

Include behaviors and transaction patterns that raised concern, such as unusual buy-ins, rapid chip movement, inconsistent source-of-funds explanations, structuring indicators, or evasive conduct. Use the activity fields to describe what happened, then explain why it seemed suspicious in the suspicion_reason section. Avoid vague labels without facts, because the report should show observable indicators rather than conclusions alone.

No. This template supports internal documentation and escalation, but it does not replace the formal SAR filing process or your casino’s compliance review. The report should feed the team responsible for determining whether a SAR is required. Keep the worksheet factual so it can be reviewed, retained, and attached to the case file if needed.

Use the patron_identifier and patron_description fields to capture whatever is available, such as physical description, loyalty number, seat or table location, and other non-sensitive identifiers. If your process allows anonymous or limited identification at the observation stage, keep the report factual and note what was not available. Do not force a full identity field when it is not known.

Use the surveillance fields to note whether video, still images, or system logs are available and where they are stored. This helps reviewers find supporting evidence quickly and maintain a clear chain of reference. If no surveillance is available, say so explicitly rather than leaving the section blank.

Common mistakes include writing conclusions instead of observations, leaving out time stamps, failing to identify the location area, and skipping the immediate action taken. Another frequent issue is using free text where structured fields would be clearer, such as entering estimated amounts without a currency type. The best reports are specific, timely, and easy for compliance to review.