AI OVERWATCH could send an already-approved China chip order back into licensing, but that consequence depends on which version Congress passes. The House committee substitute and the upon enactment. A later . For export counsel, the difference determines whether an approved but unshipped balance would need fresh authorization.
The immediate task is to identify orders with unused quantities under an existing license. Nothing in those legislative demands itself cancels an approval. Nor does the narrower amendment guarantee that an approval will survive. Existing BIS revocation authority and the terms of each license continue to govern.
Coverage depends on the text. The Senate versions use different technical tests and exclude chips not designed or marketed for data centers and certain non-GPU microprocessors. Recipient headquarters and ultimate-parent headquarters also matter. The comparison concerns orders covered by the relevant provision, not every Nvidia product or shipment to China. S. 4456 and the July amendment separately require denial for restricted integrated circuits. None of the waiting periods makes those chips eligible.
That would change the position of an exporter that has cleared U.S. licensing but has not shipped. The remaining order would lose its existing authorization under the proposed provision. A signed purchase order or completed testing would not replace that authorization. The relevant exposure is the unshipped balance tied to the terminated license, rather than the original face value of every approved sale.
The earlier texts also make replacement authorization more difficult than a routine resubmission. Their temporary prohibition requires denial of covered applications until 14 days after an American Artificial Intelligence Victory Strategy is submitted to Congress. The period therefore does not begin simply because the legislation takes effect. A company cannot derive a reliable restart date by adding 14 days to enactment.
Once that prohibition ends, the certification and review requirements remain. The strategy's submission would remove one obstacle. It would not approve the exporter, clear the end user or restore the old license.
The submitted amendment is the specific text compared here. Its appearance in the Congressional Record does not establish that Congress has adopted it or that its wording will survive negotiations.
Proposed treatment of covered chip licenses
The comparison below reflects the identified public texts as of November 10, 2026. It describes proposals, not current shipment authority. Timing applies where the text permits licensing. A final enacted text could change any of these provisions.
Public text
Existing covered licenses
New license timing
H.R. 6875, January 21 committee substitute
Terminated upon enactment
Strategy-linked denial plus advance certification of at least 30 days, or 60 for submissions from July 10 through September 7. The House text also provides for disapproval through an enacted joint resolution.
S. 4456, April 30 introduced bill
Terminated upon enactment
Strategy-linked denial and 30-day certification, extended to 60 days for submissions from July 10 through September 7.
S.Amdt. 6575, July 13 NDAA amendment
No express automatic termination clause
Certification at least 15 days before approval. No strategy-linked licensing prohibition.
A waiting period is not a delivery timetable
Under the July amendment, the 15-day minimum begins before approval, after Commerce submits the application, proposed license and required certification to the relevant committees. It is not a promise that BIS will finish processing an application in 15 days. The proposed conditions include U.S. supply, foundry capacity, end-use controls and safeguards against unauthorized remote access.
The distinction affects any contract that treats the granting of a license as the last government step before delivery. Counsel should retain the application date and the certification-submission date as separate fields. Neither the purchase-order date nor an anticipated congressional vote starts that review period.
The shipment-release file needs an enactment contingency
For each approved but unshipped covered order, counsel should preserve the license number, remaining authorized quantity, recipient and ultimate parent, license conditions, scheduled shipment and contractual consequence of losing authorization. The file should distinguish an existing approval from a pending application. Those categories face different transition risks under the earlier texts.
The analysis belongs beside the review of BIS H200 licenses from authorization to use. That review asks whether permission became shipment and usable capacity. The legislative question is whether the authorization supporting the next shipment survives enactment.
There is no safe inference that omission of automatic termination makes existing licenses irrevocable. Under 15 CFR 750.8, export and reexport licenses remain subject to revision, suspension or revocation without notice. BIS may stop a shipment in transit, and the rule requires retention of supporting records after revocation or suspension.
The next decisive record is the language actually advanced for passage. Counsel should compare its treatment of pre-enactment approvals with the license supporting each unshipped balance. If the termination clause returns, that balance needs a replacement-authorization contingency. If it remains absent, the file must still reflect current license conditions and any BIS action. A statement that AI OVERWATCH is in the NDAA cannot answer either question on its own.
Daily Trade Brief
Get the next one in your inbox.
New U.S. trade actions and the analysis that changes an import, customs, or counsel file, on weekday mornings after you confirm your address.
From reading to review
Run the numbers on your lane.
The duty calculator runs the current stack for any HTS code and origin. A free account opens full tool output, AD/CVD detail, Chapter 98 processing, and available exports.