A US-headquartered technology group decides to transfer software to an engineering partner in a third market. The item ships digitally. The in-house team assumes digital delivery is outside export-control rules. Three months later, a routine BIS audit uncovers the transfer. The question is no longer commercial – it is legal.
Export-licence determinations under the EAR (the Export Administration Regulations, administered by the US Bureau of Industry and Security) require a structured, sequential analysis: classify the item under the Commerce Control List (the CCL, the master list of controlled goods, software, and technology), identify the country and end-use destination, and then determine whether a licence exception applies or a formal licence must be sought. As of May 2026, BIS classifies items by Export Control Classification Number (ECCN) and enforces the EAR against both US-origin items and non-US items that contain a sufficient proportion of US-controlled content. A missed determination can trigger a significant civil penalty – or criminal referral to DOJ.
This guide walks through each stage of the determination process: from item classification through end-use screening, licence-exception mapping, and application submission, with cross-regime comparisons at each stage for businesses operating under both US and UK or EU controls.
Step 1: Establish whether the EAR applies to your item
The EAR applies to any item that is subject to the EAR – a defined category that extends beyond goods originating in the United States to include foreign-made items incorporating US-controlled content above the applicable de minimis threshold and foreign-produced items that are the direct product of certain US technology or software. The first task is to confirm that the item falls within this scope.
Three questions govern the initial scoping check. Does the item have a US origin or was it manufactured on US-controlled equipment? Does it incorporate controlled US-origin content above the threshold? Is it the direct product of controlled US-origin technology? If the answer to any of these is yes, the EAR reaches the item regardless of where it physically sits.
In our cross-border practice, the most frequent gap at this stage is the assumption that a product assembled entirely outside the United States is automatically outside EAR jurisdiction. That assumption is wrong wherever US technology was used in the production process or where US components contribute above the de minimis percentage. For businesses with mixed supply chains, a jurisdiction-mapping exercise is the only reliable starting point.
UK and EU export-control regimes each have their own jurisdictional triggers, built around the physical location of the goods and the residency of the exporter rather than the nationality of the technology. A compliance counsel advising on parallel UK ECJU and EU dual-use obligations should map all three triggers at once: they do not overlap perfectly, and a gap in one regime does not create a gap in the others.
Step 2: Classify the item under the Commerce Control List
Once EAR applicability is confirmed, the item must be classified against the CCL, and the result – the ECCN – determines every subsequent step in the determination. The CCL organises items into ten product groups across five technology and industry categories; each ECCN carries a set of control reasons and a corresponding list of countries to which the control applies.
Classification is the stage that rewards precision. Each ECCN has technical parameters – performance thresholds, materials specifications, function descriptors – and an item either meets them or it does not. Where the item clearly falls below the thresholds for any ECCN, it is classified as EAR99: subject to the EAR but not controlled for most destinations. EAR99 is not a licence exemption for embargoed countries or end-uses; it simply means the item has no ECCN.
When classification is genuinely ambiguous – and it often is for dual-use software or components designed to multiple specifications – the correct route is a Commodity Classification Automated Tracking System request to BIS, or, for technology, a formal classification request. In our experience, businesses that self-classify ambiguous items without a defensible written analysis are in a worse position in an enforcement inquiry than those who sought BIS guidance and received an adverse classification, because at least the latter can demonstrate good faith.
The EU dual-use regulation and the UK Export Control Order use parallel but not identical control lists. Items controlled under the EU Annex I or the UK Strategic Export Controls lists may not carry an equivalent US ECCN, and vice versa. A sanctions lawyer or export-control adviser comparing the three regimes will frequently identify mismatches that create either an unexpected control or an unexpected gap.
Step 3: Check the Country Chart and identify the applicable restrictions
With an ECCN confirmed, the Country Chart translates the control reason attached to that ECCN into a licence requirement for the specific destination country. The EAR's Country Chart maps each control reason (national security, missile technology, chemical and biological weapons, crime control, and others) against countries in groups from A through E; the combination of ECCN, control reason, and country group tells you whether a licence is required.
Country group designations matter practically. Countries in group E:1 and E:2 are subject to the most restrictive treatment; countries in group A:5 or A:6 are eligible for certain strategic trade authorisations. Destinations not individually listed still occupy a default country group, and many licence exceptions are unavailable for certain country groups regardless of the ECCN.
What happens when the Country Chart shows no licence requirement for the destination? The determination is not yet complete. Even where the Country Chart shows no licence requirement, the prohibited end-uses and prohibited end-users described in the EAR can reinstate a requirement independently of the country classification. This is a step that automated screening tools frequently skip.
Cross-border note: UK and EU regimes do not use a country-chart model. The UK uses a system of open general export licences keyed to specific destination and commodity groupings, while the EU dual-use rules create a baseline prohibition with licence exceptions for certain intra-community and allied-destination transfers. A business exporting the same dual-use item from both a US and a UK entity must run both analyses in parallel – the outcomes can differ.
Step 4: Screen for prohibited end-uses and restricted parties
End-use and end-user screening is a mandatory, standalone step in the EAR determination: even where the Country Chart shows no licence requirement, a transaction is prohibited if the exporter knows or has reason to know that the item will be used in a prohibited activity, or if the buyer or any intermediary appears on a restricted-party list.
The key restricted-party instruments under the EAR are the Entity List (parties subject to a licence requirement for all items), the Denied Persons List (parties with whom exports are prohibited), and the Unverified List (parties whose bona fides BIS has not been able to confirm). An item that would otherwise be EAR99 requires a licence if the buyer is on the Entity List.
Prohibited end-uses under the EAR include activities connected with weapons of mass destruction, certain military end-uses, and activities detailed in the military end-use and military end-user controls, commonly called MEU controls. The MEU controls have been expanded significantly over recent years and, as currently in force, apply to a broader range of items and destinations than earlier editions of the rule – verify the current scope before relying on prior classifications.
In a recent matter, a manufacturing business had correctly classified its product as EAR99 and confirmed that the Country Chart showed no licence requirement for the destination. The transaction was nonetheless blocked when a due-diligence review identified that an intermediate distributor appeared on the Entity List. The product itself was unrestricted; the distribution channel was not. This pattern – clean item, restricted intermediary – is among the most frequent red flags we encounter in export-control diligence work.
OFAC's SDN List is a separate instrument from BIS's restricted-party lists, but a transaction that is clear under the EAR may still be blocked under OFAC sanctions. Both checks must be run; the stricter prohibition governs.
Step 5: Determine whether a licence exception applies
Where the analysis at Steps 2–4 identifies a licence requirement, the next question is whether the transaction qualifies for one of the EAR's licence exceptions – defined authorisations that permit controlled exports to proceed without a case-by-case licence application. Licence exceptions are narrowly defined; eligibility must be confirmed against the specific terms of each exception for the specific ECCN, destination, and end-use.
Commonly relevant exceptions include those covering temporary exports for repair, items for personal use, certain shipments to government end-users in allied countries, and technology sharing within controlled groups. The Strategic Trade Authorisation exception permits certain exports to close allies under specific conditions; eligibility depends on both the destination country group and the ECCN. For technology transfers, the Technology and Software – Unrestricted exception applies to publicly available technology, but the publicly available threshold under the EAR is defined more narrowly than many practitioners assume.
What exporters often miss is that a licence exception does not remove the obligation to maintain records of the determination and the basis for claiming the exception. Records must be kept for a defined period under the EAR – and, as a general rule of thumb confirmed by practitioners, five years is the standard retention benchmark for export-control documentation across US, UK, and EU regimes, though the applicable instrument should always be verified. An undocumented claim to a licence exception is indistinguishable from no claim at all in a BIS audit.
Where no licence exception is available, the only lawful route is a formal licence application to BIS. Applications are reviewed against the licensing policy applicable to the item, the destination, and the end-use; some items are subject to a presumption of denial for certain destinations, while others carry a case-by-case review standard. An experienced compliance counsel will assess the realistic licence-policy outcome before investing in a full application.
Step 6: Prepare and submit the licence application, or document the exception
If a formal BIS licence is required, the application is submitted through the Simplified Network Application Re-engineering system. The application must describe the item, the quantity and value, the end-use, the end-user and all intermediate parties, and any supporting technical documentation. BIS may refer the application to other agencies – including the Departments of State and Defense – and the review timeline varies by item and destination.
The application package is more than a form. BIS reviewers are looking for coherent consistency between the item description, the stated end-use, the counterparty profile, and the ECCN. Discrepancies – even inadvertent ones – can prompt a request for additional information that extends the timeline materially or, in some cases, triggers a referral to the Office of Export Enforcement. In our experience, applicants who submit a well-structured technical narrative alongside the form receive fewer additional-information requests than those who rely on the form fields alone.
Where the determination concludes that a licence exception applies, the work is documenting the analysis: a written record identifying the ECCN, the applicable exception, the basis for eligibility, the destination, and the end-use. That record belongs in the transaction file before the shipment or transfer occurs – not reconstructed afterwards.
UK and EU parallel obligations: a business that exports the same item from a UK entity will need an ECJU licence or will need to document reliance on an open general export licence. The documentation requirements differ in structure from BIS's, but the underlying discipline – classify, check, document – is common to all three regimes.
The position above covers the standard determination pathway. Your specific facts – the item's technical parameters, the supply chain structure, the destination, the end-user's profile – change the analysis at every step. For a structured review of your classification position or a licence application, contact Calder & Vance at info@caldervance.com.
Where do most export-licence determinations go wrong?
The most consistent failure mode is treating the determination as a single-step screening exercise rather than a sequential analytical process. An item cleared at Step 2 (classification) can still require a licence at Step 3 (country chart) or Step 4 (end-use / end-user). Stopping the analysis early – after confirming the ECCN but before running the country chart and the restricted-party screen – is the pattern behind a significant proportion of the violations we see in enforcement-defence mandates.
A second recurring problem is stale classification. An ECCN assigned three years ago to a product may not reflect design modifications that have taken the item across a performance threshold. BIS does not notify exporters when a product crosses a threshold; the obligation is on the exporter to review classifications when the product changes. Have you built a classification-review trigger into your product development process?
Third: the deemed export risk. A deemed export occurs when controlled technology is disclosed to a foreign national within the United States, because the EAR treats that disclosure as equivalent to an export to the individual's home country. Many businesses have well-managed physical-goods programmes but entirely unmanaged technology-sharing practices in their engineering teams. The deemed-export obligation applies to technology at the same ECCN level as the physical item – and it applies in an office meeting, not just at the shipping dock.
If a transaction has already been flagged, or a shipment has already departed without a licence determination on file, early review is critical. Options that are available before an enforcement notice is received narrow significantly after one arrives. For a confidential review of a potential violation, contact us at info@caldervance.com.
Cross-regime comparison: how does BIS / EAR differ from UK and EU controls?
BIS / EAR export-licence determinations differ from UK and EU equivalents in three structurally important ways: jurisdictional reach, list architecture, and licence-exception design. Understanding where the regimes diverge is essential for any business with a multi-jurisdiction export programme.
On jurisdictional reach, the EAR applies on the basis of item origin and content, not exporter location. A German company exporting a non-US product has no BIS obligation unless the item crosses one of the EAR's jurisdictional triggers. The UK Export Control Order and the EU dual-use regulation apply primarily to exporters established or operating from within those jurisdictions and to items physically located there. In practice, this means that a US company exporting via a UK subsidiary must run a BIS analysis on the item and a UK analysis on the act of export from the UK – two distinct determinations, potentially two licences.
On list architecture, the EAR's CCL and ECCN system provides a single reference point for both the control reason and the applicable country restrictions. The UK Strategic Export Controls lists and the EU Annex I are structured differently: they reference the same Wassenaar Arrangement, Australia Group, and MTCR control lists, but the national implementations carry differences in scope and in the treatment of software and technology transfers. An ECCN that maps cleanly to an EU dual-use entry may not map to its UK equivalent after the UK's post-2020 divergence from EU rules.
On licence exceptions, the EAR's system of named exceptions (Technology and Software – Unrestricted, Strategic Trade Authorisation, and others) has no direct equivalent in the UK regime. The UK uses open general export licences (OGELs) that allow certain categories of goods to be exported without a case-by-case application, provided the exporter registers. The conditions attached to OGELs differ from those attached to EAR exceptions, and a transaction eligible for an EAR exception may require an OGEL registration in the UK. The stricter position governs where both regimes apply.
For businesses with operations in both the United States and the European Union or the United Kingdom, we regularly advise on mapping the EAR determination against the parallel ECJU and EU dual-use obligations before any shipment decision is taken. The investment in a cross-regime classification matrix at the product-design stage avoids repeated one-off determinations later.
Related practices
- Deemed export and technology controls under BIS / EAR – advising on technology-sharing, ECCN classification, and foreign-national disclosure risk.
- Export-licence determinations guide, part 3 – further practical guidance on BIS licensing procedures and exceptions.