A US-listed supplier has just been removed from BIS's Entity List (the list of foreign parties to whom exports, re-exports, and transfers of items subject to the Export Administration Regulations require a licence). The relief feels immediate. Procurement resumes. Relationships restart. Yet within months the same party reappears – re-listed, often with a broader licence requirement than before. That pattern is not theoretical. It reflects a structural feature of how BIS manages the Entity List: removal is conditional, not permanent, and the conditions attach to conduct that continues after the ink dries on the removal notice.
Managing relisting risk under the BIS / EAR means building a sustained compliance posture that satisfies the expectations BIS attached to removal – because BIS monitors post-removal conduct and can re-list a party, or flag its trading partners, if those expectations are not met. The governing authority is the Bureau of Industry and Security, acting under the Export Control Reform Act and the Export Administration Regulations. No specific timeline for re-listing is fixed; the risk is open-ended and continuous.
This guide walks through the relisting mechanism, the obligations that survive removal, the cross-regime dimensions every exporter must consider, and the practical steps that reduce the probability of re-listing or mitigate its consequences.
How does BIS use the Entity List, and what triggers re-listing?
Re-listing occurs when BIS determines that a previously removed party has resumed, or never fully ceased, the conduct that produced the original listing. The Entity List is maintained by BIS as a tool of export control, designating parties that present an unacceptable risk of diversion or misuse of items subject to the EAR. Removal follows a petition process; re-listing does not require a fresh petition from BIS – it is initiated unilaterally.
The triggers that practitioners see most frequently cluster around three patterns. First, the removed party resumes procurement of controlled items through routes that bypass the licence requirements that were the basis of the original listing. Second, changes in ownership or corporate structure bring in affiliates or shareholders who themselves present concerns to BIS. Third, the removed party fails to implement the internal control undertakings, whether formal or informal, that supported the removal decision.
A fourth trigger is less visible but equally significant: the conduct of a trading partner. If a customer or supplier of the removed party engages in conduct that BIS links back – factually or analytically – to controlled items sourced from that party, BIS may treat the removed party as a knowing participant. In our cross-border practice, this is the trigger businesses most consistently underestimate. They focus on their own processes and overlook what their downstream customers are doing with the goods.
What obligations survive removal from the Entity List?
Removal from the Entity List does not restore the removed party to the same legal position as a party that was never listed; it creates a monitored status with continuing expectations that BIS may articulate in the removal notice or in associated correspondence. Understanding these obligations is the foundation of any relisting-risk management programme.
The central obligation is licence compliance. A removed party must obtain all licences required under the EAR for exports, re-exports, and in-country transfers of controlled items. This sounds obvious, but the practical difficulty is that the scope of licence requirements under the EAR depends on the classification of the item (its ECCN – Export Control Classification Number under the US Commerce Control List), the destination, the end-use, and the end-user. A removed party that does not classify its procurement inputs correctly will mis-identify its licence obligations – and that mis-identification can itself become a trigger for re-listing.
Beyond licence compliance, BIS expects a removed party to maintain records of its transactions in controlled items. The EAR's record-keeping requirements run for a defined period following each transaction. We regularly advise parties who have been removed from the Entity List to treat their record-keeping as a live audit file: every licence, every classification determination, every end-use certificate, and every screening decision should be documented in a form that BIS could review at short notice.
Screening obligations follow from the removal itself. A removed party should not supply controlled items to parties that are themselves on the Entity List, the Denied Persons List (BIS's list of parties whose export privileges have been revoked or denied), or OFAC's SDN List (the Specially Designated Nationals and blocked persons list). Failing to screen – or screening only at transaction initiation and not thereafter – creates a gap that BIS will notice if it reviews the party's records.
Step-by-step: building a post-removal compliance programme
A post-removal compliance programme is not a one-time exercise; it is a continuously maintained set of controls, each of which addresses a specific relisting-risk vector. The steps below reflect the sequence we work through with clients who have achieved removal and need to sustain it.
- Map the item inventory against the Commerce Control List. Every product, component, and technology that the removed party procures, produces, or supplies should be classified under the EAR. Classification determines licence requirements. Unclassified items are EAR99 by default, but that classification should be confirmed, not assumed. Where items sit in dual-use categories, a qualified export-control adviser should review the classification before procurement resumes.
- Establish a screening cadence – not just a one-off check. Screen all counterparties – buyers, suppliers, freight forwarders, financial intermediaries – against the Entity List, the Denied Persons List, the SDN List, and any other applicable lists at transaction initiation and at defined intervals thereafter. List updates occur frequently. A counterparty that was clear at contract signature may be listed by the time the shipment moves.
- Document the end-use and end-user for each controlled shipment. BIS expects that exporters and their trading partners know where controlled items go and what they are used for. End-use certificates and end-user statements are not mere formalities; they are evidence that a removed party is managing its obligations and is not a knowing participant in diversion.
- Review ownership and corporate structure for changes that affect EAR status. A change of beneficial owner, a new investor, or a reorganisation that brings in a party connected to a sanctioned jurisdiction can change the risk profile of the removed party significantly. Any such change should be assessed against BIS criteria before it completes.
- Establish a voluntary self-disclosure (VSD) protocol. A VSD is a disclosure to BIS of an apparent violation, made before BIS initiates its own investigation. BIS treats a timely, complete VSD as a mitigating factor in enforcement. A removed party that discovers an apparent violation – a shipment made without a required licence, a counterparty that subsequently appears on a restricted list – should assess immediately whether a VSD is appropriate. Acting promptly preserves options; delay narrows them.
- Conduct periodic internal reviews. At least annually, the compliance programme should be stress-tested: classification decisions reviewed, screening logic tested, record-keeping audited, and counterparty relationships assessed for any changes that were not flagged at the time. Where a matter has been handled by external counsel, the review should include an assessment of whether the programme still reflects the current state of the EAR and any BIS guidance issued since removal.
The position above covers the standard post-removal posture. Your facts – the goods, the markets, the counterparties, the corporate structure – change the analysis. If you are unsure whether a specific transaction or counterparty presents relisting risk, contact Calder & Vance at info@caldervance.com for an early assessment.
How does BIS / EAR relisting risk differ from other export-control and sanctions regimes?
The BIS Entity List mechanism has specific features that distinguish it from analogous restriction lists in other regimes – and those differences matter for any business operating across multiple jurisdictions. Cross-regime awareness is not optional; it is a component of effective relisting-risk management.
Under the EU's dual-use export-control regime, restrictions on specific end-users are imposed through catch-all controls and, in certain cases, through the EU's restrictive measures directly. The legal basis differs from the EAR: the EU framework does not maintain a single entity list with the same administrative-petition removal mechanism. A party that achieves removal from the BIS Entity List may still face export restrictions from EU member-state authorities on the same goods, to the same end-use, under entirely different legal instruments. The two outcomes are independent.
The UK, through ECJU, operates its own export licensing regime with catch-all powers that apply regardless of whether a specific end-user is listed. Following the UK's departure from the EU, the UK regime has developed its own guidance and enforcement posture. A removed party that trades with UK exporters must account for ECJU requirements alongside BIS requirements. The licences are separate; the analysis is separate.
OFAC sanctions add a further layer. An entity that has been removed from the BIS Entity List may still be designated on the SDN List or subject to OFAC's sectoral or other restrictions. BIS removal does not affect OFAC status. Practitioners advising on BIS matters note that the OFAC check is frequently the one that surprises clients – particularly where the removed party's shareholders or affiliates have any exposure to a jurisdiction subject to OFAC's sectoral measures. Does your counterparty-screening programme check OFAC in addition to the BIS lists? If not, the gap is material.
For businesses with operations in Singapore, the UAE, Japan, or Australia, local export-control and autonomous-sanctions regimes add further obligations. A removed BIS party that supplies goods into those markets must comply with the applicable country regime as well. In our cross-border practice, the most common gap we see is a compliance programme designed around BIS requirements that has not been mapped to the local regime of the end-market. That gap can create independent liability – and, where it results in a shipment that BIS identifies as linked to a problematic end-use, it can become a relisting trigger.
What are the most significant relisting risk flags in practice?
Risk flags are the observable indicators that a removed party's position is deteriorating and that re-listing has moved from a theoretical concern to an active probability. Identifying them early is what separates a manageable compliance issue from a crisis.
The first flag is a shipment of items with a dual-use classification to a jurisdiction or end-user that was associated with the original listing reason. BIS's analysis of the original listing will have identified a specific concern – proliferation, diversion, military end-use – and any transaction that maps onto that concern will receive heightened scrutiny even after removal.
The second flag is a change in ownership that brings in an investor connected to a jurisdiction or sector that BIS treats with scepticism. Investors from jurisdictions subject to broad US export-control restrictions can change the calculus even where the investor's ownership share sits below any formal threshold. BIS does not apply a mechanical ownership test equivalent to OFAC's 50 percent rule (OFAC's rule treating entities owned 50 percent or more by blocked persons as themselves blocked); it applies a broader assessment of who controls and benefits from the entity's activities. That assessment is more difficult to predict and requires careful pre-transaction analysis.
The third flag is a failure to resolve an outstanding customs or import-control matter in a third country. A finding by another jurisdiction's authority that a shipment involved a controlled item without proper authorisation will, in many cases, come to BIS's attention. Where that shipment involved items that were exported from the US, or items with US-origin content, the EAR's extraterritorial reach may bring the matter within BIS's jurisdiction regardless of where the export control violation was detected.
The fourth flag is a VSD that is incomplete. A VSD that discloses only part of the apparent violation – whether because the full scope was not investigated, or because disclosure was strategically limited – will be treated by BIS more harshly than no disclosure at all. If a VSD is the right response to an apparent violation, it must be thorough. The decision to file, and the scope of what is disclosed, requires legal advice before submission.
If a transaction has already been flagged, or if you have identified an apparent violation following removal from the Entity List, an early review can preserve options that narrow with time. Contact Calder & Vance at info@caldervance.com.
A common misconception: removal from the Entity List means the compliance obligation is over
The most consistent misconception we encounter in our practice is that Entity List removal is a clean break: the listing is gone, the compliance burden is lifted, and business can resume as if the listing never occurred. That reading of the removal mechanism is incorrect and operationally dangerous.
Removal does not erase the record of the listing. BIS retains knowledge of the conduct that produced the original designation. It retains the analytical framework it applied to that conduct. And it applies that framework to post-removal activity. A removed party that treats removal as a full discharge of its compliance obligations – rather than as the beginning of a monitored period – is in a significantly more exposed position than one that maintains its programme consciously and continuously.
A second element of this misconception is the assumption that the removal petition process, once successfully concluded, has resolved the underlying export-control risk permanently. Petition processes address a defined factual record. The EAR's export-control requirements do not become less demanding after removal; they remain in force and, in some cases, BIS may have identified additional areas of concern during the review process that inform its post-removal monitoring. We have acted for parties who, following removal, received informal BIS inquiries about specific shipments within a relatively short period. Proactive engagement – rather than waiting for BIS to contact the removed party – is almost always the more effective posture.
When should a business involve sanctions and export-control counsel?
Counsel should be involved at the point of removal – not after a problem has emerged. The post-removal period is when the compliance architecture is set, and the decisions made in that period determine whether the removed party maintains its status or faces re-listing.
There are, however, specific events that require immediate legal review. A change in beneficial ownership is one. Discovery of an apparent violation of the EAR – whether the violation involves a licence that was required and not obtained, a controlled shipment to a restricted party, or a record-keeping failure – is another. Receipt of a BIS inquiry, whether formal or informal, is a third. None of these events should be managed without legal advice.
The timing question is also relevant for businesses that are not themselves listed but that source from, or supply to, a recently removed party. The removed party's compliance posture affects the risk of its trading partners. If a supplier has recently been removed from the Entity List and your supply chain depends on that party, a review of the supply chain's EAR exposure – including classification, end-use controls, and screening – is warranted before procurement resumes at scale. This is especially important where the goods involved have dual-use characteristics or where the end-market is one that BIS monitors.
Related practices
- Delisting evidence package (Australia) – building a complete, documented case for removal under the Australian autonomous-sanctions regime.
- Managing relisting risk under Canada's sanctions regime – the GAC framework, removal conditions, and post-removal obligations compared.
- Managing relisting risk across jurisdictions – how concurrent listings under BIS, OFAC, OFSI, and the EU interact and what a coordinated response looks like.