ITAR and EAR Visitor Control: Where the Two Regimes Differ at the Front Desk
At a facility that holds controlled technical data, the front desk is an export-control checkpoint, not a guestbook. Here is what the ITAR and EAR actually require of a visitor program, where the two regimes part company, and how to meet both without turning every guest into a 20-minute ordeal. For the product side of this, see the ITAR visitor management system.
If you run a federal contractor, aerospace prime, defense supplier, or advanced manufacturer with ITAR- or EAR-controlled work, your visitor program has one job that an ordinary sign-in app cannot do: make sure no one reaches controlled technology they aren’t authorized to see and prove, afterward, that you controlled it.
That is the part people miss. Under the ITAR (22 CFR Parts 120–130) and the EAR (15 CFR Part 734), giving a foreign person access to controlled technical data or technology inside the United States can be a deemed export to that person’s home country, an export that may require authorization before it happens. A visitor who can read a drawing on a screen or watch a process on the shop floor is squarely in scope. The visit, not just the shipment, is the export event.
The deemed-export angle in one line
A clean badge is not an access decision. The control question is not “did they sign in?” it is “could this person reach controlled technology, and on what authority were they allowed to?” (ITAR 22 CFR 120.50; EAR 15 CFR 734.13)
What an ITAR/EAR visitor program typically includes
There is no single “ITAR visitor form” in the regulations. The program follows from the duty not to make an unauthorized export. Four practices teams commonly put at the door: identify the visitor, screen against OFAC and BIS, control access to controlled technology, and keep the record.
Identify the visitor
Capture who is arriving and the facts needed to assess person status: name, employer, citizenship/person-type, purpose, and the areas they have asked to enter.
Screen against restricted-party lists
Check every visitor, vendor rep, and contractor against OFAC and BIS lists before access. EU and UN lists are available in the product; they are not ITAR or EAR screening obligations. A hit is a hold for review, not a quiet note for later.
Control where they can go
Gate controlled areas, assign and record escorts, and flag foreign-person access to spaces holding controlled technology for the host’s export-control decision.
Keep audit-ready records
Record who entered, when, escorted by whom, which areas, the screening result and list version, and any NDA or export acknowledgment, kept for your recordkeeping window.
None of this means slowing the lobby to a crawl. Most visitors are low-risk and should clear quickly; the program’s job is to put the friction exactly where the risk is (a foreign-person request for a controlled area) and nowhere else.
Screen access, not nationality
This is where well-meaning programs create new liability. Export controls restrict access based on the controlled technology and the person’s status, decided case by case, with authorization where it’s required. They are not a license to apply a blanket “no foreign nationals” rule.
Over-applying ITAR/EAR (treating lawful visitors or workers unequally by national origin) has produced real settlements enforced by the Department of Justice’s Immigrant and Employee Rights Section. A good visitor program flags foreign-person access to controlled areas for a real export-control review; it does not quietly turn into national-origin screening. The decision stays yours, made on export-control grounds, with counsel where the stakes are real.
How SecurePoint USA supports this
SecurePoint Visitor was built for this intersection rather than retrofitted for it. It does not make your export determinations; it captures the facts, enforces your policy, and records that it did, which is what an auditor actually asks for. The pieces map to ITAR/EAR visitor workflows, restricted-party visitor screening, and audit-ready visitor logs.
Pre-registration with person status
Hosts pre-screen visitors ahead of arrival; requests for controlled areas and foreign-person access are flagged for review before the visit.
Restricted-party screening at check-in
Every visitor and vendor is screened against OFAC and BIS lists, with the result and list version recorded. EU and UN lists are available; they are not ITAR or EAR obligations. A hit holds entry for human review.
Escort & restricted-area enforcement
Badges and escorts are tied to the cleared screen and the approved areas; unresolved foreign-person access defaults to escort-required or hold.
Tamper-evident audit trail
Who entered, when, escorted by whom, which areas, and the screening result, in a time-stamped, SHA-256 hash-chained log you can export for a DCMA/DCSA review or a CMMC assessor.
For defense customers, that audit trail is not a nicety: NIST SP 800-171 PE 3.10.1, 3.10.3, and 3.10.4 cover limiting physical access, escorting visitors, and keeping physical-access logs. SecurePoint produces evidence for those visitor-facing practices. It does not, and we never claim it does, grant a certification. See CMMC visitor logging and defense contractor visitor management.
Common pitfalls
Treating the front desk as a guestbook
Fix: Build it as a gate: screen, gate areas, and record the access decision before entry, not after.
Blanket "no foreign nationals" rules
Fix: Decide access on the controlled technology and the person’s status, case by case, with authorization where needed. Over-applying export controls is its own legal risk.
Tracking exemptions and escorts on paper
Fix: Require a digital sign-off with reviewer, rationale, and expiry so the evidence exists when an auditor asks.
Waving people through when status is unclear
Fix: Default to deny or escort-required until person status and area access are resolved.
A practical starting sequence
Map where controlled technical data and technology actually live (labs, server rooms, shop floors, conference areas).
Define area access tiers and the host/security owner who approves entry to each.
Stand up pre-registration that captures person status and requested areas before arrival.
Screen every visitor against restricted-party lists at check-in; hold hits for review.
Tie badges and escorts to the cleared screen and the approved areas.
Capture NDAs / export-control acknowledgments and retain the full access record.
ITAR & EAR visitor management: FAQ
Primary sources
- ITAR: 22 CFR Parts 120–130 (eCFR)
- ITAR "release" / deemed export: 22 CFR 120.50
- EAR export incl. deemed export: 15 CFR 734.13
- DDTC (State Dept.): pmddtc.state.gov
- BIS (Commerce): bis.gov
- NIST SP 800-171 Rev. 3 (physical protection)
- DOJ Immigrant & Employee Rights (anti-discrimination)
ITAR and EAR requirements and penalty figures change; verify the current text against the issuing agency before relying on it. This article is educational and is not legal advice.
Turn your front desk into an export-control checkpoint
See how SecurePoint USA screens visitors, records escort assignments, and keeps tamper-evident records that support an ITAR/EAR program.
Go deeper on the ITAR visitor management platform or read the ITAR visitor screening whitepaper.
