Practical guide
What is continuous sanctions monitoring? Cadence and alerts
Understand ongoing sanctions monitoring, scheduled and source-triggered rescreening, changing customer details, alert review, and important coverage limits.
On this page
Monitoring repeats a defined check as information changes
Ongoing sanctions monitoring retains selected subjects and rescreens them against selected coverage. It is designed to bring relevant changes back to the people responsible for the relationship. “Continuous” describes an ongoing process, not a guarantee that every authority change is detected instantly.
Monitoring has several clocks: authority publication, provider ingestion, source activation, rescreen scheduling, successful completion, and analyst review. A useful service makes those distinctions understandable rather than collapsing them into “always up to date.”
Scheduled and source-triggered checks do different work
A scheduled rescreen runs on a chosen cadence. A source-triggered process responds to qualifying changes in the source data. Both need successful completion and an operational owner. A source update notification alone is not evidence that every monitored subject was rescreened.
SanctionsKit supports six-hour, daily, and weekly schedules, together with qualified source-triggered full rescreens. See the current monitoring product page and documentation for behavior and controls.
Monitor the right version of the subject
The service can only screen the retained subject information. When a customer changes legal name, a company changes identity details, or an identifier is corrected, update the monitored record through the documented process. A current sanctions list cannot compensate for stale customer input.
For an invented supplier, the procurement system changes the legal entity after a restructuring. If monitoring still uses the old entity, a successful rescreen does not answer the question procurement now needs answered.
Give relevant changes a review path
A new candidate, changed source evidence, or a previously dismissed comparison may require investigation. Preserve the earlier result and reasoning, identify the changed facts, and assign the next action. Do not automatically treat every notification as a confirmed match.
SanctionsKit’s monitoring inbox distinguishes evidence changes and screening issues and can connect them to retained investigations. Acknowledging a notification is not the same as resolving an identity question.
Plan for failures, pauses, and closure
An unavailable required source, a failed rescreen, or a capacity issue needs a visible operational path. Track the last successful check as well as the next planned run. A monitor that exists in a database is not proof that checks are completing.
Define when relationships are paused or stopped and how historical evidence is retained. Removing a monitored subject should not be confused with erasing the organization’s earlier decisions.
What monitoring does not do
Sanctions monitoring is not transaction-behavior monitoring, automatic beneficial-ownership discovery, or a guarantee that all restrictions appear in the selected lists. Reviewers remain responsible for identity assessment and the authorized business action.
Use the screening frequency guide to select a policy-driven cadence and the monitoring operations checklist to test whether the process is working.