The first cases you read in law school will feel like they were written to defeat you. They're long, the sentences run for half a page, judges bury the point in the middle of a paragraph about railroad timetables, and half the words are Latin. Here's the reframe that changes everything: you are not reading a case to appreciate it. You are reading it to extract something specific. A case is not literature — it's a container for a legal rule, and your entire job is to find that rule and understand how the court reached it. Once you know what you're hunting for, cases stop being intimidating and start being fast.
This guide gives you the exact method: how to read a case the first time, how to read it the second time, the seven parts you're extracting, and the mistakes that get 1Ls destroyed on cold calls. Learn this in your first two weeks and every reading assignment for the rest of the year gets shorter.
Judicial opinions weren't written for you. They were written for lawyers, other judges, and the parties — people who already know the area of law. So the opinion doesn't stop to explain doctrine, it doesn't tell you which facts matter, and it doesn't announce "here is the rule." You have to build all of that yourself. That's the skill. And it's genuinely a skill, not a talent — the students who read cases quickly by November read them exactly as slowly as you do in September. The difference is method. The following method is what separates a two-hour reading assignment from a forty-minute one.
Do not brief on this pass. Do not highlight everything. Read the case the way you'd read a news article about a lawsuit: Who sued whom? What happened to them in the real world? Who won? Your only goal on the first read is to understand the narrative arc and the outcome. If you finish the first read and can say in one sentence what the fight was about and who prevailed, you've done the first read correctly.
Resist the urge to understand every sentence. You will hit paragraphs that make no sense — legal terms you haven't learned, procedural moves you can't yet name. Keep going. The first read is for orientation, and things that were opaque on the first pass often become obvious once you know the outcome.
Now you read like a lawyer. This is where you pull the case apart into the components you'll actually use — in class, in your outline, and on the exam. There are seven, and they map almost exactly onto a case brief.
Separate the legally significant facts from the background. A legally significant fact is one that, if you changed it, might change the outcome. In a case about whether a store owed a duty to a customer who slipped, the fact that it was raining outside might be significant (was the floor wet?); the fact that the customer was buying milk probably isn't. Professors love to test this line: "What if the plaintiff had been an employee instead of a customer — same result?" If you can't tell which facts drove the decision, you can't answer that.
This is the part 1Ls skip and regret. Procedural posture tells you what the court is actually deciding. A court ruling on a motion to dismiss is deciding whether the complaint, if everything in it is true, states a claim — it is not deciding who's telling the truth. A court reviewing a jury verdict is asking whether any reasonable jury could have reached that result. Same facts, completely different question. If you state the holding without knowing the posture, you'll say the court "found the defendant negligent" when the court actually held that the plaintiff had alleged enough to get to trial. That's a cold-call death.
Frame the issue as a precise legal question, usually answerable yes or no: "Does a railroad owe a duty of care to a passenger injured by an explosion the railroad's employees could not have foreseen?" Not "Was the railroad negligent?" — too vague. The narrower and more precise your issue, the more you actually understood the case.
The holding is the court's answer to the issue — the outcome tied to the legal question. "The railroad owed no duty because the injury was unforeseeable." The holding is narrow and specific to this case's facts.
The rule is the generalizable principle the case establishes — the thing that governs future cases, and the thing that goes in your outline. The rule is broader than the holding: "A defendant owes a duty of care only to those within the foreseeable zone of danger." When your professor asks "what's the rule from this case?" this is the answer. Distinguishing the rule from the holding is one of the most valuable habits you can build early.
How did the court get from the issue to the holding? This is the court's logic — the policy arguments, the precedent it relied on, the analogies it drew. Reasoning is what you'll deploy on an exam when you argue how a court would decide a new fact pattern. A holding tells you the answer; the reasoning tells you how to argue the next case.
Read them when they're assigned — and notice that they're usually assigned on purpose. A dissent exists because a smart judge thought the majority got it wrong, which means the dissent is a map of the majority rule's weakest point. Professors assign famous dissents precisely because the tension between majority and dissent is the doctrine's live nerve. On an exam, the dissent's reasoning is often exactly the counterargument you're expected to make.
Say you're assigned a torts case about a plaintiff hurt in an unusual chain of events. First read: a passenger was carrying a package, railroad employees pushed him to help him board, the package fell, it turned out to contain fireworks, they exploded, and the shockwave knocked over a scale far down the platform that injured a different passenger. Who won? The railroad. Good — first read done.
Second read, you extract: Facts — the injured plaintiff was standing far away; the harm to her was not a foreseeable result of helping the package-carrying man. Posture — the case reached the state's highest court on appeal from a verdict for the plaintiff. Issue — does a defendant owe a duty to a plaintiff whose injury was unforeseeable? Holding — no; the railroad owed no duty to this plaintiff. Rule — duty is owed only within the foreseeable zone of danger. Reasoning — negligence is relational; there is no wrong "in the air" divorced from a duty to the particular person harmed. Dissent — argues duty should extend to anyone actually harmed by a negligent act, with liability limited later by proximate cause. Notice how the dissent hands you the entire alternative framework. That tension is the whole point of the assignment.
The seven parts aren't busywork — they are the raw material for everything downstream. Your case brief is just these seven parts written down. Your cold-call answers come straight from the facts, posture, holding, and rule. Your outline distills to the rule from each case plus a one-line trigger of the facts. And your exam answers are built by taking the rules you extracted and applying their reasoning to new facts. Reading a case well is the foundation the entire year sits on. Do it deliberately for the first month and it becomes automatic.
Full second-read extraction is a first-semester discipline. By second semester, most students book-brief — annotating the casebook margins with the seven parts rather than writing separate briefs — because the method is internalized and they can extract on a single careful read. That's fine and expected; it means the skill worked. But don't skip to book-briefing in week one. You earn the shortcut by doing the long version until the seven parts jump off the page on their own.