11 hours
average time to detection
Measured across six weeks of OFAC and EU changes against a nightly batch.
By use case
Monitoring that follows the customer
Approval is one moment. Risk keeps moving after it: sanctions, PEP status, adverse media, ownership. Every change is caught, reviewed against the customer's history, and decided on the same record.
What you switch on
Modules active for this use case
The monitoring system carries out the watching, while the other three assign a weight to each alert.
Why this matters here
A monthly review has a monthly blind spot.
Rescreening calendars were built when lists moved monthly. Lists now move daily. Until the next run, a newly designated customer is still approved.
Full rescreen
full alert volume
Running the whole book again brings back every alert 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
Between sweeps
Delta only
Changes that trigger an alert
3,000+
Sources monitored
Zero
Batch windows
Workflow · Against the clock
Scroll to advance
Every change, step by step
-
Step 01
Define the monitored book
Each approved customer makes one call and is fully covered in every segment.
-
Step 02
Version every source
With each list update, we provide a version number and timestamp; changes are sent as diffs, not full reloads.
-
Step 03
Alert on real change, decide in context
New designations, changes in PEP tier, adverse media, and ownership changes trigger alerts, which are then checked against the customer's risk profile and history, and the risk assessment is updated on the same record; delistings are automatically cleared.
-
Step 04
Clearances that hold
The decision is recorded against the name and its evidence, not the alert, and holds through list updates while the customer stays monitored.
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
The interval is not determined by any government; instead, each regime questions the reason for your choice.
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
How often is the book rescreened?
Delta-only sweeps run every fifteen minutes across the monitored book. Each sweep checks what has changed in the sources since the last one, rather than rescreening every customer from scratch.
Why fifteen minutes and not real time?
Sources publish in batches, so a shorter interval would re-read unchanged data without catching anything sooner. Fifteen minutes keeps detection close to publication and removes the overnight gap a nightly batch leaves open.
Will more frequent screening multiply our alerts?
No. Only genuine deltas raise an alert, so volume tracks list activity rather than sweep frequency. Running more often does not bring back names already cleared, which is what happens when the whole book is rescreened.
Which changes raise an alert?
New designations, PEP tier changes, adverse media and ownership changes. Each alert is checked against the customer's risk profile and history, so the reviewer sees what changed and why it matters for this customer.
What happens when a customer is delisted?
The alert auto-clears and the case records why, so nobody re-investigates a resolved name. The customer's history keeps both the original designation and its removal, which an examiner may still ask about.
Do cleared matches return after a list update?
No. The decision is recorded against the name and its evidence, not the alert, and the customer stays monitored. A cleared false match does not return after the next list update, while a genuine change to that entry still raises a new alert.
Can we show which list version a decision used?
Yes. Each list update carries a version number and timestamp, and changes arrive as diffs, not full reloads. You can show which version of a list a decision was made against, which is the first thing asked when a past clearance is challenged.
Can we monitor only part of the book?
Yes. Scope is set per customer or segment, and the scope decision is recorded with its rationale. Whatever you leave out of monitoring has to be defended, so the reason sits on file next to the choice.
How is an alert judged against the customer's history?
Against the customer's risk profile and history, and the risk assessment updates on the same record. A PEP tier change means something different for a dormant retail account than for an active corporate client, and the review reflects that.
Does any regulation set the monitoring interval?
No. FATF and the EU framework require monitoring for the full length of the relationship, in proportion to risk, but no regime fixes the interval, and supervisors ask you to justify the one you chose. Sanctions are the exception in practice: freezing obligations apply from designation, without delay.
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