An exporter in the technology sector finalises a shipment of dual-use equipment destined for a buyer in a sensitive third market. The goods fall under the Export Administration Regulations ("EAR"), administered by the Bureau of Industry and Security ("BIS"). A licence exception covers most transactions – but not this one. Without a specific licence (a case-by-case BIS authorisation to export, re-export, or transfer an item that no exception covers), the shipment cannot lawfully proceed. Getting the application right determines whether the business ships or stalls.
Specific licence applications under BIS / EAR are submitted through BIS's SNAP-R online system, require a complete commodity classification, end-use and end-user documentation, and a narrative that directly addresses BIS review criteria. As of June 2026, BIS processing times vary significantly by case complexity and the applicable Country Chart controls; an incomplete application restarts the clock entirely.
This guide walks through each step of the BIS specific licence application process, identifies where applications most commonly fail, and notes how the US regime compares to the UK, EU, and Canadian counterparts – a comparison that matters whenever the same transaction touches more than one jurisdiction.
Step 1: Confirm that a specific licence is actually required
A specific licence is required only after you have confirmed the item's classification, identified the end destination and end user, and exhausted all available licence exceptions. Skipping any of those checks leads to applications that BIS rejects or returns without review – and wastes weeks.
Start with the Export Control Classification Number ("ECCN"), the alphanumeric code that places an item on the Commerce Control List ("CCL"). The ECCN determines which countries, end uses, and end users trigger a licence requirement under BIS's Country Chart. If the item is EAR99 – meaning it does not appear on the CCL – a specific licence is rarely needed, though destination and end-use controls can still apply.
Once you have a confirmed ECCN, check each applicable licence exception. BIS publishes a structured set of exceptions covering categories such as technology and software for civil purposes, shipments to close allies, and temporary exports. If even one exception fits your facts, a specific licence application is unnecessary. In our experience, a significant share of applications arrive at BIS when an exception was available – a time cost that falls entirely on the exporter.
Only when classification is confirmed, no exception applies, and the Country Chart shows a "X" for your ECCN-and-destination combination, does a specific licence application become the right path.
Step 2: Classify the item and assemble the technical package
Accurate classification is the foundation of every successful BIS specific licence application; a wrong ECCN produces a wrong licence type, wrong review criteria, and a near-certain return of the application. If any doubt remains about the correct ECCN after consulting the CCL, a commodity classification request submitted to BIS through SNAP-R provides an official determination.
The technical package must demonstrate exactly what the item is, what it does, and the parameters that place it where it sits on the CCL. For hardware, that means specification sheets, performance data, and any controlled technology that accompanies the item. For software and technology, it means a functional description, the algorithms or capabilities at issue, and the parameters that control levels address.
A common error at this stage is conflating the Export Control Classification Number with the item's customs harmonised-tariff code. They are different systems. ECCN classification governs BIS licensing; the HS code governs customs duties and import clearance in the destination country. Both are needed, but mixing up their functions produces filings that satisfy neither authority.
Where the item involves cryptography, military end-use review criteria, or items on the Entity List – BIS's list of parties subject to specific licence requirements regardless of item classification – the classification assessment requires additional scrutiny. Counsel experienced in BIS / EAR classification is worth engaging before, not after, the SNAP-R submission.
Step 3: Conduct end-user and end-use due diligence
BIS evaluates not just what is being exported but where it is going, who will use it, and for what purpose; a strong classification package paired with inadequate end-user diligence produces a denial or, worse, a licence that BIS later revokes. This step is where many applications fail.
At minimum, the applicant must screen the end user against BIS's Denied Persons List, the Entity List, the Unverified List, and OFAC's SDN List (OFAC's list of Specially Designated Nationals and blocked persons). A party on any of those lists either precludes the licence or dramatically narrows what BIS will authorise. The OFAC SDN check is not a BIS requirement per se, but a licence from BIS provides no protection against OFAC sanctions prohibitions – a point that cross-border counsel must address explicitly.
Beyond list screening, BIS requires a description of the end use and often a BIS-711 Statement by Ultimate Consignee and Purchaser. That form commits the end user to a specific use and to not re-exporting without authorisation. Obtaining a signed, accurate BIS-711 from an end user who is either unwilling to complete it or who completes it with inconsistent information is itself a red flag that BIS reviewers will catch.
In our cross-border practice, we see the end-use verification stage treated as a formality. It is not. An exporter who ships on a BIS licence issued on the basis of inaccurate end-use information bears legal exposure whether or not it was the end user who supplied the incorrect information.
Step 4: Submit through SNAP-R and address BIS queries
All BIS specific licence applications are submitted electronically through the SNAP-R portal; paper submissions are not accepted for standard licence applications, and a SNAP-R account registration should be completed before the export opportunity arises, not after it has been identified. Account setup is straightforward but takes time.
The SNAP-R application itself captures the applicant's details, the item's ECCN and description, the destination country, the end user, the end use, the value of the transaction, and a licensing narrative. That narrative is the part of the application that applicants most frequently underestimate.
The licensing narrative must directly address the review policies applicable to the item's ECCN. BIS reviews dual-use items against different policy standards depending on the technology, the destination, and the end use. For items with nuclear, biological, chemical, or missile end-use concerns, the policy standard is considerably more demanding. A narrative that describes the commercial rationale without addressing the applicable policy criteria will prompt a return or a query.
Once submitted, BIS may issue a request for additional information ("RFI"). The RFI is not a denial. It is a formal request for clarification, additional documentation, or an expanded end-use explanation. An RFI should be answered fully and promptly. A partial or late response extends processing time and – in BIS's practice – can lead to a denial on grounds of inadequate documentation.
Processing timelines depend on the review tier, the destination country, and whether inter-agency referral is triggered. Inter-agency review – where BIS consults the Departments of State, Defense, or Energy – adds time. Where a timeline is commercially critical, tracking the application's status through SNAP-R and maintaining regular, professional correspondence with the BIS licensing officer assigned to the case keeps the matter moving.
How does BIS / EAR differ from other licensing regimes?
The BIS / EAR specific licence application sits within a US framework that is more granular in its item-classification architecture than most comparable regimes, and more extensive in its extraterritorial reach. Understanding those differences is essential for any exporter operating across multiple jurisdictions.
Under the UK regime, the Export Control Joint Unit ("ECJU") processes export licence applications through the SPIRE system. The UK's dual-use list closely mirrors the EU's following retained EU law, but ECJU assessment criteria and processing timelines differ from BIS. In our experience, ECJU applications for identical items often require a separate narrative approach because the policy considerations that drive UK licensing decisions – while similar at the technical level – are applied through different administrative guidance.
The EU's dual-use rules operate through both a Union General Export Authorisation (which covers defined destinations without a case-by-case application) and individual national competent authorities for specific licences. A company that holds an EU-level general authorisation has not thereby satisfied BIS; the systems are parallel and non-substitutable.
Canada's export control regime, administered by Global Affairs Canada ("GAC"), uses a permit structure that differs from the US licence architecture, and Canadian permit conditions may be narrower or broader than a corresponding BIS licence for the same shipment. Where a transaction involves a Canadian parent, subsidiary, or re-exporter, a BIS licence alone does not address GAC permit requirements. Our guide on specific licence applications under the Canadian regime sets out the comparable GAC process.
The critical cross-border point is this: BIS's de minimis rules and foreign direct product rules extend US export-control jurisdiction to foreign-produced items that incorporate or are derived from US-origin technology or software above defined thresholds. A European manufacturer producing goods that incorporate US-controlled technology may require a BIS re-export licence even where the goods never enter the United States. That extraterritorial reach is wider than the comparable jurisdictional rules under ECJU or the EU regime. Whether it applies to your product is determined by the ECCN of the US content and the destination of the final item.
Common mistakes and risk flags
The most common failure point in BIS specific licence applications is a licensing narrative that does not engage with BIS policy review criteria; applicants describe the deal but do not address why BIS should approve it against the applicable export policy for that ECCN and destination. A well-prepared narrative anticipates the examiner's objections and resolves them on the page.
Several other risk flags appear consistently:
- Incomplete end-user documentation. A BIS-711 that is unsigned, undated, or describes an end use that is inconsistent with the stated application raises immediate concerns. BIS reviewers are experienced at identifying internal inconsistencies.
- Stale screening. Screening the end user once at the start of the application and not again before shipment misses the possibility that a party is designated between application and licence use. Licences typically authorise multiple shipments over a period; each shipment requires a fresh check.
- Treating BIS approval as sanctions clearance. A BIS licence covers BIS's export-control requirements. It does not authorise a transaction that would violate OFAC sanctions. Both checks are required, and they run on different lists under different legal authorities.
- Under-documenting re-export and retransfer. Where the item may be onward-shipped by the foreign buyer, the BIS licence must address re-export and retransfer conditions. Ignoring these conditions produces a licence that the foreign buyer cannot lawfully use for its commercial purpose.
- Missing Entity List screening. The Entity List changes frequently. A party that was clear at application time may be listed before the licence is used. The licence does not automatically override an Entity List requirement added after it was issued.
A practical myth worth addressing: some exporters believe that a BIS licence, once granted, provides a permanent safe harbour for all shipments to the same buyer. It does not. A licence is a conditional authorisation subject to the specific facts set out in the application. Material changes to the end user, end use, quantity, or route require either an amendment or a fresh application. In our practice, the assumption that an existing licence covers a changed transaction is one of the most reliable routes to an apparent violation.
The position above covers the standard application path. Your facts – the ECCN of the item, the destination, the end user's profile, and any US-origin content in a foreign-manufactured product – change the analysis materially.
For a confidential review of your BIS licensing requirements or to assess whether a specific licence is the right route for your transaction, contact Calder & Vance at info@caldervance.com.
When to involve sanctions and export-control counsel
Counsel should be engaged before the SNAP-R submission is filed – not after a return or a denial. BIS denials are published on the agency's website, and in cases involving apparent violations they are referred to BIS's Office of Export Enforcement. A denial after a poorly prepared application is a different problem from a classification question resolved before submission.
The trigger points that consistently warrant counsel are:
- Any item with dual-use potential relating to nuclear, biological, chemical, or missile end uses, regardless of the stated end use by the buyer
- End users in destinations subject to heightened BIS review or US sanctions programme overlap
- Transactions where the item incorporates US-controlled content under the foreign direct product rules
- Licence applications that have already been returned or denied and are being resubmitted
- Transactions that involve both a BIS licence requirement and an OFAC sanctions assessment, requiring coordination across two regulatory regimes
- Any matter where the exporter is uncertain whether the ECCN used is correct
If a transaction has already been flagged, or a filing has been refused, an early review can preserve options that narrow significantly with time. The window to seek reconsideration of a BIS denial, or to correct an apparent violation through a voluntary self-disclosure ("VSD") before BIS opens an investigation, is real but not indefinite.
For a review of a returned application or to discuss the voluntary self-disclosure process, write to info@caldervance.com.
Related practices
- Frozen account management under BIS / EAR – managing blocked-property and account-freeze situations under the US export-control regime
- Specific licence applications under the Canadian regime – step-by-step guide to GAC export permit applications
- Canadian specific licence applications: extended guide – deeper analysis of Canadian permit conditions and cross-border interaction with BIS