An exporter receives a notice that its organisation – or a key supplier – has been added to the Entity List (the BIS register of parties subject to licence requirements under the Export Administration Regulations, "EAR"). Shipments stop. Banking relationships tighten. Contracts held in pipeline become unlawful to perform. The business asks the only question that matters: can this designation be challenged, and if so, how?
As of March 2026, judicial review of a designation under BIS / EAR rules follows a specific administrative-law path. The Bureau of Industry and Security administers the Entity List under the Export Control Reform Act and the EAR. An aggrieved party may petition the End-User Review Committee for removal, and – where the administrative route is exhausted – may seek judicial review of a final agency action in the federal courts under the applicable administrative-procedure standard. The threshold question is always whether the agency acted within its statutory authority and on a sufficient evidentiary basis.
This briefing sets out who administers the process, what the BIS / EAR regime prohibits once a designation is in place, how the removal and judicial-review procedure works, how the standard of review compares with the OFAC and EU approaches, and what risk flags an affected business must manage from the moment of listing.
Who administers the Entity List and what is its legal basis?
The Bureau of Industry and Security, within the US Department of Commerce, administers the Entity List under authority derived from the Export Control Reform Act and implemented through the EAR. BIS acts through the End-User Review Committee – a multi-agency body that includes representatives from the Departments of State, Defense, Energy, and Treasury – which makes the original listing decision and reviews removal petitions.
The EAR governs the export, re-export, and in-country transfer of items subject to US jurisdiction. When a party is added to the Entity List, exporters, re-exporters, and transferors anywhere in the world who deal in items subject to the EAR must obtain a licence before transacting with that party. Licence applications are reviewed under a policy that, in practice, results in denial for a significant proportion of listed parties – a point that makes the listing itself the operative prohibition for most businesses.
The legal basis matters for the review analysis. Because the Entity List is a regulatory mechanism created under statutory export-control authority rather than a sanctions designation under IEEPA or TWEA, the procedural path for challenging it differs from the OFAC route. It is administered within the executive branch's trade-control structure, and judicial oversight operates through the lens of administrative-procedure law rather than Treasury's licensing and designation framework.
In our cross-border practice, clients often conflate Entity List designations with OFAC SDN listings. They are distinct instruments, operated by different agencies, with different legal consequences, different review bodies, and different judicial-review standards. Getting that distinction right at the outset shapes every subsequent decision.
What does a BIS / EAR designation prohibit?
An Entity List designation imposes a licence requirement on all exports, re-exports, and in-country transfers of items subject to the EAR to the listed party, regardless of the item's Export Control Classification Number (ECCN – the classification that identifies an item's control status under the Commerce Control List) or whether it would otherwise qualify for a licence exception. For most listed parties, the applicable review policy is a presumption of denial, making a licence effectively unavailable in practice.
The reach of the prohibition is extraterritorial. Items "subject to the EAR" include goods, software, and technology that incorporate more than a de minimis proportion of US-controlled content, or that are the direct product of certain US-origin technology, regardless of where those items are located when the transaction occurs. A European manufacturer re-exporting a component that contains US-origin technology to an Entity List party triggers the EAR requirement – even if no US person is involved in the re-export.
That extraterritorial scope is where cross-border risk concentrates. A business in Singapore, Japan, or the UAE that receives an order from a listed party must assess whether the goods or technology are subject to the EAR before it ships. Failure to obtain the required licence, or reliance on an exception that does not apply, constitutes a violation even if the transaction is otherwise lawful under the applicable country regime. The stricter prohibition governs – and for items with US content, the EAR is frequently the stricter rule.
Separately, the Denied Persons List and the Unverified List carry different, though related, restrictions. The Denied Persons List imposes an outright prohibition; the Unverified List triggers a due-diligence obligation and eliminates certain licence exceptions. An affected business must map its exposure across all three lists, not only the Entity List.
How does the administrative-removal procedure work?
An Entity List party – or any person directly affected by the designation – may submit a removal or modification request to the End-User Review Committee. The petition should set out the factual and legal basis on which the listing criteria are said to have been met incorrectly or no longer apply. There is no prescribed form, but in practice a well-structured petition addresses each element of the listing determination directly and provides supporting documentation.
The End-User Review Committee reviews the petition and may grant removal, modify the designation, or deny the request. There is no public timeline published for this review, but affected businesses should treat the process as taking a significant period – commonly measured in months rather than weeks. During that time the licence requirement remains fully operative. Planning around a pending petition, without obtaining the required licences where lawful, carries the same legal risk as ignoring the designation.
A denial of the removal petition is an agency action. It is at that point that the question of judicial review arises. We regularly advise clients on the discipline of building the administrative record during the petition stage, because the record before the agency is, in most judicial-review proceedings, the evidentiary limit of what the court will consider. Introducing new material at the judicial stage is constrained; the petition must already tell the complete story.
The position above covers the standard case. Your facts – the goods, the ownership chain, the route, the regime in play – change the analysis materially. For an assessment of your exposure under the BIS / EAR rules, contact Calder & Vance at info@caldervance.com.
What is the judicial-review standard, and how does it compare with the OFAC and EU approaches?
Judicial review of a final BIS / EAR designation decision is available in the federal courts under the administrative-procedure standard applicable to final agency actions. The reviewing court asks whether the agency's decision was arbitrary, capricious, an abuse of discretion, or otherwise not in accordance with law – a deferential standard that gives the agency considerable latitude in its national-security and foreign-policy assessments.
That deference is the central difference from the EU approach. Before the EU General Court, an annulment action under the relevant Council Regulation requires the institution to produce evidence sufficient to justify the designation, and the Court conducts a substantive review of that evidence. The standard is not one of mere rationality but of proportionality. Designated parties have succeeded in annulment actions where the Council failed to meet its evidentiary burden – an outcome that is structurally far less common in the US federal-court context, where national-security and export-control determinations attract strong deference.
The OFAC delisting route sits between the two. OFAC's administrative-review process is the primary route; the agency's designations also attract significant deference in federal court, but the constitutional due-process arguments available in the OFAC context – particularly where the listed party is a US person – are somewhat more developed than in the Entity List context, where the focus is on the agency's regulatory authority over trade. Our colleagues advise on the OFAC approach in detail; see the judicial review of a designation under OFAC briefing and its companion piece on judicial review of an OFAC designation – procedural aspects for a full comparison.
Under UK law, a designation by OFSI under SAMLA is subject to challenge by way of judicial review in the High Court, and the court may apply a proportionality standard in cases engaging human-rights considerations. The UK standard therefore differs again from the US administrative-procedure approach. For a business listed across multiple regimes, the divergence in standards means that the most promising route – and the most efficient use of legal resource – must be assessed separately for each regime. One successful challenge does not automatically lift designations imposed by a different authority.
If a transaction has already been flagged, or an administrative petition has been refused, early counsel can preserve routes that close with time. Contact us at info@caldervance.com to discuss the options.
What are the principal risk flags once a designation is in place?
Once an Entity List designation takes effect, the risk environment for the listed party and its counterparties broadens rapidly. The following risk areas arise most frequently in practice.
- Supply-chain disruption. Counterparties subject to the EAR – including non-US businesses handling items with US content – must obtain licences or cease transacting. In our experience, most will cease transacting before a licence is sought, because the reputational and compliance cost of maintaining the relationship outweighs the commercial value for many. De-risking is the default.
- Banking and payment infrastructure. Financial institutions screening counterparties will flag the designation. Even where the banking relationship is not directly prohibited, correspondent banks may decline to process payments associated with a listed entity, creating practical disruption that compounds the legal restriction.
- Technology and software access. Cloud services, software licences, and technology transfers that involve items subject to the EAR require separate analysis. The scope of the restriction is broader than physical goods.
- Subsidiary and affiliate exposure. Subsidiaries and affiliates of a listed party may themselves face heightened scrutiny. Exporters and compliance teams assessing a transaction must map the corporate structure, not only the named entity.
- Parallel designations. A BIS / EAR listing is frequently accompanied by, or followed by, action under other US and non-US regimes. A party named on the Entity List may also face OFAC action, EU restrictive measures, or designation under the applicable country regime. Each carries its own prohibition and its own review procedure.
- Record-keeping obligations. Parties involved in transactions subject to the EAR carry record-keeping obligations. Those records are the foundation of any enforcement defence and of a voluntary self-disclosure.
Have you mapped the full exposure across all relevant regimes, or only the BIS / EAR dimension? In our experience, the greatest risk is not the designation itself but the assumption that managing one regime is sufficient.
How does the BIS / EAR regime interact with non-US export-control regimes?
The EAR does not operate in isolation. Any business involved in goods, software, or technology of mixed US and non-US origin must consider how the EAR interacts with the export-control regime in its home jurisdiction and in every jurisdiction along the transaction chain.
The EU dual-use rules impose their own licence requirements for controlled items exported from EU territory. An item that requires a BIS licence because of its US content may also require an EU export authorisation under the EU dual-use regulation, even where the EU alone would not have required a licence. The two sets of obligations run concurrently; satisfying one does not discharge the other.
Japan, Singapore, and the UAE each operate their own export-control regimes. Japanese export controls are among the most technically detailed outside the US and EU systems. Singapore's strategic goods controls align closely with multilateral control lists. The UAE's export and re-export controls apply to goods transiting through its free-trade zones, a route that is sometimes incorrectly assumed to be outside the scope of origin-country controls. In all three cases, the rule from the applicable country regime may be stricter than the EAR in specific categories, and the stricter prohibition governs.
For a business defending an Entity List designation while continuing to trade in third markets, the cross-regime analysis is not optional. A licence obtained from BIS for a specific counterparty does not authorise the export under the EU dual-use rules, nor does it satisfy the applicable country regime's separate requirements. Each regime must be addressed on its own terms.
We advise on the evidence package for a delisting challenge under the Australian regime as well as the US and EU routes, and we engage local counsel in the relevant jurisdiction where a matter extends beyond our primary coverage areas.
When should an affected business involve export-control counsel?
Counsel should be involved at the earliest practicable point – ideally before the removal petition is filed, not after it is denied. The administrative record is built during the petition stage, and that record is what a federal court will review. A petition drafted without legal input frequently leaves out precisely the arguments and documentation that would later be needed at the judicial stage.
There is a common assumption that Entity List challenges are rarely successful and therefore not worth pursuing. That is a myth. The End-User Review Committee does grant removal in appropriate cases – particularly where the original listing was based on information that has changed, where the stated basis for listing does not withstand factual scrutiny, or where the listed party has taken concrete remediation steps that address the Committee's concerns. The challenge is building and presenting that case correctly. A poorly constructed petition can foreclose the judicial route even where the underlying facts support removal.
The decision matrix runs broadly as follows. Where the designation is recent and no licence applications are pending, the priority is immediate triage: map the prohibited transactions, assess parallel-regime exposure, and decide whether to pursue removal or to apply for specific licences for essential transactions while the removal route is pursued. Where the designation has been in place for a period and a prior petition was denied, the analysis shifts to whether the grounds for judicial review are sufficiently strong to justify the cost and duration of federal-court litigation, and whether the EU or UK review routes – if the party has a European presence – offer a more effective parallel track.
Enforcement is the alternative scenario. Where a business suspects it has committed an apparent violation – by transacting with a listed party without a licence, or by mis-classifying an item – the question of voluntary self-disclosure (a VSD: a proactive disclosure of an apparent violation to BIS) arises. A timely and complete VSD can significantly affect the outcome of an enforcement proceeding. It is a decision that requires legal advice before any disclosure is made.
Related practices
- Delisting evidence package – Australian sanctions regime – building the evidentiary record for a removal challenge under the Australian autonomous-sanctions framework.
- Judicial review of an OFAC designation – how the OFAC administrative-review and federal-court routes work, and where they differ from the BIS / EAR process.