No WAR Act
- Sponsor
- Rep. Hoyle, Val T. [D-OR-4]
- Committees
- Rules Committee (primary)
- Last action
- Apr 30, 2026
Bottom line
This bill aims to reinforce congressional war powers by blocking the use of budget reconciliation to fund military operations against Iran unless explicitly authorized by Congress.
What it actually does
This bill amends the Congressional Budget and Impoundment Control Act of 1974 to establish a new point of order in both the House and Senate. This procedural rule would prevent the consideration of any budget reconciliation measure that appropriates or provides budget authority for military hostilities against the Islamic Republic of Iran, unless Congress has explicitly authorized such hostilities through a declaration of war or a specific authorization for use of military force.
Proponents argue
Supporters argue this bill upholds the constitutional prerogative of Congress to declare war and authorize military force, preventing executive overreach in initiating conflicts without legislative consent, particularly through a process designed for fiscal policy. It ensures that decisions regarding potential military engagement with Iran are subject to robust legislative debate and approval.
Opponents contend
Opponents might argue that this bill could unduly restrict the executive branch's ability to respond to emergent national security threats, potentially hindering timely action in complex geopolitical situations involving Iran. They may also contend that it adds unnecessary procedural complexity to budget tools, potentially impacting the efficiency of government operations.
The bill is concise and can be read quickly, making its core intent clear to any informed reader.
Section 2, amending sections 310 and 904 of the Congressional Budget and Impoundment Control Act of 1974
Establishes a Point of Order Against Unauthorized Iran Hostilities Funding via Reconciliation
This provision amends existing budget law to create a new procedural rule in both the House and Senate. It makes it 'not in order' (meaning subject to a procedural challenge) to consider any budget reconciliation bill, resolution, amendment, or conference report that provides funding for military hostilities against Iran, unless Congress has already passed a declaration of war or a specific Authorization for Use of Military Force (AUMF) for such actions. This effectively prevents the executive branch from using the budget reconciliation process to fund military engagements with Iran without explicit congressional approval.
Supporters argue
Supporters argue this provision is crucial for restoring Congress's constitutional authority over war-making, preventing the executive branch from unilaterally engaging in military conflicts with Iran by leveraging the budget reconciliation process, which is intended for fiscal policy, not war authorization. It ensures a robust debate and explicit legislative consent before committing U.S. forces.
Critics contend
Critics might contend that this provision could tie the hands of the executive in responding to rapidly evolving national security threats, particularly if a swift military response against Iran is deemed necessary and a full legislative authorization process is too slow. They may also argue that reconciliation is a legitimate tool for funding, and this adds an unnecessary restriction.
Tradeoffs
The provision balances the constitutional separation of powers regarding war authorization against the need for executive flexibility in foreign policy and national security. It also weighs the procedural efficiency of budget reconciliation against the principle of explicit congressional approval for military engagements.
This section defines 'hostilities' to include any offensive military operation, strike, covert action, or sustained engagement involving armed conflict against Iranian military forces, territory, or government institutions. It also defines 'proxy force' as any foreign military, paramilitary, or irregular force operating at the direction, request, or with the material support of the United States.
Section 2(1), adding subsection (h)(2) to section 310 of the Congressional Budget and Impoundment Control Act of 1974.
Why it matters:This is standard legislative practice to define terms within the relevant section to ensure clarity and avoid ambiguity in application. It is not intended to be evasive.
Case for: Proponents argue that precise definitions are essential to prevent loopholes and ensure the point of order is applied consistently and effectively to all forms of military engagement, including indirect actions through proxies, which could otherwise circumvent congressional oversight.
Case against: Critics might argue that overly broad definitions of 'hostilities' or 'proxy force' could inadvertently capture legitimate defensive actions or support to allies that do not constitute unauthorized war, thereby creating unintended procedural hurdles for necessary national security operations.
Estimated impact: These definitions significantly broaden the scope of actions that would trigger the point of order, extending beyond direct military confrontation to include covert actions and support for proxy forces.