Deemed Export Checklist: Foreign National Employees, Interns and Visitors
Releasing controlled technical data to a foreign person inside the United States is treated as an export to that person's country. This checklist helps HR, engineering and compliance keep new hires, interns, contractors and visitors inside the rules.
0 of 31 items complete
11 critical items still open - these are the highest-risk gaps.
Before the offer or visit
Screening and employment forms
Access control
Training and awareness
Records and monitoring
Count completed items and weight critical items double. Any unchecked critical item should be closed before a foreign person gets access. Note that US permanent residents and protected individuals are generally not foreign persons under the ITAR, but the EAR uses a different test. Confirm status with counsel.
Check ERP access for restricted users
Optional: a read-only review of ERP and PLM permissions against a list of restricted users and controlled projects.
Optional. The tool and every export work without this. No spam.
How to use the checklist
Run the checklist once per foreign person role, not once per company. Start with the pre-offer group, because most problems begin when access is promised before anyone reviews the data involved. Mark each item as done, not applicable or open. Critical items stop the process if open. Export the result to PDF and file it with the hiring record so the decision is documented.
The concept of deemed exports
Under the EAR, release of technology or source code to a foreign person in the US is deemed to be an export to the person's most recent country of citizenship or permanent residency. The ITAR treats a disclosure of technical data to a foreign person in the US as an export as well, with the definition of foreign person differing slightly. Visual inspection, oral exchanges and ERP access can all count as release.
- Release includes viewing, speaking and system access
- Hardware itself is not the problem; technology and data are
- The test depends on the data classification and the person's nationality
Technology control plans
A technology control plan lays out how a company restricts controlled data: physical separation, IT access control, training and monitoring. It should be specific to the person or project. Your ERP is central to this. Roles and permissions must prevent a restricted user from seeing controlled part numbers, drawings or work instructions, including through reports, attachments and search.
Common mistakes
The recurring failures are signing the visa petition export attestation without analysis, giving access first and reviewing later, and forgetting about interns and contractors. Another is relying on a person's current residency while ignoring prior citizenship where the rules look at it. Treat every new foreign person role as a review trigger and keep the paperwork.
Frequently Asked Questions
What is a deemed export?
A deemed export is the release of controlled technology or source code to a foreign person inside the United States. It is treated as an export to that person's home country, so a license may be needed even though nothing leaves the country.
Do permanent residents count as foreign persons?
Under the ITAR, lawful permanent residents and certain protected individuals are generally not foreign persons. The EAR uses a similar approach for deemed exports but definitions differ. Confirm status for your case with counsel before granting access.
What is the visa petition export certification?
US employers petitioning for certain work visas must certify whether a license is required to release controlled technology or source code to the beneficiary. The answer should come from a documented export analysis, not an automatic checkbox.
Can a verbal conversation be an export?
Yes. Release can happen by visual inspection, oral exchange or system access, not only by sending a file. Meetings, shop floor walkthroughs and screen shares can all release controlled technical data to a foreign person.
If you want ERP and PLM permissions checked against a restricted-user list automatically, we can build a read-only access review on your own servers. The checklist is free and complete without it.
Related Tools
ITAR USML Categories I to XXI Reference
All 21 USML categories with their official titles and a plain summary of what a machine shop, electronics house or software team should look for.
Aerospace & DefenseITAR License, Agreement and DDTC Form Reference
A quick reference to DSP-5, DSP-61, DSP-73, DSP-85, DSP-83, TAA, MLA, WDA and other ITAR authorizations and what each is used for.
Compliance & ContractsExport Control Program Maturity Assessment
Ten questions that score how well your export control program covers classification, screening, licensing, training, records and oversight.
Compliance & ContractsNIST SP 800-171 Rev 2 Control Families Reference
Look up the 14 NIST 800-171 Rev 2 families, how many requirements each holds, and where each shows up in an ERP or shop floor system.
Compliance & ContractsForeign Person Visitor Access Request Template
A visitor request form that records the purpose, screening result, escort, areas visited and the controlled data the visitor may not see.
More Compliance & Contracts tools
See all- DFARS and FAR Cyber and Supply Chain Clause Reference
- ECCN Structure and Reasons for Control Reference
- SAP SoD Residual Risk Score Calculator
- SAP Firefighter ID Usage Review Log
- IBM i (AS/400) User Profile Access Review Worksheet
- SyteLine Security and User Access Audit Checklist
- Infor XA (MAPICS) User Access Review Worksheet
- China ERP Data Security and Compliance Assessment
- ERP Vendor Data Processing Agreement Outline