# Page: Common Operational Examples

## Purpose

This page provides example scenarios that help users understand how the fraud and AML experience is typically used in day-to-day operations.

## Example 1: Investigating a high-risk score

A transaction receives a high-risk score. The analyst opens the score details, reviews the supporting explanation, and decides whether the case should be escalated for manual review.

## Example 2: Handling a new case

A new case appears in the queue. The investigator opens the case, updates the status, adds notes, and confirms whether the case should be approved, declined, or deferred.

## Example 3: Updating configuration

An administrator notices that a rule is producing too many false positives. They review the rule logic, adjust the condition, and validate the updated behavior before activating the change.

## Example 4: Reprocessing historical records

A sanctions list or model update requires re-evaluation of historical transactions. The team uses reprocessing to refresh the decision outcome and review the results.

## Practical takeaway

These examples show that the system is designed to support both rapid review and careful escalation. Users should move from score to case to evidence and then to action.