A logistics manager at an international NGO receives word that a consignment of medical diagnostic equipment is bound for a country subject to US export controls. The organisation has been operating in the region for years. But nobody checked whether the shipment needs a licence under the Export Administration Regulations ("EAR") – the US rules administered by the Bureau of Industry and Security ("BIS") that govern the export, re-export, and in-country transfer of dual-use and commercial items. The consignment is delayed at port. The relief operation stalls.
Humanitarian and NGO authorisations under the BIS / EAR provide a defined legal pathway for exporting controlled items in support of relief and development work, even to countries or end-users that would otherwise attract licence requirements. The key mechanisms are the humanitarian licence exception and, where that exception does not apply, a specific licence application to BIS. Determining which route applies requires classifying the items on the Commerce Control List and confirming the destination, end-use, and end-user against the relevant order requirements.
This guide walks through each step: from item classification and exception eligibility, through the specific licence application process, to the cross-border considerations that arise when UK, EU, or UN controls run alongside the EAR.
Step 1: Understand the governing authority and legal basis
The BIS / EAR regime derives its authority from the Export Control Reform Act and associated executive instruments, including IEEPA. BIS administers the EAR through the Commerce Control List ("CCL") and the Entity List. Every controlled item is assigned an Export Control Classification Number ("ECCN") – a product-specific code that determines which countries, end-uses, and end-users trigger a licence requirement.
For humanitarian work, two distinct BIS instruments matter most. First, the EAR contains a standing licence exception (a standing authorisation that permits a defined category of transactions without a separate application) specifically designed for humanitarian operations, commonly referred to as the humanitarian licence exception. Second, where the exception does not cover the transaction, a specific licence (a case-by-case authorisation to conduct an otherwise prohibited transaction) can be sought from BIS.
The legal basis matters at every stage. BIS decisions on specific licences turn on the statutory review criteria: the foreign-policy and national-security purposes of the relevant control, the likelihood of diversion, and the end-use and end-user. Humanitarian purpose is a material, positive factor – but it is not a blanket exemption. BIS retains full discretion to impose conditions, require reporting, or decline.
In our practice, the most common early error is treating "humanitarian" as a self-executing category. It is not. The regime requires proof of classification, end-use, and end-user at every step.
Step 2: Classify the items and map the control triggers
Before any licence decision can be made, the exporter must determine whether each item is controlled under the EAR and, if so, under which ECCN. Unclassified items – those that fall outside the CCL – are designated EAR99 and generally do not require a licence for most destinations. Many basic humanitarian supplies sit in EAR99. But medical equipment, communications technology, and certain vehicles may carry ECCNs that trigger controls depending on destination country and end-use.
Classification is the exporter's responsibility. BIS offers a formal route – the Commodity Classification request – for items whose classification is genuinely unclear. In our experience, NGOs frequently underestimate the time this adds to a programme timeline, particularly where equipment has multi-purpose components. Seek classification confirmation early, before shipment windows close.
Once the ECCN is known, the matrix of licence requirements can be assessed. The relevant columns on the CCL determine which Country Groups trigger a requirement. Destinations subject to comprehensive US controls face the most restrictive analysis. For controlled destinations, the humanitarian licence exception is the first mechanism to examine.
Step 3: Assess eligibility for the humanitarian licence exception
The humanitarian licence exception permits the export of certain items without a separate BIS application, provided a defined set of conditions is met. It is the fastest route where it applies. The conditions include restrictions on item type, value, end-use, and the identity of the consignee – and for some destination categories, additional requirements attach.
Is the exception available for your shipment? The critical questions are: Does the ECCN fall within the exception's item scope? Is the end-use confined to the permitted humanitarian activities? Is the consignee an eligible organisation – typically a government entity, an international organisation, or an NGO meeting the definition in the relevant provision? Has the exporter retained documentation to substantiate each of these conditions?
Where all conditions are met, the exception is self-executing. No BIS application is required. But the exporter must be able to produce the supporting records on demand. Failure to document the basis for relying on an exception is treated by BIS as a potential violation in its own right. Our compliance work regularly surfaces organisations that relied on an exception they could not evidence – a position that is difficult to defend in a subsequent review.
One practical note: the exception does not override other BIS order requirements. If the consignee or a party in the transaction appears on the Entity List, the Denied Persons List, or is subject to another BIS order, the exception cannot be used. A separate BIS authorisation – or in some cases a licence condition waiver – will be required.
Step 4: Apply for a specific licence where the exception does not apply
When the humanitarian exception is unavailable or uncertain, the exporter must apply for a specific licence through BIS. The application is submitted via the Simplified Network Application Process – Redesign ("SNAP-R"), BIS's online licensing platform. A complete application includes the item classification, the end-use statement, end-user documentation, a description of the humanitarian programme, and supporting materials from the consignee.
BIS reviews the application against the factors stated in the EAR: the nature of the item, the destination, the end-use, the end-user, and whether the stated humanitarian purpose is credible and verifiable. BIS may refer complex applications to an inter-agency review process involving the Departments of State and Defence. That referral extends the processing window significantly.
Processing times are not fixed by statute and vary materially by destination and item. For straightforward humanitarian applications to non-embargoed destinations, a decision may arrive within weeks. For high-control destinations or items with dual-use sensitivity, the timeline can extend considerably. Exporters running time-critical relief operations should factor in a realistic buffer. We advise clients not to assume best-case timing when a humanitarian operation depends on the licence being in place.
A well-constructed application materially affects the outcome. BIS does not always grant the most permissive licence available. An under-documented application may result in a narrower licence, a shorter validity period, additional conditions, or a referral back to the applicant. The application is, in effect, the submission on which BIS forms its view of the transaction.
In a recent matter, a development-sector organisation needed to export specialised water-treatment equipment carrying an ECCN with significant dual-use sensitivity to a destination subject to partial US controls. We assessed exception eligibility, confirmed it was unavailable for that item-destination combination, and prepared a specific licence application with a detailed humanitarian end-use statement, verifiable consignee credentials, and a programme delivery plan. BIS issued the licence with a limited set of conditions. The organisation shipped on schedule.
Step 5: Manage end-use and record-keeping obligations after authorisation
A BIS licence or exception does not close the compliance file – it opens it. Once an authorisation is in place, the exporter carries ongoing obligations that run for the life of the authorisation and, in many cases, for a defined period after the transaction is complete.
End-use assurance is central. If BIS has issued a specific licence on the basis of a stated humanitarian end-use, the exporter must have reasonable grounds to believe the items are being used as stated. A re-export or transfer to a different end-user without separate BIS authorisation constitutes a violation, even if the new use is itself humanitarian. The authorisation is item-specific, end-user-specific, and end-use-specific.
Record-keeping is a hard obligation, not a best practice. The EAR requires exporters to retain records of export transactions for a defined period. Records must include the classification basis, the authorisation relied upon, the end-use statement, shipping documentation, and any correspondence with BIS. In our experience, organisations under post-shipment review are most exposed where their records are incomplete or not retrievable within a short production window.
BIS conducts post-shipment verifications through its End-User Review Committee. A foreign end-user or consignee may receive a visit from a US government representative to confirm that the exported items are where the licence said they would be and are being used as stated. NGOs operating in difficult field environments should brief their in-country teams on this possibility.
How do BIS / EAR humanitarian authorisations compare with other regimes?
The EAR humanitarian licence exception has broadly equivalent mechanisms in the UK, EU, and Canadian regimes – but the detail differs in ways that matter for organisations operating across jurisdictions.
Under the UK Export Control Order administered by the Export Control Joint Unit ("ECJU"), controlled items destined for humanitarian operations may require a Standard Individual Export Licence ("SIEL") or may qualify under an Open General Export Licence ("OGEL") – the UK's standing authorisation equivalent to a BIS exception. ECJU licensing timelines are statutory in some cases. The item-classification system uses a different numbering structure, so an item that is EAR99 under the EAR is not automatically uncontrolled under UK rules. Cross-border operations that originate in or transit the UK must run a parallel ECJU assessment.
The EU dual-use regime operates under a Council Regulation that establishes its own control list and licence categories. EU member states administer national licensing decisions, which means that an authorisation from one EU authority does not automatically cover a re-export routed through a second member state. Humanitarian NGOs with procurement hubs in multiple EU member states frequently face this problem – a licence granted by one national authority does not travel with the goods.
Canada's Export and Import Permits Act administered by Global Affairs Canada includes specific humanitarian provisions, but the permitted categories and verification requirements differ from the EAR. As with the UK and EU systems, an EAR licence exception does not satisfy Canadian requirements, and vice versa.
The operational lesson: a multi-regime authorisation strategy is not additive. Each regime requires its own assessment, its own application (where required), and its own record-keeping. Organisations that obtain a BIS licence and assume they are covered globally have addressed only one of potentially several regulatory requirements. We regularly advise NGOs and their logistics partners on parallel applications across regimes for the same consignment.
UN Security Council arms embargoes can also overlay these national regimes. Where a Security Council resolution establishes an arms embargo on a destination country, the humanitarian carve-out under the UN consolidated framework must be read alongside the national controls. In some cases the UN carve-out is narrower than the national humanitarian exception; in others it is broader. The stricter prohibition governs.
Common risk flags and when to involve counsel
Several patterns consistently produce compliance risk in humanitarian licensing under the BIS / EAR. Recognising them early reduces the chance of a violation and preserves the exporter's ability to engage with BIS constructively.
The first risk flag is misclassification. An item that should carry an ECCN is incorrectly assumed to be EAR99. The humanitarian exception does not apply to controlled items, and an export made in reliance on an incorrect EAR99 determination may constitute an unlicensed export.
The second is end-user drift. A consignee that was accurate at the time of application changes its operational structure, enters a partnership arrangement, or sub-grants equipment to a third party. The original licence covers the original end-user. Any transfer requires fresh BIS authorisation or falls outside the scope of the licence.
The third is list exposure. A party to the transaction – not necessarily the direct consignee, but a freight forwarder, a sub-grantee, or a field partner – appears on BIS's Entity List or OFAC's SDN List (OFAC's list of Specially Designated Nationals and blocked persons). BIS controls and OFAC controls are separate legal regimes with different authorities, but they interact. An item cleared under a BIS licence may still be prohibited by an OFAC restriction if a sanctioned party handles it.
The fourth is documentation failure. The organisation can show that it had a good reason to believe it was compliant – but cannot produce the records to substantiate the basis on which the exception was used or the licence was relied upon. BIS enforcement guidance treats documentation failure as an aggravating factor in penalty assessments.
A common myth in this area is that because an operation is genuinely humanitarian, BIS will treat any procedural lapse leniently. That is not the current enforcement posture. BIS has signalled that humanitarian purpose is a mitigating factor in penalty calculation, not an immunity from enforcement. Procedural failures – unlicensed exports, reliance on an unavailable exception, failure to maintain records – are assessed on their own merits. The humanitarian intent of the organisation is relevant at the penalty stage; it does not change whether a violation occurred.
Involve counsel when: the item classification is uncertain; the destination is subject to comprehensive US controls; a party in the transaction has any record of regulatory concern; the organisation has already shipped and is uncertain whether the authorisation was valid; or BIS has made contact regarding a post-shipment verification.
A voluntary self-disclosure ("VSD") to BIS – an unprompted report of a potential violation – is a formal mechanism that can materially affect the outcome of an enforcement proceeding. It is not a casual step. The decision to file a VSD, the scope of what to disclose, and the timing are questions for which legal advice is strongly advisable before any communication with BIS.
The position above covers the standard case. Your facts – the items, the destination, the consignee, the transaction structure, and any list exposure – change the analysis. If a shipment is already in transit, or BIS has been in contact, an early review can preserve options that narrow with time.
For an assessment of your export authorisation needs or to discuss a BIS / EAR licence application, contact Calder & Vance at info@caldervance.com.
Related practices and resources
- Frozen account management under BIS / EAR – managing blocked assets and authorisation requirements for account access
- Humanitarian authorisation under BIS / EAR: advanced issues – deeper analysis of end-user controls, re-export, and post-shipment compliance
- Humanitarian authorisation under Canada's export-control regime – how Global Affairs Canada's requirements compare and when parallel applications are needed