To IRAC a case, you work through four steps in order: identify the Issue (the precise legal question), state the Rule (the governing law), apply the rule to the facts (the Application), and finish with a Conclusion that answers the question you opened with. The framework forces you to show your reasoning instead of jumping to a result, and it mirrors how courts actually decide disputes. Everything below walks through each step, then puts them together in a worked example.
The Four Steps
Each letter marks a distinct phase, and rushing any one of them creates problems that ripple through the rest.
- Issue: Identify the precise legal question the facts raise.
- Rule: State the legal standard, statute, or test that governs.
- Application: Explain how the rule connects to the specific facts, element by element.
- Conclusion: Answer the question you posed in the Issue.
Step 1: Frame the Issue
The issue is a specific legal question, not a topic. “Is there negligence?” is too broad to guide any analysis. A well-framed issue weaves together the relevant legal standard and the key facts that make the answer uncertain. Compare:
- Weak: “Can the plaintiff recover damages?”
- Strong: “Did the store owner breach a duty of care to the customer by failing to clean a spill in the produce aisle for over two hours?”
The strong version tells the reader exactly what law is at stake (duty of care, breach) and exactly which facts matter (the unattended spill, the two-hour window). It narrows the analysis before you write another word.
The Under-Does-When Formula
A reliable way to draft an issue statement is the Under-Does-When formula: “Under [law], does [legal standard apply] when [key facts]?” For example: “Under Minnesota law, does the court have personal jurisdiction over a nonresident defendant when the defendant’s only contact with the state was a single online transaction?” That single sentence names the jurisdiction, the legal test, and the facts. Once you are comfortable with it, you can adapt the phrasing, but the formula keeps beginners from writing issues that are either too vague or too conclusory.
Step 2: State the Rule
The rule section lays out the legal standard that controls the issue. This might be a statute, a common-law test, a constitutional provision, or a combination. State the rule as a general principle, not as a conclusion about your case. You are building the measuring stick before you measure anything.
Think of this section as a funnel. Start with the broadest governing principle, then narrow to the specific elements or factors the court applies. For a negligence claim, you would begin with the general standard: a plaintiff must prove that the defendant owed a duty of care, breached that duty, and that the breach was both the actual and proximate cause of the plaintiff’s injuries.1Legal Information Institute. Negligence After stating the elements, define each one as necessary. If breach is the contested element, spend more time explaining what breach means. If duty is obvious, keep it brief.
How Much Detail the Rule Needs
A common mistake is giving a one-sentence rule and then jumping into the application. Your rule section should be detailed enough that someone unfamiliar with the topic could follow your analysis. If the rule has elements, list them. If courts use a multi-factor balancing test, identify the factors. If there is a key case that defined the standard, describe its holding briefly. For a contract formation issue, you would note that a valid contract requires mutual assent (offer and acceptance), consideration, capacity, and a lawful purpose.2Legal Information Institute. Contract Each of those elements can become its own mini-analysis.
Step 3: Apply the Rule to the Facts
The application section is where the real analysis happens. Everything before this was setup. Now you connect each element of the rule to the specific facts of your case, explaining why the facts satisfy or fail to satisfy each requirement.
The simplest technique: use the word “because.” For every legal conclusion you assert, follow it with “because” and then point to the facts that support it. “The store owner breached the duty of care because employees were aware of the spill and failed to clean it or place warning signs for over two hours, despite company policy requiring cleanup within fifteen minutes.” That connector forces you to link law to fact rather than restating one or the other.
Reasoning by Analogy
Strong application sections do not just match facts to elements in a vacuum. They compare the current facts to the facts of decided cases and explain why the comparison supports a particular result. If a prior case found breach where a store left a spill unattended for thirty minutes, and your case involves a two-hour delay, the comparison is powerful. If the prior case instead involved a hidden hazard and your spill was in plain view, you would need to distinguish the cases and explain why visibility matters.
Addressing Counter-Arguments
One-sided analysis is weak analysis. After presenting the stronger argument, acknowledge what the other side would say and explain why it falls short. A reliable structure: state the losing side’s argument, state the winning side’s argument, identify which side a court would favor, and explain why by pointing to precedent or policy. In the spill example, the store owner might argue the customer should have seen the spill and avoided it. You would then explain why that argument fails under the applicable standard, perhaps because the duty to maintain safe premises does not shift to customers who are focused on shopping rather than scanning the floor.
Focus on arguments a competent attorney on the other side would actually raise. You do not need to address every conceivable objection.
Step 4: Write the Conclusion
The conclusion directly answers the legal question you posed in the Issue. It should flow logically from your application, introduce no new facts or arguments, and stay concise. A sentence or two is usually enough: “The store owner likely breached the duty of care to the customer, and the customer can probably establish the remaining elements of negligence.”
How Certain to Sound
How definitive your conclusion should be depends on the context. On a law school exam, professors generally want you to pick a side and commit, even when the facts are close. Hedging with “it could go either way” signals that you could not make up your mind rather than that you saw both sides. In a predictive office memo, some qualification is appropriate because you are forecasting what a court would do, not advocating for a client. In a persuasive brief, the conclusion is a firm assertion of your client’s position.
Whatever the context, the conclusion must match the analysis. If three out of four elements were clearly met but the fourth was questionable, your conclusion should reflect that nuance rather than declaring a clean victory.
A Worked Example
Seeing all four steps applied to a single fact pattern makes the framework concrete.
Facts: Maria slipped and fell on a wet floor in a grocery store. An employee had mopped the aisle ten minutes earlier but never posted a “wet floor” sign. Maria broke her wrist and incurred $8,000 in medical bills.
Issue: Whether the grocery store is liable for negligence by failing to warn Maria of the wet floor after an employee mopped the aisle.
Rule: A negligence claim requires proof of four elements: (1) the defendant owed the plaintiff a duty of care, (2) the defendant breached that duty, (3) the breach was the actual and proximate cause of the plaintiff’s injury, and (4) the plaintiff suffered cognizable harm.1Legal Information Institute. Negligence Business owners owe invitees a duty to maintain reasonably safe premises, which includes warning of known hazards.
Application: The store owed Maria a duty of care because she was a business invitee shopping during normal hours. The store breached that duty because its employee created the hazard by mopping and then failed to post any warning sign, falling below the standard a reasonable business owner would meet. Causation is straightforward: Maria would not have slipped but for the unmarked wet floor, and a slip-and-fall injury is a foreseeable consequence of an unwarned wet surface. The store might argue Maria should have noticed the wet floor herself, but this argument is weak because the store’s own employee created the danger and the store had a superior ability to warn. Maria suffered concrete harm in the form of a broken wrist and $8,000 in medical expenses.
Conclusion: Maria can likely establish all four elements of negligence, and the store will probably be held liable for her injuries.
Notice how the application moves through each element, uses “because” to connect law to fact, and addresses the store’s likely counter-argument before explaining why it fails. That is the pattern to aim for.
Handling Multi-Element Problems with Nested IRACs
Real legal problems rarely involve a single clean issue. When a rule has multiple elements, each contested element gets its own mini-IRAC nested inside the larger framework. For a negligence claim, that looks like:
- Overall Issue: Whether the defendant is liable to the plaintiff for negligence.
- Overall Rule: List all the elements (duty, breach, causation, damages) and any general principles that apply across elements.
- Analysis: Perform a separate IRAC for each element. For breach alone, you would state the sub-issue (“whether the defendant breached the duty of care”), define the standard for breach, apply the facts to that standard, and reach a sub-conclusion.
- Overall Conclusion: Synthesize the sub-conclusions into a final answer.
You do not need a full nested IRAC for uncontested elements. If duty is obvious because the defendant was the plaintiff’s doctor, a sentence acknowledging that is enough. Spend your analytical firepower on the elements where the facts cut both ways.
Variations: CRAC and CREAC
Not every professor or firm uses the same acronym. Two common variations reorganize the same core logic:
- CRAC (Conclusion, Rule, Application, Conclusion): Leads with the conclusion rather than a question, then supports it with rule, application, and a restated conclusion. This front-loads the answer, which is standard in office memos where the reader wants the bottom line first.
- CREAC (Conclusion, Rule, Explanation, Application, Conclusion): Adds an explicit “Explanation” phase between the rule statement and the application. In that phase, you discuss how courts have applied the rule in prior cases, illustrating the rule in action before you apply it to your own facts.
The underlying logic is identical. If your professor or firm uses CREAC, the Explanation section is where you would walk through the relevant facts and holdings of prior cases so the reader understands the rule’s boundaries before you start your analysis.
Mistakes That Cost the Most Points
Legal writing professors see the same problems repeatedly:
- Conclusory application: Writing “the defendant breached the duty of care” without explaining which facts demonstrate the breach. Every legal conclusion needs factual support connected by reasoning.
- Fact dumps without analysis: Restating the entire fact pattern in the application section without connecting any of it to the rule. Your job is to explain what the facts mean legally.
- One-sentence rules: Stating “negligence requires duty, breach, causation, and damages” and immediately jumping to the application. That is a label, not a rule statement. Define the elements and explain the standard.
- Arguing only one side: Presenting only the facts that support your conclusion while ignoring the other side. Addressing counter-arguments and explaining why they fail makes your conclusion stronger, not weaker.
- New arguments in the conclusion: If you find yourself raising a new point at the end, it belongs in the application section.
- Vague issue statements: Writing “Is there a tort?” instead of identifying the specific cause of action and the facts that make it debatable.
The common thread across all of these is skipping reasoning. IRAC exists to make you show your work. Every time you assert a legal conclusion, ask yourself whether you have explained why the facts lead there. If you cannot point to specific facts and connect them to the rule with a “because,” you have not finished the step.