Academic English revision

Your Issue Statement Is Hiding Your Bad Logic

Clarity in legal writing isn’t decoration — it’s the logical skeleton forced into view. Vague issue statements are the most expensive form of laziness.

It’s 2 AM. You’ve rewritten the issue statement three times. Your professor left one word in the margin: “unclear.” You want to scream, because you *did* write it plainly. The problem isn’t your English. It’s that your logic never landed. An issue statement is not a rhetoric exercise — it’s the question stem for a judgment call. It must let the reader see, instantly, what is actually in dispute. Most students write background instead of controversy.

The biggest trap: turning the issue statement into a fact summary. Look at this classic failure: ❌ “The memo addresses the defendant’s claim that the contract was breached due to supply delays.” This tells you what the defendant *said*, not what legal element is in play. The reader still doesn’t know if you’re analyzing breach liability or force majeure excuse. Fix it: ✅ “Whether supply delays constitute a valid force majeure defense under the UCC, thereby excusing breach.” See the difference? One reports speech. The other names the legal test.

The second trap is more subtle: you think longer sentences sound smarter. ❌ “The issue involves whether the plaintiff can recover damages for the tort of negligence given that the defendant acted reasonably under the circumstances at the time of the incident.” Three clauses deep, and by the end, the reader forgets who the subject was. ✅ “Can a plaintiff recover tort damages where the defendant acted reasonably, if reasonable conduct still breached the duty of care?” Shorter. But now the real tension — reasonableness vs. duty breach — is exposed. Clarity isn’t built with adjectives. It’s built by exposing the logical frame.

The third trap is where AI drafts go to die. You ask an LLM for an issue statement and it hands you: ❌ “This memo examines the legal implications of recent regulatory changes on corporate liability.” Which regulation? What kind of liability? “Implications” is a catch-all word — it means everything, therefore nothing. ✅ “Does the 2024 ESG disclosure mandate create direct statutory liability for board members under Delaware law?” Specific statute. Specific actor. Specific jurisdiction. That’s what a lawyer writes, not a summarizer.

Here’s the counterintuitive part: the *simpler* your issue statement, the more your professor trusts you. Not simple vocabulary — precise terms + narrow dispute scope. Clarity in legal writing comes from constraint, not richness. Writing “negligence” is clearer than “careless conduct,” because negligence has defined elements. Citing “UCC §2-601” is clearer than “the relevant statute,” because it’s verifiable. Abstract advice is useless. Specificity to elements, case names, and statutory sections — that’s accuracy.

So what about AI drafts? My workflow is blunt: write your own version first, even if it’s ugly. Then ask three questions — What is the actual legal issue? Which statute or case governs? Can a reader restate my dispute in one sentence after reading it? If the answer to #3 is no, don’t submit that draft. *Then* I run it through easydue to check structure and term consistency, saving time for case research. The tool polishes expression; you carry the logic.

One line to tattoo on your brain: clarity is not politeness. It’s respect for the reader’s time and confidence in your own reasoning. If you make them guess what you’re arguing, you’re making them doubt whether you know what you’re doing. The issue statement is the spine of your memo. If it’s soft, everything else collapses — no matter how pretty the prose.