# ITAR Technical Data Transfer Log Worksheet > Source: https://netray.co/tools/itar-technical-data-transfer-log-worksheet > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer An editable log that records each release of technical data, who received it, under which authorization and how it was sent. ## Category compliance-legal ## Industry Defense Contracting ## Region United States ## Audience - Export compliance officer - Engineering manager ## Tool **Kind:** worksheet **Mode:** editable **Columns:** #### Date sent **Key:** date **Type:** date #### Document or drawing **Key:** doc **Type:** text #### Rev **Key:** rev **Type:** text #### USML category or ECCN **Key:** category **Type:** text #### Recipient **Key:** recipient **Type:** text #### Country **Key:** country **Type:** text #### Authorization **Key:** auth **Type:** select **Options:** - DSP-5 - TAA - MLA - Exemption - License exception - NLR - Domestic US person #### Authorization number **Key:** auth_no **Type:** text #### Method **Key:** method **Type:** select **Options:** - Encrypted email - Secure portal - Encrypted media - Hand carry - Verbal #### Files sent **Key:** files **Type:** number **Format:** integer **Rows:** **Date:** 2026-10-05 **Doc:** HSG-2210 housing drawing **Rev:** C **Category:** USML Cat VIII(h) **Recipient:** Prime engineering **Country:** United States **Auth:** Domestic US person **Auth no:** N/A **Method:** Secure portal **Files:** 3 **Date:** 2026-10-09 **Doc:** CBL-884 harness spec **Rev:** B **Category:** ECCN 9E003 **Recipient:** UK subcontractor **Country:** United Kingdom **Auth:** License exception **Auth no:** Per file note **Method:** Encrypted email **Files:** 2 **Date:** 2026-10-14 **Doc:** MNT-120 mount drawing **Rev:** A **Category:** EAR99 **Recipient:** Canadian machine shop **Country:** Canada **Auth:** NLR **Auth no:** N/A **Method:** Secure portal **Files:** 1 **Date:** 2026-10-16 **Doc:** ELX-301 board layout **Rev:** D **Category:** USML Cat XI(d) **Recipient:** Allied partner **Country:** Australia **Auth:** TAA **Auth no:** Enter number **Method:** Encrypted media **Files:** 4 **Totals:** #### Total files transferred **Key:** files **Agg:** sum **Format:** integer #### Transfers logged **Key:** doc **Agg:** count **Format:** integer **Summary:** #### Average files per transfer **Key:** avg_files **Expr:** sum_files / count **Format:** decimal **Notes:** Example classifications are illustrative placeholders, not determinations. Classify your own items using the USML or Commerce Control List, or request a commodity jurisdiction or classification ruling when unsure. Authorization column values are suggestions, adjust to your program. Not legal advice. ## Content **Intro:** Auditors and the State Department ask for proof of what technical data left your company, to whom and under which approval. This worksheet gives export staff a simple running log that exports cleanly to Excel. **Sections:** #### How to use the log **Body:** Enter one row per release event. Record the document and revision, the controlled category you determined, the recipient and country, the authorization used and its number, and how the data moved. Keep the list append-only: correct mistakes with a new dated row rather than overwriting history. **Bullets:** - Log before or at the time of sending, not later - Tie each row to an authorization number - Record the transmission method - Review monthly for gaps #### Why a log helps **Body:** ITAR requires registrants to keep records of defense article and technical data transactions, generally for five years. EAR has its own recordkeeping rule. A single log answers the common audit questions fast: who received revision C of this drawing, and which agreement covered the transfer. It also reveals patterns such as many transfers with no authorization number. #### Reading the totals **Body:** File counts show volume by period, which helps you see where to automate or tighten controls. Pair the log with a quarterly sample: pick five rows, trace each to the signed agreement and the stored message. Differences between the log and reality are the findings you want to catch before an outside party does. #### Common mistakes **Body:** Using email for controlled data without encryption, logging a verbal discussion as nothing, and forgetting that uploading to a cloud tool outside the U.S. may itself be an export. Include verbal and visual releases. **Cta:** Netray can discuss pulling document release events from your ERP or PLM into a log like this, on-prem. The worksheet works on its own. **Faq:** #### Does ITAR require a transfer log? **Answer:** ITAR requires records of defense article and technical data transactions, generally retained for five years. It does not prescribe this exact format, so a log like this is a practical way to meet the requirement and to answer audit questions quickly. #### Should domestic transfers be logged? **Answer:** Transfers to U.S. persons are not exports, but many companies log them for CUI traceability. Include them if you need a full chain of custody, and mark the authorization as domestic US person. #### What if I am unsure of the classification? **Answer:** Do not guess. Ask your empowered official, request a commodity jurisdiction determination from the State Department, or a classification from Commerce BIS. Treat the item as controlled until you have an answer. #### Can I attach the files? **Answer:** No, keep the log free of controlled content. Store the transferred files in your controlled repository and reference the document number and revision here. ## Search terms itar technical data log, export control transfer log excel, itar recordkeeping template, technical data release log, itar 122.5 records, export compliance tracking spreadsheet --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json