Who Decided Judges Could Invalidate Laws?
The judicial power, and duty, to invalidate unconstitutional laws wasn’t the work of one inventive judge. It grew out of a legal tradition that predates the United States and was adapted by American courts as they confronted written constitutions and contested statutes. That evolution is worth tracking because it shapes how courts weigh laws today.
English common law provided the backbone: judges long refused to apply statutes that clashed with fundamental principles or charters. Colonial jurists operated in that same intellectual world, treating higher law concepts as guiding limits on government acts. Those practices filtered into early American thinking about courts and constitutions.
After the Revolution, state constitutions put courts in the role of resolving disputes about legislative power and rights. In many states, judges exercised review of statutes when they were seen to violate constitutional provisions or entrenched rights. These episodes show judicial review as a practical answer to conflicts between written constitutions and enacted laws rather than a sudden invention.
At the federal level, Marbury v. Madison in 1803 gave the Supreme Court a clear, authoritative statement that the judiciary must say what the law is. John Marshall’s opinion articulated how a written constitution implies limits that courts can enforce when faced with concrete cases. Still, that landmark explained and consolidated an existing practice rather than presenting a lone, novel creation.
Judicial review rests on two basic ideas: a constitution is the supreme law, and courts are the institutions tasked with applying law to disputes. When a statute clashes with higher text, a court deciding an actual case may refuse to enforce the statute. That function protects legal expectations and individual rights that constitutions are meant to guarantee.
But judicial review has built-in constraints. Courts resolve real cases and controversies brought before them, which limits judges from striking down laws in the abstract. Remedies and doctrines—like standing, ripeness, and mootness—channel when and how review happens, keeping the power tethered to lived disputes.
The practice also invites debate about judicial posture. Critics warn that too eager a court risks substituting its policy preferences for legislative judgments. Defenders counter that courts constrain power and uphold bargained constitutional commitments that majorities or temporary political passions might override.
Practical approaches to review vary across time and chambers: some courts read constitutions strictly, leaning on text and original meaning, while others emphasize evolving standards and broader principles of justice. That diversity reflects different philosophies about the role of judges in a mixed government and the best way to preserve constitutional integrity. It also means the practice adapts to changing public expectations and legal problems.
History shows that judicial review emerged from precedent, debate, and institutional need rather than a single moment of invention. Understanding that lineage helps clarify why courts sometimes strike down statutes and why they often proceed cautiously. The balance between enforcing written limits and respecting democratic decision-making remains a live, contested feature of constitutional life.
Today, judges still face the same tension: enforce constitutional text and protect rights, but avoid stepping into policy-making better left to elected branches. That tension keeps the doctrine dynamic and forces judges to justify when they set aside a statute, using reasoned opinion and established legal tools. The result is a system where review is routine in principle but careful in practice.


Comments 10
Author
mQpzOGQRVTQdhEemmGTu
Author
Today, while I was at work, my cousin stole my apple ipad and tested to see if it can survive a forty foot drop, just so she can be a youtube sensation. My apple ipad is now destroyed and she has 83 views. I know this is completely off topic but I had to share it with someone!
Author
Hi there, I discovered your website via Google at the same time as looking for a similar matter, your web site came up, it looks great. I have bookmarked it in my google bookmarks.
Author
Loving the info on this web site, you have done great job on the blog posts.
Author
Something about the tone of this piece feels quietly encouraging, and every claim you made was backed by something concrete rather than left floating. I shared this with a friend who is going through the same thing, I feel a little less alone in finding this difficult. I will be following along closely and looking forward to whatever you publish next.
Author
It takes skill to make something this substantial feel this easy to read
Author
The thinking behind this piece runs far deeper than its length suggests. You treated the reader as capable of handling the complicated version. I keep starting over every time the results are slower than I imagined. The next ninety days suddenly feel like mine to shape. Please keep taking the long way round in your writing.
Author
I usually distrust posts on this topic but yours is the exception. You made the invisible costs visible and that changes the whole calculation. I have been quietly waiting to feel qualified before I begin. I am choosing to keep going quietly and steadily. Please keep taking the long way round in your writing.
Author
I usually distrust posts on this topic but yours is the exception. You demonstrated the point instead of merely asserting it. I keep starting over every time the results are slower than I imagined. I am closing this page ready rather than anxious. This deserves a far bigger audience and I hope it finds one.
Author
You wrote this for the reader rather than for the algorithm. You treated consistency as the main event rather than as a footnote. My first attempt collapsed and I never really recovered from it. I am done treating slow as a synonym for failing. Keep writing and keep building and thank you for both.