> ## Documentation Index
> Fetch the complete documentation index at: https://sims-bae272dd.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Loss Prevention

> Investigating ticket shortages, register variances and suspicious patterns.

**Lottery Management → Loss Prevention** (headed **Loss Prevention & Owner
Alerts**) collects everything that did not add up: physical ticket shortages,
POS register variances and suspicious patterns.

Columns: Date & Time, Type, **Severity**, Variance Amount, Description, Status
and Action.

## What raises an alert

| Type | What it means |
| - | - |
| `BIN_POS_VARIANCE` | Tickets counted out of a bin do not match POS scratch sales |
| `TERMINAL_POS_VARIANCE` | The state's terminal report does not match POS |
| `UNRECORDED_ACTIVATION` | A pack was sold from without being activated |
| `MISSING_PACK` | A pack cannot be accounted for |
| `SUSPICIOUS_PAYOUT` | A cashing pattern worth a look |
| `CASH_SHORTAGE` | The drawer is short against lottery activity |

Severity runs low, medium, high, critical.

## Investigate one

**1. Open the alert**

**Investigate Alert #…** shows the variance and how it arose.

**2. Note who was on shift**

An alert can record a suspected employee. Because audits are per shift, the
window is usually narrow.

**3. Write resolution notes**

What you found, and what you did about it.

**4. Mark as Resolved**

Or dismiss it if it was not real.

Statuses: `OPEN`, `INVESTIGATING`, `RESOLVED`, `DISMISSED`.

> [!WARNING]
>
> Treat one alert as a question, not an accusation. A single bin variance is
> often a misread ticket number or a pack activated late. It is a **repeated**
> pattern — same shift, same bin, same person — that means something, and that
> is what this log is built to make visible.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.