Skip to main content
v2026.11,986 entries · CC-BY 4.0

Supreme Court Database (SCDB): Coverage, Versions and Variables

What the Supreme Court Database (SCDB) codes, how its Modern and Legacy releases differ, and which release to cite in judicial-behavior research.

Written and maintained by CASRAI Editorial Board

Published

On this page

The Supreme Court Database (SCDB) is a research dataset that codes decisions of the United States Supreme Court into variables a scholar can count, filter and model: who voted which way, which legal provisions and issues a case raised, how it was decided and who won. It is not a legal research service for reading opinions. It is a coded data resource for judicial-behavior and public-law research, hosted at scdb.la.psu.edu (checked 2026-11-18), and it is the right starting point when your question is about patterns across many cases rather than the text of one.

What the Supreme Court Database is

Harold Spaeth proposed the project to the National Science Foundation, collected and coded the data, and made it public in the late 1980s, according to the database’s own description of the collection. The original aim was to record the votes of the Justices in all argued cases across five decades. The project has since been extended in both directions, so it now spans the Court’s history from 1791 to the most recent completed term, and it is updated after each term.

This page is about the SCDB maintained at scdb.la.psu.edu, not a general case-law search service. If you need the full text of opinions or the dockets, see the alternatives table below and our guides to CourtListener, and Westlaw legal research.

Who runs it and what it covers

Maintainers

The contributors page (read 2026-11-18) lists Lee Epstein of Washington University in St. Louis, Michael J. Nelson of Penn State and Andrew D. Martin of Washington University as the current team, and credits Spaeth as the creator with support from the National Science Foundation. Sara Benesh, Ted Ruger and Jeffrey Segal are listed as previous contributors. The site now lives at scdb.la.psu.edu; the older scdb.wustl.edu address was the project’s earlier home, so citations and bookmarks from before the move may point to the old domain.

Two databases: Modern and Legacy

The collection is split into a Modern Database, covering the 1946 term to the present, and a Legacy Database, covering the 1791 term through the 1945 term. The project states that the two can be easily combined. The split matters in practice, because the two parts were built at different times and the codebook documents different limits for each (see the strengths and limits section).

What is coded for each case

The project groups its variables into six categories, each described in the online codebook:

  • Identification variables, such as citations and docket numbers.
  • Background variables, such as how the Court took jurisdiction of the case.
  • Chronological variables, such as the decision date, the term and the natural court.
  • Substantive variables, such as the legal provisions and issues involved and the direction of the decision.
  • Outcome variables, such as the disposition, the winning party and whether a law was declared unconstitutional.
  • Voting and opinion variables, such as individual votes, opinions written and agreement among Justices.

The size of the database is described in two different ways on two official pages. The page describing the collection says there are 247 pieces of information for each case. The online codebook says there are sixty variables for each case and 157,980 data points. The counts are measured differently, so quote whichever one you use with its source rather than treating them as interchangeable.

How to work with the SCDB

The official pages describe the content and structure of the database and its codebook, not a step-by-step search interface, so the sequence below follows what the codebook and download pages say you need to do before an analysis.

  1. Decide whether your question sits in the Modern or Legacy period. Modern covers terms 1946 onward and Legacy covers 1791 through 1945. A study of the contemporary Court uses Modern; a long-run study joins the two.
  2. Open the data page and note the release. The Modern Database is released by year and release number (the current one at the time of checking is 2026 Release 01, covering terms 1946 to 2025). Legacy releases are numbered SCDB Legacy 01 to 07.
  3. Read the online codebook entry for every variable you plan to use. Each entry gives the current variable name, the name in earlier versions of Spaeth’s data, any normalization applied, a description and the list of allowed values.
  4. Check the unit of analysis. The codebook notes that only the case-centered version of the Legacy data is available at present and that the next major release will include a docket-centered version. Read the case-centered definition before you count cases or votes.
  5. Load the data into your statistical package. The codebook notes the data can be imported into statistical packages and that users may redefine variables in their own copies. Keep the original file untouched and do your recodes in a script.
  6. Record the release you used. The codebook advises checking the version date because the database is updated continuously. Put the release name and download date in your methods section.

For the web interface for post-1946 terms, the codebook states it can calculate and display relationships among variables, which is useful for a quick look before you commit to a download. For file handling and versioning habits that carry across datasets, see our guides on versioning research datasets and the dictionary entry for a DDI codebook, the general social-science convention for documenting variables.

Which release should you cite?

Because the database is revised, the same analysis can give slightly different numbers on different releases. The project keeps an archive of earlier Modern releases back to 2009 and of Legacy releases 01 to 07, and the codebook states that earlier legacy versions are hosted so that past analyses can be replicated. That archive is the practical reason to name your release.

The data table below lists a sample of releases from the official release list. It shows how often the Modern Database is reissued and how the term coverage grows with each release, while the Legacy Database has been stable since its most recent release in 2021. Treat it as a guide to choosing between replication and an up-to-date dataset:

  • Replicating a published study: use the release that study names, taken from the archive, so your results can match.
  • A new analysis of the contemporary Court: use the newest Modern release and cite it by name, since it includes the most recent terms.
  • A historical or long-run study: use Legacy 07 with the current Modern release, and read the legacy caveat below first.

These are editorial recommendations built from the project’s own statements about versions, not rules the project publishes. The project’s pages give no citation format, so follow your discipline’s data-citation convention and include the release name, the date you downloaded and the URL.

Which variable families answer which research questions?

The following mapping is editorial interpretation, intended to help a new user pick variables; it is not published by the project.

  • Judicial behavior and ideology: voting and opinion variables combined with the direction of the decision from the substantive variables, grouped by term or natural court.
  • Court-level change over time: chronological variables (term, natural court, decision date).
  • Agenda and case selection: background variables on how jurisdiction was taken.
  • Constitutional review: outcome variables, including whether a law was declared unconstitutional.
  • Linking to other data: identification variables such as citations and docket numbers, which let you join SCDB records to opinion text or dockets held elsewhere.

Strengths and limits

Strengths

  • Long coverage, from 1791 to the most recent completed term, in two databases that can be combined.
  • A public codebook that records each variable’s current name, earlier names, normalization and values, which makes variable lineage auditable.
  • A release archive that supports replication of past analyses.
  • Regular updates after each term.

Limits to plan for

  • Legacy cases record only the first of several issues or provisions. The codebook warns that analyses of multi-issue legacy cases may therefore be incomplete.
  • Only a case-centered Legacy version exists at present. A docket-centered version is planned for the next major release.
  • Versions change. Because the database is updated continuously, results should be tied to a named release.
  • It holds coded variables, not opinion text. The coding reflects the project’s own category scheme, and users who redefine variables in their own copies should say so when they report results.

Alternatives and companions

Most studies pair coded data with text or dockets. The Free Law Project’s dataset page (read 2026-11-18) describes a Supreme Court dataset that it says combines the Supreme Court Database with Resource.org, Library of Congress and supremecourt.gov material, available in bulk and through a REST API. It also describes CourtListener case law, which it says contains over nine million decisions from over 2,000 courts, and the RECAP Archive, to which Supreme Court dockets and filings since 2000 were added in 2026. For state courts, see our guide to the National Center for State Courts.

Resource What it provides (per its own pages) Best used for
Supreme Court Database (SCDB) Coded variables for Supreme Court cases, 1791 to the latest completed term, in Modern and Legacy databases Quantitative studies of votes, issues and outcomes
Free Law Project: Supreme Court data Bulk data and REST API combining the SCDB with Resource.org, Library of Congress and supremecourt.gov sources Joining coded variables to documents
Free Law Project: CourtListener case law More than nine million decisions from over 2,000 courts Reading and searching opinion text across courts
Free Law Project: RECAP Archive Docket entries and documents, including Supreme Court dockets and filings since 2000 added in 2026 Dockets, briefs and motions

If you need full-text opinions with editorial tools, commercial legal research services are a separate category from the open datasets above.

Where it fits in a research workflow

For a typical project, the database supplies the variables and an opinion source supplies the text. Pull the SCDB variables for the terms you need, join them to opinions or dockets on citation or docket number, and keep a data dictionary of any variables you derive. Because identifiers are in the identification variables, the join step is the place to check for mismatches, for example cases with several docket numbers. Report your release name, any recodes and the number of cases dropped. Researchers in the legal and social sciences can browse related CASRAI material under law and legal studies.

Sources

Data: Supreme Court Database release history (selected Modern and Legacy releases)

Selected releases of the Supreme Court Database, compiled from the project's official release list, showing release date and the terms each release covers. Legacy terms 1791-1945 are taken from the project's description of the Legacy Database.

Period covered: 2009/2026. Coverage: United States.

Supreme Court Database release history (selected Modern and Legacy releases)
ReleaseRelease dateTerms covered
Modern: 2026 Release 012026-09-071946-2025
Modern: 2025 Release 012025-09-011946-2024
Modern: 2024 Release 012024-10-011946-2023
Modern: 2023 Release 012023-12-241946-2022
Modern: 2022 Release 012022-11-021946-2021
Modern: 2018 Release 022018-10-171946-2017
Modern: 2009 Release 012009-04-301953-2007
Legacy: SCDB Legacy 072021-10-011791-1945
Legacy: SCDB Legacy 062020-09-291791-1945
Legacy: SCDB Legacy 012016-03-141791-1945

Sources

Compiled by CASRAI from the sources above. Free to reuse under CC BY 4.0 with attribution.

Follow CASRAI

Research-administration guidance, standards updates and independent tool reviews.

Ask CASRAI · full access

Ask about Supreme Court Database (SCDB): Coverage, Versions and Variables

Full access: large monthly usage, up to 10 source passages behind each answer, and MCP and API access for Claude Code, Codex and other CLIs. Cancel any time.

An AI assistant for research: funder rules, compliance, methods and publishing. It links the sources behind its answers and labels answers that come from a web search.

Answers draw on CASRAI's guides and dictionary plus the federal and funder documents we index: Federal Register, Grants.gov, Regulations.gov and UKRI.

Works on this site and inside Claude, Cursor and the AI tools you already use.

Everything CASRAI publishes — this page, the dictionary, the guides and the news — stays open to read, with no account and no card.

Referenced across the research world

University of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logoUniversity of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logo
  • University of Cambridge logo
  • Columbia University logo
  • Crossref logo
  • University of Edinburgh logo
  • Harvard University logo
  • University of Oxford logo
  • Princeton University logo
  • Stanford School of Medicine logo
  • University College London logo
  • ORCID logo

View CASRAI adoption →