The War Powers Act Explained

The Constitution draws a bright line that most of us never hear clearly: Congress declares war, and the President commands the military. So why does modern American conflict so often start without a formal declaration, and why does the “commander in chief” argument keep winning in practice?We sit down with Dr. Sean Beienberg to unpack the War Powers Act, also known as the War Powers Resolution of 1973, and the long tug-of-war over constitutional war powers. We connect the founding debates in Federalist 69, Pacificus, and Helvidius to the Civil War-era Prize Cases, where the Court recognizes defensive presidential action while still rejecting the idea that one person should decide to move the nation from peace to war. From there, we track how authorizations for use of military force (AUMFs) become the modern workaround, and how Korea and Vietnam reshape expectations about what “counts” as war.The most sobering part is enforcement. Courts largely treat these fights as political questions, meaning they won’t order troops home, and Congress is left with blunt tools like funding cuts that are politically risky. We also dig into how the 2011 Office of Legal Counsel Libya memo broadens the modern theory of presidential power by narrowing what qualifies as “real war” and expanding what qualifies as a U.S. interest. The result is a War Powers framework that exists on paper, but often feels hollow in real time.If you care about separation of powers, checks and balances, and how U.S. military force gets authorized, this conversation is for you. Subscribe, share with a friend who loves civics, and leave a review with your take: should Congress reclaim the war power, or has the presidency already absorbed it? Check Out the Civic Literacy Curriculum!School of Civic and Economic Thought and LeadershipCenter for American Civics