A deemed export license application should focus on the foreign person who may receive controlled technology or source code. Spouse information is generally not a standard submission requirement, but applicants still need a disciplined process for identity documentation, risk review, data minimization, and responses to follow-up questions.
What a Deemed Export License Application Should Cover
A deemed export can occur when controlled technology or source code is released to a foreign person in the United States. The release may take place through visual inspection, technical discussions, electronic access, laboratory work, training, or other forms of disclosure. Hiring a foreign person does not automatically create a licensing requirement. The determining issue is whether the person will receive technology or source code that requires authorization under the Export Administration Regulations.
Applications are generally person-specific and technology-specific. The applicant must clearly identify the individual, explain the proposed access, describe the controlled technology, and establish why the requested authorization is appropriate. An application should not be treated as a broad authorization covering every foreign person employed by the company.
Core Identity and Employment Information
The Letter of Explanation typically identifies the foreign person through information such as:
- Full legal name
- Citizenship and immigration status
- Current and permanent addresses
- Passport number, expiration date, and place of issuance
- Visa type, expiration date, and place of issuance
- I-94 number and expiration date, if applicable
- I-20 number and expiration date, if applicable
The supporting package will also generally include relevant identity and immigration documents, a detailed resume, and a job description. The resume should provide sufficient information about education, employment, technical expertise, research, publications, and professional affiliations to support the government's review.
The job description should do more than repeat a human resources posting. It should explain the employee's responsibilities, the technology or source code involved, the facilities and systems the person may access, and the safeguards that will govern access. A vague description can lead to follow-up questions because reviewers need to understand the actual scope of the proposed release.
The company's classification analysis must also be complete before submission. Without an accurate understanding of the technology, applicable control reasons, and relevant country considerations, even a thorough identity package cannot establish whether a license is required.
When Spouse Information May Become Relevant
Spouse passport numbers, visa details, dates of birth, and similar personal data are generally not standard requirements for a deemed export license application. The application concerns the foreign person who will receive controlled technology or source code. Routine submission of a spouse's identity documents is therefore usually unnecessary when the spouse will not receive access and is not otherwise involved in the proposed activity.
A previous company file containing spouse information does not establish that such information is mandatory. Older applications may reflect a voluntary submission, a case-specific government request, a former internal practice, or an overly broad document collection process. Compliance teams should not automatically copy the contents of an earlier file into a new application.
Optional Background and Case-Specific Requests
An applicant may describe the foreign person's ties to the United States, including family or property, when that background is relevant. A reference to a spouse or other family relationship does not ordinarily require submission of the family member's passport, visa, or complete biographical record. For example, a resume or Letter of Explanation might state that the employee has immediate family residing in the United States without attaching those individuals' identity documents.
Government reviewers may request additional information when necessary to evaluate a particular application. Follow-up questions could arise when information is incomplete, inconsistent, or relevant to concerns about the proposed technology access. The licensing officer may request clarification or supporting material through the electronic licensing system. Applicants should respond precisely to the request rather than submitting unrelated personal information.
Spouse information may also become relevant if the spouse independently requires access to controlled technology. For example, spouses employed by the same research organization could each participate in controlled technical work. In that situation, each person's access would generally require a separate authorization analysis. The spouse would not be documented merely because of the marriage. The spouse would be evaluated as another potential recipient of controlled technology.
The same principle applies to household members, visitors, contractors, interns, and collaborators. Relationship status alone does not determine licensing requirements. Actual or anticipated access is the central compliance question.
Building a Defensible Documentation Process
A strong deemed export compliance process begins before the license application is prepared. Export compliance, human resources, information security, legal, and the relevant business unit should coordinate to identify controlled technology and determine who can access it. This prevents the company from collecting large amounts of personal data before understanding whether a license is even necessary.
The first step is to classify the technology or source code involved. The company should then evaluate the foreign person's anticipated duties, physical access, system permissions, citizenship, immigration status, and other relevant facts. If authorization is required, the application package should be tailored to the specific person and proposed release.
Data Minimization and Application Controls
Personal data should be collected for a defined compliance purpose. Passport copies, immigration records, home addresses, and employment histories are sensitive records. Collecting spouse information without a clear legal or case-specific reason increases privacy, security, retention, and access-control obligations without necessarily improving the application.
A documented workflow should address:
- Who determines whether technology is controlled.
- Who assesses whether the employee's access requires authorization.
- Which identity and immigration documents are required.
- Who may review and approve the application.
- How follow-up government questions are handled.
- Where sensitive records are stored and when they are deleted.
- How technology access is restricted while an application is pending.
The company should also reconcile the license application with its technology control plan. The individual's job description, system permissions, physical access, training, supervision, and approved technical scope should tell a consistent story. If the application says that access will be limited to a specific project, internal controls should enforce that limitation.
Restricted-party screening is another important but distinct control. Screening helps identify potential concerns associated with employees, counterparties, institutions, and other relevant parties. It does not replace classification, licensing, or technology access controls. A spouse should not automatically be screened or documented solely because of the relationship, unless the spouse is a relevant party, will receive access, or becomes material to a government request or internal risk review.
Periodic reviews are also essential. A change in job duties, citizenship, immigration status, project assignment, technology classification, or system access can alter the authorization analysis. Compliance should therefore continue after a license is issued.
- BIS September 2024 guidelines for deemed export and deemed reexport license applications list required foreign person identity details in the Letter of Explanation as full name, citizenship or immigration status, permanent and current addresses, passport number/expiration/place of issuance, visa type/expiration/place of issuance, I-94 number/expiration (if applicable), and I-20 number/expiration (if applicable). Spouse or other family member personal data such as passport, visa, or date of birth is not listed as required.
- The same guidelines note in the resume section that applicants should list any specific ties the foreign person has to the United States, such as family or property, but this is presented as optional background rather than mandatory documentation of a spouse's details. BIS can still request extra information during review if needed for the determination.
- No regulatory changes or updates to deemed export license application documentation requirements, including Letters of Explanation, appear in the past 30 days. Related recent BIS activity includes General Order No. 6 (effective September 6, 2024, with later reporting under 15 CFR 743.7 and 743.8) authorizing certain deemed exports of GAAFET and quantum technology under specified conditions, plus ongoing Entity List and SDN coordination rules that can affect deemed export reviews.
- Practitioner discussions on X in the recent period focus on broader deemed export tightening, ITAR distinctions, and hiring restrictions for non-U.S. persons, with no identified posts addressing spouse information in license applications or Letters of Explanation.
Frequently Asked Questions
Is spouse information mandatory in every deemed export license application?
No. Spouse passport information, visa details, and date of birth are generally not part of the standard submission for an employee's deemed export license application. The application typically focuses on the foreign person who will receive the controlled technology or source code. Additional family information should be included only when it is relevant or specifically requested.
Why might an older application contain a spouse's personal data?
The information may have been submitted voluntarily, requested during a case-specific review, or collected under an older internal procedure. Its presence does not prove that it was legally required. Companies should evaluate current application needs instead of using a prior filing as an unquestioned template.
Can a licensing officer request spouse information later?
Yes. A licensing officer can generally request additional information considered necessary to complete the review. The applicant should examine the exact request, confirm which documents or facts are needed, and provide a focused response through the appropriate licensing channel. Unrequested personal data should not be added merely as a precaution.
Should the Letter of Explanation mention family ties in the United States?
It may mention relevant ties, such as immediate family or property, as part of the foreign person's broader background. Such a statement does not ordinarily require detailed spouse documentation. The applicant should distinguish between a concise description of ties and the disclosure of sensitive identity records.
What happens if the spouse will also access controlled technology?
The spouse should receive a separate deemed export analysis based on the spouse's own citizenship, immigration status, duties, and anticipated technology access. If authorization is required, a separate application may be necessary. Marriage to an existing applicant does not extend that applicant's authorization to another person.
Can access begin while the application is pending?
Controlled access should not begin unless an applicable authorization, exception, exclusion, or other valid basis permits it. Companies typically use technology control plans, system restrictions, facility controls, supervision, and training to prevent unauthorized releases while a licensing decision is pending.
How Stable Software Can Help
A Practical Compliance Connection
Deemed export licensing depends on accurate identity information, consistent review procedures, and clear controls around relevant parties. Restricted-party screening supports that broader compliance framework, although it does not replace technology classification, licensing analysis, or a properly prepared Letter of Explanation.
Stable Software offers a denied-party screening platform for organizations managing trade compliance responsibilities. Customs brokers, importers, and compliance teams can evaluate how screening software fits into their procedures for reviewing employees, counterparties, institutions, and other parties connected to controlled transactions. Organizations assessing their deemed export processes can explore the platform as part of a coordinated compliance program.
Resources
| Type | Resource |
|---|---|
| Source | Primary source |
