Restricted party screening is the institutional process of checking a person or organization’s name against government restricted- and denied-party lists before engaging with them, as distinct from the lists themselves. The Consolidated Screening List (CSL), the OFAC List (SDN List), and the underlying ITAR and EAR regulations define what a restricted party is and which transactions with one are prohibited or licensable. Restricted party screening is the operational program — policy, staffing, software, and documented decision points — that a research institution runs to catch a match before it becomes a compliance violation.
Why This Is a Distinct Practice From the Underlying Lists
Knowing that the CSL exists and knowing how to run a defensible screening program across every point an institution engages a new person or organization are different problems. A university can have accurate knowledge of the CSL, OFAC’s SDN List, and the Entity List and still have no institutional answer to practical questions like: who is responsible for running the check, at what point in an onboarding or procurement workflow does it happen, what counts as a “hit” worth escalating versus a common-name false positive, and how is the decision documented. Those questions — not the content of the lists — are what a restricted party screening program has to answer.
Which Lists Get Screened
Most institutional screening programs run a name against some or all of the following in a single pass, typically through the CSL as the consolidation point rather than checking each source separately:
- Commerce Department/BIS: the Denied Persons List, Entity List, Unverified List, and Military End-User List.
- State Department: the AECA Debarred List and the Nonproliferation Sanctions list.
- Treasury/OFAC: the Specially Designated Nationals and Blocked Persons (SDN) List and related sanctions lists — see OFAC List (SDN List).
Institutions running federal-award due diligence typically pair this with a separate check of SAM.gov exclusions, since procurement/award debarment under 2 CFR Part 180 is a different eligibility question than export/sanctions restricted-party status, even though the two checks are often run together as part of the same onboarding or subaward due-diligence pass.
When Screening Is Required
A restricted party screening program has to define concrete trigger points in institutional workflow, not just a general policy statement. Common trigger points include:
- Appointing a foreign national. Before extending an offer to a visiting scholar, postdoc, graduate student, or visiting researcher who will have access to controlled equipment, software, or technical data — often run alongside the visa sponsorship process (J-1 DS-2019 issuance, H-1B petition preparation), since both processes need the same identifying information early.
- Executing an international agreement. Before signing a subaward, material transfer agreement, data use agreement, or collaboration agreement with a foreign institution or individual investigator.
- Onboarding a vendor or shipping to a destination. Before purchasing from, or exporting equipment or technical data to, a foreign vendor or shipping address.
- Accepting a gift, sponsorship, or foreign funding source. Before accepting funds from a foreign sponsor or gift source, alongside the institution’s broader foreign-influence and research-security disclosure review.
- Authorizing international travel to, or a deemed-export disclosure involving, a country subject to comprehensive OFAC sanctions.
Because the CSL’s underlying source lists are refreshed daily, a screening result is only current as of the day it was run. Programs handling ongoing relationships — an existing subrecipient, a recurring vendor, a multi-year visiting appointment — typically re-screen periodically or subscribe to continuous-monitoring alerts through their screening software rather than treating a single point-in-time check as permanently valid.
Who Performs the Screening
Responsibility is typically distributed rather than centralized in one office, though a single office usually owns the policy and the escalation decision:
- Export control officer / research security office — owns the screening policy, handles escalated potential matches, and makes the final determination on ambiguous hits.
- International student and scholar services (ISSS) or HR — runs or triggers the initial screen at the point a foreign national is offered an appointment, since that office already collects the identifying information (full legal name, date of birth, nationality, passport details) a screen needs.
- Sponsored programs / research administration — screens counterparties before executing subawards, collaboration agreements, or MTAs.
- Procurement — screens vendors and shipping destinations before purchase orders involving controlled items are issued.
Many institutions license commercial restricted-party screening software (sometimes bundled into export-control-compliance or trade-compliance platforms) that pulls its underlying data from the CSL’s public API and other source lists, rather than having each office manually search trade.gov independently. The software doesn’t replace the institutional decision points above — it automates the lookup, not the judgment call on an ambiguous match.
Handling Potential Matches and False Positives
Name-matching against restricted-party lists produces far more potential matches than actual matches, because list-matching software typically flags partial and phonetic similarity, not just exact matches, to avoid missing a genuine hit due to a transliteration or spelling variant. A defensible screening program documents a consistent process for resolving each potential match rather than leaving the call to whoever happened to run the search:
- Disambiguate with additional identifiers. Date of birth, nationality, passport number, known aliases, and address are used to confirm or rule out a name-only match — a common surname shared with a listed party is not, by itself, a positive match.
- Escalate genuine uncertainty. A potential match that can’t be confidently ruled out on identifying information is escalated to the export control officer or institutional counsel rather than resolved informally by the office that ran the initial screen.
- Document the resolution. Institutions keep a record of every potential match and how it was resolved — cleared as a false positive with the disambiguating information relied on, or escalated — both to support the underlying decision later and to demonstrate a functioning compliance program if the institution is ever audited.
- Treat a confirmed positive match as a hard stop. A confirmed match halts the transaction, appointment, or agreement pending legal/export-control review; engaging with a listed party without an applicable license or authorization is a violation regardless of institutional intent.
Recordkeeping and Audit Trail
Because a clean screen at one point in time doesn’t establish that a relationship remained clean, institutions retain screening records — the search performed, the date, the result, and how any potential match was resolved — as part of the same export-control and research-security recordkeeping obligations that apply to Technology Control Plans and other export-compliance documentation. This record is what demonstrates, after the fact, that the institution ran a good-faith screening process rather than simply asserting one existed.
Restricted Party Screening vs. Export Control Classification
A clean restricted party screen answers only one question: does this specific person or organization appear on a restricted-party list today. It does not answer whether the research activity, equipment, software, or technical data involved is itself subject to export control — that is a separate classification question governed by the EAR and ITAR (see ITAR and EAR and export-controlled research), and whether a foreign sponsor or collaboration triggers a research-security or foreign-influence disclosure obligation is a further, separate compliance question. A complete pre-engagement review typically runs restricted party screening alongside, not instead of, export control classification and research-security disclosure review. Institutions engaging in more than incidental international collaboration generally build these into a single coordinated intake process rather than three disconnected checks run by three different offices at three different times.
Frequently Asked Questions
Is restricted party screening legally required?
There is no single blanket federal statute that names “restricted party screening” as a mandatory institutional program. The underlying obligation is indirect: engaging in a prohibited transaction with a party on the SDN List, Entity List, or Denied Persons List, or exporting controlled items/technology to one, violates OFAC sanctions law or the EAR/ITAR regardless of whether the institution screened first. Screening is the practical due-diligence mechanism institutions use to avoid that violation, and it is also frequently a condition institutions accept in federal award terms, university export-control policy, or contractual representations to sponsors and vendors.
How often should an existing relationship be re-screened?
There’s no single federally mandated interval. Because the CSL’s source lists update daily, institutions with ongoing foreign-national appointments, subrecipients, or recurring vendors commonly re-screen periodically (for example, at each appointment renewal or subaward continuation) or use continuous-monitoring alerts from their screening software, rather than relying indefinitely on a single point-in-time check from onboarding.
What happens if a screen returns a confirmed match?
The transaction, appointment, or agreement is paused pending review by the export control officer and, typically, institutional counsel. Depending on the list and the underlying regulation, proceeding may require an OFAC license, a BIS export license, or may not be authorizable at all — the specific path depends entirely on which list produced the match and what the institution is trying to do with that party.
Do institutions need commercial screening software, or is a manual CSL search enough?
The CSL Search tool at trade.gov is free and sufficient for occasional, low-volume screening. Institutions running high volumes of appointments, subawards, and vendor onboarding — or wanting continuous monitoring against daily list updates rather than point-in-time checks — commonly license commercial screening software instead, but the software is an efficiency layer over the same underlying public lists, not a different compliance standard.
Does a clean restricted party screen mean an activity is export-compliant?
No. It means the specific party checked does not currently appear on a restricted-party list. It says nothing about whether the item, software, or technical data involved is export-controlled, or whether a foreign funding source triggers a research-security disclosure obligation — both are separate questions requiring separate review. See export-controlled research.
