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.
Test the secondary discriminators
Is there anything that positively rules this in or out?
Date of birth, nationality and a strong identifier are the discriminators that turn an unresolvable name match into a decision. Where a discriminator is missing, that absence is itself recorded — an alert cleared because the data was thin is a different decision from one cleared because the data disagreed.
Discriminator review
Sample dataDate of birth
DiscriminatesBoth records carry a full date and they are seventeen years apart. On its own this clears the hit.
Nationality
DiscriminatesEvery nationality held by the customer is recorded, and none overlaps the listed jurisdiction.
Strong identifier
UnavailableThe list publishes no identifier for this entry, so no positive confirmation is possible from it.
Address
Weak signalCountry-level only on the list side. Recorded, but it decides nothing either way.
Why it matters. Recording which discriminators were available, not only which ones matched, is what lets the same alert be re-examined years later without repeating the investigation.
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.