To write an IRAC, state the legal Issue as a precise question, lay out the Rule that governs it in general terms, Apply the rule element by element to your facts, and close with a Conclusion that answers the question in one or two sentences. The structure works because it forces you to keep three things separate: what you’re asking, what the law says, and how the law meets your specific facts. Law students learn it in the first week of legal writing, and practicing attorneys use variations of it every time they draft a memo or brief.
Write a Sharp Issue
Every IRAC starts with a question. The classic phrasing opens with “whether”: “Whether a valid contract was formed between the parties despite the absence of a written agreement.” That format works because it forces you to name both the legal doctrine at stake and the factual wrinkle that makes the answer uncertain. “Did” and “Can” openings do the same job if your professor prefers them.
The most common mistake is writing the issue too broadly. “Whether the defendant is liable” tells the reader nothing. Compare it with “Whether the defendant owed a duty of care to a trespasser who entered the property after hours.” The second version names the doctrine, the parties, and the fact that creates the tension. A good test: your issue should be narrow enough that a reader can predict what your Rule section will cover.
When a problem raises more than one legal question, give each its own IRAC. If a negligence claim involves disputes about both duty and causation, write a separate analysis for each element rather than cramming both into one. Nesting the analyses keeps each piece focused and prevents tangled reasoning.
State the Rule in General Terms
The Rule section lays out the law that governs your issue. Think of it as the measuring stick you will hold against the facts in the next section. State the general principle first, then break it into its elements. For a negligence claim, you would explain that negligence requires a duty of care, a breach of that duty, causation, and harm, and then briefly define each element.
Keep the rule general. This is where many writers slip: they start weaving in facts from the specific scenario, which blurs the line between what the law says and how it applies. The Rule should read as if it could apply to any case involving the same doctrine. No client names, no specific dates, no reference to “the defendant’s car” or “the plaintiff’s broken arm.” The client’s story belongs in the Application.
Synthesizing Rules From Multiple Sources
Legal rules rarely come from a single case or statute. When your rule draws from several authorities, synthesize them into a coherent statement rather than summarizing each source in sequence. If three cases each clarify a different aspect of “reasonable care,” pull the principles together: “Courts evaluate reasonable care by considering the foreseeability of harm and the severity of potential injury, weighed against the burden of taking precautions.” That is synthesis, and it reads cleaner than a string of case summaries.
Knowing Your Source Hierarchy
Where your rule comes from matters. Constitutional provisions carry the most weight, followed by statutes, then regulations, then case law from higher courts, then case law from lower courts. Secondary sources like treatises and law review articles sit at the bottom. On a law school exam this rarely matters, but in a practice memo or brief, citing a trial court opinion when a Supreme Court case is on point undermines your credibility quickly. When two authorities conflict, the higher one controls.
Apply the Rule to Your Facts
The Application is where the real analysis happens. Everything before it is setup; everything after it is cleanup. Take each element from your Rule section and show, fact by fact, whether the scenario satisfies it. The word that should appear constantly in this section is “because.” If your Application paragraphs do not contain it, you are probably stating conclusions without supporting them.
Work through the elements one at a time. If your rule lists four elements, address all four, even the ones that seem obvious. Skipping an element because it is “clearly met” is one of the fastest ways to lose points on an exam. A sentence or two on an uncontested element is enough, but silence suggests you did not spot it.
Using Analogical Reasoning
The strongest applications compare your facts to the facts of decided cases. Analogical reasoning follows a predictable pattern: identify a precedent with similar facts, point out the key similarities, then explain why those similarities should produce the same outcome. If you are arguing the other side, emphasize the differences and explain why they call for a different result.
Say a precedent found that a store owner owed a duty of care to customers who slipped on a wet floor, and your case involves a customer who tripped over loose cables. You would argue that both situations involve hazardous conditions on business premises that the owner knew about or should have discovered. The comparison works because you are connecting specific facts to specific facts, not gesturing at general principles.
Addressing Counterarguments
Strong legal analysis does not just argue one side. After presenting your primary argument for each element, address what the opposing side would say. A useful structure is to present the weaker argument first, then the stronger one, and finish by explaining why the stronger argument prevails. Counterarguments belong in the Application, not the Conclusion. The Application is where you weigh competing interpretations; by the time you reach the Conclusion, the weighing should be done.
Write the Conclusion
The Conclusion answers the question you posed in the Issue. Keep it to one or two sentences. Do not rehash the analysis or introduce new arguments. If your issue asked whether a valid contract was formed, the Conclusion says yes or no with a brief reference to the decisive reasoning: “A court would likely find that no valid contract was formed because the defendant’s response did not constitute an unequivocal acceptance.”
Your tone depends on the document. In a predictive memo for a supervising attorney, hedge appropriately: “The court will probably find that…” or “A claim is unlikely to succeed because…” You are predicting an outcome, not advocating for one. In a persuasive brief to a court, drop the hedging: “The court should grant summary judgment because…” The same IRAC framework supports both registers; only the confidence of that final sentence changes.
A Worked Example
Here is a condensed IRAC on whether a police officer used excessive force, so you can see how the four sections connect.
Issue: Whether Officer Smith’s use of force against Victim during a routine traffic stop was excessive under the Fourth Amendment.
Rule: The Fourth Amendment prohibits unreasonable seizures, including the use of excessive force during an arrest. Courts evaluate whether force was reasonable by considering the severity of the crime, whether the suspect posed an immediate threat to safety, and whether the suspect was actively resisting or attempting to flee.
Application: Victim was stopped for a broken taillight, a minor traffic infraction. He remained seated in his vehicle with his hands visible on the steering wheel. Nothing in the facts suggests he threatened Officer Smith or attempted to flee. Despite this, Officer Smith pulled Victim from the car and used a chokehold to restrain him. Because the underlying offense was minor, because Victim posed no safety threat, and because Victim was not resisting, all three factors weigh against the reasonableness of Officer Smith’s actions.
Conclusion: A court would likely find that Officer Smith’s use of force was excessive because Victim posed no threat and was compliant during a stop for a minor infraction.
Notice how the Application does not restate the rule or redefine legal terms. It picks up each factor from the Rule section and matches it to a specific fact. That is the mechanical rhythm of good IRAC writing: element, fact, link.
Mistakes That Cost Points
- Mixing rule and application. Dropping case-specific facts into the Rule section collapses the structure. The moment you mention your client by name in the Rule, you have jumped ahead.
- Stating conclusions without reasoning. Writing “the defendant breached the duty of care” in the Application without explaining which facts establish the breach. Every legal conclusion in the Application needs a “because” and at least one fact attached to it.
- Skipping uncontested elements. If the rule has four elements, address all four. A sentence explaining why an easy element is satisfied is enough, and on exams this is where cheap points live.
- Introducing new law in the Conclusion. The Conclusion should flow from analysis you have already done. If you find yourself citing a new case there, that material belongs back in the Rule and Application sections.
- Writing a vague issue. “Whether negligence occurred” does not tell the reader which element is disputed or what facts create the controversy. Precision in the Issue section saves you from wandering in the Application.
When the Problem Has Multiple Issues
When a legal problem involves several sub-issues, an umbrella paragraph at the top of your analysis gives the reader a roadmap before you dive into individual IRACs. The umbrella states the overarching legal question, identifies the sub-issues you will address, and provides any legal authority that applies to all of them.
If you are analyzing negligence and the dispute involves both duty and causation, your umbrella paragraph would note that negligence requires four elements, flag duty and causation as the contested ones, and set up the two separate IRACs that follow. Keep it to a paragraph or two. Its job is to orient, not to analyze. Each sub-issue then gets its own self-contained IRAC with its own issue, rule, application, and conclusion.
CRAC and CREAC Variations
IRAC is not the only framework for legal analysis. Two common variations rearrange the same building blocks.
CRAC (Conclusion, Rule, Application, Conclusion) leads with the answer. Instead of posing a question and working toward a resolution, you state your conclusion up front, explain the rule, apply it, and restate the conclusion. Many practicing attorneys prefer this format for memos and briefs because busy readers want the bottom line immediately. If a partner asks whether a client has a viable claim, they do not want to read three pages before finding out.
CREAC (Conclusion, Rule, Explanation, Application, Conclusion) adds an Explanation section between the Rule and Application. The Explanation illustrates how courts have applied the rule in past cases, giving the reader concrete context before you apply the rule to your own facts. CREAC is useful when the rule is abstract and the reader needs to see it in action before your analysis will land.
Which framework you use depends on your professor’s preference in law school or your firm’s conventions in practice. The analytical thinking underneath is identical. Once you can write a strong IRAC, adapting to CRAC or CREAC is a matter of rearranging sections and, for CREAC, adding case illustrations before the Application.