Start by mapping your own regulator and its instruments, then attach every exam topic to a named source in that map. The difficulty is jurisdictional variation, so study CTR versus SAR triggers, segregation of duties, and responsible gaming routing as concepts tied to your specific authority, rehearsed through labeled paper scenarios rather than memorized generic rules.
Who licenses you changes what you must know
Before memorizing any rule, identify your jurisdiction's gaming authority, the license categories it issues, and the conduct rules attached to your category. Everything else — AML, internal controls, conduct — hangs on that specific framework.
Gaming regulation is fragmented. In the United States, state commissions such as the Nevada Gaming Control Board license employees alongside tribal regulators and federal AML law; other countries run national or provincial regimes with different names for similar roles. A rule learned in one jurisdiction may be irrelevant or contradictory in another. When you study any duty, write its source beside it — which regulator, which regulation or control standard — so your knowledge stays anchored instead of blending into a generic casino rulebook.
Turn this into a working exercise: choose your own jurisdiction and complete a one-page map with five fields — regulator's name, employee license categories, AML reporting channel, responsible gaming program name, and one internal control document it references. Expected observations: you finish with real names and formal titles, not generic phrases. If a field stays blank, that blank is your first study target, because an unanchored duty is exactly where a confident wrong answer forms.
CTR versus SAR: two reports, two different triggers
Under the U.S. Bank Secrecy Act — one common model casinos operate under — a Currency Transaction Report logs large cash transactions by rule, while a Suspicious Activity Report documents behavior that looks structured, evasive, or unexplained regardless of amount.
The two reports answer different questions. A CTR asks 'how much cash moved?' and is triggered mechanically when currency transactions exceed the reporting threshold — $10,000 in a gaming day in the U.S. example — aggregated across related transactions. A SAR asks 'does this behavior make sense?' and depends on judgment: repeated transactions just under the threshold, quick swaps of chips for cash, or a patron coaching another patron. Same shift, different documents, different reasoning.
Study the distinction by classifying paper cases rather than memorizing definitions. Write ten short vignettes — some purely high-value, some odd but small — and sort each into CTR-trigger, SAR-consideration, both, or neither. A high-value, straightforward cash buy-in lands in the CTR column; a patron splitting activity across cages after asking about reporting rules is a SAR candidate even below the threshold. The classification habit matters because both exam items and floor reality present mixed facts, not clean labels.
| Feature | Currency Transaction Report (CTR) | Suspicious Activity Report (SAR) |
|---|---|---|
| Core question | How much currency moved? | Does the behavior look evasive or unexplained? |
| Typical trigger | Cash transactions above the set threshold, aggregated across related activity | Judged suspicion at any transaction amount |
| Nature of the filing | Rule-based and mandatory once the threshold is met | Judgment-based escalation for compliance review |
| Employee's role | Follow cage and floor procedures; capture identification as trained | Never signal the patron; refer observations and written notes to compliance |
A floor scenario: structuring and tipping off
When a patron probes how to keep transactions under reporting thresholds, the risk is twofold: helping structure the activity and tipping the patron off. The safe pattern is neutral service plus immediate internal referral.
Scenario: at the cage, a patron asks, 'If I do two $6,000 cash-ins instead of one $12,000, do you still have to report it?' A plausible mistake is answering helpfully — 'sometimes it depends' — or quietly processing split transactions to keep the paperwork down. Both responses can be read as assisting the structuring of currency transactions and as tipping off, and it is the employee's own license on the line, not just the house's compliance file.
The better decision follows a fixed script: answer nothing about reporting rules, process the transaction exactly as procedure dictates, and refer the remark to the compliance or AML officer the same shift with a short written note of what was said. Why it matters: compliance teams can only assess pattern behavior from unfiltered facts, and a tipped-off patron changes behavior, destroying that record. Rehearse the script aloud until it survives a live counter question.
Segregation of duties: drop, count, and who must not touch both
Gaming internal controls rest on separating custody, recording, and verification. One person handling both the drop and the count defeats the control — and leaves that employee unable to prove innocence if a variance appears.
Scenario: a slot drop team is short-staffed, and the shift manager asks one employee to pull the drop boxes and then stay to verify the count sheet. The plausible mistake is complying to be a team player, since the work itself seems routine. Minimum internal control standards — Nevada's MICS are a widely cited example — require different people to transport drop boxes and to perform or verify counts, precisely so that no single person can both take custody of the money and attest to its amount.
The better decision is to raise the staffing conflict through the supervisor chain before touching the second task, and to document who performed each step if the schedule cannot be fixed immediately. Why it matters twice: first, the control exists to deter theft; second, it protects the employee from unresolvable suspicion. In study terms, learn internal controls as a pattern — custody, recording, verification kept separate — then test any paper scenario against that pattern.
Surveillance and security: different eyes, different authority
Surveillance observes and documents; security intervenes on the floor. Game integrity problems usually begin as a surveillance observation that flows to the pit, not as an immediate confrontation. Knowing the hand-off is the exam-relevant skill.
A camera operator watching a dealer's hands holds an observation duty: track the game, note the exact position of cards or chips, record times, and report through the surveillance chain without leaving the room. A security officer holds intervention authority but limited gaming-specific observation duties, and a floor supervisor holds the authority to stop a game. These are distinct roles with distinct chains of command, and written questions probe exactly where one role ends and another begins.
Practice the hand-off with a narrated case: you observe what looks like a dealer pay error on video. Write the sequence — what the surveillance operator records, who is notified, who verifies at the table, and who decides on correction or review — then check each step against your jurisdiction's or employer's stated procedure. Observations to expect: timestamps and game position recorded before any judgment, no direct contact between surveillance and the patron, and one accountable decision-maker at the pit.
Responsible gaming: what you must do and what you must never promise
Responsible gaming duties center on recognizing problem gambling indicators, following the jurisdiction's self-exclusion process exactly, and referring rather than counseling. Employees must never improvise treatment advice, negotiate exclusion terms, or promise outcomes.
Self-exclusion is a formal, regulated process, not a favor an employee can grant or undo at the counter. In most frameworks the patron files through a defined channel, the exclusion binds the operator once processed, and contact during an active exclusion triggers defined action. Learn the names and steps in your own jurisdiction from the regulator's program — the flow matters more than the exact form, because both exam questions and floor situations test whether you route the patron correctly instead of handling it personally.
Draw a hard line between duties and boundaries. Duties: notice indicators such as distressed play or direct requests to be banned, follow reporting steps, and treat all patrons consistently. Boundaries: no diagnosis, no advice about gambling limits beyond the posted programs, and no side agreements such as 'just don't come in on Tuesdays.' That informal arrangement is the classic wrong answer, because it bypasses the legal exclusion and exposes both the employee and the license. Route through the program, every time.
A four-week sequence with readiness checks
Structure preparation in three passes: map and terminology first, scenario classification second, timed mixed review last. Close by scoring yourself against concrete observations, treating those scores as learning milestones rather than predictions of any outcome.
Week one: build the jurisdiction map from the first section and attach every topic to a named source. Week two: work AML and internal control scenarios — classify ten CTR/SAR vignettes, run the drop-and-count case, and write out the tipping-off script word for word. Week three: add surveillance hand-offs and responsible gaming routing, narrating each aloud. Week four: mix everything under time pressure and re-score the rubric, revisiting whichever field of the map still reads generic rather than named.
Use this self-check rubric, scoring each item yes or no: you can name your regulator and license category from memory; you can distinguish CTR from SAR triggers in one sentence each; you can state one segregation-of-duties rule and explain why it protects the employee; you can describe your jurisdiction's self-exclusion route step by step; you can narrate the surveillance-to-pit flow without notes. Five yes answers signal content familiarity for further practice; any no points directly at your next study session.