The Law That Nobody Enforces

The War Powers Resolution is supposed to stop presidents from starting wars — but most ignore it

American and Israeli forces have now struck targets deep inside Iran — including a joint operation that killed Supreme Leader Ayatollah Ali Khamenei, the country’s highest authority and the face of its theocratic regime. Iran has vowed revenge, regional capitals are bracing for additional escalation, and the conflict has already spilled into multiple fronts across the Middle East.

President Donald Trump publicly celebrated Khamenei’s death and encouraged Iranians to seize this moment to “take back” their country, signaling that the goal of the campaign goes beyond deterrence to something closer to regime change.

Most of the coverage has focused — understandably — on military objectives, retaliation risks, and how this may reshape power dynamics across the region.

But beneath the geopolitical chess match lies a quieter constitutional question that has resurfaced in every major US military intervention since the 20th century: Does the president have the unilateral authority to launch military strikes — even to take the United States to war — without Congress?

That question is not new. It reflects a long-running struggle over the balance of power between Congress and the White House. The pendulum has swung back and forth throughout American history, and although it currently rests heavily with the president, that wasn’t always so.

President Lyndon B. Johnson in Vietnam in 1966

In the early 1970s, after years of war in Vietnam and expanding executive action abroad, Congress decided the pendulum had swung too far. Lawmakers in both parties believed presidents had accumulated too much unilateral authority over decisions of war and peace. So they did what they were uniquely positioned to do: they legislated. In 1973, Congress passed the War Powers Resolution to claw back its constitutional role in war-making. And when President Richard Nixon vetoed the bill, Congress overrode him.

That override was not symbolic. It was an assertion of institutional power and a reminder that under the Constitution, decisions of war were meant to be shared, but Congress was to be the lead actor.

Now that the US has attacked Iran, that same unresolved struggle sits just beyond the headlines. To understand what a president can legally do — and what Congress can do in response — you have to understand the law born from that earlier fight, and why the battle over war powers never truly ends.

Why the War Powers Resolution exists

The Constitution does not stumble into ambiguity on war. It is explicit.

Article I, Section 8 gives Congress, and only Congress, the power “to declare War.” Not imply war. Not ratify war after the fact. Declare it. Alongside that authority, Congress is empowered to raise and support armies, provide and maintain a navy, and control military funding. These are not decorative clauses. They are enumerated powers — placed deliberately in the hands of the branch closest to the people.

The framers debated this design carefully. They had just fought a revolution against a monarch who could drag his nation into conflict at will. They did not want decisions of war and peace subject to the impulses of a single executive. If the United States were to go to war, they intended it to be debated publicly and approved through a recorded vote in Congress. War would require deliberation. It would require accountability. It would require shared political ownership.

The president, by contrast, was named commander in chief, a role focused on directing military forces once authorized, not unilaterally deciding when to launch them into sustained conflict.

For much of the nation’s early history, that balance largely held. Congress formally declared war in 1812 against the United Kingdom, in 1898 against Spain, and in 1917 and 1941 during the world wars. Even when presidents moved quickly in limited circumstances, major conflicts bore Congress’s formal stamp.

Lithograph of the Battle of New Orleans in the War of 1812

Then the 20th century — and America’s global role — began to stretch the design. In fact, 1941 — after the attack on Pearl Harbor — was the last time Congress officially declared war.

After World War II, the United States stationed forces around the world. The Cold War introduced new forms of conflict that did not resemble traditional declared wars. In Korea, President Truman committed US troops under the banner of a United Nations “police action,” without a declaration of war. In Vietnam, Congress passed the Gulf of Tonkin Resolution in 1964, authorizing force but not declaring war. That resolution became the legal foundation for years of escalating combat, including operations in Cambodia and Laos that many lawmakers later said they had neither anticipated nor fully understood.

By the early 1970s, the war in Vietnam had deeply eroded public trust. Many members of Congress concluded that they had ceded too much authority to the president on issues of war — not in a single dramatic moment, but incrementally. Executive power had expanded through practice, precedent, and congressional acquiescence.

The War Powers Resolution was Congress’s attempt to reverse that drift.

Passed in 1973, the statute declared that the president’s constitutional powers as commander in chief may be exercised only pursuant to (1) a declaration of war, (2) specific statutory authorization, or (3) a national emergency created by an attack on the United States, its territories, or its armed forces.

President Richard Nixon saw it very differently.

In his veto message, Nixon warned that the resolution would “attempt to take away, by a mere legislative act, authorities which the President has properly exercised under the Constitution for almost 200 years.” He argued that the law would “seriously undermine this Nation’s ability to act decisively and convincingly in times of international crisis” and insisted that it was “both unconstitutional and dangerous.”

That language is revealing. Nixon did not dispute that Congress had a role in war-making. He disputed Congress’s ability to restrict what he viewed as inherent authority of the commander in chief. In other words, the argument was not simply about policy. It was about constitutional power — about who decides the threshold between peace and war.

Congress overrode Nixon’s veto by votes of 284–135 in the House and 75–18 in the Senate.

That override is one of the most important — and often overlooked — moments in modern separation-of-powers history. It required bipartisan supermajorities in both chambers willing to rebuke a sitting president on constitutional grounds. Lawmakers were not merely criticizing Nixon. Congress was reasserting its institutional and constitutional role.

Fifty years later, the pendulum has swung back toward the White House. But the tension the law was designed to address — whether war decisions belong to the many or the one — remains unresolved.

What the law requires

The War Powers Resolution tries to operationalize Congress’s constitutional role through three mechanisms: consultation, notification, and a deadline. On paper, they form a sequence — talk to Congress, tell Congress, and, if Congress does nothing, bring the troops home.

In practice, each step has been contested.

1. Consultation

The statute requires that the president “consult with Congress in every possible instance” before introducing US armed forces into hostilities or situations where hostilities are imminent. The key words here are “consult” and “before.”

That language was intentional. Lawmakers wanted consultation to mean more than a courtesy call after bombs had already been dropped. They envisioned real engagement — advance notice, discussion of objectives, and an opportunity for members to weigh in before the country crossed the threshold into armed conflict.

What has it meant in practice?

It has ranged widely, and consultation has often been minimal or nonexistent.

Before the 1991 Gulf War, President George H. W. Bush consulted extensively with congressional leaders and ultimately sought formal authorization. Before the 2003 Iraq War, President George W. Bush also went to Congress for an authorization for use of military force (AUMF), securing a recorded vote. It wasn’t a formal declaration of war, but it did provide the president authority to involve US troops abroad, a move that kept Congress in a lead-actor role.

President George H.W. Bush

But in other instances, consultation has looked far narrower. In 2011, before US air operations began in Libya, the Obama administration briefed congressional leadership, but critics argued those briefings fell short of meaningful consultation. The Obama administration argued that the president did not need authorization from Congress because US operations — largely conducted through airpower and support roles — did not rise to the level of a full-scale “conflict.” He went ahead with the strikes, leading the House of Representative, including 70 Democrats, to reject his administration’s request for formal authorization.

In 2020, after the strike that killed Iranian general Qasem Soleimani, many members of Congress said they were not meaningfully consulted in advance. Instead, they were briefed after the fact or in tightly controlled classified settings. The decision had already been made; Congress was reacting, not deliberating.

More recently, military actions tied to Venezuela — including the capture and removal of Nicolás Maduro — also proceeded without any prior congressional consultation. Lawmakers reported notification and briefings only once events were underway.

These episodes expose the central weakness in the consultation requirement: the statute never defines what “consult” actually means — or when consulting must occur.

The law says the president must consult “in every possible instance” before hostilities begin. But it does not require a vote. It does not specify how many members must be involved. It does not clarify whether consultation must meaningfully shape the decision or merely precede it.

As a result, presidents have interpreted consultation narrowly. Often it means briefing a small group of congressional leaders — the so-called Gang of Eight made up of the leadership of both parties in both chambers, plus the chairs and ranking members of the House and Senate intelligence committees — sometimes only hours before action, sometimes after it has already begun. Technically, the box is checked. Substantively, Congress has little influence over the decision.

2. Notification within 48 hours

Once US forces are introduced into hostilities — or into situations where hostilities are imminent — the president must submit a written report to Congress within 48 hours.

That report must include:

• The circumstances necessitating the introduction of forces

• The constitutional and legislative authority relied upon

• The estimated scope and duration of the involvement

This reporting requirement has, technically speaking, largely been followed.

Since 1973, presidents of both parties have submitted over 130 such reports. They have covered everything from evacuations of US citizens within foreign embassies to targeted airstrikes to sustained combat operations.

For example:

• In 1983, President Ronald Reagan submitted reports regarding the deployment of Marines to Lebanon and the invasion of Grenada.

• In 1999, President Bill Clinton reported on US air operations in Kosovo.

• In 2001 and 2003, President George W. Bush submitted reports tied to operations in Afghanistan and Iraq.

• In 2011, President Barack Obama filed a report after US forces joined NATO operations in Libya.

• In 2020, President Donald Trump submitted a report following the Soleimani strike.

• In 2021, President Joe Biden filed reports related to strikes on Iranian-backed militia targets in Iraq and Syria.

But there’s a pattern in how these reports are written.

Presidents typically say they are submitting the report “consistent with” the War Powers Resolution, rather than “pursuant to” it. That wording matters. It signals compliance with the reporting framework without conceding that Congress can constitutionally limit the president’s authority as commander in chief.

In other words, presidents observe the notification rule while preserving their argument that the law cannot fully constrain them.

That tension — comply, but contest — has defined much of the War Powers Resolution’s history.

3. The 60-day clock

The reporting requirement triggers the most important feature of the law: the 60-day clock.

If Congress has not declared war or specifically authorized the military action within 60 days, the president must terminate the use of armed forces. The statute allows an additional 30 days for safe withdrawal.

This was Congress’s enforcement mechanism. It was meant to prevent prolonged military engagements without legislative approval. The idea was simple: if the president moves first, Congress must decide whether to sustain the mission.

But here is where practice diverges sharply from theory.

In 2011, during the Libya intervention, the Obama administration argued that because US operations did not rise to the level of “hostilities,” the 60-day clock was not triggered. Many members of Congress disagreed, but Congress did not pass binding legislation to force withdrawal. The operations continued.

In Kosovo in 1999, the House of Representatives rejected a resolution authorizing the use of force — but it also rejected a resolution directing withdrawal. The result was stalemate. The air campaign continued.

The law also originally included a provision allowing Congress to direct the removal of forces through a “concurrent resolution.” A concurrent resolution requires approval by both chambers of Congress but does not go to the president for signature. That mechanism mattered because it allowed Congress to act without giving the president a veto.

But in 1983, the Supreme Court decided INS v. Chadha, a case unrelated to war powers that nonetheless reshaped the separation of powers. The Court struck down legislative vetoes — provisions in which Congress, without presenting a bill to the president, attempted to nullify rulemaking or other decisions by executive agencies — as unconstitutional. The Constitution, the Court held, requires bicameral passage and presentment to the president for any binding legislative action.

Translated into plain terms: Congress cannot unilaterally override the executive through a simple resolution. If Congress wants to force withdrawal, it must pass a law — which the president can veto — or use its funding power.

That ruling significantly weakened the War Powers Resolution’s enforcement bite.

Today, if Congress wants to compel the end of military engagement, it generally must pass legislation subject to presidential veto or restrict funding through appropriations. Both routes require majorities — and often supermajorities — in politically polarized environments.

The clock still exists. But it ticks within a political system that often struggles to act collectively.

Taken together, consultation, notification, and the 60-day limit create a framework for shared war-making authority. But they depend heavily on political will — on Congress choosing to assert itself, and on presidents choosing not to stretch their authority to its outer limits.

Which is why every potential conflict — including the current conflict with Iran — reopens the same constitutional question.

Has the War Powers Resolution worked?

The answer depends on what our definition of “worked” is.

If the goal was to prevent presidents from initiating military action without prior congressional approval, the answer is plainly no. Over the past five decades, presidents have repeatedly introduced US forces into armed conflict or sustained military campaigns without a formal declaration of war by relying on outdated AUMFs sought by previous presidents and passed by previous Congresses.

Consequently, the modern era of American foreign policy — counterterrorism operations, drone strikes, limited air campaigns, special forces deployments — has unfolded without Congress issuing declarations of war in the constitutional sense.

But if the goal was to slow presidents down, to force transparency, and to create recurring moments of accountability, the answer is more complicated.

The resolution has at least created a paper trail, at least sometimes. Administrations must articulate their legal theories. Members of Congress have a statutory basis to demand hearings, briefings, and votes. Courts may be reluctant to referee political disputes over war powers, but Congress is not left empty-handed. The statute gives lawmakers a foothold should they want to use it.

It has also shaped how presidents frame military action. No modern administration openly claims the authority to wage unlimited war wherever it chooses. Instead, presidents ground their actions in some combination of Article II self-defense authority, prior statutory authorizations, and precedents supplied by their predecessors. That legal choreography — however contested — is a product of the War Powers era.

Still, the structural imbalance remains.

The president controls the military. The president controls intelligence. The president can act quickly, sometimes within hours. Congress, by contrast, is collective. It must organize majorities in both chambers. It must move through leadership, committees, floor time. It must act publicly, often amid partisan division.

In moments of crisis, that asymmetry favors the executive. Lawmakers may disagree with a president’s decision to use force, but cutting off funding or overriding a veto requires political consensus that is difficult to achieve — especially once troops are in harm’s way.

The nature of warfare has also shifted. Many contemporary operations are limited in duration, conducted from the air, or executed by special operations forces. They do not resemble the mass troop deployments of Vietnam that originally animated the War Powers Resolution. That ambiguity gives administrations room to argue that certain actions fall well short of “war” in the constitutional sense, even when they carry significant geopolitical consequences.

Congress, to be clear, retains formidable tools. It controls appropriations. It can repeal or replace outdated authorizations for use of military force. It can refuse to expand missions. It can hold public votes that force members to go on record.

What Congress has rarely done — and never successfully in the modern War Powers era — is use those tools to terminate an ongoing military engagement over a president’s objection. Lawmakers have voted to restrict funding, and in 2019 they even passed a bipartisan War Powers resolution to end US involvement in Yemen. But when President Trump vetoed that measure, Congress lacked the votes to override him. The operation continued.

The War Powers Resolution has not restored the balance envisioned in the Constitution. But it has ensured that every major use of force sparks the same constitutional conversation. It has institutionalized skepticism. It has preserved Congress’s claim — even if not always its leverage.

And in the long arc of separation-of-powers struggles, sometimes preserving the claim is the first step toward reclaiming the power.

The Iran question

Which brings us back to Iran.

President Trump has ordered strikes on Iranian targets, arguing that the action was necessary to deter imminent threats, protect US personnel and allies, and prevent further destabilization in the region. The administration has framed the operation as limited, defensive, and consistent with the president’s constitutional authority as commander in chief.

The immediate strike itself fits within a well-established pattern. Presidents of both parties have used military force in limited engagements without prior congressional authorization. That precedent is real.

The constitutional test begins now.

Under the War Powers Resolution, the president must formally notify Congress within 48 hours. That report will outline the legal authority relied upon and the anticipated scope and duration of operations. Once submitted, the 60-day clock begins.

What happens next will determine whether this episode becomes another example of executive drift — or a rare moment of legislative assertion.

If the strikes remain limited and Iran does not retaliate in a way that draws the United States deeper into sustained hostilities, Congress may do what it has often done: debate, posture, and ultimately acquiesce.

But if escalation follows — if retaliatory strikes widen the battlefield, if US forces become engaged in ongoing operations against a sovereign state — the constitutional stakes change. Sustained military engagement begins to look less like a discrete defensive action and more like war in the traditional sense.

That is precisely the scenario the War Powers Resolution was designed to confront.

Congress now faces a choice: authorize the continued use of force, attempt to restrict or condition it, or remain silent. Silence, historically, has been the most common path.

The political incentives are familiar. In moments of crisis, lawmakers often rally behind the president, at least initially. No member wants to appear unsupportive of troops once operations are underway. And forcing withdrawal would require majorities strong enough to overcome a likely presidential veto.

But there is also fatigue. After two decades of post-9/11 military engagements and repeated reliance on broad executive authority, lawmakers in both parties have signaled interest in reclaiming Congress’s constitutional role.

The War Powers Resolution does not stop presidents from acting. It was never designed to. It was designed to ensure that war — especially sustained war — requires shared responsibility.

The missiles have already flown.

Now the constitutional clock is ticking.