How to Bluebook Cite a Case: A Complete Reference Guide

One misplaced comma or wrong reporter abbreviation tells every reader your research may be just as careless. Here is exactly how to build a Bluebook case citation that holds up before anyone reads your argument.

The common assumption among litigation paralegals and legal assistants doing first-pass research is that Bluebook citation is a rote mechanical task where close enough is good enough, that minor formatting slips are cosmetic and will be caught in attorney review anyway. Precision in Bluebook citation is the real legal work, at least as far as the first reader who picks up your brief is concerned. Before a partner scans the argument section, before a clerk reads the first case you're relying on, the citations are already being evaluated, and the judgment they form travels forward into everything else they read.

Precision in Bluebook citation isn't a finishing touch applied after the real legal work is done. It is the real legal work, at least as far as the first reader who picks up your brief is concerned.

Paralegal desk with red-marked brief citation, magnifying glass, and AI legal research screen

The Bluebook's governing premise, that precision in every citation element is a professional obligation, reflects a broader reality that legal readers routinely treat citation form as a proxy for analytical rigor, evaluating research credibility before engaging with substantive arguments. A malformed court parenthetical or incorrect typeface signals that the research behind the citation may be equally careless. The logic is direct: if the paralegal didn't verify the reporter abbreviation, did they verify that the case still stands?

Paralegals who consistently return clean first-pass drafts, ones where citation errors are caught before attorney review, tend to be repositioned over time as trusted analytical contributors rather than mechanical task executors, a pattern widely recognized across legal support practice communities. An attorney who receives a clean draft spends review time on substance, and that shapes how they think about the paralegal's contribution. The practical consequence of a citation error in any element is that the authority becomes unverifiable, and in a brief where every case carries the drafter's credibility, one citation that cannot be located puts every other citation under heightened scrutiny. The next section breaks down the exact five-component structure The Bluebook: A Uniform System of Citation requires for every case citation.

Key takeaways

Bluebook citation is a credibility signal before it is a research tool, a malformed parenthetical quietly undermines the authority behind the case before anyone reads the substance.
Rule 10 sets a fixed, non-negotiable sequence: case name, reporter, volume, page, court, and year, every element in its slot, or the verification chain breaks.
Case-name formatting rules shift by document type, so a correctly italicized name in a brief is a formatting error in a law review footnote; applying one rule across all contexts is the mistake.
The court-and-year parenthetical is a jurisdictional signal, not a formality, it tells the reader whether the authority binds, persuades, or simply fills space.
A wrong reporter abbreviation passes every visual check and only fails when someone tries to pull the source after the brief is already filed.
Short-form citation errors travel backward, they cast doubt on the full citation and the authority it was meant to establish.
AI citation tools hallucinated in 17 to 33 percent of queries in 2024 testing, meaning verification cannot be outsourced without knowing what accurate output looks like.
OpenCase closes the loop by grounding every citation and research answer in real law, so legal teams can verify, draft, and file faster without trading speed for accuracy.

The Basic Structure Every Bluebook Case Citation Must Follow

Rule 10 of The Bluebook establishes a fixed, non-negotiable sequence for every case citation, and the order is a verification chain. When each component sits in its correct slot, any reader can locate the opinion in seconds. When even one element is out of place or missing, the citation breaks down as a findability tool before it fails as a formatting matter.

"I struggle with how to accurately represent the nature of a citation when the cited case uses a 'cf.' signal, and I'm concerned that the standard '(citing …)' parenthetical format may be misleading in such contexts."

— what we hear from legal professionals

Five interlocking citation scaffold blocks showing case name, volume, reporter, page, and court-year components

The Five-Component Scaffold Rule 10 Requires in Exact Order

Case Name
Volume Number
Reporter Abbreviation
First Page
Court-and-Year Parenthetical

The scaffold is rigid because each slot answers a distinct question: who are the parties, which volume, which reporter series, where does the case begin, and which court decided it in which year.

How to Read a Fully Annotated Citation So Every Slot Is Accounted For

Brown v. Board of Education, 347 U.S. 483 (1954) is the cleanest illustration of the scaffold in action. "Brown v. Board of Education" is the Case Name (slot one); "347" is the Volume Number (slot two); "U.S." is the Reporter Abbreviation (slot three); "483" is the First Page where the opinion begins (slot four); and "(1954)" is the Court-and-Year Parenthetical (slot five).

Slot

Component

Example Value

Case Name

Brown v. Board of Education

Volume Number

347

Reporter Abbreviation

U.S.

First Page

483

Court-and-Year Parenthetical

(1954)

Bluebook citation structure is a functional retrieval system in which every slot must be present and correctly ordered.

Where Pinpoint Citations Slot In and Why the Comma Placement Is Not Optional

Using Brown as the base, a pinpoint to page 495 reads: Brown v. Board of Education, 347 U.S. 483, 495 (1954). The comma between the first page and the pinpoint page is mandatory, not decorative; it is the only signal that distinguishes two separate page numbers from a single garbled string.

The error pattern is predictable: a paralegal locates the first page correctly, adds the pinpoint, but skips the separating comma, producing "347 U.S. 483495" or a similarly garbled string.

How to Format Case Names Without Typeface Errors That Signal Inexperience

Case-name formatting is uniquely dangerous because the rules governing it shift silently across document contexts. The paralegals and attorneys we work with at OpenCase encounter this problem not in theory but in live drafts, briefs, memos, and law review submissions open simultaneously, each demanding a different convention from the same case name.

Brief and law review documents side by side showing italic versus plain case-name formatting

Italics in Briefs, Plain Text in Footnotes

Case names are italicized or underlined in court documents and briefs under The Bluebook: A Uniform System of Citation Rule 10.2, but that same typeface treatment is a formatting error in law review footnotes, where case names appear in roman (plain) text. It is a distinction easy to miss when moving between document types in the same drafting session.

OpenCase's Microsoft Word Integration and Google Docs Integration are designed with exactly this failure mode in mind. Because OpenCase works inside the document environment where the draft actually lives, it can assess document type in context and flag typeface treatment accordingly, without requiring the drafter to remember which convention applies before opening the file. The skill that matters here is the same one that anchors OpenCase's approach to legal research: find the statute, regulation, or court rule that governs a situation before the draft is finished, not after a reviewer returns it marked up.

Which Party Names to Keep, Which to Cut, and How Table 6 Governs Every Abbreviation

First, use only the first listed party on each side of the case. Under The Bluebook: A Uniform System of Citation Rule 10.2.1, the following terms are omitted from the citation entirely:

Inc.
Co.
Ltd.
et al.

Second, words that survive the party-name cut are then subject to abbreviation under Table 6 (T6) when the case name appears in citation form. That distinction between text and citation form matters: write out "the Association of American Railroads" in your brief's text, but abbreviate it inside the citation itself only when citation form is required.

The practical problem for legal teams is that catching these errors requires checking citations against The Bluebook: A Uniform System of Citation (21st ed.) and against the underlying source document at the same time, a task that is tedious precisely because it is mechanical. From our experience with file analysis workflows, combined with OpenCase's integrations with Google Drive and Dropbox, the source documents are already accessible in the same environment where the citation check happens. Cross-referencing party names against Table 6 is the kind of work that should not consume billable hours, and OpenCase's approach to building the research record for a memo without billing twenty hours to it applies equally to citation hygiene.

The "United States" Exception and Other Case Name Rules That Catch Paralegals Off Guard

Never abbreviate "United States" to "U.S." when it appears as a named party, even though Table 6 governs abbreviation of many other words in the same citation. United States v. Nixon, not U.S. v. Nixon, is the correct form, a rule that runs counter to the abbreviation instinct Table 6 otherwise encourages.

The broader principle is that The Bluebook: A Uniform System of Citation Table 6 is a list of permissions, not a mandate to abbreviate every word that appears on it, and knowing which exceptions override it requires consulting the authoritative text rather than relying on habit. OpenCase's search across 100+ legal databases and its Cornell LII Integration give legal professionals a direct path to the authoritative rule text, so an exception like the "United States" rule is confirmed from the source rather than recalled from memory or habit.

For teams that also deal with federal agency litigation or regulatory matters, OpenCase's Federal Register Integration and Daily PACER Integration mean the same research environment that surfaces a Bluebook exception can also pull the underlying docket or regulatory text that makes the citation necessary in the first place, keeping the full research record in one place rather than scattered across browser tabs. The core skill OpenCase is built to support is the same one citation formatting demands: summarize a long opinion down to the holding that matters here, and then represent that holding in a citation that is correct in every dimension.

What Goes in the Court and Year Parenthetical for Every Court Level

The court-and-year parenthetical looks like a minor formatting detail, but it carries real jurisdictional weight: it tells the reader which court decided the case and therefore how much authority that decision actually carries. Rule 10.4 governs the format, and its logic shifts depending on the court level, because the reporter itself sometimes signals the deciding court and sometimes does not.

Court-level hierarchy icons radiating from a central parenthetical symbol showing jurisdictional authority tiers

The Parenthetical as Jurisdictional Signal

The parenthetical is the reader's first signal about how much weight to assign a decision. Rule 10.4 governs this directly, and its core logic is a decision tree: the court designation you include, or deliberately omit, depends entirely on what the reporter already signals about the deciding court.

U.S. Supreme Court Parentheticals Contain Only the Year

Because the United States Reports are published exclusively for Supreme Court decisions, Supreme Court citations include only the year in the parenthetical, with no court label. The reporter does the work. When a citation reads United States Reports (U.S.), the reporter itself signals the Supreme Court, so adding "U.S." inside the parenthetical would be redundant under Rule 10.4. Miranda v. Arizona, 384 U.S. 436 (1966) is the correct form.

OpenCase's Cornell LII Integration surfaces the verified reporter abbreviations tied to each court level, so when you pull a Supreme Court case you can confirm at a glance that the parenthetical needs only a year. Because OpenCase searches across 100+ legal databases simultaneously, you are not relying on a single source's formatting conventions; you are cross-referencing the authoritative record of how the case was reported.

Federal Courts of Appeals - Circuit Designation Comes Before the Year Every Time

A single rule, circuit abbreviation before the year, covers all thirteen circuits simultaneously. The correct form is the circuit abbreviation followed by the year inside a single parenthetical, for example (7th Cir. 2004) or (9th Cir. 2019). United States v.... 3d 508 (7th Cir. 2004) illustrates the pattern exactly. Table 1 (T1) in The Bluebook lists verified abbreviations for every circuit, running from 1st Cir. through the D.C. and Federal Circuits.

OpenCase's Daily PACER Integration addresses this directly by pulling current docket-level data so you can identify not just what a circuit held, but whether controlling authority in your specific circuit has since distinguished or adopted that reasoning, before the parenthetical is ever typed.

Federal District Court Parentheticals Require the District Abbreviation and Year

The Federal Supplement (F. Supp. 2d, F. 3d) publishes decisions from every federal district court in the country, so the reporter tells a reader nothing about geography. The parenthetical must therefore supply both the district abbreviation and the year, for example, (N.D. Cal. 2015) for the Northern District of California. Cohen v...., 162 F.... 2001) shows the complete form. Inventing a district abbreviation is a common error; T1 supplies the verified short forms, with Table 7 (T7) as a fallback.

OpenCase's Document Drafting and File Analysis tools flag unfamiliar district abbreviations inline, and because they integrate directly with Microsoft Word and Google Docs, the correction happens inside the environment where you are already writing, without a context switch to a separate reference tab.

State Court Parentheticals Follow Table 1 and Drop the Court Name When the Reporter Already Says It

When a state publishes an official reporter dedicated to a single court, Rule 10.4 does not require repeating the court name inside the parenthetical. The practical trap is assuming a regional reporter is court-specific; a regional reporter such as the Atlantic 2d requires the court abbreviation inside the parenthetical.

OpenCase's Statute Analysis feature extends this logic to state statutory citations, and its search across 100+ legal databases means state-specific reporters and their jurisdictional scope are matched against current T1 entries rather than relying on a researcher's memory of which regional reporters are multi-state.

Weight of Authority Parentheticals - When en banc, per curiam, and Similar Signals Belong in the Cite

Rule 10.6 governs weight-of-authority descriptors, which must appear whenever the procedural posture of a decision affects how much deference it commands. The format places the descriptor in lowercase inside the same parenthetical: (7th Cir. 2004) (en banc) or (9th Cir. 2019) (per curiam).

These markers are easy to miss when a case is pulled from a database that strips procedural headers. OpenCase's File Analysis surfaces those procedural markers when it processes a case document, and its Cornell LII Integration cross-references the case record so weight-of-authority descriptors are identified before the cite is drafted, not discovered later during a partner review. When you are working across Outlook, Google Drive, or Dropbox, OpenCase keeps that context attached to the document regardless of where the file lives, so the procedural signal travels with the research rather than getting lost in a separate note.

Where to Find Reporter Abbreviations and Jurisdiction Tables Without Guessing

Paralegal cross-referencing Bluebook reporter abbreviation table on laptop beside open reference book

Table 1 (T.1)

The table is organized by jurisdiction with federal reporters listed first, followed by state-by-state entries. Reading an entry correctly requires three steps: locate the jurisdiction, identify the reporter name within that jurisdiction's listing, and confirm that the court level tied to that reporter matches the court whose opinion you are citing. Courts of Appeals decisions published after 1993. * The table ties each abbreviation to a specific court level, which is the verification step most practitioners skip.

OpenCase's Microsoft Word Integration and Google Docs Integration let attorneys and paralegals run that T.1 lookup directly inside the document they are drafting, without breaking flow to switch tools, open a separate browser session, or abandon the brief mid-sentence.

Table 7 (T.7) and Rule 10.5 When Court Name Abbreviations Require a Separate Lookup

Table 7 (T.7) covers court name abbreviations for situations where an abbreviated court designation must appear within the citation itself. When a reporter self-identifies the court, T.7 is unnecessary; when it does not, T.7 supplies the correct abbreviated form rather than T.1.

For practitioners answering a client's question same-day without opening a formal research matter, the T.1 / T.7 distinction is a common stumbling block, and OpenCase searches across 100+ legal databases and surfaces the relevant Bluebook table guidance alongside the case law itself, so the abbreviation check and the substantive research resolve in a single pass rather than two separate workflows.

The Outdated-List Trap - Why the Source of Your Abbreviation Matters as Much as the Abbreviation Itself

The Bluebook: A Uniform System of Citation, 21st Edition makes clear that relying on unofficial or outdated abbreviation lists found online produces citation errors, not cosmetic formatting slips.

OpenCase's Outlook Integration, Google Drive Integration, and Dropbox Integration mean that when a file analysis surfaces a prior brief or template, the abbreviation sourcing can be checked against current authority immediately, without a separate manual audit.

Once T.1 and T.7 have given you a verified full citation, case name, reporter, court, and date all locked in, the next decision is whether you even need to write it out again.

Short Form Citations and When to Switch from the Full Citation

Under Rule B10 of The Bluebook: A Uniform System of Citation, a short form is only permissible after the full citation has already appeared in the same general discussion, and the reader must be able to locate it without confusion. Two short-form options are available once that threshold is met:

Full citation card versus short-form citation card showing correct Bluebook switching moment

One party's name combined with volume, reporter, "at," and pinpoint page.
"Id." when citing the immediately preceding authority.

The Baby Blue's Manual of Legal Citation offers a freely accessible companion reference for confirming these mechanics when you are away from a library copy of the Bluebook.

The Two-Question Eligibility Check Before You Shorten Any Citation

Before shortening any citation, two questions must be answered: whether the full citation has appeared in the current general discussion, and whether the authority being cited is the immediately preceding one.

One persistent struggle for legal drafters, particularly those working at volume, is that standard tooling like Word combined with reference managers routinely fails to track ibid and short-form eligibility correctly across a document. The failure mode is systematic: the tool applies a short form before the full citation has been established in the current general discussion, or it resets the eligibility window incorrectly when pages are reordered or sections are merged.

OpenCase's Microsoft Word Integration and Google Docs Integration are built to surface eligibility context inside the document itself, flagging whether the full citation has already appeared in the current general discussion before a short form is accepted, rather than requiring a separate manual lookup after the draft is complete.

Id.: One-Party Short Form Under Rule B10

In practitioner documents, including court briefs and memoranda, "Id." is not italicized under standard Bluebook practice for court filings; italicization applies in law review footnotes. Drafters moving between law review work and court filings frequently carry the wrong convention into the wrong document type, and the distinction has real consequences.

For the one-party short form, the rule is equally specific: use the name of one party, followed by the volume, reporter, "at," and the pinpoint page. So a full citation to *Miranda v. Selecting the wrong party name, particularly defaulting to a government agency's abbreviation that does not appear in the reported name, is flagged as a common citation error under Rule B10.

How to Cite a Case Referenced Inside Another Opinion

When an opinion you are reading quotes or discusses a second case, and you want to cite that second case, you cite the original opinion directly, not the quoting case. Citing the quoting opinion instead misrepresents the source and can introduce error if the quoting court paraphrased or selectively excerpted the original.

This matters because the short form you then use must also trace to the original. Verifying that every citation in a brief traces to a real, correctly quoted opinion, and not to a downstream reference that paraphrased the original, is a discipline that requires access to the source material itself, not just the citing document.

OpenCase's integration with 100+ legal databases, Cornell LII, and its Daily PACER Integration means that confirming the original opinion is a lookup inside the drafting environment rather than a separate research detour. When a case appears only inside a quotation in the document you are reading, OpenCase can surface the original through its database connections so you can establish the full citation properly before any short form becomes available.

Standard drafting tools introduce a related risk when citations are reordered or sections are merged. The tool may apply a short form before the full citation has been established in the document's flow, or silently select the wrong party name. OpenCase's integration with your drafting environment, whether Microsoft Word, Google Docs, Google Drive, or Dropbox, is designed to surface that eligibility context in the document itself rather than requiring a separate lookup.

How AI Citation Tools Either Confirm Your Work or Quietly Introduce New Errors

Leading AI legal research tools hallucinated in 17 to 33 percent of queries when tested in 2024, with even the best performers returning misleading or false information more than one time in six. The tools studied returned misleading or unsupported information at rates that varied significantly by system and task type, with no tested platform reaching a level a litigator could treat as inherently reliable.

Paralegal spotting a subtly flawed AI-generated case citation among accurate ones

Why AI-Generated Case Citations Require Manual Verification Against Primary Sources

A fabricated citation at least has a chance of failing a basic docket search. The subtler problem, identified in empirical legal research, is misgrounding: the citation is real, the reporter abbreviation looks right, the parenthetical is plausible, but the source does not actually say what the model attributed to it. That output arrives with the same fluent confidence as a fully accurate citation, which is precisely what makes it dangerous.

Retrieval-augmented generation removes most pure fabrication, but misgrounding survives it, because the model can still overread a real document or draw an unsupported proposition from it. A paralegal who accepts that output without cold-verifying each element against a primary source has traded one error class for a harder-to-detect one that carries identical filing risk. Courts have suspended attorneys and referred entire legal teams for bar discipline after both sides submitted AI-generated citations that no one verified against the actual record.

How to Use Source Traceability to Confirm Every Bluebook Citation Element

Whether every component a tool returns can be traced back to an auditable primary source you can open yourself is the question that matters.

A structurally correct citation string, correct reporter format, real-looking pinpoint, plausible court parenthetical, is visually indistinguishable from a wrong one, and when an error reaches a filing, the credibility damage lands on the paralegal who submitted it, not the tool that generated it.

OpenCase's legal research workflow surfaces citations alongside direct links to the underlying primary source record, so each Bluebook component, reporter abbreviation, court parenthetical, pinpoint page, can be confirmed by opening the actual opinion rather than trusting the citation string alone. Opening the linked record, rather than reading the citation string alone, is what separates a defensible workflow from a fast one.

Half of that workflow is having a tool that makes source traceability possible in the first place. The other half is building a repeatable verification habit you run before every filing, regardless of how the citation was generated.

Next steps

If your citations are passing visual review but failing at verification, the path forward starts with treating every citation component as a credibility data point, not a formatting courtesy.

The five-element verification chain means a wrong reporter abbreviation is structurally invisible until a clerk tries to pull the source, at which point the brief is already filed. The misgrounding problem with AI citation tools means a real citation can still misattribute a holding, delivered with the same fluent confidence as an accurate one. Together, they point to a verification habit that runs before filing, not after, built on a research environment where every component traces back to a primary source you can open yourself.

Start with legal AI and run your next citation check there. Each Bluebook element arrives alongside the underlying opinion, so the T1 abbreviation, court parenthetical, and pinpoint are confirmed by opening the actual record, not trusting the string.

Frequently Asked Questions

Do I always italicize the case name in a Bluebook citation?

It depends on the document type. Case names are italicized or underlined in court documents and briefs, but in law review footnotes the same case name must appear in roman (plain) text. Applying the brief convention to a footnote is a formatting error that any journal editor will flag immediately.

Why does the Supreme Court parenthetical only show a year, with no court label?

Because the reporter abbreviation already identifies the tribunal. When a citation uses 'U.S.' as the reporter, that signals the Supreme Court, making a court label inside the parenthetical redundant under Rule 10.4. The correct form is simply the year, for example, (1966) in Miranda v. Arizona, 384 U.S. 436 (1966).

Can I abbreviate 'United States' to 'U.S.' when it appears as a party in a case name?

No. 'United States' is never abbreviated when it appears as a named party, even though Table 6 governs abbreviation of many other words in the same citation. United States v. Jones stays United States v. Jones in every citation context.

Where exactly does a pinpoint page number go in a Bluebook case citation?

A pinpoint citation slots in immediately after the first page number, separated by a comma and a space, giving you the form: Case Name, Volume Reporter FirstPage, PinpointPage (Court Year). Omitting the separating comma collapses the two page numbers into an ambiguous string that obscures where the opinion starts and which page you are actually citing.

What are the most common case name formatting mistakes to watch out for in a first-pass draft?

The post highlights three recurring errors: carrying the italics habit from briefs into law review footnotes where plain text is required; including 'et al.' or business-entity suffixes like 'Inc.' and 'Co.' that should be omitted entirely under Rule 10.2.1; and failing to apply Table 6 abbreviations (such as 'Ass'n' for 'Association') inside the citation while correctly spelling the word out in running prose. Each signals to a reviewing attorney that the drafter did not know where one rule ends and another begins.