Sanctions screening frequency: choose and verify a schedule

Start with the approved reason for repeat checks

SanctionsKit supports six-hour, daily and weekly schedules, plus qualified source-triggered full rescreens. The right frequency depends on your obligations, relationships and risk assessment. These software options do not set a legal interval for your organization.

Record the recurring schedule and events that require a separate check, such as a corrected identity or new payee. Running the old customer's name more often does not answer a question about a different legal party. Use both recurring checks and the event triggers your process requires.

Set the schedule in the dashboard

Open Monitoring in the dashboard, select the subject and choose Change cadence. Review the forecast, then save Every 6 hours, Daily or Weekly. Check the resulting schedule and make sure someone owns any new review events.

A policy-backed monitor uses its approved policy cadence. An owner or administrator changes that policy in Screening policies and publishes a version. Update the saved monitor to the current policy deliberately. The change does not rewrite the schedule or evidence recorded for earlier screenings.

Update an API-managed schedule safely

Read GET /api/v1/monitoring?monitorId=ID for the current revision. Send the body below to PATCH /api/v1/monitoring/{id} with monitors:write and a fresh Idempotency-Key. Replace the example revision 1 with the real returned revision. This example requests daily checks.

intervalHours accepts 6, 24 or 168. Reload after the change to verify the new revision and schedule. If you receive stale_revision, reread current state before deciding whether the change still makes sense. Do not force an old request over someone else's change. The create-monitor body does not accept intervalHours.

{
  "expectedRevision": 1,
  "intervalHours": 24
}

Estimate the recurring work before changing frequency

For an illustrative group of 500 subjects, daily checks plan 15,000 scheduled comparisons in 30 days. Six-hour checks plan four per day, or 60,000 over that period. Extra source-triggered runs, changed enrollment and failed or deferred work can change actual usage.

Use the estimate to plan allowance and review capacity. Then check actual completed runs. A faster schedule cannot repair an old customer name, missing coverage or ignored alert. Read input quality, source health and the last successful check together when assessing whether the control is working.

Verify completion, not just nextRunAt

Inspect lastSuccessfulAt, lastScreeningId, health and required sources. nextRunAt is a plan. A failed or overdue active monitor needs attention. Resolve the issue, use Retry check now where available, and verify the later successful result. Queuing another attempt is not completion.

Read Changes needing attention for failed checks, recoveries and changed evidence. Acknowledge an event separately from completing its case. Inspect source versions in the retained result so a frequent schedule cannot hide stale required data.

Keep a reason for the frequency you chose

For each group, note the relationship type, relevant obligations, business events, cost of delay and review owner. Record the chosen cadence and event triggers. Those reasons let a later policy review check whether the assumptions still hold.

OFAC FAQ 28 discusses internal policy and screening frequency. Use relevant sector guidance as well. The tool lets you carry out a chosen schedule; it does not decide which frequency meets your organization's requirements.

Revisit the schedule as relationships change

Update saved subject facts when reliable customer details change. Resolve a pause caused by editing a linked profile. Stop monitoring when the approved relationship process calls for it. Old evidence still has its own retention lifecycle.

Use monitoring operations to compare active relationships, saved requests, successful checks and open reviews. The freshness guide explains why a new source file and a completed customer rescreen are separate events.

Frequently asked questions