Privacy and preparation
Supply chain embargo scope review: technical data vs procurement records
By SourceX Editorial · Reviewed by Noah Loul ·
9 sections
Short answer
Separate restricted technical data from procurement workflow records field by field, not system by system. Keep the transactional skeleton of dates, quantities, statuses and approval steps; exclude or reduce the free text, attachments and change records that can describe how a part is designed, made or repaired; flag embargo and sanctions exposure; and have counsel sign a source and exclusion brief before any record leaves.
Redaction
Supply chain embargo scope
Key takeaways
- Separate technical data from workflow records field by field; dates, quantities, statuses and approvals usually carry no design or production content.
- An embargo scope review covers three exposures: destinations and parties, technical content in the records, and who will see them.
- Line notes, RFQ attachments, supplier qualification files, change notices and nonconformance reports are where technical content hides.
- Markings such as distribution statements route a whole program to exclusion, and a commercially sold part does not make its customer drawing public.
- Counsel signs a versioned source and exclusion brief before records move, and export clearance never substitutes for the right to license.
How do you separate restricted technical data from general procurement workflow records?
Review each field and attachment type for what it can contain, then keep, reduce or exclude it, rather than approving or rejecting a whole system. A purchase order's dates, quantities, status changes and approval steps rarely say anything about how a part is designed or made. Its line description, attached drawing and supplier quality notes can.
The ITAR defines technical data as information required for the design, development, production, manufacture, assembly, operation, repair, testing, maintenance or modification of defense articles, including information in blueprints, drawings, photographs, plans, instructions or documentation. The same definition excludes basic marketing information on function or purpose and general system descriptions. The EAR controls technology for dual-use items on a parallel logic. Neither rule cares whether the information sits in an engineering vault or in a procurement ticket.
That is why the separation is a scope review of record types, written down as a brief that names each source, what was kept, what was taken out and who decided. The brief is the deliverable; the cleaned extract follows from it.
Why an embargo scope review is more than a country list
A country screen on suppliers and customers catches only one of three exposures. The other two are the technical content inside the records and the nationality of whoever will see them.
At a glance
Why an embargo scope review is more than a country list
On the country side, Part 746 of the EAR collects the licensing rules for destinations under general embargoes or comprehensive sanctions; its introduction still names Cuba, Iran and Syria, and it separately requires a license to export almost any item subject to the EAR to North Korea. The list moves: BIS relaxed its Syria controls in September 2025, so screen against the text in force on the day of the extract. Records of past transactions touching those places are not technical data in themselves, but they raise sanctions questions that belong with counsel, not with the person building the extract.
On the people side, the EAR treats a release of technology or source code to a foreign person inside the United States as an export to that person's most recent country of citizenship or permanent residency. A release can happen through visual inspection or through oral or written exchanges. If a labeling vendor, an offshore reviewer or a buyer's engineer will read the records, that review step is itself the export question, so the brief has to say who will see what.
- Destination exposure: counterparties, ship-to addresses and end users in embargoed or sanctioned places.
- Content exposure: design, production, repair or test information embedded in fields and attachments.
- Access exposure: the nationality and location of everyone who will view or process the records.
Where technical data hides inside procurement records
Technical content enters procurement systems through the fields people use to make sure the right part gets bought. The table lists the usual places and a default treatment that counsel can then confirm or tighten.
Change records deserve special care because they keep what the live record no longer shows. Odoo's product lifecycle documentation, for example, says design files archived from a bill of materials are removed from the bill of materials but remain accessible in the engineering change order, so an extract that reads only current records can still pull old drawings through the change history.
| Record | Field or attachment | What can hide there | Default treatment |
|---|---|---|---|
| Purchase order | Line description and notes | Drawing number with revision, material and process callouts, tolerances | Keep part key and quantity; replace text with a category code |
| Request for quotation | Attachments and statement of work | Drawings, models, specifications, inspection plans | Exclude attachments; keep RFQ dates, invitee count and award outcome |
| Supplier approval | Qualification evidence | First article reports, process specifications, special process approvals | Keep approval status and dates; exclude evidence files |
| Engineering change notice | Change description and design files | Before and after design detail, archived drawings | Keep change type, dates and approval chain; exclude description and files |
| Nonconformance report | Defect description and disposition notes | Measured values, failure analysis, rework instructions | Keep defect category and disposition code; exclude measurements and instructions |
| Email and chat threads | Message bodies and attachments | Anything above, pasted or forwarded | Exclude unless a reviewer clears each thread |
| Contract and order header | Markings, clauses, program codes | Distribution statements, CUI markings, program identifiers | Use as a routing flag for exclusion; do not extract the marking text itself |
Which markings and public-domain claims change the default
A marking on the source document overrides any default in the table. The CUI Registry defines Controlled Technical Information as technical information with military or space application that is subject to access and dissemination controls, and says it is marked with distribution statements B through F. Its examples include engineering drawings, technical reports, data sets and software code. Export Controlled is a separate CUI category.
Any record that carries one of those markings, or belongs to a contract that requires them, goes into the excluded set for the whole program until counsel says otherwise. A procurement line that merely cites the drawing number of a marked document should be treated as related to it: the number may be harmless, but the line text next to it usually is not.
Public availability works in the other direction, and it is narrower than it looks. The EAR says information that is published, meaning available to the public without restrictions on further dissemination, is not subject to the EAR, and the ITAR excludes public-domain information from technical data. A supplier's catalog page can be public. A customer's drawing that the supplier received under a purchase order is not public because the part is sold commercially.
The counsel-reviewed source and exclusion brief
This is the reusable asset: one brief per extract, versioned and dated, that counsel signs before records move. It has a header block and one row per source, and a reviewer should be able to check any record in the extract against it.
At a glance
The counsel-reviewed source and exclusion brief
Fill the header first, because the scope decisions in it change every row below.
- Header: brief version, date, extract purpose, systems and date range in scope, owner, counsel reviewer.
- Programs and customers excluded in full, with the reason code (marked contract, defense program, customer restriction).
- Destinations and parties flagged for sanctions review, with the screening list and date used.
- Recipients: every party that will view or process the records, with location and whether foreign persons are involved.
- Per-source rows: source system and record type, fields kept, fields reduced and how, fields excluded, attachments policy, change-history policy.
- Classification questions sent to counsel or the export compliance owner, each with the answer and date.
- Sampling check: how many records were inspected by hand after the filters ran, and what was found.
- Sign-off: names and roles of the procurement owner, data owner and counsel, with dates.
Why the fastest exclusion rule usually fails
The tempting shortcuts each leave a route for technical content to get through. Naming them in the brief makes it obvious that the team considered and rejected them.
Dropping attachments but keeping all text fails because buyers and engineers paste specifications into line notes and approval comments. Excluding only the defense customer fails because a commercial program can buy dual-use parts, and because shared suppliers carry the same drawings across programs. Trusting an item master's classification field fails when nobody maintained it, and a blank or default value is not a classification. Filtering current records only fails because change history and archived files keep what the current view hides.
The rule that holds is narrower and slower: keep only fields whose content is structurally limited, such as dates, codes, quantities and status values, and admit free text only after a reviewer has inspected a sample and counsel has accepted the result.
Structural limits also need checking rather than assuming. A commodity code is safe only if the code list itself carries no design detail, and some companies build codes that encode material grade, finish and process. A status field is safe only if users cannot type into it. Test each kept field by listing its distinct values, or a large sample of them, and reading the list before trusting the filter.
Illustrative case: a contract manufacturer with mixed programs
The manufacturer below is hypothetical, and every count is illustrative. A contract manufacturer wants to offer purchasing and supplier-approval records from its ERP covering six years and three business lines: industrial equipment, medical device housings and a defense subassembly program.
The brief excludes the defense program in full, because its contracts carry distribution statements and its purchase orders cite marked drawings. For the other two lines it keeps purchase order headers, line quantities, dates, approval steps and receipt events, and replaces line descriptions with a commodity code. RFQ attachments, supplier qualification files, engineering change descriptions and nonconformance measurements are excluded everywhere.
The hand check after filtering finds the exception. In a sample of 400 commercial purchase order lines, 9 had approval comments that quoted a tolerance and a heat-treatment specification copied from a customer drawing, and 2 of those drawings belonged to a customer who also buys for a defense prime. The team extends the exclusion to all approval comments, records the finding in the brief, and sends counsel a question about the two shared parts. Counsel answers that both part histories are excluded in full.
What remains is a clean workflow record: who requested, who approved, when the supplier quoted, when goods arrived and how exceptions were dispositioned, with no content about how anything was made.
Decisions that belong to counsel, not the data team
The data team can apply the brief, but it cannot decide what a record is under export or sanctions law. Hand the decision over whenever classification is uncertain, whenever records concern embargoed destinations or listed parties, and whenever foreign persons will see records that have not been cleared.
Stop entirely if review turns up a possible past violation, such as a drawing sent to a supplier in a place that needed a license. That finding goes to counsel and the export compliance owner first, and the extract waits.
Export clearance is also only one gate. The company's right to license the records depends on customer contracts, supplier terms and any government data-rights clauses, and removing technical content does not create that right. De-identification of people in the records is a further, separate step.
Keep counsel's answers inside the brief rather than in a separate email chain. For each classification question, record the record type it covers, the facts counsel relied on, the answer, the date and whether it applies only to this extract or to future ones. When the next extract is prepared, the team can reuse settled answers and send only the new questions, and a later reviewer can see why a field was kept.
Revisit the brief whenever its inputs change: a new program or customer, a new supplier country, a change to the systems in scope, a new recipient, or an update to the regulations it relied on. A brief that was correct for last year's extract can be wrong for this year's without any change to the records themselves.
Offering cleared procurement workflow records
Procurement histories with approvals, supplier responses and exception handling are useful to AI developers building agents for purchasing and supply chain work, and a signed exclusion brief shows early which parts of a company's records can be in scope at all.
When a manufacturer decides to license cleared purchasing history, SourceX runs the work from sourcing and rights review through contracting, preparation, delivery and payment, turning the selected records into a licensed dataset for AI developers. Records go nowhere until the company has approved the scope and terms and signed the agreement.
Eligibility is checked through a brief company assessment, without uploading any data.
Frequently asked questions
Is a part number on a purchase order technical data?
Usually a bare part number is not, because it does not say how to design or make the part. The text and attachments around it often are, and a part number that points to a marked or controlled drawing should route that record to review. Counsel makes the call for anything uncertain.
Does removing attachments make procurement records safe to share?
No. Line notes, approval comments and nonconformance descriptions often contain specifications copied from drawings, and change histories can still hold archived files. Treat free text as excluded until a reviewer has inspected a sample and counsel has accepted the filter.
Can showing records to a foreign reviewer in the United States be an export?
Under the EAR, releasing technology or source code to a foreign person in the United States is a deemed export to that person's most recent country of citizenship or permanent residency, and a release includes visual inspection. Who will see the records is therefore part of the scope review.
If a part is sold commercially, is its documentation public?
Not automatically. Published information under the EAR means available to the public without restrictions on further dissemination. A customer drawing received under a purchase order is normally shared under restrictions, even when the finished part is a catalog item.
Who should sign the source and exclusion brief?
The procurement or supply chain owner who knows what the fields contain, the data owner who runs the extract, and counsel or the export compliance owner who decides classification questions. Record names, roles and dates in the brief.
Sources
- The ITAR defines technical data as information required for the design, development, production, manufacture, assembly, operation, repair, testing, maintenance or modification of defense articles, including blueprints, drawings, photographs, plans, instructions or documentation, and excludes public-domain information, basic marketing information on function or purpose and general system descriptions. Source
- Part 746 of the EAR contains the licensing requirements for countries under general embargoes or comprehensive sanctions, currently Cuba, Iran and Syria, and requires a license to export almost any item subject to the EAR to North Korea. Source
- Under the EAR, releasing technology or source code to a foreign person in the United States is a deemed export to that person's most recent country of citizenship or permanent residency. Source
- Under the EAR, technology or source code is released through visual or other inspection by a foreign person, or through oral or written exchanges with a foreign person. Source
- Under the EAR, unclassified technology or software that is published, meaning available to the public without restrictions on further dissemination, is not subject to the EAR. Source
- The CUI Registry defines Controlled Technical Information as technical information with military or space application subject to access and dissemination controls, marked with distribution statements B through F, with engineering drawings, technical reports, data sets and software code as examples. Source
- Odoo's documentation says design files archived in an engineering change order are removed from the bill of materials but remain accessible in the change order. Source
- BIS published a final rule on September 2, 2025, Relaxing Export Controls for Syria, which implements Executive Order 14312 and eases EAR restrictions on Syria. Source
See if your company qualifies
A short company assessment. No data uploads are needed.