What structure should every legal argument follow?
Use CREAC: Conclusion, Rule, Rule Explanation, Application, Conclusion. It is IRAC with the missing piece restored. IRAC's weakness is that it lets you jump from an abstract rule straight to your facts, which produces conclusory writing. The Rule Explanation step forces you to show the reader how courts have actually operated the rule before you claim it produces a result here.
Lead with the conclusion. Legal readers are not reading for suspense; a judge or a supervising attorney wants the answer in the first sentence so she can evaluate everything that follows against it. Then state the rule at the level of generality that decides your case. Then explain the rule using two or three cases, drawing out the facts that mattered and the reasoning that connected those facts to the outcome. Then apply. Then conclude.
One CREAC per legal issue, and one issue per section. If your case turns on whether a contract was formed and, if so, whether it was breached, that is two complete CREACs under two headings—not one long blur. If an element is uncontested, say so in a sentence and move on; spend your words where the fight is.
How do you state the rule?
Start from the highest mandatory authority and work down. A statute or regulation controls if one exists; quote the operative language rather than paraphrasing it, because the words are the law. If the governing rule is judge-made, find the highest court in the controlling jurisdiction and quote its formulation. Only then move to lower courts, which typically supply the sub-rules and factors that do the real work.
Most of the time you will have to synthesize a rule rather than find one stated. Synthesis means reading a line of cases and articulating the principle that explains all of the outcomes, including the ones that came out the other way. If four cases found personal jurisdiction and two did not, your synthesized rule should predict all six results. A rule that only explains the cases you like is not a rule; it is advocacy disguised as a rule, and opposing counsel will dismantle it.
Distinguish mandatory from persuasive authority explicitly. A federal district court in Ohio is bound by the Sixth Circuit and the Supreme Court; a Ninth Circuit decision is persuasive only, and you should signal that with framing like "the Ninth Circuit has held" rather than presenting it as settled law. Never cite an unpublished disposition without checking the court's rule on citing them.
How do you explain a rule using cases?
Rule explanation is where you build the comparison set you will use in the Application section. For each illustrative case, give the reader the legally significant facts, the holding, and the court's reasoning—in that order, in two to four sentences. Legally significant means the facts the court relied on, not everything that happened. In Palsgraf v. Long Island Railroad Co., 162 N.E. 99 (N.Y. 1928), the significant fact is the distance and unforeseeability between the guard's act and the plaintiff, not that the package contained fireworks in newspaper.
Choose cases for their factual proximity to yours, not their fame. A published trial-level opinion with facts nearly identical to your client's will do more work in the Application section than a landmark decision announcing the standard in the abstract. You need the landmark for the rule; you need the close case for the comparison.
Include at least one case that came out the other way. You cannot argue that your facts fall on the plaintiff's side of the line unless the reader can see where the line is, and lines are drawn by contrasting outcomes.
How do you apply the law to your facts without being conclusory?
Application means comparison, not assertion. "The defendant's contacts with the forum were substantial" is a conclusion. "Like the defendant in Smith, who shipped 400 units annually into the state and maintained a resident sales agent, the defendant here shipped 380 units and employed a resident technician" is analysis. Name the case, name the fact from the case, name the parallel fact from yours, and state why the similarity matters under the rule you explained.
Track your own rule's architecture. If you told the reader the test has four factors, address four factors in the same order, under the same labels. If a factor cuts against you, address it in place rather than skipping it; the reader is keeping score, and a silent gap reads as a loss.
Use the record. In a brief, every factual assertion gets a citation to the appendix, deposition transcript, or declaration. In a memo, tie facts to the source you were given and flag what you do not know—"if the deposition confirms that the agent had authority, then"—because a supervisor needs to know which conclusions are contingent on unresolved facts.
How do you handle counterarguments and adverse authority?
Address the other side's best argument, not a weak version of it. State it fairly in one or two sentences, then answer it on the merits: distinguish the facts, show the case is from a non-controlling jurisdiction, show it has been narrowed by later decisions, or argue that the rule it announces does not reach your situation. Rebut, then stop—do not let the counterargument take over the section.
You may have an ethical obligation to disclose bad law. ABA Model Rule of Professional Conduct 3.3(a)(2) requires a lawyer to disclose to a tribunal legal authority in the controlling jurisdiction known to be directly adverse to the client's position when opposing counsel has not disclosed it. Beyond ethics, hiding a controlling case that the judge's clerk will find in ten minutes destroys your credibility for the rest of the brief.
Distinguish honestly. A distinction based on a fact the court did not care about is not a distinction. If the adverse case is genuinely on point and controlling, your argument has to be that the rule should be extended, limited, or that the case is factually inapposite in a way that matters to the rule's purpose—not that the plaintiff there had a different job title.
What changes when the argument is persuasive rather than predictive?
An office memo predicts; a brief persuades. In a memo you give an honest answer even when it is bad news, and you quantify your confidence. In a brief you argue for one outcome. The analytical skeleton is identical—the differences are framing, emphasis, and structure of presentation.
In a brief, convert headings into full-sentence assertions. "Personal Jurisdiction" becomes "The Court lacks personal jurisdiction because Defendant's only contact with Nevada was a single unsolicited email." A judge who reads only your table of contents should be able to reconstruct your argument. Order your arguments by strength, not by the order the elements appear in the statute, unless a threshold issue like jurisdiction or standard of review must come first.
State the standard of review early and use it. Whether the court reviews de novo, for abuse of discretion, or for clear error often decides appeals before anyone reaches the merits. Check the applicable procedural and formatting rules: Fed. R. App. P. 28 sets required brief contents, Fed. R. App. P. 32 sets type-volume limits (13,000 words for a principal brief, 6,500 for a reply), and local circuit and district rules add requirements on top. Length and formatting rules vary by court; verify before you draft, not after.
How should you cite, and how should you edit?
Cite in citation sentences after the proposition they support, with a pincite to the page where the proposition appears—a full-case cite with no pincite tells the reader you did not read the case. The Bluebook's Bluepages (the blue-tabbed front section) govern court documents and legal memoranda; the white pages govern law review footnotes and use different typeface conventions. Learn Rule 10 for cases, Rule 12 for statutes, Rule 1.2 for introductory signals, Rule 1.4 for ordering authorities within a citation, Rule 4.1 for "id.", and Rule 5 for quotations and alterations. Some schools and jurisdictions use the ALWD Guide or a state-specific style manual instead; check your syllabus and, in practice, the local rules.
Edit in passes rather than all at once. First pass: is there a complete CREAC for each issue, in the right order? Second pass: does every application paragraph contain a case comparison rather than a bare assertion? Third pass: sentence-level—cut nominalizations ("made a determination" to "determined"), put the actor in the subject slot, and keep the subject and verb close together. Fourth pass: citations and quotations, checked against the source, not against your notes.
Read the argument aloud. Sentences you stumble over are sentences the reader will stumble over, and paragraphs that sound like assertion when spoken are conclusory on the page.