To write a case brief using the IRAC method, read the full opinion once without taking notes, then build four sections: the Issue (the specific legal question the court answered), the Rule (the general legal principle it applied), the Application (how it connected that rule to the facts), and the Conclusion (what it decided). Each section has a specific job, and most briefing mistakes come from blurring them together.
Read the Opinion Before You Write Anything
Court opinions don’t follow IRAC order. Judges digress, address procedural motions, and sometimes bury the key reasoning in the middle of a long discussion. Your first read-through tells you what the case is actually about. On the second pass, you start identifying what belongs in each section.
While you read, flag the material facts — the specific circumstances that actually affected the decision. If the court wouldn’t have ruled differently without a particular fact, that fact is material. Everything else is background. In a breach of contract case, the dates of the agreement, each party’s obligations, and the actions that constituted the breach are material. The fact that the parties met at a conference or that the contract was printed on blue paper is not. Students routinely include too much factual detail, which clutters the brief and obscures the reasoning. If removing a fact doesn’t change the analysis, leave it out.
Track the procedural history too, but only enough to understand what question is in front of this court. Note who won below, who appealed, and what specific ruling is being challenged. An appellate court reviewing a summary judgment ruling is asking a different question than a trial court weighing witness credibility, and your issue statement has to match the question actually before the court.
Write the Issue as a Specific Question
Frame the issue as a question, usually starting with “whether.” It should be specific enough that someone unfamiliar with the case can understand the legal problem the court faced. Avoid questions so narrow they only describe the parties (“whether Smith breached his contract with Jones”) and questions so broad they could apply to hundreds of cases (“whether the defendant was negligent”).
Combine the legal standard with the key facts. Something like: “Whether a landlord who knows about a broken staircase railing but fails to repair it for six months has breached the implied warranty of habitability.” That question identifies the doctrine at stake and the factual circumstances that make it a close call.
Sometimes the court tells you exactly what question it’s answering, often in the opening paragraphs. Other times, the lawyers’ arguments frame the issue, and you have to extract it from how the court responds.
State the Rule in General Terms
The Rule section states the legal principle the court applied. It might come from a constitutional provision, a federal or state statute, a regulation, or prior case law. If the court relied on a statute, identify it and explain what it requires. If the rule comes from case law, state the principle from the earlier case that the court treated as controlling.
The single biggest mistake here is writing the rule as if it only applies to the parties in front of the court. “The defendant owed a duty of care to the plaintiff” is a conclusion about this case, not a rule. “A property owner owes a duty of reasonable care to lawful visitors” is a rule that can be applied to other situations. Ask whether your rule statement would make sense in a case with completely different facts. If it wouldn’t, you’ve written a conclusion disguised as a rule.
Trace the Court’s Reasoning in the Application
The Application is the hardest section to write well, and it’s where the real analytical work happens. You need to show how the court connected the general rule to the specific facts: which facts satisfied which elements of the legal test, which evidence the court found persuasive, and how it addressed counterarguments or distinguished earlier cases cutting the other way.
Don’t just summarize the court’s conclusion. Trace the reasoning. If the court found that a defendant’s actions satisfied all four elements of negligence, walk through each element and explain what facts the court pointed to. If the court distinguished a precedent the losing side relied on, explain why the court found the earlier case inapplicable.
Resist the temptation to insert your own analysis. The Application describes the court’s reasoning, not yours. If you disagree with the court, save that for class discussion or a separate annotation.
Keep the Conclusion Short
State what the court decided and what it did with the case: affirmed, reversed, remanded, granted the motion, denied the claim. One or two sentences is enough. If your conclusion runs longer than a short paragraph, you’re probably rehashing the Application.
Separate the Holding from Dicta
This is the pivot that makes the Rule and Conclusion sections accurate. The holding is the legal principle the court actually used to decide the case. Dicta — short for obiter dicta — are statements the court made along the way that weren’t necessary to the outcome. Only the holding creates binding precedent.
A practical test: ask whether the decision would have come out differently if the court had omitted a particular statement. If yes, that statement is part of the holding. If the court could have reached the same result without it, the statement is dicta. Judges sometimes flag dicta explicitly, noting that an issue “need not be decided here” or that a point is raised “in passing.” Other times you have to figure it out from context.
Mistake dicta for the holding and you’ll misstate the precedential value of the case, which is the whole point of briefing it.
Cases With More Than One Issue
Many opinions address more than one legal question. A single case might involve both a constitutional challenge and a statutory interpretation question, or a court might need to decide whether a duty existed and, separately, whether that duty was breached. Run a separate IRAC analysis for each issue. Each gets its own issue statement, rule, application, and conclusion.
Order the issues the way the court addressed them, since later issues often depend on how earlier ones were resolved. If the court found no duty of care, it might not reach the question of breach, and your brief should reflect that logical sequence. Label each issue clearly so a reader can follow the structure.
Mistakes That Make Briefs Useless
The most frequent error is copying large blocks of the opinion verbatim instead of synthesizing the reasoning in your own words. A case brief is a thinking tool, not a transcript. If you can’t restate the court’s reasoning without copying it, you probably don’t understand it yet, and the brief won’t help you in class or on an exam.
Including irrelevant facts is another common problem. Background details that didn’t influence the outcome distract from the legal analysis and make the brief harder to use as a reference.
Confusing the court’s reasoning with the parties’ arguments trips up students regularly. What the plaintiff argued and what the court actually relied on are often different. The Application should track the court’s analysis, not restate the lawyers’ briefs.
Treat the brief as a living document. After class discussion, a professor may emphasize aspects you underweighted or reframe the holding in a way you hadn’t considered. Go back and revise. The students who get the most value from briefing are the ones who update their briefs after class.
Citations and Page References
A case brief for class doesn’t need the formal formatting required for court filings, but readability still matters. Use clear headers for each IRAC section so you can find what you need at a glance.
When your brief references a statute, a prior case, or a specific page of the opinion, cite it accurately. The Bluebook — formally titled A Uniform System of Citation — provides formatting rules for virtually every type of legal authority you’ll encounter.1The Bluebook. A Uniform System of Citation Getting citation format right in briefs builds habits that pay off when you write legal memoranda and appellate briefs later. Double-check volume numbers, reporter abbreviations, and page references against the original source; a transposed digit can send a reader to the wrong case entirely.
Pin cites deserve special attention. When you quote or reference a specific passage, include the exact page number. If you’re citing a dissent or concurrence, say so explicitly. Vague references to “the court’s opinion” without page numbers make your brief much less useful when you’re reviewing dozens of cases before an exam.
Where IRAC Goes After the Case Brief
IRAC isn’t just for summarizing opinions. The same structure drives legal memoranda, bar exam essays, and the analytical sections of appellate briefs. On a bar exam, you’re essentially running IRAC under time pressure: spotting the issue in a fact pattern, stating the governing rule, applying it to the facts, and reaching a conclusion. Students who internalize the framework through case briefing tend to perform that analysis faster when it counts.
You’ll also encounter variations. CRAC starts with the Conclusion, then moves to Rule, Application, and a restated Conclusion. It works well in persuasive writing where you want the reader to know your position before you explain the reasoning. CREAC adds an Explanation step between Rule and Application, discussing how earlier courts applied the same rule before applying it to your facts. Different law schools and professors prefer different versions, but the underlying logic is identical: identify the question, state the law, apply the law to the facts, and reach a result.