When technical records need an export-control review

Review the information, not just the file label

A production archive may contain sales totals, maintenance histories, engineering drawings and detailed process settings in the same folder. Those are not interchangeable review subjects. Describe which information is proposed for disclosure and what it enables a recipient to do. A harmless directory name can conceal technical attachments; an industrial subject does not automatically make every associated business record controlled.

The EAR technology definition concerns information necessary for specified development, production or use activities tied to the relevant control provisions, and includes tangible and intangible forms. Section 734.13 addresses transmission outside the United States and deemed-export releases. BIS explains that releasing controlled technology or source code to a foreign person within the US can be a deemed export. This is why server location alone does not answer the access question.

Have the export-control owner identify jurisdiction, classification and any required authorization using the actual content, parties, destinations and activities. Do not turn the absence of a classification entry in an internal inventory into proof that no control applies. Keep the data-security review separate: a well-secured channel can still carry a disclosure that requires an export determination.

A completed technical-content and access map

Hypothetical example: a US manufacturer is considering a technical-record evaluation. Its proposed package mixes aggregated order counts with equipment calibration instructions, a CAD attachment and troubleshooting notes. The potential recipient has a US office and a mixed team whose access arrangements are not yet documented. No classification, jurisdiction or authorization conclusion has been recorded.

The map below separates the questions instead of classifying every file as controlled or clear. The team can consider a category-level introduction while holding actual technical contents. Removing an attachment changes the proposed package; it does not prove that the remaining notes contain no relevant technical information.

Keep a determination attached to the reviewed version

Build a concise review package: content inventory and representative description, item or technology context, jurisdiction/classification question, named entities, relevant access-person facts, destinations, end use and proposed access method. Ask the specialist which information is actually needed and handle personal access facts appropriately. The goal is a supported decision about a defined release, not indiscriminate collection of passport information by a sales team.

Record who made the determination, what version it covers, its assumptions and which changes reopen it. A recipient adding another engineering team, an owner adding a richer attachment, or a product changing from passive analysis to technical replication can matter. The operating team should not silently expand an approved package because the customer’s original evaluation went well.

Use inventory to separate technical contents and due diligence to identify the receiving parties. Preserve any allowed category-level description in the introduction brief. VOID’s referral service is not an export-classification service or a promise to broker controlled technical inventory. An introduction, sample and license require separate decisions.

This guide is an educational agenda for selected US EAR provisions, not a classification, license determination or end-use clearance. Other US regimes, sanctions and non-US rules may also need review. The eCFR pages read on 10 October 2026 displayed a 7 October cutoff. Confirm the applicable current provisions and the actual transaction with a qualified reviewer; no complete current regulatory survey is claimed here.