Manufacturing operations face intense competitive pressures, increasingly complex supply chains, and strict compliance requirements like CMMC and ITAR...
Healthcare providers face mounting pressures from ever-evolving technology...
Accounting firms handle sensitive financial data—from tax filings to audit...
Law firms operate under strict confidentiality obligations and face evolving...
Auto dealerships handle a wealth of customer information, from financing details...
In Oil & Gas, uptime, safety, and data integrity are paramount. Whether you’re managing offshore rigs,...
Financial institutions bear a heavy responsibility: they hold sensitive client information and manage...
In the insurance sector, safeguarding sensitive policyholder information is essential—not just to meet...
Auto dealerships handle a wealth of customer information, from financing details...
Small and medium-sized businesses are the backbone of our economy, but they often face...
Manufacturing operations face intense competitive pressures, increasingly complex supply chains, and strict compliance requirements like CMMC and ITAR...
Healthcare providers face mounting pressures from ever-evolving technology...
Accounting firms handle sensitive financial data—from tax filings to audit...
Law firms operate under strict confidentiality obligations and face evolving...
Auto dealerships handle a wealth of customer information, from financing details...
In Oil & Gas, uptime, safety, and data integrity are paramount. Whether you’re managing offshore rigs,...
Financial institutions bear a heavy responsibility: they hold sensitive client information and manage...
In the insurance sector, safeguarding sensitive policyholder information is essential—not just to meet...
Auto dealerships handle a wealth of customer information, from financing details...
Small and medium-sized businesses are the backbone of our economy, but they often face...
A technology control plan (TCP) is a written plan that describes how a company keeps export-controlled technology, technical data, and defense articles away from people who aren’t authorized to have them, most often foreign nationals. It names what’s controlled, who may access it, how that access is enforced, and who owns the plan.
Most of what’s written about TCPs comes from universities and research labs. If you’re a manufacturer, the question is more practical: who can open the drawing, and how do you prove it?
This guide covers what a TCP is, who needs one, what goes in it, and the part most guides skip: how your IT systems make it real. It’s general information, not legal advice. Your Empowered Official and export counsel should own the content.
A TCP is a facility- or program-specific plan to safeguard technology that’s controlled for export under the International Traffic in Arms Regulations (ITAR), administered by the State Department’s Directorate of Defense Trade Controls (DDTC), or the Export Administration Regulations (EAR), administered by the Commerce Department’s Bureau of Industry and Security (BIS). ITAR covers defense articles and technical data on the U.S. Munitions List (USML), and the EAR covers dual-use items on the Commerce Control List. Both sets of export control regulations apply to technology and technical data as well as physical items. It’s the working procedure for access to your controlled technology: it turns “we don’t let unauthorized people see this” into something specific and checkable.
The reason it matters is the deemed export. Under both regimes, releasing controlled technical data to a foreign person inside the United States can be treated as an export to that person’s most recent country of citizenship or permanent residence, with no shipment involved. We cover the mechanics in our guide to deemed export. A TCP is how you prevent that release and show that you’re preventing it.
A TCP isn’t the same as your whole export control compliance program. The program covers classification, export licensing and authorizations, screening, and recordkeeping across your business. The TCP is narrower: it controls access to specific controlled technology and helps ensure compliance where foreign persons could be involved.
It depends on how you came to need one, and the honest answer has three layers.
Companies under FOCI mitigation must have one
DCSA requires approved TCPs for companies under certain security agreements and may impose additional requirements in other situations. The TCP must set out the security measures needed to reasonably foreclose unauthorized access to classified or export-controlled information by non-U.S. citizen employees, visitors, or affiliates. 32 CFR § 117.11 lists a TCP among the supplemental FOCI mitigation measures. We cover how facility clearances work in our guide to facility security clearance and NISPOM.
Many others are asked for one. In practice, a TCP often shows up as a condition on an export license or agreement, a requirement in a government contract, or a flow-down from a prime. If a customer asks whether you have one, that’s usually the reason
Everyone else should treat it as the standard way to show control
If your shop handles technology subject to ITAR or the EAR, and any foreign national could plausibly reach it (unless an exemption clearly applies), whether an employee, a contractor, a vendor tech, or a visitor, a TCP is how you demonstrate that you’ve thought about it. ITAR registration isn’t a certification you pass. It’s self-attested, which means your internal compliance program, including policies, defined roles, and ongoing training, is the evidence. A TCP belongs in it. For the broader picture, see our guide to ITAR compliance.
The test is whether someone is a U.S. person or a foreign person, which isn’t the same as “born here.” U.S. citizens, lawful permanent residents (green card holders), and protected individuals such as refugees and asylees are U.S. persons. Someone on a temporary work visa is generally a foreign person, as are foreign national visitors, vendors, and contractors who don’t fall into those categories. We walk through those categories in our deemed export guide.
That answers a question we hear often: “Am I legally able to work under ITAR regulations?” Being a U.S. person is the baseline for accessing controlled technical data without authorization. A foreign person generally needs an export authorization first, and “we trust him” isn’t one. Access to controlled technical data should only be granted once authorization exists. A TCP records who has been cleared and on what basis.
A caution: citizenship and immigration status are sensitive information. Keep the records you need to make access decisions limited to HR and your compliance owner, not in a shared access list anyone can open.
A TCP follows a simple cycle: identify what’s controlled, control who can reach it, train the people involved, and review it on a schedule. The plan itself usually includes these elements:
| Element | What it covers | Example control |
| Controlled technology inventory | Which items, technical data, and software are controlled, under which list (a USML category or an Export Control Classification Number, ECCN), and where they live | A maintained inventory tied to the repositories and folders where the data is stored |
| Authorized personnel | Who may access it, and the basis for that access | Named access groups; access removed when someone changes roles or leaves |
| Physical security | Where controlled items and data can be handled, and who can enter | Badge-controlled areas, visitor logs and escorts, locked storage |
| Information security | How controlled data is stored, shared, and logged | A dedicated repository, group-based access, encryption, logging, email controls |
| Training and briefing | What people are told, and when | Initial briefing, annual refresher, briefing for new hires and visitors |
| Responsible party | Who owns the plan and approves changes | The Empowered Official or export compliance lead |
| Monitoring and review | How you catch drift and update the plan | Review on personnel changes, annual review, periodic access reviews |
| Incident reporting | What happens if someone gets access they shouldn’t | A defined escalation path and documented response |
This is the part that turns a TCP from a document into a control, and it’s the part most guides leave out. The plan can say “only authorized personnel may access this,” and access should be limited to authorized people only. Your systems have to make that true, and the security requirements in the plan should match the security measures actually configured.
Controlled drawings and models shouldn’t live wherever they happened to land: email attachments, personal folders, a laptop desktop. Use a dedicated repository, and make that the only place the data is supposed to be.
Limit membership to authorized personnel, manage it through groups so it’s easy to audit, and remove people promptly when roles change or they leave. Our team recently updated a manufacturer’s file platform documentation so administrators could enforce citizenship-based access restrictions consistently.
That’s useful for cloud storage. It isn’t a free pass. It covers the encrypted data, not a foreign person who can decrypt and view it. Who holds the keys and who can open the file are exactly what your TCP should control. If the data is also CUI, DFARS cloud requirements apply on top, which we cover in our guide to DFARS compliance.
External sharing should be off by default for the repository, with email controls that stop controlled files from leaving by accident. A single misdirected attachment to a non-U.S. person can create unauthorized access to controlled data and a reportable event, as we describe in our ITAR vs. EAR guide.
Know who accessed what and when, and make sure someone actually looks. Logs nobody reads don’t prove control.
A new hire’s laptop and access shouldn’t be set up the same way for everyone. Access that depends on status has to be staged accordingly, a point we cover in the deemed export guide.
Controlled technology isn’t only digital. A TCP identifies controlled areas, manages visitor badges and escorts, and restricts unauthorized access to sensitive technical information. A plant tour that passes controlled equipment or processes can create the same exposure as a shared folder. We cover visitor management in more detail in our guide to facility security clearance and NISPOM.
Someone specific has to own it. In ITAR-registered companies that’s usually the Empowered Official or an export compliance lead (what universities call an export control officer), supported by HR, facilities, and IT.
Because the TCP is a controlled document, treat changes carefully. At one manufacturer we work with, the ITAR-focused TCP requires legal approval for any change. When the company prepared for CMMC, we recommended only minimal adjustments to it. The same applies in reverse: when your systems change, check that the plan still describes reality.
Review it on a regular schedule, commonly an annual review, and whenever something changes: new personnel, a new foreign national employee or visitor program, a new system holding controlled data, or a new contract. A TCP that no longer matches who has access is worse than useless, because it documents a control you no longer have.
It can be. Under the Arms Export Control Act, 22 U.S.C. § 2778(c), a person who willfully violates the statute or its regulations faces a fine of up to $1,000,000 per violation, up to 20 years in prison, or both. Criminal penalties require willfulness. Civil penalties are a separate track that doesn’t require the same showing: the statute sets them at the greater of $1,200,000 or twice the value of the transaction, adjusted annually by regulation. Both civil and criminal penalties can apply to unauthorized exports, including a release of controlled technology to a foreign person.
A TCP prevents unauthorized access to controlled technical data through emails, shared folders, visitors, and new employee accounts.
If you can’t say with confidence who can open your controlled data today, or whether your systems match what your plan says, that’s the place to start. Our team works with manufacturers in the DoD supply chain on exactly this kind of access control, so the plan on paper matches what your IT environment actually enforces.
Schedule a free consultation with our team to talk through how your technology control plan and your IT environment fit together.
An export compliance program covers your whole export function: classification, licensing, screening (including against sanctions lists maintained by the Office of Foreign Assets Control, OFAC), recordkeeping, and training. A TCP is narrower. It controls access to specific controlled technology and is usually one component of the broader program.
For companies cleared under FOCI mitigation agreements, yes: DCSA requires an approved TCP. Outside that situation, a TCP is commonly required by a license condition, a contract, or a customer, and otherwise is the standard way to show you control foreign person access. Ask your Empowered Official or counsel which applies to you.
Organizations use TCPs for ITAR and EAR compliance because unauthorized foreign-person disclosures can trigger deemed export requirements. Several federal regulations may apply at once, so the plan should reflect what you actually handle. The format isn’t prescribed, so scale it to what you actually handle.
Universities run research labs that often work with controlled equipment and data, and their export control offices publish plans for researchers, so most search results come from them. Manufacturing work is typically different: it’s production work under a contract, with proprietary technical data and a facility to secure. That’s why a manufacturer’s TCP leans on access control, physical security, and IT systems rather than research project management.
No. The 50 Percent Rule concerns screening foreign entities based on their ownership by listed parties. A TCP controls access by individual people to controlled technology. They’re separate compliance questions, which we explain in our deemed export guide.
A template is a reasonable starting point, but a generic one won’t describe your systems, your facility, or your people. Use the structure to document controlled data locations, authorized personnel, and the security measures that enforce access restrictions.
A technology control plan (TCP) is a written plan that describes how a company…
Microsoft Secure Score is a numerical score that shows how well your Microsoft 365…
End-user security awareness training teaches the people who use your systems every day, from…