OFAC program pages organize authorities—not one global sanctions rule

Program identity comes before a transaction conclusion

The direct answer on OFAC's page is plural: the agency administers different sanctions programs. OFAC also says those sanctions may be comprehensive or selective. That means a workflow needs the relevant program, authority and instrument, applicable prohibitions or conditions, parties and ownership facts, goods or services, geography, dates, and transaction activity before an accountable reviewer can reach a bounded conclusion.

A generic country-risk flag is not the same record. Some programs are framed around countries or regions, while others address activities or policy targets. One transaction can implicate several programs, lists, licenses, exceptions, reporting rules, or other legal authorities. The system should preserve each possible basis and its evidence instead of collapsing them into a single red or green country status.

Comprehensive and selective are materially different scopes

OFAC's distinction between comprehensive and selective sanctions matters to product design and operating review. A broad program may restrict a wide category of dealings, while a selective program may focus on designated parties, specified conduct, sectors, instruments, or transaction types. The program name alone does not explain which provision applies to a real transaction or whether authorization is available.

A defensible record should link the exact source and version used, program and legal authority, relevant list or non-list restriction, party identity and ownership analysis, activity, jurisdictional nexus, license or exception review, decision owner, disposition, conditions, and review time. Screening can surface a record for review; it does not replace interpretation of the program and transaction facts.

Last-updated dates support change control—not automatic rescreening logic

OFAC publishes the active-program roster with program-specific last-updated dates. Those dates are useful monitoring signals because different programs move on different schedules. But the date does not identify by itself what changed, which authority or document changed, which transactions are affected, or whether a prior disposition must be reopened. Teams need the underlying official action and a governed impact assessment.

A monitoring workflow should capture the observed page state, compare the relevant program record, retrieve the official action or amended instrument, classify the change, identify affected populations, route review, and retain the decision. A platform may automate detection and population matching, but accountable sanctions and legal owners must define the scope and handle uncertain identity, ownership, jurisdiction, and authorization questions.

The official source set remains wider than the program page

The page separately points users to the SDN and non-SDN lists, other lists, recent actions, licenses, FAQs, enforcement information, reporting, selected general licenses, and archived inactive programs. That structure is an operational warning against treating the roster as a complete rulebook. Program pages orient the reviewer; applicable regulations, orders, directives, licenses, FAQs, and current actions supply additional controlling context.

This article does not identify an applicable program, interpret a prohibition, determine ownership or control, resolve a match, establish U.S. jurisdiction, approve a transaction, or provide a license or reporting conclusion. Organizations need current official materials and qualified sanctions, export, customs, financial-crime, operational, and legal review. The system should make that reasoning inspectable without presenting a program label as a transaction authorization.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Trade Controls Brief will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.