Guide — ITAR / EAR

ITAR visitor screening starts before arrival.

Deemed-export and foreign-national access rules require a documented decision before someone reaches controlled technical data or hardware. Regulated Access structures that decision — intake, screening gate, human review, and evidence export.

  • Pre-access review
  • Match resolution
  • Evidence pack
Regulated Access intake workflow for ITAR visitor screening

Decision before access

Intake, screening, review, approval gate, and evidence export stay on one record.

Requirements

What regulators and auditors expect

ITAR § 120.19 and EAR deemed-export rules expect a written access determination before foreign nationals encounter controlled technical data or defense articles. That determination should show who was reviewed, what lists were checked, who approved access, and what conditions applied.

Email threads and ad hoc spreadsheets rarely survive an audit or export-control review. A structured case record — with screening runs, reviewer actions, and an append-only audit chain — is the durable alternative.

Product fit

How Regulated Access maps to the workflow

  • Intake: capture subject identity, citizenship, host, site, scope, and supporting documents before the visit is scheduled.
  • Screening: denied-party screening runs at submit for configured pilots; the approval gate blocks final decisions while matches remain unresolved.
  • Review: compliance staff resolve matches, request information, and issue approve / deny / conditional decisions with self-review blocked server-side.
  • Evidence: export JSON, PDF, or ZIP manifests with PII-scrubbed metadata for audit or customer review.