Sessions on the Hill

Video · 7 min 16 sec · H. Con. Res. 89

Iran War Powers Resolution (H. Con. Res. 89)

A closer look at the proposed concurrent resolution and its path through the House and Senate.

About this episode

H. Con. Res. 89 text and House-to-Senate procedure through September 24, 2026. Statutory background reflects the retrieval-time edition.

Source cutoff: September 26, 2026 at 01:05 UTC.

Coverage limits. Selected records through September 24, not continuous coverage of every congressional action. H. Con. Res. 93 and later developments are outside scope. Statutory background reflects the retrieval-time edition. Committee-report evidence remains unresolved; this does not establish whether a report exists. The episode title refers to a proposed concurrent resolution, not a newly enacted act.

Watch the explainer

Read the human-reviewed transcript

Select a timestamp to seek, then press play. Timestamps are navigation markers, not word-level captions.

Cutoff clarification: The narration refers to actions through September 24, 2026. Retained source retrieval extends through September 26 UTC.

Welcome to this explainer.

Today, we're doing what we do best, skipping the noise and diving straight into the primary sources.

We are going to break down the exact text and the chronological congressional journey of one specific piece of legislation, H. Con. Res. 89.

We'll be mapping its precise sequence right up to our evidence cutoff date of 09/24/2026.

If you've ever wanted to understand how a measure actually moves through the chambers of Congress based purely on the documented record, well, you're in exactly the right place.

Here's a quick road map for our explainer today.

We'll start with the resolutions proposal, move into the statutory reference it makes, track its consideration and vote in both the house and the senate, and finally determine its exact status and scope.

Alright.

Part one, the resolution's proposal.

Let's look at what this measure actually proposed doing.

So looking at the engrossed in house text from 07/23/2026, the resolution proposed directing the president, pursuant to the war powers resolution, to remove United States Armed Forces from specified hostilities with Iran.

That is unless it was explicitly authorized by a declaration of war or a specific authorization for the use of military force.

It's incredibly important to use the precise language here, what the text states it would direct, rather than just reducing the whole thing to a single blanket command.

Now here's where reading the fine print is absolutely crucial.

The resolution proposed wouldn't actually require the removal of all US forces from the entire region.

Instead, the text states several express qualifications.

It deliberately carves out exceptions for defense against an imminent attack, maintaining a regional troop presence for defensive purposes, forces in the region that simply aren't engaged in hostilities against Iran, and specified intelligence related activities.

On top of that, the text includes an express statement that the resolution itself does not authorize the use of military force.

Moving right along to part two, let's examine the exact statutory reference made within the resolution.

You see, the resolution invokes section 5(c) of the war powers resolution, which is codified at 50 U.S. Section § 1544(c).

What this statutory text states is that US forces engaged in hostilities outside The United States without a declaration of war or specific statutory authorization shall be removed by the president if the Congress so directs by concurrent resolution.

We've gotta be really careful here to separate the existing law from the proposed resolution itself.

The war powers resolution is an established existing law, whereas H. Con. Res. 89 was a proposed concurrent resolution trying to invoke that law's specific mechanism.

In this explainer, we're objectively observing the mechanism it references.

We aren't drawing any independent legal conclusions about its constitutional validity, whether it's enforceable, or what would happen with a presidential veto.

We are strictly sticking to what the supplied statutory text says.

Okay, part three.

Let's trace how this piece of legislation actually moved through the House of Representatives.

Tracing the congressional record, things moved pretty quickly in the House.

On 07/22/2026, the House agreed to an order that provided for the consideration of the resolution.

The very next day, on July 23, they held a recorded vote and agreed to the measure.

After that July 23 agreement, the records document that the resolution was officially transmitted and referred over to the Senate.

Let's zoom in on the rules of that debate for just a second.

The July 22 order allocated exactly one hour of debate.

This time was divided equally among representatives Mast, Meeks, and Jayapal or their respective designees.

It's a small detail, but an important one.

The debate time was divided among those specific representatives or their designees, not just broadly split down the middle between two sides.

Also, keep in mind that the order specifies the allocated time, which is procedurally different from whatever the elapsed debate time ended up being on the floor.

And the outcome of all this?

Well, on July 23, the house agreed to H. Con. Res. 89 by a recorded vote of two fourteen to two zero eight.

That was designated as house roll call two eighty two.

But as anyone who follows the legislative process knows, agreement by just the house alone does not constitute agreement by both chambers of Congress.

A concurrent resolution like this requires concurrence from both sides, which naturally brings us to the senate.

The senate's consideration and subsequent vote.

Over in the senate, they were operating under a previous unanimous consent order.

This specific order was reached during a legislative session that started on August 7 and continued into August 8.

It set the stage for the action that took place weeks later.

On September 24, acting under that previous order, the committee on foreign relations was discharged from further consideration, and the senate proceeded to immediate consideration of the resolution.

Now looking back at that August unanimous consent order, it specifically provided for six hours of allocated debate time divided between the leaders or their designees.

It's really worth pointing out that when the record notes the senate proceeded to immediate consideration on September 24, that procedural phrasing doesn't imply there was absolutely no intervening debate.

Once again, we have to distinguish the time allocated by the order from the time that actually elapsed.

So what happened when it finally came to a vote?

The September 24 proceeding was logged as senate roll call two forty four, and it resulted in 49 yeas, 50 nays, and one not voting.

Because of those 50 nays, the senate ultimately rejected H. Con. Res. 89.

Finally, let's wrap things up with part five.

We'll look at the final documented status and the precise scope of these events.

When analyzing congressional records, precision is literally everything.

We have to be clear that senate roll call two forty four was strictly and specifically a vote on H. Con. Res. 89.

For example, it was definitely not a vote on H. Con. Res. 93, which is an entirely distinct and separate measure.

This recorded vote strictly concerns the specific proposed resolution we've been examining today.

Because we're looking at this strictly by the book, we shouldn't treat this specific rejection as some grand definitive ruling on the broader legality of military operations or presidential war powers.

The vote is a documented procedural reality that is limited precisely to the text of H. Con. Res. 89.

So summarizing the sequence up to our 09/24/2026 cutoff, the factual disposition is crystal clear.

The house agreed to the resolution back in July, but the senate rejected it in September.

Therefore, at the end of this covered sequence, it simply had not received agreement from both chambers of congress.

As we close out this explainer, I wanna leave you with a thought.

How does understanding the exact text, the very specific express qualifications, and the precise chamber by chamber journey of a resolution equip you to analyze legislative procedure.

Well, by relying strictly on the documented record, the exact dates, the allocated debate times, the roll call votes, we completely avoid making unsupported assumptions.

Instead, we get a much clearer, highly objective view of how our congressional process actually functions.

Thanks for joining me today.

And as always, keep focusing on the facts.

Download the supporting evidence

Retained official-source extracts, source links and the topic map. These are selected records, not a complete record of congressional activity.

Download the evidence packet (ZIP)

Three takeaways

  1. The proposal

    Compare the House-passed resolution with the version referred to the Senate.

    See official sources · 2
  2. Its path through Congress

    Trace the selected House and Senate actions through their votes and procedural records.

    See official sources · 5
  3. War Powers background

    Explore the statutory provisions in the edition retrieved for this episode.

    See official sources · 1

Explore in NotebookLM

Ask questions and explore the episode’s source notebook.

Open the video explainer’s source notebook ↗

Want more explanations like this? Subscribe to Political Oversight Weekly.