Department of War (DoW) Export Control License FAQs

Export controls are governed by several key federal regulations, each administered by a different agency.

Note: The Arms Export Control Act (AECA) is the foundational law that requires the U.S. government to monitor how defense articles and services are used by foreign entities.

Official applications must be submitted through the appropriate federal portal:

• For ITAR (USML) items: Use the Department of State's Defense Export Control and Compliance System (DECCS) at: https://www.pmddtc.state.gov/ddtc_public?id=ddtc_enroll_landing.
  
  • Note: Registration is prerequisite for a company to apply to DDTC for licenses, Technical Assistance Agreements (TAAs) and other authorizations. Registration is also required for a company to rely on ITAR exemptions.
• For EAR (CCL) items: Use the Department of Commerce's Simplified Network Application Process – Redesign (SNAP-R) at https://snapr.bis.gov/register.
  
• For nuclear items subject to the Atomic Energy Act (AEA): Contact the Nuclear Regulatory Commission (NRC) at nrc.gov/nuclear-material/nrc-form-7.html or the Department of Energy (DOE) at https://www.energy.gov/nnsa/national-nuclear-security-administration.

Determining whether a product, software, or technical data is subject to the International Traffic in Arms Regulations (ITAR) or the Export Administration Regulations (EAR) requires a strict, legally mandated process known as the "Order of Review."

Under federal guidelines, Industry partners must first check the United States Munitions List (USML) for ITAR jurisdiction before proceeding to the Commerce Control List (CCL) for EAR classification. If self-classification remains ambiguous, companies should seek a formal government determination.

The Step-by-Step Order of Review

What to Do If You Are Still Unsure?

If your engineering and compliance teams cannot reach a definitive conclusion, the U.S. government provides official channels to resolve the ambiguity:

• Commodity Jurisdiction (CJ) Request: Submitted online to the Department of States' DDTC. A CJ determines the jurisdiction (whether the item is ITAR or EAR) but does not provide a specific classification code.
  
• Commodity Classification (CCATS) Request: Submitted to the Department of Commerce's BIS. A CCATS assumes the item is under EAR jurisdiction and provides the official ECCN.

Note: DTSA reviews these CJ and CCATS submissions on behalf of the DoW to ensure national security interests are maintained during the classification process.

A complete application is essential for a timely review. Here's what you should include:

A properly scoped request clearly defines what is "in the box" (the scope of the export) and what is "outside the box" (what is excluded from export). Failing to define this scope can lead to negative outcomes such as:

• Return Without Action (RWA): The application is sent back with no decision.
  
• Denial: The request is recommended for denial.
  
• Restrictive Conditions: A reviewer may impose provisos or conditions that are more restrictive than desired based on national security concerns.

To help ensure a faster review, provide a clear and detailed application.

• Be Specific: Clearly state what the request includes (e.g., hardware, technical data, defense service) and, just as importantly, what it does not include.
  
• Parties to the Transaction: In addition to end-users, include all U.S. and international parties involved in the export transaction including but not limited to sublicenses, consignees, and freight forwarders.
  
• Over-Communicate: Explicitly define all technical parameters, the end-use (to include the platform as appropriate), and the end-user. Spell out acronyms.  Do not assume reviewers are familiar with your product.
  
• Include Key Documents: Always provide a Letter of Explanation (LOE) or Transmittal Letter and detailed technical specifications.  Product brochures, pictures, etc. are also helpful.
  
• List Precedent Licenses: If a similar technology has been approved before, provide the previous license case number and explain its relevance.

Delays are typically caused by one of three issues:

1. Incomplete technical specifications.
   
2. An ambiguous end-user statement.
   
3. The need for complex coordination on sensitive or emerging technologies (e.g., AI/ML, autonomous systems).

Yes, but such requests face heavy scrutiny. They can advocate for a priority review through official channels.

An informal response to the Licensing Officer is not sufficient, as the updated information needs to be in the official record for DTSA to conduct its national security review.  Responses to an RWA must be submitted as a formal license application through the official application system (DECCS for ITAR/USML applications; SNAP-R for EAR/CCL applications).

Not necessarily. Every license is reviewed based on its own merit and a variety of factors, including:

• The specific commodities
  
• Destination country
  
• Intended end-use and end-user
  
• Other parties to the export transaction
  
• Current U.S. foreign policy
  
• The geopolitical situation at the time of the review

Every license is reviewed as a new request. Provisos may change due to:

• Advancements in the technology.
  
• Changes in the geopolitical landscape or U.S. policy.
  
• Lessons learned from previous licenses.

Note: While you cannot change a proviso directly with DTSA, you can request a formal proviso reconsideration through the Department of State. Reconsideration requests must be submitted via DSP through DECCS and should explain the basis for the request.  More guidance can be found on the DDTC website: https://www.pmddtc.state.gov/ddtc_public.

To facilitate the review of a bulk license, please follow these guidelines:

• Limit each request to a single country.
  
• Scrub the representative parts list (RPL) to ensure it contains no USML items (and no items for which a Commerce authorization is not required).
  
• Provide a comprehensive RPL that includes the ECCN, Part (Nomenclature), and Part Number for each item.
  
• Group the parts by the end-item system they belong to (e.g., F-16, B-52).

Here is an example of a well-formatted RPL:

Note: You need to include the specific ECCN (e.g., 9A610.a or 9A602.x).

No.  According to Section 5.8 of DoDD 5230.25, Qualified U.S. contractors who receive technical data governed by this Directive may disseminate such data for purposes consistent with their certification without the prior permission of the controlled DoW office or when such dissemination is to any foreign recipient for which the data are approved, authorized, or licensed under E.O. 12470, or the Arms Export Control Act.

Yes. Exporting a satellite for a foreign launch requires an authorization for defense services under Category IV.  DTSA will determine if a Technology Transfer Control Plan (TTCP) and/or monitoring is required. These controls apply whether the satellite is ITAR or EAR controlled.

Note: Please refer to Part 748, Supp. 2, paragraph (y) of the EAR.  If SECs apply, State or Commerce will issue license conditions explaining the requirements and if any reimbursement is necessary.  DTSA will then contact your company to complete the SEC documentation.

Possibly. All remote sensing satellites are subject to a potential review by the remote sensing interagency working group (RSIWG). You should mention in your application that the item is a remote sensing satellite and that this review may be required.

Note: Please see 15 CFR 750.4(d)(2)(iv) of the EAR.  Although, this is an interagency review initiated after export license submittal and may be determined to not apply to your satellite, the applicant should mention within the export license application that the satellite is a remote sensing satellite and RSIWG review may be required.

If an unauthorized export (including an accidental "deemed export") occurs, Industry partners must immediately halt the transfer, quarantine the affected data or hardware, and engage internal legal/compliance teams. The most critical regulatory step is initiating a Voluntary Self-Disclosure (VSD) to the appropriate federal authority (State or Commerce) to mitigate potentially severe civil and criminal penalties, while also notifying the DoW if defense contracts or cleared facilities are involved.

Immediate Incident Response: The First 48 Hours

When an unauthorized export is discovered—whether a physical shipment of a controlled component, an email attachment sent to a foreign national, or an unauthorized network access event—your organization must take immediate, documented action:

The Voluntary Self-Disclosure (VSD) Process

Under federal export control laws, waiting for the government to discover a violation often results in maximum penalties, which can include millions of dollars in fines and debarment from federal contracting. Submitting a VSD is the standard industry mechanism for reporting violations and demonstrating a commitment to compliance.

ITAR Violations (Department of State): Submit the VSD to DDTC.  For more information please visit: https://www.pmddtc.state.gov/ddtc_public?id=ddtc_public_portal_compliance_landing

• EAR Violations (Department of Commerce): Submit the VSD to the BIS Office of Export Enforcement (OEE).  For more information please visit: https://www.bis.gov/OEE.

The VSD typically occurs in two phases:

1. Initial Notification: A brief, formal letter stating that a suspected violation occurred and that a full investigation is underway.
   
2. Full Narrative Report: A comprehensive document detailing the "who, what, when, where, and why" of the violation, along with a detailed Corrective Action Plan (CAP) explaining the steps your company has taken (e.g., new training, IT upgrades, firing responsible parties) to ensure it never happens again.

This requires a two-step approval process:

1. Export License: The applicant must first determine if a "deemed export" will occur under the DoW contract.  The applicant must determine export jurisdiction (ITAR or EAR) and classification of the technology (or technical data).  Then the applicant must determine if a license exception applies or if a license is required.  If the export-controlled technology is determined to be ITAR controlled technical data, the applicant must then obtain a DSP-5 license from the Department of State to authorize the "deemed export" to the foreign national.
   
2. DoW Approval: The applicant must then get separate, explicit approval from the DoW Contracting Officer and DoW Security to grant that individual access to DoW facilities or networks.

Note: DSP-5 – Application for Permanent Export of Unclassified Defense Articles, Related Technical Data, and Defense Services.

The DoW strictly enforces export controls to protect the defense supply chain.  From the DoW's perspective, prime contractors are fully responsible for ensuring that any foreign sub-licensees down the supply chain adhere to U.S. export control laws.

To enforce this, the DoW utilizes specific Defense Federal Acquisition Regulation Supplement (DFARS) clauses, most notable DFARS 252.225-7048 (Export-Controlled Items).  This clause mandates that contractors comply with all applicable laws and regulations regarding export-controlled items, including the requirement to obtain necessary licenses before sharing technical data with foreign persons or entities.  Furthermore, strict cybersecurity requirements (such as CMMC) are imposed to ensure that electronic technical data is not inadvertently exposed to unauthorized foreign sub-licensees via non-compliant cloud environments or unsecured communication channels.

Not automatically.  You should assume export controls apply unless you have a written exemption from the regulating authority of the ITAR/EAR.

A "deemed export" is the release of export-controlled technical data, source corde, or technology that is visually, orally, or physically disclosed to a foreign national within the United States or on a DoW facility.  Under federal law, this disclosure is legally treated as if the DoW physically shipped that data to the foreign national's home country.  A license is required if a DoW project involves foreign nationals who may access such technology, unless a specific authorization applies.

DoW military members, civilians, and contractors routinely operate in joint environments where the risk of an accidental deemed export is high. This rule applies directly to DoW personnel in scenarios involving:

• Foreign Liaison Officers (FLOs): Allied military personnel embedded within DoW commands.
  
• Foreign Contractors & Researchers: Non-U.S. citizens working on DoW bases, in defense laboratories, or at university research centers partnering with the DoW.
  
• Base Tours and Visits: Permitting a foreign delegation to visually inspect export-controlled equipment or manufacturing processes during a facility tour.
  
• Joint Operations & Training: Discussing the technical parameters, vulnerabilities, or source code of a weapons system with coalition partners.

A TTCP is a mandatory, facility, specific security blueprint.  It outlines the exact physical, electronic, and procedural safeguards a company will implement to prevent unauthorized access to export-controlled data and classified information by foreign nationals (which prevents illegal "deemed exports"). 

A standard TTCP must establish:

• Physical Security: Badge access restrictions, isolated work areas, and escorted visitor protocols to ensure foreign nationals cannot physically observe export-controlled hardware or documents.
  
• Information System (IT) Security: Network segmentation, restricted server access, and strict user permissions (e.g., ensuring a foreign national employee cannot access network drives containing ITAR-controlled blueprints).
  
• Personnel Procedures: Briefing and onboarding procedures for all employees (both U.S. and foreign) to ensure everyone understands the strict limitations on technical discussions, data sharing, and email transmission.
  
• Oversight & Auditing: Mechanisms for the Facility Security Officer (FSO) to monitor compliance and report any security anomalies or suspected deemed exports.

The DoW and federal export control agencies (State/Commerce) require Industry partners to implement a formally approved TTCP in the following scenarios:

DTSA is the primary DoW gatekeeper and enforcement authority for TTCPs.

While other agencies handle standard corporate security plans, DTSA actively reviews, approves, and physically monitors TTCPs—specifically for high-stakes exports like commercial satellites, spacecraft, missiles, and UAV technology—to ensure critical military-related technology is not illegally transferred to foreign entities

The Role of DTSA in the TTCP Lifecycle

DTSA's Export Control Directorate (ECD), specifically the Missiles, UAVs, and Space Division (DTSA/MUS), manages the creation, execution, and enforcement of a TTCP through a highly structured, multi-phase process:

Why DTSA's Role is Critical for Industry Compliance

Industry partners cannot treat a TTCP as a static compliance document. Because DTSA has the authority to suspend export privileges, freeze review processes in Spacelink, or report violations to federal enforcement agencies, companies must maintain their TTCP as a "living document" that is updated and re-cleared through DTSA whenever a program's technical scope or foreign partnership structure changes.

DTSA is DoW's central point for reviewing export license applications. After you submit an application to the Department of State or Commerce, it is routed to DTSA. Our role is to:

• Evaluate the technical, operational, and policy implications for national security.
  
• Assess the technology's impact on U.S. military modernization.
  
• Analyze the risk of diversion to unauthorized users.
  
• Determine the operational necessity for allied interoperability.
• Consolidate feedback from all relevant DoW components into a single recommendation for the approving agency (State or Commerce).

DTSA plays a central role in the DoW review process for export license applications of defense-related and sensitive dual-use items.  When DTSA receives a license application from a referring agency (such as DDTC or BIS), it executes a highly structured national security review.

The standard process followed by DTSA is as follows:

1. Reception and System Processing

• USXPORTS Integration: DTSA utilizes a specialized secure database and case management system called USXPORTS. When license applications are submitted to State or Commerce, they are electronically referred to DTSA via USXPORTS.
• Assignment: Applications are assigned within the Export Control Directorate (ECD) to specialized licensing officers, licensing analysts, and technical reviewers for detailed adjudication

2. Comprehensive Security & Technical Review

DTSA's ECD evaluates the proposed transfer against the potential risks to national security.

Key factors analyzed include:

• The Technology: Assessing the sensitivity of the defense article, service, or dual-use commodity proposed for export, evaluating whether it threatens to diminish the U.S. qualitative military edge.
• The Transaction Parties & End-User: Verifying the bona fides and track record of the foreign recipient, checking the destination country's export controls, and identifying other parties in the transaction (brokers, distributors, freight forwarders).
• End-Use & Proliferation Risks: Analyzing if the technology is appropriate for the stated end-use and assessing the risk of diversion, misuse, or strategic competitor acquisition.

3. DoW Interagency Coordination

• Internal Stakeholders: DTSA acts as the single point of contact representing the DoW's position.  They coordinate directly with relevant military departments (Army, Navy, Air Force), the Joint Staff, and other specialized defense agencies to consolidate their technical and security assessments.
• Patent and Intelligence Checks: Where applicable, DTSA checks intelligence assessments, and coordinate reviews with agencies representing foreign visits, space monitoring (via Spacelink), or patent applications under secrecy orders.

4. Mitigation and Requirement Definition

If there are national security concerns that do not require an outright denial, DTSA works to actively manage the risk:

• Provisos and Limitations: DTSA drafts customized licensing conditions (provisos) tailored to the transaction to limit how the technology is deployed, used, or shared.
• Technology Security / Transfer Plans (TSP/TTCP): DTSA may mandate that the applicant or foreign recipient establish a formal Technology Security Plan or Technology Transfer Control Plan to guarantee compliance and physical security protocols.

5. Final DoW Recommendation

Once the internal review is consolidated, DTSA formulates the official DoW position and submits it back to the licensing agency (State or Commerce).  DTSA recommends one of four paths:

These recommendations are processed within strict statutory timelines to maintain a balance between safeguarding technology and supporting the defense industrial base.

DTSA operates under strict statutory and regulatory timelines that dictate how quickly it must process export license applications. For standard Dual-Use applications, DTSA has a 30-day statutory window to submit its recommendation back to the Department of Commerce.

For Munitions (ITAR) applications, DTSA aims to align with the Department of State's broader 60-day target to adjudicate defense trade licenses.

Detailed Review Timeframes

DTSA's review clock depends strictly on whether the license is for Dual-Use technology (regulated by the Department of Commerce under the EAR) or Munitions/Defense articles (regulated by the Department of State under the ITAR).

1. Dual-Use Technology (EAR Licenses)

The timeline for dual-use applications is heavily regulated by Executive Order 12981 and codified in 15 CFR § 750.4:

• Referral Window: Once the Department of Commerce registers an application, it has 9 days to refer it to DTSA.
• DTSA Review Period: DTSA is legally mandated to provide its recommendation (Approval, Denial, or Approval with Conditions) within 30 calendar days of receiving the referral.
• The "No Objection" Rule: If DTSA fails to provide its recommendation or request an extension within those 30 days, it is legally deemed to have no objection to the transaction, and the Department of Commerce may proceed.
• Clock Stops: The 30-day countdown can be temporarily paused ("the clock is stopped") only under specific conditions—such as when DTSA formally requests more technical information from the applicant.

2. Munitions & Defense Services (ITAR Licenses)

For defense articles governed by the Arms Export Control Act (AECA) and the International Traffic in Arms Regulations (ITAR):

• The 60-Day Target: Under National Security Presidential Directive 56 (NSPD-56), the overall target to adjudicate and complete defense trade licenses is 60 days.
• DTSA's Slice of the Timeline: While DDTC holds the final signature, DTSA typically completes its internal DoW-wide technical and security reviews within 30 to 45 days to allow the DDTC time to process and issue the final decision.

Factors That Can Extend the Timeline

While the statutory guidelines are clear, several factors frequently extend the actual elapsed time before an exporter receives a final answer:

• Interagency Dispute Escalation: If DTSA disagrees with another reviewing agency (like the Department of Energy or State), the license is escalated to the interagency Operating Committee (OC).  This dispute resolution process can add weeks to the final timeline.
• Congressional Notification: Major defense transactions or licenses involving significant military equipment (SME) require formal Congressional notification. This adds an automatic 30 to 90 calendar days to the process, during which the review clock is effectively suspended.
• Complex Technical Reviews: Highly advanced technologies (such as next-generation semiconductors, artificial intelligence, or space systems) may undergo extensive technical evaluation, causing delays beyond the standard averages.

Yes. If the DoW makes an administrative, technical, or clerical error when drafting and applying provisos to a license, there is an established pathway to have the license corrected and re-issued.

The mechanism used to resolve this depends heavily on the nature of the error.

Administrative & Clerical Errors ("Corrections")

If the error is purely administrative—such as a typo, incorrect serial number, transposed numbers, or a miscopied phrase that was not part of the intended DoW policy decision, the process is relatively fast.

• The Process: The exporter submits a formal "Correction Request" directly to the licensing agency (DDTC for ITAR or BIS for EAR).
• DoW Role: If an error was introduced during the final assembly of the license by State or Commerce, those agencies will correct it directly. If the typo originated in DTSA's transmittal, the licensing agency will query DTSA, and DTSA will rapidly issue a corrected recommendation back to the lead agency to trigger a re-issue.

Technical & Substantive Errors ("Reconsideration")

If the DoW applied a proviso that was technically or operationally flawed due to a misunderstanding of the hardware, technology, or end-use (e.g., applying a missile-technology proviso to a ground radar component), this is treated as a substantive error.

• The Process: This requires a formal Proviso Reconsideration Request. The exporter must submit this through the respective licensing agency's system
• DoW Role: DTSA will review the submission, coordinate with the originating military department, acknowledge the technical discrepancy, and formally recommend that the licensing agency amend and re-issue the license with the corrected or deleted proviso.

No, but with a critical national security caveat. Technically, ITAR and EAR license provisos—including standard "do not discuss, offer, or release..." provisos—only have legal jurisdiction over export-controlled technical data, defense services, or commodities. They do not govern purely public domain information or data that is genuinely exempt from export controls.

However, within DoW's operational framework, data that is "non-export controlled" may still be subject to strict Controlled Unclassified Information (CUI) (see DoDI 5200.48), or Distribution Statements (see DoDI 5230.24) markings that prohibit its release.

For any questions or disagreements about a proviso, you must start by contacting the respective Department's Licensing Officer (LO) directly to discuss/resolve any issues before submitting a reconsideration.  For Department of State licenses (USML) contact the DDTC LO, and for Department of Commerce licenses (CCL) contact the BIS LO. They will instruct you on the formal submission process for a clarification or reconsideration. DTSA cannot adjudicate these matters informally via email or phone given the legal implications of the license.

For further information please visit:

Department of State, DDTC: https://www.pmddtc.state.gov/ddtc_public
Department of Commerce, BIS: https://www.bis.gov/

Department of State (DDTC):

• General regulatory questions (ITAR) - Response Team: (202) 663-1282
• Technical system issues (DECCS) - Help Desk: (202) 663-2838
• Specific license or proviso questions – contact the respective Licensing Officer (LO) directly

Department of Commerce (BIS):

• Questions about EAR licenses - (202) 482-4811
• Specific license or proviso questions – contact the respective Licensing Officer (LO) directly
  

Department of War (DTSA):

• Technical questions or requests for DoW assistance dtsaoutreach@mail.mil
  
  • Note: If you believe you have a circumstance that requires DTSA assistance (new technology, new program, etc.) please reach out to DTSA at any time during the license process using the outreach email box listed above and your request will be forwarded to the respective Integrated Product Team (IPT) as appropriate.