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.
Record the disposition and the rationale
What is the decision, and why would it stand up?
The disposition closes the alert; the rationale is what makes it defensible. It is written for a reader with no access to this system, months from now, who needs to follow the judgement, the evidence behind it and why the alternative was rejected. A reason code sits beside the free text so decisions can be counted and compared across analysts.
Disposition
Sample data- Decision
- False positive — not the listed party
- Reason code
- DOB_AND_NATIONALITY_DISCRIMINATE
- Rationale
- The similarity is carried entirely by the name. The recorded date of birth differs from the listed date by seventeen years and the customer holds no nationality connected to the listed jurisdiction; both are evidenced in the customer file. The list publishes no identifier for this entry, so confirmation by identifier was not available and was not relied on. The alternative — treating the name similarity as sufficient — was rejected because it would require disregarding two independent contradicting fields.
- Recorded by
- Sample Analyst (synthetic identity) · reviewed under maker-checker separation
Why it matters. A one-line rationale — "not a match" — closes the alert and fails the review. The rationale is the part of this record that leaves the institution.
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.