The screening lifecycle

IN ONE LINE

An everyday analogy: watch one visitor cross the gate.

The gatekeeper compares the visitor with the posters.

Almost always there is no resemblance, and the visitor walks through without ever knowing a check happened.

Occasionally something looks similar; the visitor is asked to wait, and a second, trained person compares everything on the poster with everything the visitor can show.

The outcome is written in a logbook: released as an innocent lookalike, or escalated because it really might be the person on the poster.

The visitor never gets a quiet shrug — every hold ends in a recorded decision.

That routine, repeated millions of times, is the screening lifecycle.

WHAT IT ACTUALLY IS

The lifecycle has a standard shape.

Input data — a customer record or payment message — is normalised and compared against the watchlist.

Most records match nothing and pass straight through; processing continues untouched.

When the matcher finds a resemblance above threshold, it raises an alert: the payment is held in a queue, or the onboarding pauses, until a trained reviewer compares the alerted party with the list entry.

The reviewer's documented outcome is the disposition: release as a false positive, or escalate as a potential true match, at which point sanctions compliance decides on freezing, rejecting, or reporting — with legal advice where needed.

Every step is logged: what was screened, against which list version, who decided what, and why.

HOW IT WORKS

Practitioners live in the proportions.

The overwhelming majority of screened traffic passes untouched; of the alerts that are raised, most turn out to be false positives; genuine matches are rare.

That shape has consequences: reviewer staffing follows alert volume, queues must be worked fast enough that held payments still meet cut-offs, and the rare true match must survive the monotony — the process has to stay sharp through thousands of innocent lookalikes.

Controls reflect this: maker-checker review on releases, so no single person can wave a payment through; queue aging and backlog monitoring, because a growing queue is both a service problem and a risk problem; and quality sampling of closed alerts to confirm dispositions would survive scrutiny.

THE WORDS

Alert

The record a screening system creates when a name scores as a possible watchlist match, queued for investigation and decision.

Disposition

The recorded decision that closes an alert — such as false positive or true match — together with its rationale and evidence.

READ FIRST

• Customer vs transaction screening

CONNECTED TO

• CHECKPOINT Name matching checkpoint
• SCREENING LAB A clean pass through the filter

SOURCES

• Wolfsberg Group Sanctions Screening Guidance — The Wolfsberg Group
• Payments Signal editorial teaching models — Payments Signal