War Powers and the Constitution

March 3, 2026

Recent military action has revived a familiar constitutional debate: who holds the authority to take the nation into armed conflict?

The Constitution divides that power. Article I grants Congress the authority to declare war and control funding. Article II designates the president as Commander in Chief. That allocation was not accidental. The Framers rejected both unchecked executive war-making and legislative paralysis in moments of crisis. So they split the power.

Throughout American history, presidents of both parties have ordered military operations without formal declarations of war. Congress has sometimes authorized force in advance. At other times, it has reacted after the fact — through funding decisions, oversight, or political consequences.

In 1973, Congress enacted the War Powers Resolution to reassert its role after Vietnam. It requires presidents to notify Congress when forces are introduced into hostilities and sets time limits unless Congress approves continued engagement. But subsequent Supreme Court doctrine clarified that Congress cannot compel withdrawal through a simple vote; any binding restriction must pass through the full legislative process.

The result is not clarity but tension — and that tension is deliberate. War powers were structured to require engagement between branches rather than unilateral action by one.

The debate we see today is not new. It reflects an enduring feature of our constitutional design: shared authority, institutional friction, and the expectation that both branches will assert their roles.

Whether that system functions effectively depends not only on the text of the Constitution, but on how Congress and the President exercise the powers it assigns.