False positives & efficiency
How many ordinary customers does your screening flag, and why?
Every alert on an innocent customer costs analyst time, and it doesn't fall evenly. We measure alert rates by customer corridor and threshold, show which names carry them, and trace each one to the engine, the configuration or the data.
Sample report · 2,250 synthetic customers · October 2026
Read alerts per 1,000 customers, not just the rate.
Three corridors screened against the UK and OFAC lists on name alone. The rate says how many customers are touched; alerts per 1,000 says how much an analyst has to clear. A flagged Nigerian name brings six alerts on average, because names such as Mohammed and Ibrahim appear in many listed records.
Who it falls on, and why
The alerts land on a few name origins, and each cause has an owner.
In the Nigerian corridor, 100 of the 101 alerting names were Muslim or Hausa-Fulani names. Most alerts came from the engine treating a customer's names as matching a longer listed name, not from a true namesake.
Secondary data
What date of birth can clear, and what it can't.
Measured on the list records behind every alert. A full date of birth is the biggest lever, but some alerts sit against records with none, and no amount of customer data will clear those. Your own test measures how many your system actually clears.
Run this on your engine
Synthetic customers built for your corridors, run through your own screening.
The figures on this page come from Escalate's in-house test engine, built on open-source matching, screening names alone. Your report runs the same method through your own screening, with date of birth and nationality, so you see how many alerts clear automatically and how many reach an analyst.
- 20 minutes to agree corridors, lists, the secondary data you hold, and what you return: alert or no alert, score and matched record.
- You receive test IDs and names, plus the secondary fields your system accepts. No expected results.
- You run the file and send back the results.
- You get the report on your own engine, across every corridor and threshold.