11 hours
average detection lag
Measured across six weeks of OFAC and EU changes against a nightly batch.
By use case
Ongoing monitoring and rescreening
Screening at onboarding covers one moment. Monitoring covers the relationship — which is where designations actually land.
What you switch on
What this use case needs switched on
Monitoring is the module. The other three decide what it is worth.
Why this matters here
A monthly review is a monthly blind spot.
Most programmes rescreen on a schedule designed for a world where lists changed monthly. The list changed this morning. The question is how long your customer stays approved while it does.
Full re-run
means full re-noise
Rescreening everything regenerates every alert you already cleared.
Cleared twice
whitelists that do not hold
If a whitelist attaches to a match rather than a name, the same customer comes back.
15 min
Sweep interval
Delta only
What raises an alert
3,000+
Sources monitored
0
Batch windows
Workflow · Against the clock
Scroll to advance
The workflow, step by step
-
Step 01
Register what stays in scope
One call per approved customer. Scope is explicit, so nobody wonders whether a segment is covered.
-
Step 02
Sources versioned on publication
Every list carries a version and a timestamp, so a change is a diff rather than a reload.
-
Step 03
Only genuine deltas alert
Additions, tier changes and delistings each behave differently. Delistings clear automatically.
-
Step 04
Whitelists that survive updates
A clearance attaches to the name and the evidence, not to the alert — so it holds through the next publication.
complead / monitoring / scope
- In scope1,284,902
- Added today4,182
- Removed96
complead / sources
- Sources3,014
- Updated in last hour11
- Last publication6 min ago
complead / monitoring / feed
- Delta alerts today7
- Auto-cleared3
- Escalated1
complead / whitelist
- Active clearances2,441
- Survived last update100%
- Re-raised0
Scope
Sources
Deltas
Clearances
What you answer to
What the obligation actually says
No regime names an interval. Every regime expects you to justify the one you chose.
Read the compliance guides
FATF R.10
Ongoing due diligence throughout the relationship
Continuous
EU AMLD
Monitoring proportionate to risk, documented
Ongoing
Supervisor
Justification for your chosen interval
Per review
OFSI / OFAC
Freezing on designation, without delay
Same day
Case study · Telecom
Read the case study
A national operator moved 1.2M subscribers onto continuous screening
Manual list checks ran monthly and covered one jurisdiction. After migration the whole base is rescreened every fifteen minutes across 220+ countries, and clearances carry a reason code.
−72%
Manual review hours
1 day
To integrate
1.2M
Names in scope
Cross-family links
Where teams like yours go next
FAQ
Before you ask us
Why fifteen minutes and not real time?
Sources publish in batches; a shorter interval would re-read unchanged data. Fifteen minutes is the point where detection lag stops being the constraint.
Does this multiply our alerts?
No. Only genuine deltas raise an alert, so volume tracks list activity rather than sweep frequency.
What happens on a delisting?
The alert auto-clears and the case records why, so nobody re-investigates a resolved name.
Can we monitor only part of the book?
Yes, scope is explicit per customer or segment — and the scope decision itself is recorded.
Find out how long your gap actually is
Send us a week of list changes and your current schedule. We will show you the exposure hours between them.
3,000+
Data sources checked
220+
Countries covered
15 min
Always real-time data