What is a rule proof, and how is it different from the rule statement?
The rule statement tells the reader what the law is. The rule proof shows the reader that you did not make it up. It is the second component of CREAC (Conclusion, Rule, Explanation/Proof, Application, Conclusion) and the "P" in CRuPAC. Different schools use different labels — rule explanation, rule illustration, rule proof, case discussion — and some professors treat the rule statement and rule proof as a single "R" block. The label varies; the function does not.
The defining constraint is that a rule proof is entirely about the authorities. It is written in past tense, it never names your client, and it never argues that your facts resemble anything. Every comparison to your client belongs in the application. If a reader can tell from the rule proof which side you represent, you have leaked application material upward.
The second defining constraint is that a rule proof is not a book report. You are not summarizing cases; you are proving a specific proposition. Each illustration exists because it demonstrates something the reader needs before your application will make sense.
What is the basic architecture?
A rule proof moves from abstract to concrete. Start with the general rule or the element you are proving. Then narrow to a synthesized sub-principle — the pattern you extracted from reading the cases together. Then illustrate that principle with facts from one or two decisions. If the element has two sides (what satisfies it and what does not), give the reader both.
Written out, the sequence looks like this:
- Rule statement for the element at issue, cited to the controlling authority.
- Synthesized principle: the factor, threshold, or dividing line the cases reveal.
- Illustration of a case satisfying the principle: trigger sentence, key facts, holding, court's reasoning.
- Contrasting illustration, if the dividing line matters to your analysis.
- Optional closing synthesis sentence tying the illustrations back to the principle.
How do you write a single case illustration?
Use four moves, in order. First, a trigger or hook sentence stating why the case is here — the proposition it proves — not "In Wardlow, the defendant was arrested." Second, the legally relevant facts, and only those; a fact belongs in the illustration only if the court relied on it or if you will analogize to it later. Third, the holding on that issue. Fourth, the court's reasoning — the "because" that makes the case usable.
For example, on reasonable suspicion under Terry v. Ohio, 392 U.S. 1 (1968): "Behavior that is innocent in isolation can support reasonable suspicion when it occurs in a suggestive context. In Illinois v. Wardlow, 528 U.S. 119 (2000), officers patrolling an area known for heavy narcotics trafficking saw the defendant holding an opaque bag; he looked at the officers and fled. Id. at 121-22. The Court held the stop reasonable. Id. at 124-25. Although flight alone is not proof of wrongdoing, the Court reasoned that headlong flight is the consummate act of evasion, and that officers may consider the surrounding neighborhood in evaluating an otherwise ambiguous act. Id."
Notice what is absent: the procedural history, the parties' arguments, the dissent, the remedy, and any sentence beginning "Here." Notice also the pin cites. Every factual assertion about a case gets a pinpoint page. Use Id. under Bluebook Rule 4.1 when the immediately preceding cite is the same authority, and a short form under Rule 10.9 (e.g., Wardlow, 528 U.S. at 124) once another authority intervenes.
When should you use a parenthetical instead of a full illustration?
Full illustrations are expensive — often 80 to 120 words each. Spend them only on cases you will actually analogize to or distinguish in the application. For supporting points, background rules, and the fifth case that says the same thing as the first four, use an explanatory parenthetical under Bluebook Rule 1.5.
Parentheticals normally begin with a present participle and do not end with a period inside the parentheses: (holding that an anonymous tip describing a suspect's location and clothing, without more, does not establish reasonable suspicion). A well-drafted parenthetical carries facts, not just conclusions. "(finding no reasonable suspicion)" tells the reader nothing usable; "(finding no reasonable suspicion where the tip predicted no future conduct and the caller was never identified)" does.
A reliable rule of thumb: if the case will appear in your application, illustrate it in full; if it will not, parenthetical it or drop it. A string cite of six cases you never mention again is padding, and graders read it that way.
How do you synthesize multiple cases instead of listing them?
Synthesis means stating the principle first and using the cases as evidence, rather than marching through them chronologically and hoping the reader spots the pattern. Read your cases and ask: what fact drove the different outcomes? That answer becomes your topic sentence, and the cases become proof.
Contrast is the most efficient synthesis tool. Pairing a case that satisfied the element with one that did not gives the reader a range and gives you two analogies in your application. Compare the tip in Florida v. J.L., 529 U.S. 266 (2000), which the Court held insufficient because it lacked indicia of reliability, with the corroborated, context-rich facts in Wardlow. Once you have both, you can tell the reader where the line sits.
Order authority by weight, not by the order you happened to read it. Binding authority precedes persuasive authority; higher courts precede lower ones; within the same court, more recent decisions generally precede older ones. Bluebook Rule 1.4 governs ordering within a citation sentence, and the same logic should govern your prose. If you lead with an out-of-circuit district court opinion while a controlling appellate case sits in footnote territory, you have signaled that you do not understand the hierarchy.
How long should a rule proof be, and how do you know it is finished?
There is no fixed ratio, but in a typical office memo the rule proof for a contested element runs roughly as long as the application for that element, sometimes slightly longer. Uncontested elements get one sentence and a citation. Do not proof a rule nobody disputes.
Use this completeness test: cover the application section and read only the rule proof. Every legal standard, factor, and case fact you rely on in the application must already appear there. Conversely, cover the rule proof and read only the application — if the application introduces a case fact for the first time, or a court's reasoning the reader has never seen, your proof is incomplete. Nothing new may appear in the application except your client's facts.
The reverse error is over-proving. If an illustration contains facts you never use, cut them. If a case supports a proposition no one contests, downgrade it to a parenthetical or a bare cite.
What mistakes cost the most points?
Graders see the same failures every semester. Fixing these four moves most memos from average to strong.
- Chronological case-by-case narration with no synthesized topic sentence — the reader has to do your analytical work.
- Including procedural history, dissents, and unrelated holdings, which buries the facts that matter.
- Leaking the client into the proof ("like our client, the defendant fled") — save it for the application.
- Missing or inaccurate pin cites; a case fact without a pinpoint page is unverifiable and, in practice, a credibility problem.
- Ignoring adverse authority; in a memo you owe your reader the cases that cut against you, and in a brief Model Rule 3.3(a)(2) requires disclosure of directly adverse controlling authority not disclosed by opposing counsel.