An NGO prepares to ship medical diagnostic equipment to a field hospital in a country subject to US export controls. The goods are clearly humanitarian. The end-user is a registered non-governmental organisation with no sanctions exposure. Yet the shipment requires a licence under the Export Administration Regulations (EAR – the US export-control regime administered by the Bureau of Industry and Security, or BIS). Getting this wrong exposes the NGO, its donors, and its logistics partners to enforcement risk under some of the most rigorously applied export-control rules in the world.
Humanitarian and NGO authorisations under BIS / EAR operate through a structured set of licence exceptions and, where no exception applies, a formal licensing process before BIS. As of June 2026, the two primary pathways are targeted licence exceptions for specified humanitarian activities and a case-by-case specific-licence application to BIS's Office of Exporter Services. Choosing the right pathway depends on the classification of the item, the destination country, and the end-user's status under the applicable country regime.
This guide walks through the governing authority, the classification step, the two main authorisation pathways, the cross-border considerations that catch NGOs off guard, the most common compliance failures, and when to involve counsel.
Step 1: Understand the governing authority and legal basis
BIS administers the EAR under authority derived from the Export Control Reform Act and, for older controls, IEEPA. The EAR covers dual-use goods, software, and technology – items with both commercial and potential military or proliferation applications. Humanitarian goods – medical devices, food, certain personal protective equipment – may appear benign, but many carry an Export Control Classification Number (ECCN – the alphanumeric code under the Commerce Control List that determines licence requirements and available exceptions).
Not every humanitarian export is controlled. Items classified as EAR99 – the residual category for goods not specifically listed on the Commerce Control List – generally do not require a licence to most destinations. The critical first question is therefore always: what is the ECCN of every item in the shipment? Only once that is established can you identify what authorisation, if any, is required. In our experience, NGOs most frequently underestimate the classification step, treating it as an administrative formality rather than a legal determination.
BIS policy treats legitimate humanitarian assistance as a recognised interest. The regulatory structure contains specific provisions designed to facilitate it. But those provisions are not self-executing: the exporter must affirmatively invoke the correct authorisation, maintain the required records, and – where conditions attach – document end-use and end-user.
Step 2: Classify every item before selecting an authorisation pathway
Classification determines everything that follows. An item's ECCN is found by checking it against the Commerce Control List, which is organised by product category and technology parameter. For humanitarian shipments, the most relevant categories are medical devices and equipment, food and agricultural commodities, and communications technology.
Where an item does not appear on the Commerce Control List, it is classified EAR99. EAR99 goods face no licence requirement for most destinations and most end-users, though they remain subject to the EAR and can still be prohibited if the end-user appears on a restricted-party list – most notably BIS's Entity List (a list of foreign persons subject to enhanced licence requirements or presumption of denial) or the Denied Persons List (persons with export privileges revoked by BIS).
For items that do carry an ECCN, the licence requirement then depends on the reason for control (the "reason for control" column on the Commerce Control List) and the destination country. Some ECCN-controlled items are subject to controls because of missile-technology or chemical/biological-weapons proliferation concerns. Humanitarian purpose does not automatically lift those controls. This is the point at which many NGO compliance teams assume that because their mission is benign, the regulatory burden is lighter. That assumption is incorrect.
Practical classification steps for humanitarian exporters:
- Obtain the manufacturer's ECCN or request a commodity classification from BIS if the item is complex or novel.
- Confirm whether the item is subject to controls for anti-terrorism, national security, or proliferation reasons – each reason affects which exceptions are available.
- Screen every line item in the shipment separately; a single controlled item in a mixed humanitarian load changes the analysis for the entire shipment.
- Document the classification determination and retain records. BIS requires export records to be kept for five years from the date of export.
Step 3: Determine whether a licence exception covers the shipment
BIS licence exceptions are standing regulatory authorisations that permit exports without an individual licence application, provided all stated conditions are met. For humanitarian and NGO activity, two exceptions are particularly relevant: one targeting humanitarian donations of certain goods to specified recipients, and a broader exception for civil end-users in specified destinations.
The humanitarian donation exception covers items such as food, medicine, medical devices, and personal hygiene and sanitation goods donated without charge for the personal use of recipients. Conditions include that the goods are genuinely donated (not sold or bartered), that the donor retains no ownership interest, and that the recipient is not a prohibited party. The exception does not extend to every item an NGO might ship – communications equipment, for instance, frequently falls outside it.
A second set of exceptions covers exports to civil end-users in certain country categories, subject to anti-diversion requirements. These require that the exporter has no knowledge or reason to believe the goods will be diverted to a military, government security, or intelligence end-user – the civil end-user condition that the EAR imposes.
Exceptions carry conditions that must be satisfied for every shipment. An exporter cannot apply an exception once and assume it covers future transactions. Each shipment requires its own analysis. A common structural failure we encounter in practice is an NGO that correctly invoked an exception on a first shipment and then extended that analysis to subsequent consignments without re-checking the end-user, the item classification, or whether the destination's exception eligibility had changed due to a new Commerce Department rule or country-group reclassification.
The position above covers the standard case. Your facts – the counterparty, the goods, the route, the regime in play – change the analysis. For a review of whether a licence exception covers your specific humanitarian programme, contact Calder & Vance at info@caldervance.com.
Step 4: Where no exception applies – the specific-licence application to BIS
Where classification and destination analysis confirm that no licence exception is available, the exporter must apply for an individual specific licence (a case-by-case authorisation from BIS to conduct an otherwise controlled export) through the Simplified Network Application Process Redesign system, the US government's electronic export-licence portal. BIS is the issuing authority. In some cases, other agencies – including the State Department and the Department of Defense – are mandatory referrals and will review the application in parallel.
The application requires detailed identification of the exporter, each consignee and end-user, every item to be exported (by ECCN and technical specification), the stated end-use, the quantity, and the value. For humanitarian applications, supporting documentation typically includes:
- A description of the humanitarian programme and the organisation's mandate.
- Registration documents for the NGO in both the exporting and receiving country.
- An end-user statement or undertaking from the recipient confirming end-use and no onward transfer.
- Evidence of the recipient's not-for-profit or humanitarian status.
- Logistics details, including the freight forwarder and any intermediate transit points.
BIS processing times for humanitarian licences vary. Applications that are straightforward – EAR99-adjacent items, well-documented NGOs, transparent supply chains – are typically processed more quickly than applications involving higher-controlled items or complex end-user situations. In our cross-border practice, we have seen humanitarian licence applications resolved in a matter of weeks when the file is well-prepared; incomplete or under-documented applications extend the timeline substantially.
What is the realistic processing expectation? BIS does not publish a binding service standard for humanitarian cases. The honest answer is that processing is measured in weeks to months, not days. Programmes with time-critical delivery requirements need to factor this into their planning horizon.
If a transaction has already been flagged, or a filing is in progress and complications have emerged, an early review can preserve options that narrow with time. Contact Calder & Vance at info@caldervance.com for a confidential review.
How does BIS / EAR compare with other regimes for humanitarian authorisations?
Humanitarian authorisations under BIS / EAR are structurally similar to – but substantively distinct from – the licensing carve-outs available under OFAC, the UK's export control regime (administered by the Export Control Joint Unit, or ECJU), and EU dual-use controls. Understanding the differences is essential for any cross-border humanitarian programme.
OFAC versus BIS: OFAC and BIS operate parallel but distinct authorisation regimes. OFAC controls financial transactions and services; BIS controls goods, software, and technology. A humanitarian programme typically needs to clear both. OFAC maintains general licences for humanitarian assistance under most of its country programmes, authorising certain categories of financial transactions in support of non-commercial activity. Those OFAC general licences do not extend to BIS licensing requirements. An NGO that has confirmed OFAC cover for its financial transactions cannot assume BIS has authorised the underlying export.
UK ECJU: The ECJU administers Open General Export Licences (OGELs) that in some circumstances permit exports to humanitarian organisations without an individual application. The ECJU's approach to humanitarian end-use incorporates a record-keeping and compliance framework that differs in several respects from the EAR's conditions. The UK does not use the Commerce Control List; items are classified separately under the UK Strategic Export Control Lists. Dual-jurisdiction exporters – for instance, a UK subsidiary of a US parent shipping goods from the UK – must ensure compliance with both regimes independently.
EU dual-use controls: The EU's dual-use export-control regime, set by the relevant Council Regulation, also applies separately from BIS / EAR. EU member states have individual national licensing authorities. Unlike the EAR, the EU regime has no single central portal; applications go to the competent national authority of the exporter's member state. Cross-border humanitarian programmes originating in an EU member state are typically subject to that regime, not the EAR – unless the goods also have a US-origin component, in which case BIS / EAR de minimis rules may bring US controls into play even for the EU-origin shipment.
The de minimis rule: The EAR's de minimis provisions mean that foreign-origin goods incorporating more than a specified share of US-origin controlled content are subject to the EAR even when exported from a third country by a non-US person. For humanitarian programmes with supply chains that pass through the United States or incorporate US-manufactured components, this is a material compliance consideration. The rule extends BIS's reach extraterritorially – an aspect of the EAR that frequently surprises European and Asian NGO logistics teams.
The comparative picture matters because multi-jurisdictional humanitarian programmes often have activities in scope of two or more regimes simultaneously. Where those regimes produce conflicting or overlapping requirements, the stricter prohibition governs. We regularly advise international NGOs on exactly this intersection.
For guidance on humanitarian authorisations under the Canadian regime, see our humanitarian authorisation Canada guide and humanitarian authorisation Canada guide (part 2).
Step 5: Screening end-users and managing restricted-party risk
Licence exceptions and specific licences alike are voided if the end-user or any party in the transaction appears on a prohibited-party list. BIS maintains several such lists. The most consequential for humanitarian exporters are the Entity List, the Denied Persons List, and the Unverified List – the last of which signals that BIS has been unable to verify the end-user's bona fides through a pre-licence check or post-shipment verification.
Screening against BIS lists alone is not sufficient for a well-constructed humanitarian compliance programme. OFAC's Specially Designated Nationals and Blocked Persons List (the SDN List – OFAC's list of blocked persons and entities) must also be checked. So must the UN Security Council's Consolidated List. An end-user not on BIS lists may nonetheless appear on OFAC's SDN List, triggering an entirely separate set of prohibitions under the financial-sanctions regime.
Practical screening requirements:
- Screen all end-users, consignees, freight forwarders, and any intermediate parties against BIS restricted-party lists, OFAC's SDN List, and the UN Consolidated List before each shipment.
- Establish a documented process for handling partial name matches and transliteration variants.
- Re-screen for long-running programmes; lists are updated without advance notice, and a counterparty that was clear on first check may be designated before the next shipment departs.
- Retain records of each screening check for the BIS-required five-year retention period.
The Unverified List deserves particular attention. Where a prospective end-user appears on it, BIS's position is that the exporter has a heightened due-diligence obligation before proceeding. In our practice, we advise clients to treat an Unverified List hit as a stop and escalate point, not merely an additional paperwork step.
Risk flags and common compliance failures
Most BIS / EAR enforcement actions against humanitarian exporters do not arise from wilful misconduct. They arise from procedural failures that compound over time. What are the patterns we see most often?
The first and most common failure is classification by assumption. An NGO procurement officer identifies an item as "medical" and concludes it is freely exportable. The analysis stops there. No ECCN determination is made. No Commerce Control List check is run. The item turns out to carry an ECCN with national-security or anti-terrorism controls that preclude the most convenient exception.
The second failure is stale exception reliance. An export-control assessment is conducted for a programme at inception. Three years later, the programme is still running under the same analysis, but the item mix has changed, the destination's regulatory status has been revised, and one new item was added to the controlled list in the interim. The original assessment no longer covers the current shipments.
A third pattern is freight-forwarder delegation without oversight. NGOs frequently delegate export documentation to freight forwarders. A forwarder may be competent in commercial logistics but not in BIS compliance for controlled items. Errors in the Electronic Export Information filing, the end-user description, or the authorisation cited on export documents create an enforcement record even where the underlying transaction was lawful.
A fourth risk flag: diversion through transit countries. A shipment that leaves the United States for a first destination may require an end-use assurance not only for the primary recipient but for any transit point where goods could be diverted. BIS pays close attention to transit through jurisdictions with weak export-control enforcement. Anti-diversion clauses in contracts with logistics partners are a minimum; they are not a substitute for due diligence on the transit route.
Finally, incomplete or missing voluntary self-disclosure. Where an apparent violation is identified, a VSD (voluntary self-disclosure to BIS) is a recognised mitigating factor in enforcement proceedings. The decision whether to file a VSD, and how to frame it, requires counsel. Filing a VSD that is incomplete or that misstates the facts of the violation can worsen the outcome.
Step 6: Record-keeping, post-shipment verification, and ongoing programme management
Compliance under BIS / EAR does not end when the goods leave the country. The EAR imposes record-keeping obligations that require exporters to retain documentation supporting every export for five years from the date of export. For humanitarian programmes spanning multiple years, this means maintaining accessible archives of classification records, exception analyses, licence applications and approvals, end-user statements, and shipping documentation for every consignment.
Post-shipment verification is a further consideration. BIS conducts end-use checks through its Export Control Officers posted at US embassies and consulates worldwide. A Blue Lantern check – BIS's post-shipment verification programme – may be triggered for any licenced export, including humanitarian ones. An NGO that cannot produce the end-user, demonstrate that the goods reached the stated destination, or provide records showing end-use consistent with the licence may face a demand for return of the goods or a finding that the licence conditions were not met.
Ongoing programme management best practices include:
- Designating a named export-compliance officer within the organisation with clear authority over shipment approval.
- Scheduling a periodic review of the programme's item mix, destinations, and end-users against current BIS rules – at least annually, and whenever a material change occurs.
- Maintaining a written export-compliance programme with documented procedures for classification, screening, exception analysis, licence application, and record-keeping.
- Training procurement, logistics, and field staff on the basics of the EAR and on escalation procedures when a red flag arises.
Calder & Vance also advises on the related question of frozen-asset management and blocked-account considerations for NGOs with financial exposure to the BIS / EAR regime. See our service page on frozen account management under BIS / EAR for further detail.
A common myth: humanitarian purpose displaces the compliance obligation
A persistent belief among NGO leadership – and sometimes among in-house counsel who are new to export controls – is that the humanitarian nature of the mission reduces the regulatory obligation. The corollary assumption is that BIS will exercise prosecutorial discretion in favour of any clearly benign actor. Neither position is accurate as a legal matter.
BIS and DOJ have brought enforcement actions in the humanitarian and development sector. Humanitarian intent is a factor in the penalty assessment – it bears on culpability and willfulness – but it does not make an unlicensed export of a controlled item lawful. The legal obligation to obtain the required authorisation exists independently of the exporter's purpose. In our experience, BIS takes the view that the rules exist precisely because items can be diverted regardless of the original shipper's intent; the exporter's good faith does not control what the recipient does with the goods.
The practical consequence is that humanitarian organisations should approach BIS / EAR compliance with the same rigour that a commercial exporter would. The tools – classification, exception analysis, specific licence, screening, record-keeping – are the same. The stakes of failure are also the same: administrative penalties, denial of export privileges, and in cases involving wilful violations, referral to DOJ for criminal investigation.
Related practices
- Frozen account management under BIS / EAR – asset-freeze analysis and blocked-account management for US export-control matters
- Humanitarian authorisation: Canada guide – authorisation pathways under the Canadian export-control and sanctions regime
- Humanitarian authorisation: Canada guide (part 2) – further detail on Canadian programme management and cross-border comparison