Practical guide
Ongoing sanctions monitoring: an operations checklist
Operate sanctions monitoring with a reconciled customer population, current subject data, source coverage, successful rescreens, alert ownership, and closure rules.
On this page
Start with the population that should be monitored
A monitoring program needs a defined population, not just a count of monitor records. Reconcile active relationships in the business system with the subjects selected for monitoring. Explain exclusions, paused records, and closure decisions.
A customer without a monitor is different from a monitor that exists but has not completed a successful check. Both conditions should be visible to the responsible team.
Assign ownership of the retained identity
Identify which system owns the legal name, entity type, and reliable identifiers. Define how corrections reach the monitored subject and how the identity version is connected to each result.
For an invented account, the business system corrects a birth year while the monitor retains the older input. The next successful run is still a check of the old facts until the monitoring record is updated.
Watch coverage health and successful completion
Track required source availability, active source versions, last successful rescreen, and unresolved failures. The next scheduled time is not evidence of a completed check. Do not allow a missing source to become an unannounced reduction in coverage.
SanctionsKit provides scheduled and qualified source-triggered full rescreens within its documented model. Review monitoring behavior rather than assuming an instantaneous guarantee from the word ongoing.
Reconcile notifications with review work
Verify that relevant changes reach the monitoring inbox or the downstream event handler, and that investigations have owners. Duplicate events should not create duplicate identity decisions, while new evidence should not disappear behind an old dismissal.
Sample reopened cases and reused decisions. Check whether the earlier evidence and policy are still applicable to the new comparison.
Plan capacity and relationship closure
Estimate scheduled and event-triggered completed screenings, expected issue volume, and review staffing. Monitor usage and operational limits before they become repeated failures. Stopping a relationship may require pausing or removing monitoring while retaining earlier evidence under policy.
Do not keep subjects monitored indefinitely by accident, and do not delete historical evidence solely because a monitor has been stopped.
Run a periodic control check
Reconcile population, input versions, coverage, completed checks, unresolved notifications, case ownership, and evidence retrieval. Record findings and the person responsible for each correction.
Use operational reports within their documented scope and supplement them with sampled case review. The objective is evidence that the intended checks ran and the resulting questions were handled, not merely a large count of automated tasks.