To brief a case, you distill a judicial opinion into a short, structured summary with these parts: Facts, Procedural History, Issue, Holding, Rule, and Reasoning. A good 1L case brief is not a summary of the whole opinion — it isolates the legally significant facts, the exact question the court answered, the rule of law the case establishes, and why the court reached that result, all in about a page or less. Done right, a brief is the thing that gets you through the cold call and the thing you mine for your outline. Done wrong, it's a 45-minute transcription exercise that teaches you nothing.

Here's the honest version nobody puts in the syllabus: briefing is a skill you build fast and then largely abandon. By second semester most students book-brief (annotate in the margins) instead of writing separate briefs. But you can't skip the full-brief phase — it's how you train your brain to read like a lawyer. This guide gives you the method, a worked example, the mistakes that eat your time, and the point where you should stop.

What is a case brief and why do 1Ls write them?

A case brief is a short written breakdown of a court opinion that pulls out only what matters for your class. Casebook opinions are edited and dense; the court cared about things your professor doesn't, and left out things your professor does care about. Briefing forces you to answer three questions every opinion turns on: What was the legal problem? What did the court decide? What rule can I pull out and use again?

Briefing serves two moments that define 1L. First, the cold call — your professor will ask you to state the facts, the issue, the holding, and then push on the reasoning. A good brief means you're reading answers off your own page instead of flipping through the casebook while the room watches. Second, the exam — you don't apply cases on an issue-spotter, you apply the rules the cases establish. Your briefs are the raw material for the outline you'll actually be tested on.

The step-by-step method: how to brief a case

Step 1 — Read the opinion once, all the way through, without writing

Resist the urge to highlight from the first sentence. Read the whole case first so you know where it's going. You cannot identify which facts are "legally significant" until you know what the court held — significance runs backward from the holding. On this first pass, just figure out: who won, and roughly why.

Step 2 — Identify the legally significant facts

A legally significant fact is one that, if you changed it, might change the outcome. In a negligence case, the fact that the defendant was driving 50 in a 25 is significant; the color of the car is not. Write the facts as a short narrative — who did what to whom, and how the dispute arose. Aim for a few sentences, not a paragraph of everything. Include the identity of the parties (plaintiff/defendant, and who they are) because that's the first thing a cold call tests.

Step 3 — Track the procedural history

Procedural history is how the case traveled to the court you're reading. Who sued whom, what happened at the trial court, who appealed, and what this court is being asked to review. This matters more than students think: an opinion reviewing a grant of summary judgment is answering a different question than one reviewing a jury verdict. Note the disposition too — affirmed, reversed, remanded. In Civil Procedure especially, the posture is the point.

Step 4 — Frame the issue as a precise legal question

The issue is the specific legal question the court answered. Frame it narrowly and with the key facts baked in. "Was the defendant liable?" is useless. "Does a railroad owe a duty of care to a passenger standing far away when its employees' negligence toward a different passenger causes a scale to fall on her?" — that's an issue. A good test: the issue should be answerable "yes" or "no," and the answer should be the holding.

Step 5 — State the holding and the rule

The holding is the court's answer to the issue — the outcome and the reason, applied to these facts. The rule is the general principle of law the case establishes, stated so it could apply to future cases. These are related but not the same, and separating them is what turns a summary into a usable brief.

• Holding: On these facts, the railroad owed no duty to Palsgraf because the harm to her was not reasonably foreseeable.
• Rule: A defendant owes a duty of care only to those within the reasonably foreseeable zone of danger created by the defendant's conduct.

The rule is the single most valuable line in your brief. It is what goes into your outline verbatim, and it is what you apply to new facts on the exam. If you take nothing else away from a case, take the rule.

Step 6 — Capture the reasoning (and the dissent, if it's taught)

Reasoning is why the court reached its holding — the logical steps, the policy concerns, the precedent it relied on or distinguished. This is where the exam-relevant nuance lives, and it's what professors probe once you've stated the holding. Keep it tight: two to four sentences tracing the court's logic. If the case is famous for a dissent or concurrence that your casebook includes (Andrews's dissent in Palsgraf, for instance), note its competing rule — professors love making you argue both sides, and issue-spotters reward students who see the alternative framing.

Step 7 — Add your own line: why is this case in the book?

This step isn't in the opinion, and it's the one that pays off in outline season. In one line, note what doctrinal point this case is assigned to teach and where it sits in the course. "This is the case that establishes foreseeability as the test for duty in negligence." That line links the brief to the rule it stands for, which is exactly how your outline should be organized.

A worked example: briefing a negligence case

Say you're assigned Palsgraf v. Long Island Railroad Co., 248 N.Y. 339 (1928) — a first-week Torts staple. A tight brief looks like this:

Facts: A railroad employee, helping a passenger board a moving train, dislodged a package the passenger was carrying. The package contained fireworks, which exploded on impact. The shock (per the court's account) knocked over scales at the other end of the platform, injuring Mrs. Palsgraf, who was standing some distance away.

Procedural History: Palsgraf sued the railroad for negligence and won at trial; the verdict was affirmed on intermediate appeal. The railroad appealed to New York's highest court, the Court of Appeals.

Issue: Does a railroad owe a duty of care to a plaintiff standing far from the point of its employees' negligence, when the resulting harm to her was not reasonably foreseeable?

Holding: No. The Court of Appeals reversed. The railroad's employees breached no duty to Palsgraf, because the risk to her was outside the range of apprehension — she was not a foreseeable plaintiff.

Rule (Cardozo, majority): A defendant owes a duty of care only to plaintiffs within the reasonably foreseeable zone of danger; there is no liability for harm to an unforeseeable plaintiff. Negligence is relational — "a wrong to be redressed only if the eye of ordinary vigilance could apprehend it."

Reasoning: Cardozo framed duty, not proximate cause, as the threshold: negligence is not actionable in the abstract, only as a wrong to a particular person whose interest was foreseeably at risk. Because nothing about the package suggested danger to a distant bystander, the employees owed Palsgraf no duty and could not be negligent toward her.

Dissent (Andrews): Andrews argued the issue is proximate cause, not duty — a defendant owes a duty to the world at large, and liability should turn on whether the injury was a proximate (not too remote) result of the negligent act. This is the competing framework, and professors will ask you to argue it.

Why it's taught: Palsgraf is the anchor case for the duty element of negligence and the foreseeable-plaintiff rule; the Cardozo/Andrews split (duty vs. proximate cause) is the classic exam frame.

Notice the whole thing fits on a page, the rule is quotable, and you could answer any cold-call question from it without reopening the casebook.

The mistakes 1Ls make when briefing

• Transcribing instead of distilling. If your brief is nearly as long as the opinion, you've copied, not briefed. The value is in what you leave out.
• Confusing holding with rule. The holding is fact-specific; the rule is portable. Blur them and your outline becomes a pile of unusable case summaries.
• Vague issues. "Was there negligence?" tells you nothing. Bake the operative facts into the question.
• Skipping procedural history. Especially fatal in Civ Pro, where the standard of review and posture drive the analysis.
• Ignoring the dissent. When a casebook includes a dissent, it's assigned for a reason — usually because it's the counterargument you'll need on the exam.
• Briefing to feel prepared. A beautiful brief you never review is wasted work. The brief exists to be used at the cold call and mined for the outline.

When the skill matters — and when to stop

Full written briefs matter most in your first semester, when reading judicial opinions is new and you're building the instinct for what's significant. That instinct is the actual product. Once you have it — usually by second semester — most students switch to book-briefing: marking the facts, issue, holding, rule, and reasoning directly in the margins with a color code, which takes a quarter of the time and works just as well for the cold call.

The one thing you should never stop doing is extracting the rule. Whether you write a full brief, book-brief, or just annotate, the rule from each case has to migrate into your outline, because the outline — not the briefs — is what you take into the exam. Briefing is scaffolding. Build the building, then take the scaffolding down.