Core sanctions regimes covered
10+
ScreenVeritAI coverage model
Resources and Playbooks
Sanctions Re-Screening Policy Template
A template for setting re-screening frequency, trigger events, and escalation rules across customer and vendor portfolios.
One-time checks are not enough for sustained compliance. This policy template helps define recurring re-screening schedules and event-driven triggers based on risk tier, jurisdiction exposure, and business criticality.
Updated: 2026-02-20
What this workflow covers
- Set baseline frequencies by risk tier: low, medium, and high risk.
- Define trigger events such as ownership changes, jurisdiction changes, or adverse media hits.
- Assign ownership across first-line operations and second-line compliance teams.
- Measure policy adherence with monthly control metrics and exception logs.
Key statistics
Key workflow dimensions
4 (Sanctions, PEP, Adverse Media, UBO)
ScreenVeritAI workflow model
Compliance glossary
Sanctions screening
A control process that checks a person or entity against sanctions and watchlist datasets.
PEP
Politically Exposed Person: an individual in a prominent public function requiring enhanced due diligence.
UBO
Ultimate Beneficial Owner: the natural person who ultimately owns or controls a legal entity.
Authoritative references
- OFAC Sanctions Lists
U.S. Department of the Treasury
- EU Financial Sanctions Database
European Commission
- UN Security Council Consolidated List
United Nations Security Council
Expert perspective
\"Risk controls perform best when sanctions checks and ownership context are reviewed together.\"
ScreenVeritAI Compliance Team, RegTech Research
Frequently asked questions
How often should sanctions re-screening run?
Frequency should be risk-based. High-risk entities are typically screened more often than low-risk counterparties.
Which trigger events should force immediate re-screening?
Ownership changes, major adverse media events, and material jurisdiction changes should trigger immediate checks.
Who should own the re-screening policy?
Compliance should own policy design, while operations execute recurring checks and escalation workflows.
How can we prove the policy is working?
Track completion rates, time-to-review, false-positive rates, and unresolved escalations by risk tier.