H.Con.Res.40 instructs the President, invoking section 5(c) of the War Powers Resolution (50 U.S.C. 1544(c)), to remove United States Armed Forces from hostilities against the Islamic Republic of Iran. The resolution preserves an exception for those force elements that remain necessary to defend the United States or an ally from an imminent attack, but conditions those defensive uses on compliance with the War Powers Resolution’s section 5(b) requirements unless Congress explicitly authorizes continued hostilities by a declaration of war or a specific authorization for the use of force (AUMF).
This is a targeted, short text: it relies on the statute that gives Congress a procedural route to order a withdrawal and it sets a narrow self‑defense carve‑out with statutory compliance obligations. For executives, the Department of Defense, congressional oversight offices, and regional partners, the resolution creates immediate legal and operational questions about which forces are covered, how to implement a withdrawal in an active theater, and how the exception for imminent self‑defense will be interpreted and monitored.
At a Glance
What It Does
The resolution directs the President to remove U.S. Armed Forces from hostilities with Iran by invoking the War Powers Resolution’s removal mechanism (50 U.S.C. 1544(c)). It allows limited retention of forces strictly to meet an imminent‑attack self‑defense need, subject to the War Powers Resolution’s reporting and procedural conditions in section 5(b).
Who It Affects
The directive directly constrains the Executive Branch (President, Secretary of Defense, combatant commanders) and triggers responsibilities for Congress (oversight, possible authorization votes). It also affects deployed service members, defense contractors supporting operations in the theater, and U.S. partners who rely on American force posture in the region.
Why It Matters
The resolution reasserts a statutory method for Congress to force a withdrawal without enacting a new law, clarifies that only a declaration of war or a fresh AUMF can sustain hostilities, and forces immediate operational and legal planning by the Pentagon and diplomacy teams about how to execute and monitor a removal.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
H.Con.Res.40 is short and statutory in its posture: it tells the President, under the War Powers Resolution’s explicit removal power, to take U.S. forces out of hostilities with Iran. The wording doesn’t attempt to define every tactical detail; instead it invokes the WPR’s mechanism that Congress wrote to reclaim control over continuing combat operations without passing a new statute.
The resolution therefore functions as a legal instruction to the Executive that hinges on an existing federal statute rather than creating a standalone new prohibition.
The resolution carves out a limited safety valve: units or elements that are necessary to defend the United States or an ally from an imminent attack may remain in place. But those defensive uses are not freeform — the President must “comply fully” with the War Powers Resolution’s section 5(b) obligations with respect to any such use.
That reference imports the WPR’s consultative and reporting expectations (and the framework Congress designed to limit open‑ended uses of force), and it draws a line: only Congress, by declaring war or passing a specific AUMF, can permit hostilities to continue beyond that construct.Operationally, the resolution triggers a sequence of executive actions: identifying which forces are engaged in “hostilities” against Iran, planning and executing a withdrawal or repositioning, and establishing monitoring and reporting steps tied to any retained defensive forces. The language leaves implementation details to the President and Defense Department but sets clear limits on the statutory authorities available for continuing a campaign.
It also imports a statutory compliance obligation that can be the basis for congressional oversight and public scrutiny.The text is succinct enough to raise immediate legal questions — chiefly around enforceability and interpretation — but long enough to force a change in executive planning if Congress and the President treat the resolution as operative under the War Powers statute. The resolution therefore matters less for novel legal doctrine than for the practical consequences it imposes on operations, reporting, and legislative bargaining over any subsequent authorization.
The Five Things You Need to Know
The resolution invokes 50 U.S.C. 1544(c) — the War Powers Resolution provision that authorizes Congress to direct the President to remove U.S. forces — rather than creating new statutory penalties or funding restrictions.
It is a concurrent resolution, addressed to the President and adopted (if passed) by both chambers jointly; it does not amend substantive criminal or fiscal law but relies on the WPR’s existing removal mechanism.
The text preserves a narrow exception allowing ‘‘elements of the Armed Forces that may be necessary to defend the United States or an ally or partner’’ to remain for imminent self‑defense.
Any continued defensive use under that exception must comply fully with section 5(b) of the War Powers Resolution — importing the WPR’s reporting and procedural obligations for short‑term use of force.
The resolution states that hostilities may continue only if Congress explicitly authorizes them by a declaration of war or a specific authorization for use of military force (AUMF).
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Directive to remove U.S. forces from hostilities against Iran
This is the operative sentence directing the President to remove U.S. Armed Forces from ‘‘hostilities against the Islamic Republic of Iran.’’ Practically, it instructs the Executive to end participation in active hostilities under the War Powers Resolution removal authority. The clause does not enumerate which units or operations qualify as ‘‘hostilities,’’ so implementation will require executive identification of engaged forces and orders to execute withdrawal or posture changes.
Limited self‑defense carve‑out for imminent attack
The resolution explicitly allows retention of ‘‘those elements of the Armed Forces that may be necessary to defend the United States or an ally or partner’’ from imminent attack. That language narrows permitted continuing uses to defensive, imminent‑threat situations rather than offensive or coercive operations. It creates a material discretion point for commanders and the President about what counts as ‘‘necessary’’ and ‘‘imminent,’’ which will drive both operational decisions and subsequent congressional oversight.
Conditions for continued use and requirement for congressional authorization
The text conditions any continued defensive use on the President’s full compliance with section 5(b) of the War Powers Resolution — effectively importing statutory reporting, consultation, and time‑limit expectations into the carve‑out. It then states that nothing in the resolution permits continuation of hostilities ‘‘unless explicitly authorized by a declaration of war or a specific congressional authorization for use of military force against Iran,’’ placing the onus on Congress to provide affirmative statutory authority to sustain operations beyond the WPR framework.
This bill is one of many.
Codify tracks hundreds of bills on Foreign Affairs across all five countries.
Explore Foreign Affairs in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Deployed service members and their families — a directed withdrawal reduces exposure to combat and may shorten deployments for units considered to be in ‘‘hostilities.’’
- Congressional committees and oversight offices — the resolution reactivates a statutory oversight tool (WPR section 5(c)) and creates a clear basis for hearings, information demands, and legislative leverage.
- Advocacy groups and U.S. partners seeking de‑escalation — the resolution signals a statutory path toward pulling U.S. forces back from an active confrontation, which could strengthen diplomatic levers for reducing regional tensions.
Who Bears the Cost
- The Executive Branch (President, DoD) — the administration must plan and execute potentially complex withdrawals, revise mission objectives, and answer to statutory compliance demands, constraining operational flexibility.
- Combatant commanders and deployed units — commanders will face logistical burdens, possible capability gaps during drawdown, and short timelines to reconfigure missions while protecting forces.
- Defense contractors and logistics suppliers — contracts tied to operations in the theater may face curtailment, causing program disruptions and financial impacts tied to rapid redeployment.
Key Issues
The Core Tension
The central tension is between congressional constitutional responsibility to check and authorize the use of U.S. armed force and the executive’s need for timely, flexible military decision‑making: the resolution reasserts statutory congressional control to end hostilities, but mandating withdrawal and narrowly limiting defensive retention may create operational risks, diplomatic fallout, and legal uncertainty about who decides when ‘‘necessary’’ and ‘‘imminent’’ conditions are met.
Enforceability is the first practical question. The War Powers Resolution provides Congress a removal mechanism by concurrent resolution, but the historic enforcement pathway (and potential judicial review) for a statutory direction to withdraw is legally unsettled.
The resolution’s language does not add statutory penalties or funding cuts to compel compliance, leaving oversight, political pressure, and possible litigation as the most likely enforcement tools.
Operationally, the bill’s brevity shifts hard choices to the Executive: the government must decide which forces qualify as engaged in ‘‘hostilities,’’ how to withdraw forces without creating security vacuums, and how to measure ‘‘necessary’’ elements retained for imminent self‑defense. Those determinations will drive both legal disputes and on‑the‑ground risk.
The exception’s requirement to ‘‘comply fully’’ with section 5(b) imports procedural obligations but leaves open interpretive gaps — for example, what reporting suffices to justify continued defensive presence and how long such presence can lawfully continue absent a new authorization.
Finally, the resolution raises diplomatic and alliance management questions. A rapid or poorly coordinated withdrawal could leave partners exposed and complicate intelligence sharing and coalition planning.
Conversely, the resolution’s existence may strengthen U.S. bargaining positions by placing a clear congressional boundary on acceptable executive actions, but it could also constrain nimble responses to emerging threats in the region.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.