A law that keeps being used and keeps not working

The War Powers Resolution of 1973 is the main statute Congress has for asserting its constitutional war authority against a President who has committed US forces to combat without a declaration of war or a specific authorization. In the first five months of 2026, members of Congress invoked it again and again — across a conflict with Venezuela and a war with Iran, the House and Senate held something on the order of eight floor votes on resolutions to end or constrain hostilities.

Not one of them constrained the executive. The closest Congress came was on May 19, 2026, when the Senate, for the first time, voted to advance an Iran war powers resolution — by 50-47. Even that “breakthrough” only moved the resolution one procedural step; it did not become law and was not expected to.

This brief explains how the 1973 law is supposed to work, walks through the 2026 votes as a case study, and lays out why the statute has not done the job it was written to do.

What the War Powers Resolution does

Congress passed the War Powers Resolution in 1973, over President Nixon’s veto, in response to the way the Vietnam War had been conducted — years of large-scale combat without a declaration of war. The statute has three core mechanisms.

• The 60-day clock. When the President introduces US armed forces into “hostilities” or situations of imminent hostilities, the statute requires a report to Congress within 48 hours. From that point a 60-day clock runs (extendable by 30 days for safe withdrawal). If Congress has not declared war or specifically authorized the operation by the time the clock expires, the statute directs the President to terminate the use of force.
• Privileged resolutions. A member can introduce a “concurrent resolution” or “joint resolution” directing the removal of forces from an unauthorized conflict, and the statute makes that resolution privileged — it is entitled to expedited floor consideration and cannot be bottled up indefinitely in committee. This is what gives any individual senator the ability to force a vote.
• The reporting trigger. The President’s own notification to Congress is what formally starts the 60-day clock. In 2026, the administration notified Congress of the use of force against Iran in early March, which set the deadline for that conflict at roughly the start of May.

On paper, this is a real constraint: a default rule that unauthorized wars end after 60 days unless Congress affirmatively signs off.

The veto problem

In practice, the 1973 law has a structural flaw that has hollowed it out.

A resolution directing the President to withdraw forces is still ordinary legislation. To take effect over the President’s objection, it must pass both chambers and then survive a presidential veto — which requires a two-thirds majority in each chamber to override.

So the very tool meant to check a President who has gone to war is one the President can veto. A determined executive needs only 34 votes in the Senate or one-third of the House to defeat it. The Supreme Court’s 1983 decision in INS v. Chadha, which struck down the “legislative veto,” reinforced the point: Congress generally cannot reverse an executive action without presenting legislation to the President for signature or veto.

The result is a paradox. The 60-day clock is supposed to make termination the default — no congressional action required. But once a President decides to keep fighting past day 60, ending the war the statute’s other way, through a withdrawal resolution, requires the same veto-proof supermajority that a formal check on any President requires. The “automatic” termination has no enforcement mechanism other than the executive’s own compliance, and the resolution route runs straight into the veto.

The 2026 votes: a case study

Early 2026 produced an unusually concentrated natural experiment. Two conflicts — one with Venezuela, one with Iran — generated repeated war powers votes in close succession.

Venezuela, January 2026. After the administration ordered a military operation against the Venezuelan government, the Senate took up a war powers resolution directing an end to hostilities against Venezuela.

• On January 8, 2026, the Senate voted 52-47 to advance the resolution — five Republicans (Susan Collins, Lisa Murkowski, Todd Young, Josh Hawley, and Rand Paul) joined Democrats (Al Jazeera).
• On January 15, 2026, the final vote failed 51-50, with Vice President Vance breaking the tie. Two of the five Republicans who had voted to advance it — Hawley and Young — switched, after Hawley said White House assurances had eased his concerns (PBS NewsHour; NPR).

So the resolution that drew bipartisan support to reach the floor died at the final stage, defeated by a tie-breaking vote — never close to the two-thirds it would have needed to survive a veto in any case.

Iran, March–May 2026. The site dates the US/Israel strikes on Iran to March 2026. Once the administration notified Congress, the 60-day clock began. Senator Tim Kaine (D-VA) led repeated efforts to force votes on resolutions directing the removal of US forces from hostilities with Iran. Through the spring, the Senate rejected those motions multiple times, generally on near-party-line votes — for example, a procedural vote in early March failed 47-53, a mid-April vote failed 47-52 (TIME), and a late-April vote (just before the 60-day deadline) failed 47-50 (TIME), with Republican defections slowly growing from one (Rand Paul) to two (Paul and Collins).

The 60-day clock passed at the start of May with US forces still engaged and no authorization on the books — the deadline arrived and nothing happened (CNN). That is the clearest illustration of the statute’s weakness: the law’s central deadline lapsed, and the law’s central remedy (a withdrawal resolution) still could not muster a simple majority, let alone a veto-proof one.

The May 19 breakthrough. On May 19, 2026, the Senate at last voted to advance an Iran war powers resolution, 50-47 (The Washington Post). CBS News reported it as the eighth Senate motion to advance such a resolution since the war began — and the first to succeed (CBS News). Four Republicans crossed over: Collins, Murkowski, Paul, and Bill Cassidy (the first time Cassidy had supported advancing a war powers resolution). One Democrat, John Fetterman, opposed it.

It is worth being precise about what that 50-47 vote was. It was a vote to discharge the resolution from committee — a procedural step that merely cleared the resolution for further Senate consideration. It was not final passage. To become binding it would still need to pass the full Senate, pass the House, and survive a near-certain presidential veto with two-thirds majorities. A 50-47 vote is roughly 17 votes short of a veto-proof Senate margin, and the House had repeatedly rejected its own Iran war powers measures (NPR).

Why it has not constrained the executive

Pulling the 2026 record together, several reasons emerge for why the statute has not worked as intended.

The veto math is decisive. Every 2026 vote — even the May 19 “breakthrough” — fell far short of two-thirds. As long as a President is willing to veto, and roughly one-third of one chamber will sustain that veto, a withdrawal resolution cannot bind the executive. The closest the resolutions came to a majority was 52 votes; none came close to 67.

Party loyalty tracks the President. The defections in 2026 were real but small — five Republicans at the high-water mark on Venezuela, four on Iran — and some did not hold. When the President’s own party controls enough seats and mostly votes with the President, the supermajority is unreachable by design.

The 60-day clock has no enforcer. The clock is supposed to make termination automatic. But “automatic” termination depends on the executive choosing to comply. When the Iran deadline passed in early May 2026 with forces still engaged, nothing in the statute did anything. The only follow-on tool — the withdrawal resolution — runs into the veto wall.

Executives dispute the trigger. Administrations of both parties have argued that particular operations do not amount to “hostilities” within the meaning of the statute, or that they fall under existing authorities, narrowing when the clock even starts. That contest over definitions further weakens the law before the voting math is ever reached.

Votes can still matter politically, even when they fail. The 2026 resolutions did not stop any operation. But privileged resolutions force every senator onto the record, repeatedly, on whether a war should continue. The slow accumulation of defections — and the eventual 50-47 vote — is a political signal even though it is not a legal constraint. That is the realistic case for using the tool: not that it ends a war, but that it builds a record and raises the political cost of continuing one.

The reform options

Proposals to give the War Powers Resolution real teeth generally take one of a few forms.

Automatic funding cutoff. Tie the 60-day clock to appropriations, so that funding for an unauthorized operation lapses automatically when the clock runs out — converting a default the executive can ignore into one Congress would have to affirmatively reverse.

Flip the default toward authorization. Require an affirmative congressional vote to continue an operation past the clock, rather than a vote to end it — so that inaction stops a war instead of permitting it.

Tighten the “hostilities” definition. Define the statutory triggers precisely enough that the executive cannot argue a given operation falls outside the law.

Expedited judicial review. Create a fast track for courts to rule on whether the statute has been triggered and complied with, rather than leaving the question entirely to the political branches.

Each of these confronts the same obstacle the 1973 law itself confronts: enacting it requires either a President willing to sign a law constraining the presidency, or a veto-proof bipartisan supermajority. That is the recurring structural problem of war-powers reform.

What to ask your representatives

• Will they support amending the War Powers Resolution so the 60-day clock triggers an automatic funding cutoff, rather than relying on a withdrawal resolution the President can veto?
• Will they support flipping the default — requiring an affirmative vote to continue an operation past the clock, so that congressional inaction ends a war rather than allowing it?
• How did they vote on the 2026 Venezuela and Iran war powers resolutions, and how do they explain those votes?
• Do they accept the executive branch’s narrow readings of what counts as “hostilities,” or will they support a tighter statutory definition?
• If they believe Congress, not the President, should decide whether the country goes to war, what specifically will they do to make the 1973 statute enforceable?