Law School Study Guides
The IRAC Method, Explained
What IRAC stands for, how to write each of the four elements, when to use IRAC versus FIRAC or CREAC, IRAC for case briefs vs exam essays vs legal memos, and the mistakes that cost 1Ls the most exam points.
Last updated: June 2026.
What IRAC Is (and Why Every Law School Teaches It)
IRAC is a four-part structure for legal analysis: Issue, Rule, Application, Conclusion. It is the standard organizing framework for nearly every form of legal writing a law student encounters — case briefs, exam essays, in- class hypotheticals, and most legal memos in modified form.
The framework exists because legal analysis isn't free-form writing. A judge, a partner reading a memo, or an exam grader wants to see four specific things in a predictable order: what question is being addressed, what law governs it, how the law applies to these facts, and what the answer is. IRAC makes those four things visible.
The acronym is taught as early as the first week of law school because it standardizes legal reasoning. Without it, two students could write equally correct answers in radically different orders and the grader would have to reconstruct the analysis. With it, every answer reads roughly the same way and the grader can quickly verify each element is present.
The Four Elements of IRAC, One at a Time
Each letter represents a section. Understanding what belongs in each section — and what doesn't — is the entire skill.
Issue
The legal question that needs to be answered.
Frame it as a question. Make it specific enough that a reader who has never seen the facts knows what the law is being asked about. On exams, spot every issue the fact pattern raises — missed issues are missed points.
Don't restate the entire fact pattern. Don't be so general that the issue could apply to any case ("Was the defendant liable?" is not an issue — "Did the defendant breach a duty owed to a foreseeable plaintiff?" is).
Rule
The legal principle that governs the issue.
State the rule in portable form — without the case-specific facts. Include all elements of the rule (mens rea, actus reus, intent, foreseeability) so you can apply each one. Cite the source (Restatement, case, statute).
Don't write a fact-bound conclusion masquerading as a rule. Don't omit elements you'll need in Application. Don't pad with rules that don't bear on the issue.
Application (or Analysis)
Walking the facts through each element of the rule.
Go element by element. For each, identify the fact that satisfies (or fails to satisfy) it. Acknowledge counterarguments — what the other side would say, and why the rule still favors your position. This is where exam points live.
Don't re-state the rule. Don't re-state the facts as a narrative. Don't conclude without showing your reasoning — the conclusion isn't the work; the application is.
Conclusion
The answer to the issue, applied to these facts.
One sentence per issue. State the result with confidence. If multiple issues are present, conclude each one separately, then optionally a final overall conclusion.
Don't hedge ("It depends, but maybe...") — hedging tells your professor you didn't apply the rule decisively. Don't introduce new analysis here. Don't skip it — the conclusion locks the analysis in.
IRAC in Three Contexts — What Shifts and What Doesn't
The same four elements are used in case briefs, exam essays, and legal memos. What changes is which sections expand, how the ordering is presented, and how much you generate vs. transcribe.
Case Brief (extracting IRAC from an opinion)
When it applies: 1L doctrinal courses. You're reading a judicial opinion and need to identify the IRAC the court used.
What changes: The court already framed the issue, applied a rule, and reached a conclusion. Your job is to identify each and write them down. This is the easiest version of IRAC — you're not generating, you're transcribing.
Example setup: Reading Palsgraf v. Long Island Railroad. The court framed the issue as whether the railroad owed a duty to Mrs. Palsgraf; you record that as Issue. The court announced the foreseeability/zone-of-danger rule; you record that as Rule. And so on.
Exam Essay (generating IRAC from a fact pattern)
When it applies: Midterms, finals, and bar exams. You're handed a fact pattern and asked to apply the law you've learned.
What changes: You generate IRAC from scratch. Issue-spotting becomes the highest-leverage skill — missed issues are missed points. Application becomes the longest section because that's where points are awarded; conclusion is short.
Example setup: Fact pattern: A driver runs a red light and strikes a pedestrian who steps off the curb mid-text. You spot the issues (negligence, comparative fault), state the rule for each (duty of care, contributory/comparative negligence), apply, then conclude.
Legal Memo (predictive IRAC for a client)
When it applies: Legal writing courses, summer jobs, and clinic work. You're researching the law on behalf of a client and need to predict how a court would rule.
What changes: Most legal writing programs use CREAC instead — Conclusion first (so the partner reading the memo doesn't have to wait for the answer), then Rule, Explanation, Application, Conclusion. The substance is identical to IRAC; the ordering is reader-focused.
Example setup: Client asks whether their non-compete clause is enforceable. You write a memo leading with your prediction ("The clause is likely unenforceable"), then explain the rule (state-law reasonableness test), unpack it with caselaw, apply it to the client's facts, and conclude.
Want to see all three side-by-side? Our IRAC Example guide shows the same legal analysis written as a case brief, an exam essay, and a legal memo — so you can see what shifts between formats.
IRAC as Exam Strategy — Where the Points Actually Are
Law school exams are graded by a rubric, not a narrative. Every issue spotted earns points. Every correctly stated rule earns points. Every fact applied to a rule element earns points. Conclusions earn very little. This has consequences for how to allocate your writing time:
- Issue: Spot every issue. Missed issues are missed points and are not recoverable. If you spot 7 issues and a classmate spots 5, you start the exam 40% ahead before the analysis even begins. Issue spotting is the highest- leverage skill in 1L.
- Rule: State each rule completely — all elements. You will need each element in your Application. A common 1L mistake is to state only the rule's headline and skip the elements ("negligence requires duty, breach, causation, damages") — you should also state what each element requires (e.g., "duty is determined by the reasonable person standard except where a special relationship exists").
- Application: This is where most of the points are. Walk each element of the rule through the facts of the hypothetical. For each, identify the fact that satisfies or fails the element. Address counterarguments. The Application section should be the longest part of every IRAC.
- Conclusion: One sentence per issue. Don't hedge. If the rule favors one side, conclude in that direction. If the rule is genuinely close, conclude in the direction the court is most likely to reach and explain why.
The takeaway: writing time should be distributed roughly 10% Issue, 20% Rule, 60% Application, 10% Conclusion. Most failing exams flip Rule and Application — long Rule statements, short Application — and end up with the right law but no analysis.
IRAC Variants — When the Order Changes
Different forms of legal writing reorder the same elements for different audiences. The substance is identical; the sequencing is reader-focused.
| Acronym | Stands For | Best For |
|---|---|---|
| IRAC | Issue, Rule, Application, Conclusion | Universal default. 1L doctrinal courses, exam essays, casual analysis. |
| FIRAC | Facts, Issue, Rule, Application, Conclusion | Civil Procedure and any course where procedural posture is doctrinally important. |
| CREAC | Conclusion, Rule, Explanation, Application, Conclusion | Legal writing memos. Lead with the conclusion so the partner reading doesn't have to scroll. |
| CRAC | Conclusion, Rule, Application, Conclusion | Persuasive briefs — motions, appellate briefs, moot court. Lead with the result you want the court to reach. |
| IRREAC | Issue, Rule, Rule Explanation, Application, Conclusion | Programs that want you to separately explain caselaw before applying the rule. A more verbose IRAC. |
Which one should you actually use?
- 1L Torts, Contracts, Property, Criminal Law: IRAC.
- 1L Civ Pro and Federal Courts: FIRAC.
- Legal writing memos: CREAC (your instructor is grading on this format — use it).
- Moot court / appellate / motion practice: CRAC.
- Doctrinal exam essays: IRAC unless your professor explicitly prefers another format.
7 Common IRAC Mistakes (and How to Fix Them)
1. Skipping the Application section
The single most expensive mistake. Most exam points live in Application, not Rule. If your IRAC goes Issue → long Rule → Conclusion, you've skipped the section the grader is most actively scoring.
2. Writing the Rule with case-specific facts in it
A rule should be portable. "The court held the railroad owed no duty to Mrs. Palsgraf because she was far away" is a Holding masquerading as a Rule. The Rule should work for the next case: "A defendant owes a duty of care only to those whose injuries are reasonably foreseeable from the defendant's conduct."
3. Missing issues
Spot every issue, including the ones that look like throwaways. Each missed issue is a multiple-points loss. On a 4-issue negligence fact pattern, spotting only 3 issues caps you at 75% before the grader looks at your analysis. Speed-read the fact pattern once for issues before starting to write.
4. Hedging the conclusion
"It depends, but the court could go either way" is not a conclusion. Apply the rule, identify the strongest argument, and conclude in that direction. Even when the answer is genuinely close, write a definite conclusion and note the counterargument as a parenthetical.
5. Restating the facts as a narrative
The grader read the fact pattern; you don't need to summarize it. Reference facts within Application as you walk them through rule elements ("here, the defendant's knowledge of the spilled water satisfies the actual-notice prong") — not as a standalone facts paragraph.
6. Using headers for IRAC sections on exam essays
Most professors don't want "ISSUE:", "RULE:", "APPLICATION:", "CONCLUSION:" headers on exam answers. The structure should be visible from the writing itself — issue stated as a question, rule stated, application worked through, conclusion stated. Headers can fragment the analysis and look formulaic.
7. One IRAC for the whole exam answer instead of one per issue
Each separate issue gets its own complete IRAC. A negligence exam with duty, breach, causation, and damages issues should have four IRACs, not one giant IRAC with all the rules stacked in the middle. Separate IRACs make it easier for the grader to award points per issue.
Frequently Asked Questions
What does IRAC stand for?+
Why is IRAC important in law school?+
How do I write the Issue in IRAC?+
What's the difference between Rule and Application?+
When should I use FIRAC instead of IRAC?+
Should I use IRAC on every exam answer?+
Is IRAC used in real legal practice?+
What's the most common IRAC mistake?+
Apply IRAC + See It in Action
- IRAC Example — 3 Worked IRACs — IRAC applied to a case brief, an exam essay, and a legal memo, side-by-side. The companion to this method guide.
- Case Brief Example — 3 Worked Briefs — three full IRAC briefs across Torts, Contracts, and Civ Pro. See IRAC used to brief real opinions.
- Issue Spotter Tool — paste a fact pattern, get an IRAC checklist. Built for exam practice.
- Interactive Case Brief Editor — IRAC and FIRAC live preview, export as PDF or Word. Free, no signup.
- How to Brief a Case — Complete Guide — full briefing tutorial with course-specific tips and cold- call prep.
- Free Case Brief Library — 156 worked briefs across every 1L subject.
- Best AI Tools for Law Students (2026) — comparison of 8 AI tools and where each fits in a law school workflow.