H. Con.
Res. 75 is a concurrent resolution that invokes section 5(c) of the War Powers Resolution to direct the President to remove United States Armed Forces from hostilities against the Islamic Republic of Iran. The resolution identifies February 28, 2026 as the date U.S. forces entered hostilities and orders removal of the “use of United States Armed Forces” from such hostilities no later than 30 days after that date unless Congress enacts a declaration of war or a specific authorization for use of military force (AUMF) against Iran.
The resolution includes three practical limits: it preserves the right of U.S. forces to defend against imminent attacks, allows defensive troop presence in the region, and excludes forces not engaged in hostilities. It also expressly protects intelligence collection, analysis, and sharing with partners (subject to the President’s determination) and states that the resolution does not itself authorize military force.
At a Glance
What It Does
The resolution uses the War Powers Resolution’s section 5(c) mechanism to order the President to end U.S. participation in hostilities against Iran within a 30‑day window tied to February 28, 2026, unless Congress provides explicit authorization. It carves out defensive actions, defensive force posture, and non‑hostile regional presences, and preserves intelligence activities and sharing when the President finds them appropriate.
Who It Affects
The resolution directly constrains the President and the Department of Defense operationally, affects U.S. forces deployed in the Middle East (including potential ground combat units), and implicates Congress’s oversight role. It also matters to allied militaries and intelligence partners that rely on shared operations and information.
Why It Matters
The measure is a direct, statutory-pathway attempt by Congress to halt hostilities without passing a statute: it tests the War Powers Resolution’s mechanism for forcing withdrawal, raises enforcement and compliance questions, and creates immediate operational timelines and planning requirements for the military and intelligence community.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
H. Con.
Res. 75 begins with findings that frame Iran as an adversary and identifies February 28, 2026 as the date U.S. forces entered hostilities. Rather than asking the President to end military activity, the resolution invokes the War Powers Resolution’s specific provision that allows both Houses to direct removal of forces via concurrent resolution.
That statutory hook is the vehicle Congress uses here to impose a deadline on the executive branch.
The operative command appears in Section 2: the resolution directs the President to “remove the use of United States Armed Forces from hostilities” against Iran by not later than 30 days after the date named in the findings, unless Congress enacts a declaration of war or a specific AUMF. Practically, the text targets combat roles and occupations tied to hostilities; it does not automatically require a complete regional withdrawal of every U.S. presence.
Section 2(b) then provides three narrow exceptions—response to imminent attack, maintaining a defensive troop presence, and leaving in place forces not engaged in hostilities—each of which preserves operational flexibility for narrowly defined defensive or non‑hostile missions.Section 3 addresses intelligence: the resolution says it must not be read to disrupt intelligence collection, analysis, or sharing, including sharing with coalition partners, but conditions that protection on the President’s determination that sharing is appropriate and in the national security interest. Finally, Section 4 clarifies that the resolution itself is not an authorization for the use of military force, pointing readers back to the War Powers Resolution’s existing framework and to Congress’s separate constitutional power to authorize force.Because the measure is a concurrent resolution—a form that requires passage in both chambers but does not go to the President for signature—the bill relies on the War Powers Resolution’s design that such a concurrent resolution can instruct removal.
That procedural detail matters for how the directive would be issued and enforced if the resolution were adopted.
The Five Things You Need to Know
The resolution invokes section 5(c) of the War Powers Resolution as the statutory mechanism to direct removal of forces.
It sets a 30‑day deadline for removal tied to the bill’s finding that hostilities began on February 28, 2026, unless Congress enacts a declaration of war or a specific AUMF.
Section 2(b) carves out continued actions to repel imminent attacks, permits a defensive troop presence in the region, and exempts forces not engaged in hostilities.
Section 3 preserves intelligence collection, analysis, and sharing with coalition partners, but conditions sharing on a presidential determination of appropriateness and national security interest.
The measure is a concurrent resolution—so it would need both chambers to concur but does not require presidential signature; it relies on the War Powers Resolution’s built‑in enforcement mechanism rather than creating new penalties.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Factual predicate and legal framing
This section lists reasons Congress considers Iran an adversary and pins the start of U.S. hostilities to February 28, 2026. That date functions as the statutory clock’s anchor for the 30‑day removal directive; any challenge to timing or scope will turn on whether deployments after that date qualify as ‘‘hostilities’’ under the War Powers Resolution.
Directive to remove use of forces within 30 days or until Congress authorizes force
Section 2(a) is the operative command: remove U.S. participation in hostilities against Iran by no later than 30 days after the statutory anchor unless Congress authorizes continued action. For operators and planners, the phrasing targets ‘‘use of forces in hostilities’’ (combat operations, occupation, or ground combat roles) rather than every presence in the region, creating interpretive questions about posture versus kinetic engagement.
Three narrow exceptions that preserve defensive options
Congress explicitly preserves the President’s ability to defend against imminent attack, to maintain a troop presence for defensive purposes, and to leave non‑hostile forces in place. Each carve‑out is succinct but deliberately vague—terms like ‘‘imminent attack’’ and ‘‘defensive purposes’’ will be focal points for executive and DoD interpretations and could permit continued operations under narrowly framed justifications.
Protecting intelligence cooperation; confirming non‑authorization of force
Section 3 safeguards intelligence activities and bilateral/multilateral intelligence sharing when the President finds it appropriate, which reduces risk of immediate operational gaps in partner cooperation but grants the executive discretion over sharing. Section 4 reiterates that the resolution does not itself authorize the use of military force, preserving the constitutional requirement that any new, affirmative authorization come from Congress by declaration or statute.
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 U.S. servicemembers and their families — if the directive is implemented, it limits exposure to ongoing combat operations and could accelerate rotation or redeployment planning.
- Members of Congress seeking stronger legislative control over war-making — the resolution operationalizes a War Powers tool to force executive action without new statute.
- Regional civilians and humanitarian actors in areas of direct U.S.–Iran hostilities — a congressional directive to end U.S. combat roles reduces the risk of further kinetic escalation in affected localities.
Who Bears the Cost
- The President and National Security Council — the resolution would constrain executive operational choices and compress planning timelines for withdrawal and contingency operations.
- Department of Defense and combatant commanders — implementing a 30‑day removal directive will impose logistical, personnel, basing, and mission‑replanning costs; it may require rapid redeployments and reconfiguration of force posture.
- Allied partners and regional deterrence networks — allies that depend on U.S. combat presence for deterrence or stability may face gaps in security posture and intelligence sharing tensions despite the intelligence carve‑out.
Key Issues
The Core Tension
The central dilemma is constitutional and operational: Congress seeks to reclaim its Article I war‑making authority and end U.S. combat involvement quickly, but doing so via a 30‑day directive risks undercutting the executive’s ability to protect forces, preserve deterrence, and sustain vital intelligence and partner operations—choices that are legally and practically difficult to reconcile.
Two practical and legal frictions dominate. First, enforcement and compliance: the resolution leverages the War Powers Resolution’s concurrent‑resolution mechanism, but it does not create a new enforcement penalty against the President for noncompliance.
If the President declines to comply, remedies are political (pressure, appropriations riders, or additional legislation) rather than immediate judicial relief; courts have historically been reluctant to adjudicate core separation‑of‑powers disputes over war decisions. Second, the text’s operational terms are ambiguous. ‘‘Remove the use of United States Armed Forces from hostilities’’ targets combat roles but leaves room for substantial U.S. presence in non‑hostile or defensive postures.
The carve‑outs for imminent defense and for forces ‘‘not engaged in hostilities’’ create interpretive openings the executive could use to continue significant regional operations while claiming compliance.
Implementation logistics present a second set of trade‑offs. A 30‑day clock tied to a past date compresses operational planning and risks gaps in force protection, equipment retrograde, and coalition command arrangements.
The intelligence preservation clause mitigates some partner concerns but ties sharing to the President’s subjective determination, which could produce ad hoc or uneven cooperation. Finally, the resolution refrains from authorizing force, so it leaves unanswered how Congress would proceed if it wanted sustained operations: rapid passage of an AUMF or a formal declaration of war would be required to supersede the removal directive, presenting its own political and strategic complications.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.