Sponsors (3)
The bill increases congressional oversight and data-driven management of export controls but raises meaningful risks to sensitive business/national-security information, centralized data privacy, and could impose unfunded administrative costs.
Congressional oversight committees will receive annual, detailed data on export licenses and end‑use checks, increasing congressional accountability and enabling oversight of export control enforcement.
Policymakers and program managers will get aggregated statistics on license applications, enabling them to track trends and better allocate resources for export control programs.
Law enforcement will be able to exclude information that could jeopardize investigations from disclosures, preserving investigative effectiveness while still allowing required reporting.
Export applicants and private-sector end users (including financial institutions) could have sensitive business or national security details exposed to Congress under per‑application disclosure requirements, risking proprietary or intelligence harms.
Immigrants and other applicants could face increased privacy and security risks because centralizing non‑aggregate sensitive report data creates greater opportunities for unauthorized access or insider exposure within government channels.
Federal employees and taxpayers may bear additional administrative burdens because the reporting obligation is subject to appropriations and could be unfunded, creating implementation and resource strains for the Department of Commerce.
Based on analysis of 2 sections of legislative text.
Requires annual, committee‑only reports on license applications, authorizations, and end‑use checks for exports to specified covered foreign entities, subject to appropriations.
Requires the Secretary to send annual reports to two congressional committees about export license applications, authorizations, and end‑use checks for items controlled under the export control statute when the recipient is a specified foreign “covered entity.” The reports must include per‑application details (applicant, item identification including ECCN and reason for control if applicable, end‑user and location, estimated value, decision and submission date), end‑use check dates/locations/results, and aggregate statistics. Reports are subject to appropriations, must protect information that could jeopardize investigations, and non‑aggregate data in the report are exempt from public disclosure under an existing statutory exemption; the first report is due within one year of enactment.
Introduced February 13, 2025 by Ronny Jackson · Last progress August 19, 2025