How to brief a case.

A case brief is a structured summary of a court opinion. When a professor assigns a case for tomorrow's class, they expect you to have read it carefully enough to identify the facts that mattered legally, the issue the court decided, the rule it applied, the holding, and the court's reasoning. A case brief forces you to do that work systematically before you walk in the door.

Unlike reading notes, a case brief is organized by legal function — not by the order things appear in the opinion. Courts spend pages on background before getting to the legal issue. A brief cuts through that and pulls out only what you'll actually use: the facts that trigger the rule, the rule itself, the court's answer, and why. This structure is what lets you quickly reconstruct a case during cold calls, when building outlines, and when writing exam answers under time pressure.

Most law students brief every case in their first semester, then shift to lighter 'book briefing' — margin notes in the casebook — once the structure becomes second nature. The habit you're building is not note-taking. It's reading for legal rules, which is how lawyers read everything.

A complete brief has seven working parts, and each one has a job. Case details anchor the opinion in a court and a doctrine so you know where it belongs in your outline. Procedural posture — who won below, and what the lower court did — tells you what question is actually in front of this court, which is easy to misread if you skip it. Facts are the legally relevant ones only. Issue is the precise question. Rule is the general principle the court applies. Holding is the court's answer applied to these facts. Reasoning is why the court got there — the part that lets you predict how the rule behaves when the facts shift. Leave any one out and the brief stops being usable under exam pressure.

The single highest-leverage move in briefing is reading the procedural posture before anything else. A case that reaches a court on a motion to dismiss is asking a different question than the same case on appeal from a jury verdict — on a 12(b)(6) the court assumes the plaintiff's facts are true and asks only whether they state a claim, while on appeal it is reviewing what a jury already decided. Students who ignore posture routinely state a 'holding' the court never actually reached. Posture tells you the standard the court is operating under, and the standard frames the rule. Write posture first in your brief, before facts, so you never read the opinion backwards.

Briefing should get faster as the semester goes. By week four most students have internalized the structure and move to 'book briefing' — short margin annotations keyed to the same seven parts — reserving full written briefs for cases the professor signals are central or that they find genuinely hard. The goal was never to produce a tidy document; it was to train the reflex of reading an opinion for its rule and its reasoning. Once that reflex is automatic, the written brief becomes optional. Until it is, write them out.

Reading a case opinion efficiently is its own skill. Most opinions are structured the same way: background facts, procedural history, the legal question(s), the court's analysis, and the holding. Before reading word-for-word, scan those sections to orient yourself — find the issue before you wade through pages of fact recitation. Then read the analysis section slowly, because that is where the rule is constructed and tested. Reading the holding first and working backward into the analysis is a legitimate technique for dense opinions: knowing where the court landed makes it easier to understand why each step of the reasoning was necessary.

The reasoning section is the most neglected part of a case brief and the most important one for exam preparation. Most students capture what the court decided but not why — and the 'why' is what you actually need in class and on exams. The reasoning tells you which facts were essential to the outcome, what policy considerations shaped the rule, and how far the rule extends. A brief that records 'court ruled for plaintiff' without explaining the court's logic cannot be used to answer the professor's follow-up: 'What if the defendant had posted a sign?' The reasoning is where you learn the rule's scope and limits.

Briefs feed every other part of the 1L workflow. When you build an outline, you pull the rule from each brief and organize them by doctrine. When you practice IRAC, the rule and reasoning sections become the R and the analysis backbone of your A. When a professor cold-calls you, they probe the reasoning — 'Why did the court rule that way?' and 'What if the facts were different?' — not the facts you memorized. A brief without a solid reasoning section is a brief that only half-prepares you for each of those moments. Write reasoning last, after you've understood the analysis, and write it in your own words: if you can explain why the court decided what it did, you've mastered the case.

Dissents and concurrences deserve a place in your brief when they exist. A dissenting opinion is a professor's favorite tool for cold calls: 'The dissent argues X — do you agree?' If you haven't read the dissent, you cannot engage with that question, and your brief should prepare you for it. Capture the dissent's rule or policy argument in a single sentence: 'Andrews dissent in Palsgraf: duty runs to anyone harmed by defendant's breach, not just foreseeable plaintiffs.' In the exam room, knowing both sides of a contested rule is how you write the counterargument in your Application. A brief that records only the majority position leaves you half-armed.

Some opinions raise multiple legal issues — a Torts case might address both the duty question and a remoteness-of-harm question before reaching the holding. When a case has more than one issue, your brief needs a separate issue, rule, holding, and reasoning for each one. Students who collapse multiple issues into a single brief entry produce a muddled rule that doesn't travel cleanly to the outline. Label each issue with a number or header and treat them as distinct mini-briefs within the same document. This matters most for the cases professors teach over multiple class sessions — those cases usually contain at least two separable legal questions, and if you only briefed one of them, you will be caught flat-footed on day two.

When time is short and you cannot brief every case fully, triage based on professor signals. Cases on which the professor spent two or more class days, cases that appear on the practice exam, and cases the syllabus marks with an asterisk or calls 'important' always get a full brief. For cases that received five minutes of class discussion and no Socratic probing, a compressed brief — rule + holding + exam trigger, two to three lines — is sufficient. Volume of briefs is not the goal; accurate, usable briefs on the cases that actually matter is. Ten complete, reasoned briefs on the professor's central cases are worth more than forty thin summaries of the entire casebook. Quality and selectivity beat volume: a brief you can deploy under cold-call pressure — precise rule, solid reasoning, concrete exam-relevance note — is worth ten briefs you barely remember writing.