A CREAC example is the fastest way to see how the framework actually reads on the page: a one-sentence predicted conclusion, the governing rule, an explanation of how courts have applied that rule, an application of those precedents to the current facts, and a closing conclusion that restates the prediction. The worked example below uses a fictional shoplifting-detention scenario, and the sections that follow break down what each piece is doing and how to write your own.
A Full CREAC Example
The case names and facts here are invented to show the structure clearly. Read it through once as a finished piece of writing before looking at the breakdown.
Conclusion. A store owner likely did not commit false imprisonment by detaining a suspected shoplifter, because the detention fell within the merchant’s privilege.
Rule. Under the merchant’s privilege, a store owner may detain a person for a reasonable period if the owner has reasonable grounds to believe the person is shoplifting. The privilege requires three things: (1) a reasonable belief that theft occurred, (2) detention for a reasonable duration, and (3) detention conducted in a reasonable manner.
Explanation. In Smith v. Retailer, a store employee watched a customer slide a pair of sunglasses into her purse on the sales floor. The employee stopped the customer at the exit and held her in a back office for fifteen minutes until police arrived. The court held the detention was privileged, reasoning that the employee’s direct observation of concealment established reasonable grounds to suspect theft, and that fifteen minutes was a reasonable duration given the need to wait for law enforcement.
Application. Here, the store manager personally watched the customer hide a watch inside his jacket, a direct observation of concealment similar to the employee’s eyewitness account in Smith. If anything, the manager’s position is stronger: the ten-minute detention was five minutes shorter than the fifteen-minute period the Smith court found reasonable, and the manager used the time solely to wait for police rather than to interrogate or search the customer. The customer might argue the detention was unreasonable because no theft was ultimately confirmed, but the privilege does not require a completed theft, only a reasonable belief that one occurred. The manager’s direct visual observation of concealment satisfies that standard.
Conclusion. Because the manager had direct grounds to suspect shoplifting and kept the detention brief and non-coercive, the store owner is likely not liable for false imprisonment under the merchant’s privilege.
What Each Part of the Example Is Doing
The five components are separate for a reason. Each one sets up the next, and the analysis holds together only when the reader can follow that sequence.
The opening Conclusion answers the legal question in one sentence. It is not an issue statement, and it does not hedge. The reader learns immediately what position the writer is taking and the legal reason behind it. In the example, the sentence names both the predicted outcome (not liable) and the doctrine that produces it (merchant’s privilege).
The Rule is the legal test the reader will use to evaluate the facts. A good rule reads like a checklist. The example rule breaks the privilege into three numbered elements so the reader knows exactly what the Application will need to prove.
The Explanation is what distinguishes CREAC from simpler frameworks. It walks the reader through one or two prior cases that applied the same rule to similar facts. A strong explanation covers three things for each case: the relevant facts, what the court held, and the reasoning that connected the facts to the holding. The reasoning matters most, because it tells the reader what courts actually care about. The Smith paragraph above gives all three: what the employee saw, that the detention was privileged, and why the court thought fifteen minutes was reasonable.
The Application is where the argument lives or dies. It places the client’s facts next to the precedent facts and shows, element by element, why the rule is or is not met. Comparison words such as “similarly,” “unlike,” and “just as in” tell the reader that a deliberate analogy is being drawn rather than facts simply being restated. The example Application ties the ten-minute detention directly to the fifteen-minute detention in Smith, then addresses the strongest counter-argument (no theft was confirmed) rather than hoping the reader will not think of it.
The closing Conclusion restates the prediction, now carrying the weight of the analysis above. A sentence or two is enough. New arguments, new facts, or hedging language do not belong here.
How to Write Each Component Well
The Opening Conclusion
Write a single declarative sentence that names the legal standard and predicts whether it is met. Compare:
- Weak: “The issue is whether the store owner committed false imprisonment.”
- Strong: “The store owner likely did not commit false imprisonment because the detention fell within the merchant’s privilege.”
The weak version identifies a topic and takes no position. That is an issue statement, not a conclusion.
The Rule
State the rule in layers, broadest first. Statutes or foundational holdings come before the narrower judicial refinements that add detail. Paraphrase in plain terms and cite the source; do not paste raw statutory text. The goal is to give the reader a usable standard, not to prove you found the code section.
The Explanation
Reach for mandatory authority first, meaning decisions from courts that bind the tribunal where your case would be heard. Persuasive authority from other jurisdictions can supplement binding precedent but should not replace it.
When several cases support a narrow point, use parenthetical summaries after the citation rather than giving each case its own paragraph. For example: Jones v. Martin, 456 F.3d 789, 793 (7th Cir. 2003) (holding that a twenty-minute detention was reasonable where the store waited for police to arrive). Reserve full case illustrations for the one or two precedents most factually similar to your situation.
Do not ignore cases that cut against your position. Distinguish them on the facts, argue their reasoning does not apply, or acknowledge the tension and explain why the weight of authority still favors your client. Judges notice when a brief pretends unfavorable precedent does not exist.
The Application
Every factual statement in the Application should earn its place by linking to a rule element. A sentence like “The store manager held the customer for ten minutes” states a fact but performs no analysis. The analytical version connects that fact to the standard: “The store manager’s ten-minute detention was shorter than the twenty-minute detention courts have previously found reasonable, suggesting it satisfies the reasonable-time requirement.”
Anticipate the strongest opposing argument and address it before the reader raises it. State the counter-argument, explain why it falls short, and support the rebuttal with a factual or legal distinction from the Explanation.
The Final Conclusion
Mirror the opening. Restate the prediction, briefly identify the key reason the analysis supports it, and stop. If the Application was thorough, this sentence should feel almost inevitable.
How CREAC Differs From IRAC and CRAC
Three frameworks dominate legal writing courses. IRAC stands for Issue, Rule, Application, Conclusion. CRAC stands for Conclusion, Rule, Application, Conclusion. CREAC adds the Explanation between the Rule and the Application.
Two practical differences matter. IRAC opens with an issue statement, while CRAC and CREAC open with a predictive conclusion; opening with the conclusion tends to be more effective in persuasive writing because the reader immediately knows the position being argued. And CREAC structurally requires the writer to show how courts have applied the rule before analyzing the current facts. IRAC and CRAC allow that discussion but do not force it. The dedicated Explanation section is a guardrail that produces stronger analysis on complex issues, where the rule alone does not make the outcome obvious.
One structural rule applies across all three frameworks: each legal issue gets its own block. A memo that addresses whether a contract was formed and whether a party breached it needs two separate CREAC analyses, not one sprawling discussion.
Common Mistakes
Most CREAC errors cluster in the Application, and most of them are variations on the same problem: asserting rather than analyzing.
- Conclusory application. Stating that the facts “satisfy the rule” without showing how. Every factual assertion needs a connection to a specific rule element and, ideally, a comparison to the precedent in the Explanation.
- Listing facts without analysis. Reciting what happened is not the same as analyzing whether it matters legally. If a sentence describes a fact but does not link it to the rule, it belongs in a fact section.
- Skipping the Explanation. Without precedent, the Application has nothing to compare against, and the argument collapses into “here are the facts, and I think they meet the rule.”
- Blending the Rule and Explanation. New legal writers often mix the abstract rule with precedent discussion in a single paragraph. Keeping them separate forces clearer thinking: the Rule says what the law requires, and the Explanation shows what that looks like in practice.
- Ignoring counter-arguments. An analysis that only argues one direction reads as advocacy without rigor. Acknowledging and distinguishing the strongest opposing point makes the argument more credible.
If you cannot fill in the Explanation section for an issue, that is usually a sign the argument itself needs rethinking before the writing goes any further.