Analyses / Procedural Viability Check / 119 · HCONRES 75 Procedural Viability Check

119-HCONRES-75 DC Insider Procedural Viability Check

119 · HCONRES 75 Directing the President, pursuant to section 5(c) of the War Powers Resolution, to remove the United States Armed Forces from hostilities against the Islamic Republic of Iran.

language International Affairs
This concurrent resolution directs the President to remove U.S. Armed Forces from hostilities against Iran or any part of its government or military no later than March 30, 2026, unless a...
Procedural read

House-originated War Powers concurrent resolution with privileged status can reach the floor, but GOP control of both chambers and the Senate’s proven willingness to block Iran-related War Powers efforts make bicameral adoption highly unlikely; prior House attempts narrowly failed in March (212–219) and April, and Section 5(c)’s concurrent‑resolution mechanism carries post‑Chadha constitutional doubts. Composite score: 2/5. (clerk.house.gov)

212Yea (212–219) on Mar 5, 2026
House vote 1 (similar measure)
213Yea (narrow failure) mid‑Apr 2026
House vote 2 (similar measure)
1GOP majority; Thune as Majority Leader
Senate control
Published
28 Apr 2026
Updated
28 Apr 2026
Tags
War Powers · Procedural viability · Iran
Unvetted
01 · Section

Bottom line on H. Con. Res. 75 (Iran War Powers)

What it is: a House concurrent resolution, introduced March 4, 2026, invoking Section 5(c) of the War Powers Resolution to direct removal of U.S. forces from hostilities against Iran that began on February 28, 2026. (govinfo.gov)

  • House path: privileged for floor consideration; leadership can — and has — set one‑hour debate by unanimous consent on similar Iran War Powers measures. (congress.gov)
  • Recent votes: House failed to adopt a similar Iran War Powers resolution on March 5, 2026 (212–219) and again in mid‑April. (clerk.house.gov)
  • Senate reality: Republicans hold the majority; Senate has already blocked an Iran War Powers effort this spring. (senate.gov)
  • Legal wrinkle: using a concurrent resolution under Section 5(c) faces post‑INS v. Chadha constitutional questions; Congress created an alternate expedited joint‑resolution path. (congress.gov)
  • Political context: House GOP’s narrow majority (roughly 218–214) leaves little margin; cross‑party defections are episodic and have not flipped outcomes. (axios.com)
02 · Section

Procedural Viability Check

Assessment against the requested rubric, focused on power, procedure, and calendar.

Factor Assessment Rationale
Chamber of Origin Low House concurrent resolution; no identified Senate companion with traction and Senate Republicans control the floor agenda. (senate.gov)
Vehicle Type Medium War Powers concurrent resolutions are privileged but not must‑pass; no natural hook to NDAA/appropriations in this form. (congress.gov)
Senate Threshold Low Even with expedited procedures, the Senate majority has already blocked an Iran War Powers effort this spring; no 51‑vote path evident under current leadership. (washingtonpost.com)
Committee Path Medium House Foreign Affairs (Chair: Brian Mast) can clear or tee up floor time; Senate Foreign Relations (Chair: Jim Risch) is not an ally for this posture. (foreignaffairs.house.gov)
Must‑Pass Potential Low As a concurrent resolution, it cannot be stapled to a must‑pass vehicle; a funding rider would require a different vehicle and 60 votes. (congress.gov)
Budget Scorekeeping High No CBO/JCT issues; concurrent resolutions don’t have scoreable budget effects. (No citation required)
Calendar Math Low‑Medium Floor time exists to force votes, but election‑year compression and repeated House failures reduce momentum; Senate blockade persists. (clerk.house.gov)
House vote 1 (similar measure)
212Yea (212–219) on Mar 5, 2026
House vote 2 (similar measure)
213Yea (narrow failure) mid‑Apr 2026
Senate control
1GOP majority; Thune as Majority Leader

Sources: House Clerk roll call (Mar 5); Axios report (Apr 16); Senate leaders roster. (clerk.house.gov)

03 · Section

Procedural map and choke points

  1. House floor: Section 5(c)/§1546 provides a privileged path; HFAC can request UC for one‑hour debate (as occurred for H.Con.Res. 40 on Apr 15). Expect leadership to honor the privilege but whip against. (congress.gov)
  2. Senate gate: Even if the House adopts H. Con. Res. 75, Senate leadership can block, table, or run out the clock. Recent Senate action confirms low appetite to constrain the operation. (washingtonpost.com)
  3. Presentment problem: a concurrent resolution likely lacks binding effect post‑Chadha; the enforceable route is an expedited joint resolution under §1546a — which would face a likely veto and would need two‑thirds to override. (congress.gov)
  4. Alternate lever: move the fight to must‑pass appropriations/NDAA via funding prohibitions on Iran hostilities. That requires 60 in the Senate and at least acquiescence from SFRC/SASC leadership — neither is aligned. (senate.gov)
04 · Section

Strategic context

  • Hostilities began Feb 28, 2026; the White House portrays a winding‑down window but retains operational flexibility — keeping swing Republicans from breaking ranks. (apnews.com)
  • House GOP margin is razor‑thin, but leadership has eked out wins on prior Iran War Powers votes; Democratic unity plus a couple of GOP defections still hasn’t cleared the bar. (axios.com)
  • BGOV’s topline: multiple Iran War Powers votes this Congress; none have prevailed — consistent with the pattern across both chambers. (news.bgov.com)
05 · Section

Bottom line score

Composite score (0–5)
2

Rationale: Privileged in the House but not must‑pass; prior House failures; GOP‑run Senate has already blocked a parallel effort; and the concurrent‑resolution posture is constitutionally weak. Net: procedurally possible, politically unlikely to clear the Senate. (clerk.house.gov)

Discussion