Megaspeed’s Entity List voting deadline runs from Commerce’s first circulation of a proposal, a date Bessent’s account of agency support does not establish. BIS procedure leaves the chair’s circulation step without a fixed deadline.
Months of support for adding Megaspeed to the Entity List do not establish that a federal voting deadline has expired. The relevant date is when Commerce’s chair first circulated a formal proposal to every member of the End-User Review Committee. Treasury Secretary Scott Bessent’s November 13 account leaves that date unknown.
In his CNBC interview, Bessent said Treasury, the Pentagon, USTR and State had favored listing Megaspeed for months. He directed questions about the internal process to Commerce and its Bureau of Industry and Security. His account does not identify a formal proposal, its circulation date or an ERC vote.
For export-control counsel updating a Megaspeed customer brief, the distinction changes the forecast. A 30-day countdown cannot responsibly be calculated from Bessent’s remarks, the first reported objections or the age of an investigation. Any assumption about when a new restriction might arrive must remain separate from the requirements already governing the transaction.
Under Supplement No. 5 to Part 744, a participating agency submits a listing proposal to the ERC chair. The committee must vote within 30 days after the chair first circulates it to all member agencies, unless the committee unanimously agrees to postpone. Submission to the chair and circulation to the committee are different events.
The regulation makes the chair responsible for circulating member-agency proposals. It specifies no separate number of days for completing that step. The gap matters to accountability. To establish an overdue vote, an inquiry would need the circulation date and any agreed postponement, not just the date an agency first urged action.
Bessent’s list of supporters also cannot be treated as a roll call. BIS identifies Commerce, Defense, Energy and State as voting members. Treasury is consulted as needed but does not vote. USTR is not on that voting roster. The interview does not establish how the voting members acted on any formal proposal.
Commerce chairs the process, but additions are decided by majority vote. An agency dissatisfied with the result can escalate it through the specified interagency review levels, potentially to the President. The rules also provide for escalation when a majority decision is not obtained within a prescribed deadline. An ERC vote can therefore mark an intermediate decision rather than the end of the process.
None of this establishes that Commerce withheld a Megaspeed proposal from circulation. The public remarks leave open whether circulation, voting or escalation has already occurred.
The House Foreign Affairs substitute for H.R. 8169 would let an ERC member submit a proposal directly to the committee and require a vote within 30 days after submission. The chair’s first circulation would no longer supply the starting date for that period.
The proposal preserves flexibility. The chair and submitting member could agree to an additional 15 days if more information were needed, and the committee could unanimously postpone the vote. The bill would thus change the triggering event without turning every proposal into an unconditional 30-day promise.
The House bill was ordered reported by the committee on April 22. The official legislative record checked on November 13 still ends at that committee action. The proposed change shows what is missing from the current procedure, a deadline tied to a member’s submission rather than a later act by the chair. It cannot establish that Commerce mishandled a particular proposal under the rules now in force.
Even a confirmed vote date would not by itself establish when a supplier’s obligations changed. The current procedures distinguish a final interagency decision from the steps needed to implement it. A final decision clears publication of an amendment, and the chair communicates decisions requiring amendments to BIS for drafting.
There is also a route that does not require waiting for a published listing. Under 15 CFR 744.11(c)(3), BIS may give an individual notice imposing a license requirement for specified items and a particular party when the provision’s conditions are met. The notice must identify the applicable requirement, exceptions limitation and review policy. Its existence cannot be inferred from a press interview or from the absence of a new list entry.
Senator Michael Bennet’s November 11 request to Commerce separately asks about is-informed notices and possible Entity List placement. He requested a response by November 24. That requested date neither starts the ERC voting period nor establishes that a restriction will take effect that day.
For an AI hardware exporter, the useful distinction is between evidence of pressure, evidence of a pending decision and evidence of an operative requirement. The same customer brief should keep those findings separate.
Procedural comparison as of November 13, 2026. The table shows how records under the ERC’s decision procedures would change a Megaspeed assessment. It does not reconstruct undisclosed events.
| Record | What it would establish | Timing consequence |
|---|---|---|
| Agency statement favoring listing | The agency’s stated position | No ERC voting deadline by itself |
| Proposal submitted to the chair | A formal proposal entered that step | Submission is not the current 30-day trigger |
| First circulation to all members | The event specified in Supplement No. 5 | Starts the voting period, subject to authorized postponement and escalation rules |
| ERC vote and any escalation record | The decision reached and whether further review followed | A vote alone does not establish an effective restriction |
| Implementing rule or applicable individual notice | The restriction and its scope | Supplies the operative terms and effective timing to assess |
The tax committees’ inquiry into Nvidia licensing files concerns records of transactions and approvals. An ERC circulation record answers a narrower question about agency responsibility. It can establish when the voting obligation began, allowing a later inquiry to distinguish time spent before circulation from time spent in voting, postponement or appeal.
Counsel may not have access to that interagency record. The customer brief should identify the procedural stage as unconfirmed until an authoritative disclosure establishes it, while assessing any actual rule or notice on its own terms. Commerce’s response to Bennet could narrow the gap if it identifies the proposal’s procedural dates. Another statement of support would leave the timing question unresolved.
New U.S. trade actions and the analysis that changes an import, customs, or counsel file, on weekday mornings after you confirm your address.
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.