The War Powers Act, formally the War Powers Resolution of 1973, requires the president to notify Congress within 48 hours of sending U.S. troops into hostilities and to withdraw them within 60 days unless Congress authorizes the mission to continue.1Office of the Law Revision Counsel. 50 U.S.C. 1541 – Purpose and Policy Congress passed it over President Nixon’s veto to rein in unilateral presidential war-making after Vietnam. Every president since has questioned its constitutionality, no court has ever ordered a president to comply, and the 60-day clock has never actually forced a withdrawal. The law shapes political debate around military action far more than it constrains it legally.
What the Law Requires
The resolution opens with a policy statement at 50 U.S.C. § 1541(c) that identifies only three circumstances in which the president may introduce U.S. forces into hostilities: a declaration of war by Congress, a specific statutory authorization, or a national emergency triggered by an attack on the United States, its territories, or its armed forces.2Office of the Law Revision Counsel. 50 U.S.C. 1541 – Purpose and Policy Congress wrote this to reject the idea that the Commander-in-Chief clause gives the president open-ended authority to wage war. No president has accepted that framing. The executive branch treats § 1541(c) as a non-binding expression of congressional opinion and points to Article II as independent authority to act.
Before deploying troops, the president is supposed to consult with Congress “in every possible instance.”3Office of the Law Revision Counsel. 50 USC Ch. 33 – War Powers Resolution The statute doesn’t define consultation, which has given presidents wide latitude. In many cases it has amounted to a phone call to congressional leaders shortly before or after an operation begins.
Once forces are deployed, the reporting obligation in 50 U.S.C. § 1543 is more specific. Within 48 hours the president must send a written report to the Speaker of the House and the President pro tempore of the Senate covering three things: why the deployment was necessary, what constitutional or statutory authority supports it, and how long the operation is expected to last.4Office of the Law Revision Counsel. 50 U.S. Code 1543 – Reporting Requirement
The reporting requirement covers three kinds of troop movements: forces sent into actual or imminent hostilities, combat-equipped forces deployed to foreign territory, and deployments that substantially enlarge an existing combat presence abroad. Only the first category starts the 60-day withdrawal clock. That distinction matters more than any other feature of the law.
The 60-Day Clock
When a report under § 1543(a)(1) is filed or should have been filed, a countdown begins. The president has 60 calendar days to end the operation unless Congress declares war, passes a specific authorization, or extends the deadline by statute. A single 30-day extension is available, but only if the president certifies in writing that it is needed for the safe withdrawal of troops rather than continued combat.5Office of the Law Revision Counsel. 50 U.S.C. 1544 – Congressional Action
That is the law on paper. In practice, presidents have defused the clock through a wording trick. Because only a report citing § 1543(a)(1) starts the countdown, presidents submit their reports “consistent with the War Powers Resolution” without pointing to that subsection. President Reagan used that formulation for the 1983 Grenada invasion. President Clinton used it for the 1994 Haiti deployment. President George W. Bush used it after the September 11 attacks.6Congress.gov. The War Powers Resolution: Concepts and Practice By declining to acknowledge that forces face hostilities, they avoid starting a clock they would then have to honor.
More than 100 reports of this kind have been filed since 1973, covering operations from Vietnam-era evacuations to counterterrorism deployments across the Middle East and Africa.7War Powers Resolution Reporting Project. Findings and Analysis Congress can argue a particular report should have triggered the clock, but nothing in the statute forces the president to reclassify it.
The “Hostilities” Loophole
The resolution never defines “hostilities,” and the executive branch has stretched that gap far. The clearest example came during the 2011 Libya intervention. After NATO began sustained airstrikes, the Obama administration’s legal adviser argued the 60-day clock had not started, offering four reasons: the U.S. role was limited and supporting rather than leading; there were no American casualties or significant risk of them; there was no chance of escalation involving ground troops; and the military means being used were modest in “frequency, intensity, and severity.”8U.S. Department of State. Libya and War Powers Under that reading, the United States could drop bombs on another country’s military for months without it counting as hostilities.
The same logic applies to drone strikes, intelligence sharing, logistical support for partner forces, and cyber operations. If there is no sustained ground combat between organized forces, the executive branch tends to classify the activity as something other than hostilities. Congress often disagrees but has not managed to legislate a tighter definition. This ambiguity is the single biggest reason the 60-day clock has never actually forced a withdrawal.
What Congress Can Do
Beyond the automatic expiration, 50 U.S.C. § 1544(c) gives Congress a more direct tool: a concurrent resolution directing the president to pull forces out of an unauthorized conflict. This power does not depend on a report being filed. Congress can use it any time troops are engaged in hostilities abroad without a declaration of war or statutory authorization.9Office of the Law Revision Counsel. 50 U.S.C. 1544 – Congressional Action Section 1545 sets expedited procedures so a withdrawal measure cannot be buried in committee.10Office of the Law Revision Counsel. 50 U.S.C. 1545 – Congressional Priority Procedures for Joint Resolution or Bill
Neither chamber has ever fully used those expedited procedures, and Congress has never successfully forced a withdrawal under § 1544(c). Even if it did, the mechanism’s constitutionality is in doubt. In INS v. Chadha, the Supreme Court struck down the legislative veto, holding that any congressional action with the force of law must pass both chambers and be presented to the president for signature.11Justia U.S. Supreme Court Center. INS v. Chadha, 462 U.S. 919 (1983) A concurrent resolution does not go to the president. The feature that made § 1544(c) attractive to the resolution’s drafters is probably what makes it unenforceable.
Congress could pass a joint resolution instead, which does go to the president. But the president would almost certainly veto a measure ordering withdrawal, and overriding a veto requires two-thirds of both chambers. That is a hard majority to assemble on a live military operation.
Why Courts Won’t Enforce It
Members of Congress have sued multiple presidents over War Powers Resolution violations. Those suits have failed every time, not because judges have ruled the president was right, but because they refuse to hear the cases at all. Standing is the most common barrier. In Campbell v. Clinton, House members challenged the 1999 Kosovo air campaign after it passed the 60-day mark without authorization. The D.C. Circuit dismissed the case, reasoning that Congress had other tools available, such as cutting off funding, and that losing floor votes on those tools did not give individual members a right to a judicial remedy.
Courts have also invoked the political question doctrine, treating the legality of military operations as a matter for the political branches. In Smith v. Obama, a 2016 challenge to the anti-ISIS campaign, the court accepted that argument. Across roughly eight major suits brought by members of Congress since 1973, courts have reached the merits in only one, and dismissed the rest of that case’s claims on jurisdictional grounds. For practical purposes, the War Powers Resolution is judicially unenforceable.
Where Authorizations for Use of Military Force Fit In
The resolution assumes most operations will either get congressional authorization or end. That authorization typically comes as an Authorization for Use of Military Force, or AUMF, rather than a formal declaration of war. The most consequential is the AUMF Congress passed on September 18, 2001, targeting the organizations responsible for the September 11 attacks. It remains in effect and has been cited to justify operations in Afghanistan, Iraq, Syria, Somalia, Yemen, and elsewhere, far beyond what many members of the 2001 Congress likely envisioned. Bills to repeal or replace it have been introduced repeatedly and none has become law.
Congress did repeal two older authorizations. The 1991 and 2002 Iraq AUMFs were repealed when President Trump signed the fiscal year 2026 National Defense Authorization Act on December 18, 2025.12Senate.gov. Passage of My Bill to Formally End Gulf and Iraq Wars Those repeals were largely symbolic because the Iraq AUMFs were no longer supporting active operations, but they were the first formal clawback of a war authorization since the resolution was enacted.
What the Act Actually Does
Given that no president fully complies, no court will enforce it, and its strongest tool is probably unconstitutional, it’s fair to ask whether the War Powers Act does anything. It does, but not in the way its authors intended. The 48-hour reporting requirement and the 60-day clock frame the public debate whenever a president deploys troops. Members of Congress use the resolution to challenge operations they oppose, force floor votes, and put colleagues on the record. It gave Congress a vocabulary and a procedural framework for war-powers fights even though that framework has never actually stopped a military operation.
The law also creates a political cost for ignoring Congress outright. The 100-plus reports presidents have filed are not accidental. Refusing to report at all would invite a backlash that no favorable court ruling could offset. The “consistent with” formulation is itself a kind of tribute: presidents invoke the resolution’s language while carefully sidestepping its consequences, because openly defying it would be a harder position to defend than quietly working around it.