The IRAC method is a four-part structure for legal analysis: Issue, Rule, Application, Conclusion. You frame the legal question, state the controlling law, apply that law to the specific facts, and commit to an answer. It’s the default framework taught in American law schools and used in memoranda, exam answers, and briefs. The concept is straightforward. The discipline is in the Application section, where most of the analytical work happens and where most writers fall short.
Before You Write: Facts and Authorities
Two things come before the first sentence of IRAC. First, a clear picture of what happened. Pull dates, locations, what each party did or said, and the sequence of events from the record. If you have a case file, work through the complaint, contracts, correspondence, and any reports.
Then sort the facts. A material fact is one that could change the outcome; a background fact is everything else. The test is simple: if you can remove a fact without affecting your conclusion, it’s context, not material. In a negligence case, texting while driving is material. The color of the car is not.
With facts in hand, gather the legal authorities that control the issue: statutes, regulations, and binding court opinions. Whether the dispute falls under federal or state law determines which rules apply and which courts have authority. A court opinion from one state has no binding effect in another, so jurisdiction matters from the first citation.
Writing the Issue
The issue frames the whole analysis. If the issue is wrong or too broad, the rest of your IRAC answers the wrong question.
The Under-Does-When Formula
The most reliable structure is: Under [governing law], does [legal question arise] when [key facts]? That single sentence forces you to identify the controlling authority, the precise legal question, and the facts driving the uncertainty. For example: “Under the Fourth Amendment, did officers conduct an unreasonable search when they entered the apartment without a warrant after smelling marijuana from the hallway?”
Match the verb to the timing. Use “did” for completed events, “does” for ongoing issues, and “would” for hypotheticals. Include only the facts that could swing the outcome; leave the rest for the fact section.
Avoiding a Broad Issue
“Did the defendant commit negligence?” tells the reader nothing. Compare: “Under California negligence law, did a property owner breach the duty of care when she failed to repair a broken staircase railing for six months after receiving written notice of the hazard?” The second version names the jurisdiction, the legal standard, the defendant, and the facts that matter. Aim for that level of specificity.
Writing the Rule
The rule section lays out the legal standard before you apply it. State the law here; don’t argue about how it applies yet. Open with the general principle, then break it into its elements. In a contract analysis, you’d state that a valid contract requires mutual assent, consideration, capacity, and a lawful purpose, then define each element so the reader knows what you’ll be testing against the facts.
Synthesizing From Multiple Sources
Legal questions rarely have one complete source. A statute may supply the elements while court opinions interpret them. Weave these into one coherent rule statement rather than listing sources one at a time. A synthesized rule reads like a single standard; a poor one reads like a book report on three cases.
Put all relevant rule material near the start of the section, ideally in one or two sentences that capture the full standard. If a statute gives the elements and a case adds a key test for one of them, merge them. Don’t introduce new rule material in the Application section. By the time the reader reaches your analysis, every standard you’re about to apply should already be on the page.
Citing Authority
Every rule needs a source. Cite the specific statute section when a statute provides the rule, and cite the case when a court opinion interprets or refines it. Parenthetical explanations after case citations tell the reader why the case matters without breaking the rule statement. If no binding authority exists in your jurisdiction, say so and identify the most persuasive authority available.
Writing the Application
This is where the analysis lives. The Application connects each element of the rule to specific facts. Work through the elements in the same order you presented them in the Rule section so the reader can follow without backtracking.
For each element, identify the relevant facts, explain why those facts satisfy or fail the standard, and show your reasoning. The word “because” is the key tool. Every analytical assertion needs a factual justification. “The defendant owed a duty of care because she owned and operated the premises where the plaintiff was injured” is analysis. “The defendant owed a duty of care” standing alone is a conclusion wearing an analysis costume.
The Conclusory Statement Problem
A conclusory statement announces a result without showing the work. It is the single most common error in IRAC writing and the fastest way to lose points on an exam or credibility in a brief. The test: if you can delete the facts from a sentence and it still reads the same way, you’ve written a conclusion, not analysis.
Compare these. Conclusory: “The officer had probable cause to arrest the suspect.” Analytical: “The officer had probable cause to arrest the suspect because the suspect matched the physical description provided by two independent eyewitnesses and was found within three blocks of the crime scene less than ten minutes after the robbery.” The second version ties the legal standard to concrete facts. That connection is the entire point.
Counter-Arguments
Strong analysis anticipates the other side. After making your primary argument on an element, consider what the opposing party would argue and address it. The most effective structure is to present the weaker position first, then the stronger one, and close by explaining why the stronger should prevail. This shows you’ve looked at the problem from both sides rather than picking facts that fit a predetermined answer.
If you’re arguing a contract term is unconscionable, acknowledge the facts supporting enforcement before explaining why the circumstances make it unenforceable. Professors expect this on exams, and judges need it in briefs. Ignoring an obvious counter-argument doesn’t make it disappear; it signals that you haven’t worked the problem through.
Writing the Conclusion
The Conclusion is the shortest section and the one that needs the least creativity. State the answer to the issue directly, reflecting the analysis you just completed. If the issue asked whether the property owner breached a duty of care, your conclusion says yes or no and identifies the key reason in a sentence or two.
Two rules. Don’t introduce new facts or legal arguments that didn’t appear in your Application. And don’t hedge when the analysis supports a clear outcome. If the question was close, say so briefly, but still commit. A conclusion that reads “it depends” after three pages of analysis tells the reader you wasted their time. The point of IRAC is to reach a determination.
IRAC on an Exam vs. IRAC in Practice
The framework shifts based on what the document is for. On a timed exam, you’re proving you can spot issues, state rules accurately, and apply them efficiently. In a practice memorandum, another attorney or a judge will rely on your work to make decisions.
The clearest difference is in the Rule section. Exam answers typically state the black-letter rule and its elements without extensive case discussion, because time is short and issue-spotting counts. Practice memoranda go deeper: they break rules down by element, include case illustrations showing how courts have applied each element, and cite primary authority for every proposition. The Application in practice writing is also more elaborate, leaning on analogical reasoning and detailed comparisons to decided cases rather than pure deductive analysis.
Counter-arguments appear in both, but practice writing demands more thorough treatment. On an exam, noting the opposing argument and briefly explaining why it fails is usually enough. In a brief or memo, you may need to distinguish unfavorable cases, address policy arguments, and explain why your client’s facts are meaningfully different from cases that came out the other way.
Related Frameworks
IRAC isn’t the only option. A few variations rearrange or expand the same components for different documents.
- CRAC (Conclusion, Rule, Application, Conclusion) opens with the Conclusion instead of the Issue, so you state your answer up front and then prove it. This fits persuasive writing like briefs, where you want the judge to know your position immediately.
- CREAC (Conclusion, Rule, Explanation, Application, Conclusion) adds an Explanation section between Rule and Application. The Explanation uses case illustrations to show how the rule works before you apply it. It’s common in law school writing courses that emphasize depth in rule development.
- TREAT (Thesis, Rule, Explanation, Application, Thesis restated) replaces the opening with a thesis heading and closes by restating it. The Explanation, like CREAC, teaches the reader to interpret the rule before seeing it applied.
Each framework uses the same underlying logic: state a standard, show how it works, apply it to facts, reach a conclusion. The differences are about emphasis and ordering. If your professor or supervising attorney specifies a framework, use that one. Otherwise IRAC is the safest default because it’s the most widely recognized. Once you’re comfortable with it, moving to CRAC or CREAC is a matter of rearranging sections you already know how to write.