Rule Explanation Legal Writing Example

What Rule Explanation Legal Writing Actually Looks Like

Most law students get their first introduction to rule explanation legal writing during their second semester of legal writing, usually through a IRAC or CREAC memo. The rule statement comes first, the cases and policy that shape it come second, and then you apply it. That's the framework. But in practice, especially when you're writing for judges who have stacks of briefs on their desk and about twelve minutes to skim yours, the difference between a competent rule explanation and one that gets ignored usually comes down to how you handle the transition from the abstract rule to the concrete facts. Here's a straightforward example of what a solid rule explanation looks like in practice. Say you're drafting a memo about whether a non-compete clause is enforceable in a particular jurisdiction. The rule statement would read something like this: In this jurisdiction, non-compete agreements are enforceable only if they are reasonable in scope, duration, and geographic territory, and only if they protect a legitimate business interest of the employer. Courts will not enforce non-competes that function as general restraints on competition. The leading case on point is Martinez v. Pacific Solutions, 412 S.W.3d 891 (Tex. App. 2021), which held that a two-year territorial restriction spanning the entire state was unreasonable for a mid-level sales representative whose territory was limited to three counties. That's a functional rule explanation. It states the general rule, narrows it to the relevant jurisdiction, cites the controlling authority, and gives a concrete illustration from case law. The example from Martinez matters because it tells the reader exactly where the line is drawn. Without that case reference, the rule stays at the level of a platitude.

What I've noticed over the years is that most people underweight the explanation portion. They state the rule, cite one case, and move on to application. That approach works fine for a class assignment where the professor is checking whether you know the rule. It falls apart in actual litigation because the opposing counsel will immediately distinguish your single case and force you into a factual argument that the judge didn't need you to make. The explanation is where you neutralize those distinctions before they become problems.

How to Structure the Explanation Section Properly

The explanation section should do three things. It needs to state the black-letter rule. It needs to provide the doctrinal background through cases, statutes, or secondary authority that define the rule's boundaries. And it needs to address any competing interpretations or splits in authority that are relevant to your argument. I keep the sections roughly in that order because it mirrors how a judge would think through the issue. First, what does the rule say? Second, what has the law said about it? Third, are there any unresolved questions I need to acknowledge? I ran into a situation about four years ago where this structure mattered in a very specific way. I was working on a summary judgment motion involving an employment discrimination claim under a state statute that mirrored federal Title VII language but had one critical divergence. The state courts had interpreted the statute's notice requirement differently than federal courts interpret the analogous federal provision. My opponent filed a brief arguing that the federal standard should control, citing three federal circuit cases. I'd already covered the state-specific interpretation in my rule explanation by including a discussion of the leading state case that established the more plaintiff-friendly notice standard. Because I'd anchored the rule explanation in state authority from the start, my opponent's federal citations looked off-point rather than persuasive. The judge granted summary judgment based on my brief. If I had left the state cases for the application section instead of putting them in the explanation, the judge might have been swayed by the federal authority before reaching my factual arguments. The counter-intuitive part that most people miss is that a good rule explanation is often shorter than a thorough one. Beginners tend to pad the explanation with every case that mentions the rule, even cases that don't change how the rule applies to their facts. That creates noise. The best explanations I've written are the ones where I cut the second case, the third case, and the paragraph of secondary authority that sounded good but didn't actually add a limiting principle. You want the explanation to be just detailed enough that the application section feels inevitable, not justified.

Common Mistakes That Undermine Rule Explanation

The most common mistake is burying the rule inside a string cite. You'll see sentences like: A non-compete is enforceable if reasonable (see Smith v. Jones, 100 F.3d 200; Brown v. Davis, 205 F.3d 411; Wilson v. Edwards, 310 F.3d 555; Anderson v. Clark, 422 F.3d 789). That's not a rule explanation. That's a bibliography. Each of those cases probably involves a different factual context, and the reader has to work through all of them to figure out what the actual rule is. Put the rule in one clean sentence, then use the cases to support the boundaries of that rule, not to replace the rule itself. Another mistake is writing the rule explanation as if the reader has no context at all. Some writers treat every rule statement like it's the first time anyone has heard of the doctrine. That wastes space and makes your writing look unsure. If you're arguing a well-established proposition, you can state it concisely and move to the Nuanced boundary that matters for your case. If you're arguing something novel, then you invest more heavily in the doctrinal foundation. The amount of explanation you provide should match how contested the rule is, not how comfortable you feel explaining it. I also see a lot of writers conflate the rule statement with the conclusion. They'll write something like: The non-compete should be enforced because it's reasonable in scope and duration. That's not a rule statement. That's an argument disguised as a rule. A rule statement should be neutral and general. Whether the non-compete is reasonable belongs in the application section, where you tie the facts to the rule. Keep the two functions separate. Mixing them makes the writing harder to follow and gives the reader no clear standard to evaluate your application against.

When Rule Explanation Writing Breaks Down

This approach doesn't work well when the rule itself is unsettled. If there's no controlling authority and the courts are split, a traditional rule explanation becomes a catalog of disagreements rather than a clear statement of the law. In those situations, some writers switch to a problem-solving structure where they present the competing approaches and argue why one should prevail. That's a valid alternative, but it requires a different set of skills and a different organizational logic. You're no longer explaining a rule. You're evaluating competing interpretations. The transition isn't seamless, and if you try to force it into an IRAC framework, the analysis usually collapses. Statutory interpretation cases are another area where the standard rule explanation model struggles. Statutes don't always map cleanly onto the black-letter rule format because the text itself may be ambiguous, the legislative history may contradict the plain language, and the administrative agencies may have issued conflicting interpretations. When I'm dealing with a statutory issue, I often skip the traditional rule explanation and go straight to a text-first analysis: what does the statute say, what are the plausible readings, and which reading is supported by context and purpose. It's faster, it's more honest about the uncertainty, and it usually aligns better with how appellate courts actually decide these cases.

A Practical Workflow for Writing Rule Explanations

Here's what I actually do when I sit down to draft a rule explanation. I start by finding the controlling authority and reading it. Not skimming it, reading it. The rule statements in headnotes and restatements are useful for getting the general shape, but they're not reliable for the fine print. The actual cases tell you what the rule excludes, not just what it includes. Once I know the case, I write the rule statement in one sentence and then test it against the facts of my case. If the rule statement doesn't cover the key factual issue I'm facing, I go back and refine it. This iterative process usually takes ten to fifteen minutes and prevents me from writing a rule explanation that's technically correct but practically irrelevant. After the rule statement is locked in, I draft the explanation portion by pulling the specific holdings from the cases that define the rule's boundaries. I'm looking for cases that narrow the rule, cases that broaden it, and cases that create exceptions. I don't need every case. I need the cases that change the rule's shape. Then I write the application section, which should feel like a direct consequence of what came before it. If the application section requires new legal reasoning, that's a sign the explanation didn't do its job. The whole process, from finding the authority to drafting a complete rule explanation with application, typically takes me about forty-five minutes for a standard issue. For something more complex, like a multi-jurisdictional question or an area of law with significant uncertainty, it can take two to three hours. The time varies based on how much research is needed, not on how much writing I have to do. The writing itself is the fast part. The research is what eats your time.

If you're looking for a template to work from, there's no single downloadable document that covers all scenarios because the format shifts depending on the jurisdiction and the type of document you're drafting. What's consistent is the underlying logic: state the rule clearly, support it with authority that defines its boundaries, and apply it in a way that follows directly from the rule and the facts. Anything that strays from that structure tends to lose its persuasive force, no matter how well-researched it is.