What Is the War Powers Act and How Does It Work

A Law Born From Vietnam

Few laws in American history have generated as much controversy as the War Powers Resolution of 1973. Passed in the shadow of Vietnam and signed into law over a presidential veto, the act was Congress's attempt to claw back authority over one of the most consequential decisions a democracy can make: going to war.

More than five decades later, the resolution remains fiercely contested — invoked in congressional debates, cited in legal briefs, and routinely stretched or sidestepped by every administration that has deployed U.S. forces abroad.

What the Constitution Actually Says

The tension at the heart of the War Powers Act is baked into the U.S. Constitution itself. Article I gives Congress the exclusive power to declare war, raise armies, and regulate the armed forces. Article II, meanwhile, designates the president as commander in chief of the military.

The Framers deliberately changed the original draft language from "make war" to "declare war" — a subtle but important distinction. The intent was to allow the president to respond to sudden attacks while reserving the formal power to initiate hostilities for the legislative branch. As the National Constitution Center notes, the precise boundary between those two powers has never been settled by the Supreme Court.

This ambiguity gave presidents enormous room to maneuver. By the time the United States had fought two major wars in Korea and Vietnam — neither of which was formally declared by Congress — lawmakers had grown determined to act.

How the 1973 Resolution Works

Congress passed the War Powers Resolution in November 1973, overriding President Nixon's veto. According to Britannica, the law rests on three core obligations:

• The 48-hour rule: The president must notify Congress within 48 hours of deploying U.S. forces into hostilities or situations where hostilities are imminent. The report must describe the circumstances, the legal authority invoked, and the estimated scope and duration of the engagement.
• The 60-day clock: Unless Congress declares war or specifically authorizes the use of force, military operations must end within 60 days. A further 30-day withdrawal period is built in, giving the president up to 90 days total to disengage troops.
• Congressional termination: At any point, Congress can pass a concurrent resolution directing the president to withdraw forces — without the possibility of a presidential veto.

The law was designed to make prolonged, undeclared wars impossible by creating an automatic sunset on unauthorized military action. In practice, the mechanism has rarely worked as its authors intended.

A History of Presidential Defiance

Every president since Nixon has questioned the law's constitutionality, arguing it encroaches on executive authority as commander in chief. The pattern of defiance is well documented by History.com:

• Ronald Reagan deployed troops to El Salvador in 1981 without submitting the required congressional report.
• Bill Clinton continued airstrikes in Kosovo for two weeks past the 60-day limit in 1999 without securing authorization.
• Barack Obama argued in 2011 that the Libya bombing campaign did not qualify as "hostilities" under the resolution because U.S. aircraft faced limited risk — a legal interpretation widely criticized by constitutional scholars.

According to Wikipedia's analysis of the resolution, the 60-day time limit has rarely been triggered, and the law has never successfully brought a foreign military operation to an early end.

Why Congress Has Struggled to Enforce It

The resolution's weakness lies partly in politics and partly in design. Members of Congress are often reluctant to vote against a military operation once it is underway, fearing they will appear to be abandoning troops in the field. Courts have generally declined to rule on war powers disputes, treating them as political questions outside judicial review.

There is also a structural problem: the resolution's concurrent resolution mechanism was dealt a significant blow by a 1983 Supreme Court ruling (INS v. Chadha), which found that certain types of legislative vetoes were unconstitutional. Whether this affects war powers resolutions remains debated among legal scholars.

Still Relevant After 50 Years

Despite its checkered enforcement record, the War Powers Resolution remains the primary legal framework governing presidential war-making in the United States. Congressional debates over its application continue to arise every time U.S. forces are deployed — a reminder that the fundamental question the law was meant to answer, who has the power to take the country to war?, remains as unsettled as it was when the Framers first grappled with it more than two centuries ago.