A Senior Engineer Shares Controlled Technical Documentation With a Foreign National Colleague Who Sits Three Desks Away. Same Team. Same Building. Same Project. Two Years Working Together. Is That an Export?

Quick Answer

Does sharing controlled technical documentation with a foreign national colleague in the same US office constitute an export under the Export Administration Regulations?

Yes. A “deemed export” occurs when controlled technology is released to a foreign national, regardless of the physical location. No shipment is required. No border needs to be crossed. Sharing controlled technical documentation with a foreign national colleague in the same office, on the same Zoom call, or through the same shared drive folder constitutes a deemed export under the EAR if the technology is controlled for export to that person’s country of nationality. The employee’s familiarity with the colleague, the duration of their collaboration, and the absence of a physical transfer are not factors in the deemed export analysis.

The Situation

A senior engineer at a technology company is working on a joint development project. He needs to share a technical specification document with his colleague, Wei, who sits three desks away. Wei is a highly capable engineer who has been on the team for two years. He is a citizen and national of China on an employment visa. The technical specification contains controlled technology under the Export Administration Regulations — it is classified as EAR99 for most purposes but carries an Export Control Classification Number (ECCN) that restricts release to nationals of certain countries, including China, without a license.

The engineer adds Wei to a shared project folder on the company’s internal drive and grants him access to the full technical package. His reasoning: “Wei works here. We’re collaborating on the same project. This isn’t an export — I’m not sending anything overseas. We’ve been on the same team for two years.”

Three months later, the company’s export compliance team conducts an audit and flags the shared folder access as a potential deemed export violation.

Choice AGrant access as done. Wei is a company employee, physically present in the US, on a valid work visa. No shipment occurred. The deemed export concern doesn’t apply to colleagues working on the same project in the same location.

Choice BBefore granting access, check with the export compliance team to confirm whether the technology is controlled under the EAR, whether Wei’s nationality creates a deemed export restriction, and whether a deemed export license or license exception applies. Do not grant access until compliance has confirmed it is permissible.

Choice CShare only the non-technical portions of the specification with Wei and keep the controlled technical details on a need-to-know basis. Make the determination internally without involving the compliance team.

The Right Call

Choice B — Check with export compliance before granting access.

Choice A is the deemed export violation — the rationalization that “he works here” is factually correct but legally irrelevant. US employment status does not determine deemed export applicability. Nationality does. Choice C is the most dangerous option: the engineer is making a deemed export determination they are not qualified to make, without the classification and nationality screening that the decision requires. The export compliance team exists precisely to make this assessment. The engineer’s job is to recognize the trigger — sharing controlled technology with a foreign national — and route it to the right person. That routing is the entire training moment.

“No shipment” is the most common misconception about deemed exports — and the most common source of violations in technical organizations.

The word “export” implies a physical transfer across a border. Under the EAR, “release” of controlled technology includes any oral, visual, or electronic disclosure to a foreign national — in person, by phone, via a shared drive, or during a meeting. The absence of a shipping manifest or a customs declaration does not affect the analysis. Engineering-heavy organizations with international workforces experience deemed export exposure continuously — in technical briefings, shared repositories, demo environments, and project documentation — and most of the employees involved have no idea the concept exists.

US employment status does not override deemed export restrictions. Nationality does.

An employee on an H-1B visa working full-time in the US is still a foreign national for deemed export purposes. The EAR uses the person’s most recent non-US citizenship or permanent residency as the determining factor — not their visa category, employment status, or physical location. A foreign national colleague who has worked on the team for 2 years has the same deemed export analysis as someone who started last week.

The relevant question is not “is this person trustworthy?” — it is “is the technology controlled and does their nationality create a restriction?”

The proximity bias rationalization — “we’ve worked together for two years, I trust him completely” — is evaluating the wrong variable. Trust in the colleague is irrelevant to the export control analysis. The analysis requires: is the technology classified under an ECCN that carries country-based restrictions? Does the colleague’s nationality fall within those restrictions? If yes, is a license or license exception available? Those questions require export compliance assessment — not the engineer’s personal judgment about a trusted colleague.

What is a deemed export under the Export Administration Regulations?

Under 15 CFR § 734.13, an export includes the release of technology to a foreign national within the United States. This is called a “deemed export” because releasing the technology to the foreign national is deemed to be an export to that person’s most recent country of citizenship or permanent residency. Deemed exports can occur in person, by email, through shared drives, in technical presentations, during Zoom calls, or any other means of disclosure. No physical shipment is required.

Does US employment status — a work visa or green card — affect deemed export analysis?

Not for most purposes. Permanent resident status (green card holders) are generally treated as US persons for EAR deemed export purposes, but non-immigrant visa holders — H-1B, L-1, J-1, F-1 OPT, and others — are considered foreign nationals and their most recent non-US citizenship determines the deemed export country analysis. An H-1B employee working full-time in the US is still a foreign national for deemed export purposes.

What should an employee do when they need to share potentially controlled technology with a foreign national colleague?

Contact the export compliance team before sharing. Provide: the technology or document description, the ECCN if known, and the colleague’s nationality. The compliance team will assess whether the technology requires a license or license exception and confirm whether sharing is permissible. Most organizations with significant international workforces have established deemed export authorization processes — the employee’s role is to trigger the process, not to make the determination themselves.

How to Use This Scenario in Training

Recommended for engineering, R&D, and technical teams in organizations with international workforces — particularly relevant for technology companies, manufacturing, defense contractors, and pharmaceutical/biotech organizations with controlled technology. This scenario requires slightly more conceptual setup than others in the cluster: introduce the deemed export concept before presenting the scenario so the recognition moment lands correctly. Most effective as a Week 3 scenario in a reinforcement sequence after foundational recognition skills are established.

This scenario demonstrates the proximity bias rationalization pattern from the Decision Readiness Engine™ — “same building means same rules.” Decision-ready employees in technical roles recognize that a foreign national colleague triggers an export compliance check regardless of physical proximity, tenure, or personal trust. The routing obligation is the training behavior — not the compliance determination itself.

More Export Controls & Sanctions Scenarios