You're staring at a blank document. That's why maybe you wrote it down. The cursor blinks. Somewhere in your notes, a professor or supervisor mentioned CREAC. Maybe you nodded. But now you're wondering — what does it actually look like when the rubber meets the road?
Here's the thing: CREAC isn't a magic formula. It's a scaffold. And like any scaffold, it only works if you know where to put the weight Easy to understand, harder to ignore..
What Is CREAC
CREAC stands for Conclusion, Rule, Explanation, Application, Conclusion. It's the dominant organizational framework for legal analysis in the United States — used in memos, briefs, law school exams, and pretty much any document where a lawyer needs to show their work Easy to understand, harder to ignore. Simple as that..
Some people call it IRAC. Here's the thing — others prefer CRAC or CREAC. The difference is mostly about emphasis. That's why iRAC leads with the Issue. Consider this: cREAC leads with the Conclusion. That shift matters more than it sounds.
The Five Letters Broken Down
Conclusion — Your answer. Up front. One sentence. "The court will likely find that the defendant breached the duty of care."
Rule — The legal standard. Statute, case law, regulation. The authority your analysis rests on. Not a summary. The actual rule It's one of those things that adds up..
Explanation — Where the rule comes from and how it works. Case illustrations. Policy rationale. Statutory history. This is where you prove you understand the rule, not just that you found it.
Application — The match-up. Your facts against the rule. This is the longest section. Where the real lawyering happens.
Conclusion — Yes, again. A restatement. But now it's earned. The reader has walked the path with you.
Why It Matters / Why People Care
Legal readers are impatient. Judges, partners, clerks — they skim. Also, they want the bottom line before they invest attention. CREAC gives it to them The details matter here..
But there's a deeper reason. Worth adding: cREAC forces you to separate what the law is from what the facts are from how they interact. It's not persuasion through narrative arc. Legal analysis isn't storytelling. It's structured reasoning. Most bad legal writing muddles those three It's one of those things that adds up. That alone is useful..
I've seen associates spend three paragraphs explaining a case before telling me what rule it stands for. I've seen students apply a rule they never stated. CREAC prevents both.
The Real-World Stakes
A memo that buries the conclusion gets ignored. A brief that skips the explanation looks lazy. An exam answer that jumps straight to application without stating the rule gets partial credit at best.
And here's what nobody tells you in 1L: clients pay for clarity. In practice, they don't pay for you to "figure it out on the page. " CREAC is how you deliver the product they're buying Worth keeping that in mind..
How It Works (or How to Do It)
Let's walk through each component with the granularity that actually helps And that's really what it comes down to..
Conclusion — The Lead
Write it first. Delete it. Practically speaking, rewrite it. Make it one declarative sentence. Plus, no "it appears that. No hedging. " No "arguably.
Bad: "It seems possible that the plaintiff might have a claim for negligence."
Better: "The plaintiff has a viable negligence claim."
Best: "The defendant breached the duty of care owed to the plaintiff by failing to repair the broken stair railing within a reasonable time after notice."
Notice the specificity. The best version names the duty, the breach, and the key fact. That's not a conclusion — that's a roadmap.
Pro tip: If you can't write the lead conclusion in one sentence, you don't understand the problem well enough yet. Go back to the facts Easy to understand, harder to ignore. Turns out it matters..
Rule — The Authority
State the rule. Then cite it. That's the order.
"The elements of negligence under New York law are: (1) a duty of care owed by the defendant to the plaintiff, (2) breach of that duty, (3) proximate cause, and (4) damages. Practically speaking, co. Long Island R.Here's the thing — *, 248 N. Here's the thing — *Palsgraf v. Also, y. That's why r. 339 (1928).
Don't write: "In Palsgraf, the court held that...Consider this: " That's explanation territory. The rule section is just the rule.
If the rule has sub-elements or factors, list them. Now, number them. Make them scannable.
Explanation — The Architecture
Basically where most writers either go too thin or too thick.
Too thin: "Palsgraf established the zone of danger test."
Too thick: A three-page case summary with procedural history nobody asked for.
Right: "Palsgraf established that duty exists only where the plaintiff falls within the foreseeable zone of danger created by the defendant's conduct. Felix Contracting Corp.D.*, 51 N.2d 241 (1st Dep't 1994)) and unforeseeable intervening acts (*Derdiarian v. Think about it: ' Subsequent cases have applied this principle to limit duty in cases involving indirect causation (Ventricelli v. Kinney Systems Rent A Car, 205 A.The court rejected liability for unforeseeable plaintiffs, reasoning that 'the risk reasonably to be perceived defines the duty to be obeyed.Y.2d 308 (1980)).
Three things happening here:
- The core principle from the landmark case
- The court's reasoning in its own words (short quote)
That's it. You're not teaching the case. You're teaching the rule through the case.
Application — The Match-Up
This is where you earn your keep. Sentence by sentence. Fact by fact.
Structure each paragraph around a single element or factor. Lead with the legal standard, then map the fact The details matter here..
"Here, the defendant owed the plaintiff a duty of care. Stout*, 38 N.Here's the thing — as a commercial landlord, the defendant had a non-delegable duty to maintain common areas in reasonably safe condition. 2d 607 (1976). *Putnam v. Y.The plaintiff was a tenant using the rear stairwell — a common area — when the railing gave way Simple as that..
Next paragraph, next element Small thing, real impact..
"The defendant breached that duty. That said, no temporary warning or barrier was installed. The repair was not completed until April 17 — 45 days later. The property manager received written notice of the loose railing on March 3. During that period, three other tenants reported the same issue. A reasonable landlord would have acted sooner or mitigated the hazard Surprisingly effective..
Notice: no legal conclusions masquerading as facts. Even so, "The defendant was negligent" is a conclusion. "The repair was not completed until April 17" is a fact. Keep them separate.
Counterarguments go here too. Address them. "The defendant will argue that 45 days is reasonable given contractor availability. On the flip side, the log shows the contractor was contacted only on March 28 — 25 days after notice.
Conclusion — The Echo
Restate the lead conclusion. But now it carries weight.
"For the foregoing reasons, the defendant breached the duty of care owed to the plaintiff."
Same words. Different impact. The reader has seen the machinery. They don't have to trust you — they can check your work Small thing, real impact. And it works..
Common Mistakes / What Most People Get Wrong
Mistake 1: Confusing Explanation with Application
Explanation talks about other cases. Application talks about your facts. That's why if you're discussing Palsgraf in your application section, you've drifted. Bring it back Worth knowing..
Mistake 2: The "Rule Dump"
Listing every case you found. Day to day, maybe two if there's a split. The rule section isn't an annotated bibliography. One binding case per proposition. That's it.
Mistake 3: Burying the Counterargument
Some writers hide the weak points in a footnote. In practice, or omit them entirely. Now, bad move. The reader will find them Worth keeping that in mind. Surprisingly effective..
Mistake 4: Over‑reliance on conclusory language.
It is tempting to sprinkle phrases like “clearly negligent” or “obviously foreseeable” throughout the application. Those statements are conclusions, not facts, and they undermine the analytical rigor the IRAC‑style format demands. Instead, let the factual record speak: describe the timing of inspections, the content of maintenance logs, or the plaintiff’s own testimony about the hazard. When the facts are laid out plainly, the legal conclusion follows naturally and is harder for an opponent to rebut But it adds up..
Mistake 5: Ignoring procedural posture and burden of proof.
Here's a good example: a duty‑of‑care analysis that survives a motion to dismiss may still falter at summary judgment if the defendant produces evidence of an intervening act. A rule may be sound, but its application changes depending on whether the case is at the pleading stage, summary judgment, or trial. Because of that, tailor the depth of your factual mapping to the stage: at pleading, focus on whether the complaint alleges each element; at summary judgment, marshal affidavits, deposition excerpts, and expert reports to show genuine disputes of material fact. Neglecting this nuance can turn a otherwise solid rule application into a hollow exercise.
Mistake 6: Forgetting to tie the rule back to the policy rationale.
When you apply the rule, briefly reference that policy undercurrent. Courts often articulate the “why” behind a duty — whether it is to promote safety in public spaces, to incentivize regular maintenance, or to protect vulnerable tenants. It does not replace the factual analysis, but it shows the reader that your conclusion aligns with the law’s underlying purpose, strengthening persuasive force especially when the facts are close.
Conclusion
By distilling the rule to its essential holding, illustrating it with a concise, binding precedent, and then meticulously mapping each element to the client’s facts — while confronting counterarguments head‑on — you transform a case citation into a living tool of advocacy. Avoid the pitfalls of conclusory shortcuts, procedural myopia, and rule‑dumping, and always let the policy behind the doctrine inform your analysis. When the reader can see the exact steps from rule to fact to conclusion, your argument carries the weight of demonstrable reasoning rather than mere assertion. That is how you teach the rule through the case — and win the motion.
