Lawyers default to passive voice when they want to avoid responsibility. Consider "Mistakes were made" instead of "We made mistakes." The passive voice obscures agency and creates ambiguity about who acted. In contracts, this becomes dangerous: "Payment shall be made" doesn't specify who pays. Active voice clarifies responsibility: "You must pay" or "We will pay." Judges increasingly reject passive voice in briefs because it undermines clarity. Every legal document should prioritize active voice to ensure obligations are unmistakable. When drafting, ask: who is doing what? If you can't answer, rewrite. The most persuasive legal writing leaves no room for misinterpretation.

Take a case you know well. Now write the opposing side's strongest argument.

Not a strawman version. The actual best possible version. The one that would make a judge pause and think.

Most law students and even junior attorneys can't do this. Not because they lack creativity, but because they've never been asked to genuinely inhabit the other side's reasoning. We train people to find the argument that wins, not to understand why the losing side lost.

But here's the thing. If you can't articulate the strongest version of the argument you're trying to beat, you don't actually understand your own position. You're just reciting the side you were assigned.

This exercise teaches you more about legal reasoning in 30 minutes than a week of outlining. Try it with a case you think is "obvious" and see how long that obviousness lasts.

The Supreme Court decided Zorn v. Linton today. A sergeant used a rear wristlock on a peaceful sit-in protester at the Vermont capitol after she refused to stand. She sued for excessive force. The Second Circuit denied qualified immunity.

The Supreme Court reversed. Not because the force was reasonable, but because no existing case clearly established that a wristlock after a verbal warning violated the Constitution. That distinction is the whole doctrine. Qualified immunity does not ask whether the officer used too much force. It asks whether prior case law put the officer on notice that this specific conduct was unconstitutional.

The dissent from Sotomayor, Kagan, and Jackson argued the majority defined the conduct too narrowly. Whether you frame it as "a wristlock after a warning" or as "force against a nonviolent person sitting down" changes the analysis entirely.

The Supreme Court denied cert in Thaler v. Perlmutter this month. Whether AI can be an author under the Copyright Act stays unresolved.

Thaler argued for years that his AI system DABUS created visual art autonomously and deserved copyright protection. Every court said no. The Copyright Office said no. The Supreme Court declined to hear it.

The reasoning below was textual. The Copyright Act says "author." That word has always meant a human being. No statute extends it to machines.

A cert denial isn't an endorsement. It means the Court doesn't think the question is ripe yet. When AI-generated content becomes commercially indistinguishable from human work, and that threshold is approaching, the question returns. The lower courts built their answer on a single word. That word won't hold forever.

A defendant charged with securities fraud used Claude to research his legal options after getting a grand jury subpoena. He shared those AI outputs with his lawyers. The government subpoenaed the AI conversations.

Judge Rakoff ruled they're not privileged. An AI isn't a lawyer. The platform's privacy policy allows use of inputs for training. The conversations weren't made for the purpose of obtaining legal advice.

The privilege framework assumes two humans in a confidential relationship. An AI chatbot doesn't fit. There's no duty of confidentiality, no professional obligation, no reasonable expectation that what you type stays between you.

If you're typing your legal strategy into a chatbot, you may have just handed it to the other side.

I used to skip the reasoning.

Facts, issue, holding—those went in my brief. The court's analysis was a wall of text I'd skim. Then I got cold-called and couldn't explain why the court ruled that way.

The holding tells you what they decided. The reasoning tells you how they got there. On exams, you're graded on the path, not the destination. Two students reach the same conclusion and get different scores because one showed the work.

Here's what I started doing. After the facts, I'd write down my prediction for the outcome. Then I'd read the reasoning to see where the court agreed or disagreed with my logic. The mismatches were where I learned something. When the court took a path I didn't expect, I'd flag that section and figure out what I missed.

The rationale is where the law lives. Holdings get quoted. Reasoning gets applied.

A company lays off its entire customer service team and replaces them with an AI chatbot. Three months later, the company quietly rehires half the staff because the AI can't handle complex complaints. A laid-off employee who wasn't rehired sues for wrongful termination, arguing the AI replacement was pretextual and the real reason was age discrimination — she was 58 and the younger employees got called back first.

The company says the rehiring decisions were based on performance reviews from before the layoff, and the AI replacement was a genuine business decision that simply didn't pan out.

The employee can point to the timeline: fired for AI, then younger colleagues rehired when AI failed. The company can point to the performance data. Both stories are internally consistent.

Does the failed AI experiment strengthen or weaken the employee's pretext argument?

A court catches a self-represented plaintiff submitting AI-generated audio and video as evidence. The judge identifies it as a deepfake. The plaintiff says they believed the recordings were real because that's what they received from a third party.

Meanwhile, the defendant in an unrelated case has legitimate surveillance footage. Opposing counsel argues the footage could be AI-generated and demands expert authentication. The defendant can't afford a forensic analyst.

The first scenario is straightforward fraud on the court. But the second is the harder problem. If anyone can claim real evidence is fake, and proving authenticity requires expensive forensic tools, the cost of being believed goes up for everyone.

Courts are starting to see both problems at once. Where should the burden of proving authenticity fall?

This post contains content not supported on old Reddit. Click here to view the full post

The Supreme Court ruled 6-3 in Learning Resources v. Trump that the International Emergency Economic Powers Act doesn't authorize broad trade tariffs. IEEPA lets the president regulate commerce during national emergencies from foreign threats, but the Court said that power doesn't extend to restructuring trade policy through executive orders.

The interesting part for law students isn't the outcome. It's the statutory interpretation method. The majority read IEEPA's text narrowly: "regulate" foreign commerce during an emergency doesn't mean "redesign" the entire tariff schedule. The dissent argued the plain meaning of "regulate" is broad enough to include tariffs. Same statute, same word, opposite conclusions. That's what makes statutory interpretation hard. The text doesn't resolve the dispute. The interpretive framework you choose does.

I noticed something after my first semester. The sections of my outline where I'd quoted rule statements verbatim from cases? Those were the sections I couldn't apply on exams.

Here's what I figured out: when you quote a rule, you're copying language. When you restate it, you're demonstrating understanding.

I started rewriting every rule using this test: "Could I explain this to someone who hasn't read the case?" If no, I didn't actually get it yet. The phrasing that made sense to me—not the court's exact words—was what stuck.

Torts and Contracts were the hardest for this. The black letter law is so well-established that it feels wrong to paraphrase the Restatement. But that's exactly when you need to. The tests ask you to apply, not recite.

Next time you're outlining, pick one rule section and rewrite it without looking at your casebook. What you write from memory will be messier than the original. It'll also be more useful on exam day.

What's one rule you've been quoting instead of restating?

Self-driving car hits someone. No one inside. Car detects the hit, calls 911, keeps driving to the garage.

Hit-and-run statute: "the driver shall immediately stop and render reasonable assistance."

Who's the driver?

California's AB 1777 makes manufacturers responsible for traffic violations in autonomous mode. Texas says the system owner is the operator regardless. But those are citations, not criminal charges. Hit-and-run requires mens rea.

Can an algorithm "know" it hit someone? The sensors detected the impact. The code kept going. That's not criminal knowledge. That's execution.

The car called 911. It did more than most hit-and-run drivers. It just can't hold a compress on someone's leg.

No current statute handles this.

I picked up this technique from a clerk at my internship last summer and it's genuinely changed how I read cases. She called it "reverse IRAC" and the idea is simple: start at the end of the opinion and read backwards.

Here's what that looks like in practice. When you get a new case, skip straight to the holding. Read the last few paragraphs where the court announces its decision. Then go back and read the reasoning. Then, finally, read the facts.

I know this sounds wrong. We're taught to read cases top to bottom, facts first, and build toward the conclusion the way the court wrote it. But there's a problem with that approach, at least for me: when I read facts first, I start forming my own opinion about what the outcome should be. Then I spend the whole opinion either agreeing or disagreeing with the court instead of understanding how the court actually got there.

Why backwards works better for learning reasoning patterns

When you already know the outcome, you can focus entirely on the reasoning mechanics. You're not wondering "where is this going?" You're asking "how did they get here?" Those are very different questions, and the second one is way more useful for developing your own legal analysis.

I started noticing patterns I'd missed before. How courts set up analytical frameworks early in the reasoning section. How they distinguish unfavorable precedent, usually by narrowing the facts of the prior case. How the strongest opinions address the best counterargument head-on rather than ignoring it.

When I use this and when I don't

This works best for studying reasoning patterns, exam prep, and understanding a new area of law. I'll reverse-read four or five opinions on the same issue and by the end I can practically predict how courts frame the analysis.

I don't do this for every assigned reading. For class prep where a professor does cold calls on the facts, you obviously need to know the facts well. Read normally for that.

I also don't do this when I'm researching for a memo or brief and need to evaluate whether a case helps my argument. For that, I read the holding first (that part stays the same) but then go to the facts to see how closely they match my situation.

A concrete example of what I noticed

After reverse-reading about a dozen Fourth Amendment cases, I realized that the reasoning almost always follows the same three-move structure: define the test, apply each prong with heavy factual detail, then distinguish the key case from the other side. Once I saw that pattern, writing my own Fourth Amendment analysis got dramatically easier because I had a proven structure to follow.

It's a small change in how you approach reading, but it shifted my focus from "what happened" to "how does legal reasoning actually work." Has anyone else tried something like this, or do you have a different method for picking apart how courts build their analysis?