Why Congress Does Not Challenge Judicial Supremacy

55 Pages Posted: 24 Jan 2017 Last revised: 2 Nov 2017

Date Written: January 23, 2017

Abstract

Members of Congress largely acquiesce to judicial supremacy both on constitutional and statutory interpretation questions. Lawmakers, however, do not formally embrace judicial supremacy; they rarely think about the courts when enacting legislation. This Article explains why this is so, focusing on why lawmakers have both strong incentive to acquiesce to judicial power and little incentive to advance a coherent view of congressional power. In particular, lawmakers are interested in advancing favored policies, winning reelection, and gaining personal power within Congress. Abstract questions of institutional power do not interest lawmakers and judicial defeats are seen as opportunities to find some other way to advance the same policy priorities. Relatedly, party polarization cuts against bipartisan embraces of pro-Congress views of the law and cuts in favor of Democrats and Republicans advancing competing views of congressional authority. Finally, Congress makes use of institutional structures that accentuate lawmaker disinterest in legal questions and treat the courts as the last word in legal disputes. The committee system, the Offices of Legislative Counsel, the Congressional Research Service, and the offices of House and Senate Counsel all contribute to Congress’s acceptance of judicial supremacy.

Keywords: Congress, Supreme Court, polarization, judicial supremacy

Suggested Citation

Devins, Neal, Why Congress Does Not Challenge Judicial Supremacy (January 23, 2017). William & Mary Law Review, Vol. 58 2017, Available at SSRN: https://ssrn.com/abstract=2904294

Neal Devins (Contact Author)

William & Mary Law School ( email )

South Henry Street
P.O. Box 8795
Williamsburg, VA 23187-8795
United States
757-221-3845 (Phone)
757-221-3261 (Fax)

Do you have a job opening that you would like to promote on SSRN?

Paper statistics

Downloads
140
Abstract Views
1,112
Rank
441,176
PlumX Metrics