Guided product tour
Adjudicate a sanctions screening hit
Six steps, no account, nothing to install. Each step is its own page, so you can send a colleague a link to the part that matters and it will open exactly there.
Every name, list and identifier in this walkthrough is invented. SAMPLE SUBJECT 001 is not a person, SPECIMEN SANCTIONS LIST is not a real list, and none of these panels is a screenshot — they are drawn with the same components the application is built from.
A screening hit arrives in the queue
What was flagged, by what, and how urgent is it?
Screening runs against the lists your policy puts in scope, and anything scoring above the configured threshold becomes an alert rather than a silent pass. The queue shows the subject, the list that matched, the similarity score and how long the item has been waiting — because the review clock starts at detection, not at assignment.
Screening queue
Sample data| Reference | Subject | List | Score | Waiting | State |
|---|---|---|---|---|---|
| SPECIMEN-SCR-0001 | SAMPLE SUBJECT 001 | Specimen sanctions | 91 | 00:12 | Open |
| SPECIMEN-SCR-0002 | SAMPLE SUBJECT 002 | Specimen PEP | 78 | 01:40 | Open |
| SPECIMEN-SCR-0003 | SAMPLE SUBJECT 003 | Specimen adverse media | 64 | 03:05 | In review |
Why it matters. The threshold that turned this comparison into an alert is itself a controlled setting. Lowering it finds more true matches and far more false ones, so changing it is a reviewable change, not a preference.
After the tour
The same walkthrough, against your own list configuration
A specialist runs this on the lists your policy puts in scope, at the threshold your committee approved, with the customer types you actually onboard.