A US-headquartered technology business prepares to ship control-monitoring hardware to a distributor in South-East Asia. The item was classified years ago; the end-use certificate looks clean. Then counsel reviews the file and finds the classification was based on an outdated Commerce Control List (CCL, the master schedule of controlled items under the Export Administration Regulations) entry. The item's parameters have since shifted it into a more sensitive classification. The shipment is delayed, a licence application backlog begins, and the relationship with the distributor is strained. This is not an unusual situation. It is the predictable result of treating an export-licence determination as a one-time exercise rather than a living obligation.
An export-licence determination under the BIS / EAR (the Bureau of Industry and Security's Export Administration Regulations, the principal US export-control regime for dual-use and commercial goods) is a multi-step legal analysis: classify the item, identify the destination and end-user, assess the applicable controls and exceptions, and either confirm no licence is required or prepare and submit a licence application. As of May 2026, the regime sits under the Export Control Reform Act and is administered by BIS. The determination is not a bureaucratic formality – it carries criminal and civil exposure when wrong.
This guide walks through each step of the process, identifies the most consequential pitfalls, and flags where the BIS / EAR analysis intersects with UK, EU, and other regimes that a cross-border exporter may face simultaneously.
Step 1: Classify the item on the Commerce Control List
The first step in any export-licence determination is to establish the item's Export Control Classification Number (ECCN, the alphanumeric code on the CCL that identifies the controlled characteristics of an item and the reasons for control). If an item has no ECCN – because it is not on the CCL – it is designated EAR99, the residual category. EAR99 items carry the lightest licensing burden, but they are not unconditionally free to export.
Classification is grounded in the item's technical parameters: performance thresholds, materials, software functions, and design characteristics. The CCL is organised into ten categories and five product groups; the right entry depends on those technical specifics, not on the item's commercial name or marketing description. In our experience, in-house teams frequently rely on a manufacturer's self-classification rather than conducting an independent review. That reliance is operationally convenient but legally precarious. The exporter – not the manufacturer – bears the responsibility under the EAR.
Where classification is genuinely uncertain, BIS offers a formal route: a Commodity Classification request, submitted to the agency for a binding determination. This takes time and should be factored into transaction timelines. For items that evolve through software or firmware updates, the classification must be re-evaluated each time the technical parameters change. A hardware item classified at one specification level may migrate to a different ECCN after an update.
Step 2: Identify the reasons for control and the destination
Once the ECCN is fixed, the exporter must identify the reasons for control attached to that entry and check them against the destination country. BIS organises reasons for control around categories such as national security, nuclear non-proliferation, missile technology, chemical and biological weapons, anti-terrorism, and crime control, among others. Each reason for control has its own country chart, and the intersection of the ECCN and the destination country on that chart tells the exporter whether a licence is required.
This step is where the multi-destination problem bites. An item may require a licence to one country under a national-security entry but ship freely to a neighbouring country under the same ECCN. A distribution agreement covering an entire region must be assessed destination by destination, not as a block. We regularly advise businesses that have prepared a single export-compliance assessment for a region and then discovered mid-transaction that two of the six destination countries required licences that had not been applied for.
The destination analysis also feeds the end-user and end-use check – which is Step 3 – because some controls apply regardless of destination whenever a prohibited end-use or end-user is involved.
Step 3: Screen end-users, end-uses, and restricted-party lists
Screening is mandatory and parallel to the CCL analysis. The EAR prohibits exports to parties on the Entity List (a BIS-administered list of foreign persons subject to specific export-licence requirements), the Denied Persons List (persons denied export privileges), and, through the OFAC connection, the SDN List (OFAC's Specially Designated Nationals and blocked persons list). An ECCN that would otherwise permit export to a given destination still requires a licence – or is flatly prohibited – if the end-user or end-use triggers one of these controls.
End-use screening goes beyond list-checking. The EAR imposes a general prohibition on knowingly facilitating exports for certain uses, including weapons of mass destruction programmes, regardless of whether any party is formally listed. A red-flag check is required: if the facts present warning signs that an end-use may be prohibited – unusual payment terms, a customer uninterested in maintenance contracts, a declared end-use that does not match the quantity ordered – the exporter must investigate before proceeding. Proceeding in the face of known red flags can eliminate the "without knowledge" defence in an enforcement action.
The cross-border dimension matters here. The UK's ECJU (Export Control Joint Unit) and the EU's dual-use rules each maintain their own restricted-party instruments. An exporter cleared under BIS screening may still face a UK or EU end-user concern if the supply chain passes through a UK or EU entity. The stricter prohibition governs: where multiple regimes are in play, the most restrictive applicable rule sets the floor.
The position above covers the standard workflow. Your specific facts – the item's function, the counterparty's corporate structure, the route through which the goods travel, the regimes triggered by intermediate jurisdictions – change the analysis materially. To discuss a classification or screening question with a member of our team, contact Calder & Vance at info@caldervance.com.
Step 4: Assess licence exceptions before applying for a licence
Before filing a licence application, the exporter must assess whether a licence exception (a regulatory authorisation under the EAR that permits a controlled export without a case-by-case application) applies. The EAR contains a significant body of exceptions, including those available for technology and software, civil end-users, strategic trade authorisation, and temporary exports, among others.
Exceptions are powerful tools and frequently under-used. In our cross-border practice, we have seen exporters apply for full licences – waiting months for a decision – when a well-established exception would have permitted the export immediately. Equally, we have seen exceptions mis-applied: a business relying on an exception for which a condition – written assurance from the consignee, a destination restriction, a government end-user exclusion – was not met. Mis-application of an exception is treated by BIS the same way as a missing licence.
Two conditions are universal across exceptions: the exception cannot be used if a denial order covers the transaction, and the exporter must maintain the records that substantiate the exception's conditions. Record-keeping requirements under the EAR extend to a minimum period that practitioners describe as five years from the date of export; verify the current position before relying on it. The records must document the classification, the applicable exception, the destination, the end-user, and the basis for believing conditions were met.
Step 5: Prepare and submit the licence application where required
Where no exception applies and a licence requirement exists, the exporter files a licence application through SNAP-R, BIS's electronic submission system. The application must accurately state the ECCN, the item's technical specifications, the value of the proposed export, the end-user, the end-use, and any supporting documentation the agency will require to assess the request.
Accuracy is paramount and legally consequential. The EAR's prohibition on false statements to BIS applies to the application itself. A material mis-statement – even one that does not ultimately benefit the exporter – carries its own enforcement risk.
Processing times vary by item sensitivity, end-use, and the referring agencies involved. National-security and proliferation-sensitive applications may be referred to the State Department, the Department of Defense, the Department of Energy, or the intelligence community, each of which has its own review track. Timelines under inter-agency review can extend substantially beyond the initial BIS processing window. Exporters relying on the licence for a signed commercial contract should build realistic buffer periods, because a missed delivery obligation while an application is pending is a commercial problem BIS will not solve.
If a transaction has already been shipped without a required licence, or if a filing has returned an unexpected result, the time for corrective action is short. An early review of the options – including voluntary self-disclosure and the associated enforcement-mitigation credit – preserves routes that close as time passes. To discuss an urgent matter, contact us at info@caldervance.com.
Where does the BIS / EAR analysis differ from UK and EU export-control regimes?
The BIS / EAR operates on an extraterritorial basis (jurisdiction claimed by the US over items, technology, and software that incorporate more than a de minimis level of US-origin content, wherever they are located) that no other major regime matches in reach. The UK Export Control Order and the EU dual-use rules are primarily territorial: they apply to exports by UK or EU persons, from UK or EU territory, of UK- or EU-controlled items. The EAR can follow an item through multiple re-exports after it leaves the United States, imposing ongoing obligations on each successive exporter regardless of nationality.
On classification methodology, the UK and EU regimes track the Wassenaar Arrangement and other multilateral control lists. The CCL also tracks Wassenaar, but BIS periodically expands controls beyond the multilateral lists through unilateral action. An item that clears the EU dual-use list may still be controlled under the CCL. Conversely, an EU or UK exporter supplying US-origin goods must comply with the EAR even when the EU and UK controls permit the transaction. The prudent position is to run the analysis under all applicable regimes in parallel, treating the most restrictive outcome as binding.
The deemed export rule is a further BIS / EAR-specific dimension. Under the EAR, the release of controlled technology to a foreign national within the United States is treated as an export to the person's country of nationality. The UK and EU regimes have analogous but differently calibrated provisions. Where a business employs foreign nationals in roles involving controlled technology, a deemed-export licence analysis is required independently of any physical shipment programme.
For a deeper treatment of the deemed-export question, see our dedicated analysis at Deemed exports and technology under BIS / EAR.
Common pitfalls and when to involve counsel
The most consequential errors in export-licence determinations share a common feature: they look like compliance until an enforcement review. Outdated classifications, untested exceptions, incomplete end-user screening, and licence applications with inconsistent product descriptions are each individually correctable when caught early. They become serious enforcement issues when a pattern of errors emerges in an audit.
Five risk flags warrant prompt attention by specialist export-control counsel:
- A classification has not been reviewed since the item's technical parameters or software version changed.
- An exception is being applied to a transaction type or destination for which it was not designed.
- The end-user's corporate structure involves intermediaries in third countries not initially screened.
- A distributor agreement covers multiple destinations but the licence analysis was performed only for the primary market.
- A shipment has occurred and a subsequent review suggests the licence requirement may not have been met.
One persistent myth in this space is that a well-intentioned compliance error will be treated leniently as a matter of course. That is not the current enforcement posture. BIS weighs aggravating factors – value of the transaction, sensitivity of the controlled item, destination involved, whether the exporter was repeat-flagged – and can pursue civil penalties that accumulate quickly across a pattern of violations. A VSD (voluntary self-disclosure, a self-reported disclosure of apparent violations to BIS before the agency identifies them independently) can substantially reduce exposure but must be accurate and complete. Partial disclosures that understate the scope of the conduct attract their own scrutiny.
Is your current export-compliance programme designed around the BIS requirements that apply to your product lines, or around a generic checklist that predates your current technology stack? That distinction is worth examining before an export-control audit or an enforcement inquiry prompts the review.
Related practices
- Deemed exports and technology under BIS / EAR – classification and licence analysis for technology released to foreign nationals.
- Export-licence determinations: supplement and advanced topics – further treatment of exceptions, re-export controls, and multi-regime analysis.
- Export-licence determinations: practical compliance guide – programme design, record-keeping, and audit-readiness for exporters.