To write a law school exam, spot every legal issue raised by the facts, then for each issue apply IRAC: state the Issue, lay out the Rule, apply the Rule to the specific facts (this is where the points live), and reach a Conclusion. The exam rewards issue-spotting and fact-driven analysis of both sides — not memorized rule statements or a confident single answer. The student who argues the close calls both ways and ties every rule to a specific fact beats the student who writes a flawless rule paragraph and stops.

This is the single hardest adjustment in 1L, and nobody tells you until it's too late: the skills that got you A's in college — smooth prose, a strong thesis, confident conclusions — are actively worse than useless here. A law school exam is not an essay. It's a machine that scores whether you found the hidden issues and whether you argued them like a lawyer. This guide walks you through exactly how that machine works and how to feed it.

What is a law school exam actually testing?

Almost every 1L final is an issue-spotter: a long, fact-dense hypothetical ("Alice sells Bob a horse; Bob's neighbor's fence collapses; a bystander is injured...") followed by a call — "Discuss the rights and liabilities of the parties" or "Advise Bob." The professor has deliberately packed the facts with a dozen or more triggerable legal issues. Your job is to find them all and analyze each one competently.

Understand what that means for grading. Professors grade against a rubric of issues, often with points assigned per issue. You do not get points for knowing the law in the abstract. You get a point when you (1) recognize that a fact triggers a legal issue, (2) state the governing rule, and (3) apply that rule to the fact. Miss the issue and the perfect rule statement earns nothing, because it's answering a question the professor didn't ask.

This reframes everything. The exam is not "how much do I know?" It's "how many of the professor's hidden issues can I find and process in three hours?" Depth matters, but breadth of spotting is usually where the biggest point swings live — a student who spots ten issues and analyzes each adequately routinely beats one who spots five and writes beautifully on each.

The core method: IRAC (and its cousins)

IRAC is the skeleton of every answer. For each issue you spot, you write a self-contained block:

I — Issue

State the precise legal question in one sentence. Not "Is there a contract?" but "Whether Bob's emailed reply constituted acceptance when it added a new delivery term." A sharp issue statement signals to the grader that you know exactly what fact triggered this analysis. It also keeps you honest — if you can't frame the issue crisply, you don't yet understand it.

R — Rule

State the governing rule and, critically, its elements or sub-parts. If negligence is at issue, the rule is duty, breach, causation (actual and proximate), and damages. State the rule tightly — this is not where the points are, so don't pad it. But do include the sub-rules you'll need, and where the rule is genuinely unsettled or split (majority vs. minority approach, Restatement vs. common law), name the split. Professors love issues where the rule itself is contested, because it lets you argue.

A — Application (the heart of the grade)

This is where 70% of your points come from and where most students go wrong. Application means taking each element of the rule and connecting it to a specific fact from the hypothetical, using the word "because." Weak: "Bob probably breached his duty." Strong: "Bob likely breached his duty of reasonable care because he left the gate unlatched despite knowing the horse had escaped twice before, which a reasonable owner would have secured." See how the second version drags a specific fact (the two prior escapes, the unlatched gate) into a specific element (breach of the reasonable-care standard)?

The tell of a great answer is that it is impossible to imagine it being written for any other fact pattern, because it's welded to these exact facts. The tell of a bad answer is that it reads like a study outline copied onto the page.

C — Conclusion

State a one-line answer. "Bob is likely liable for negligence." Here's the secret: the conclusion is almost worthless to your grade. Professors care how you reasoned, not where you landed. On a genuinely close issue, either conclusion earns full marks if the analysis is sound. So conclude quickly and move on — don't agonize.

A note on the variants: CREAC (Conclusion, Rule, Explanation, Application, Conclusion) is used mostly in legal writing memos and briefs, where you lead with the answer. On timed exams, IRAC is faster and cleaner. Some professors prefer CRAC or teach their own acronym — use whatever your professor uses, but the underlying move is always the same: rule, then fact-to-rule application.

The step-by-step exam-day method

1. Read the call of the question FIRST. Before you read the fact pattern, read what you're actually being asked. "Discuss all torts claims" tells you to filter every fact for tort triggers and ignore contract issues. Reading the call first turns your first read of the facts into active issue-hunting instead of passive absorption.
2. Budget your time by points. If Question 1 is worth 60 points and Question 2 is worth 40, and you have 180 minutes, you spend roughly 108 minutes on Question 1. Write the allocation at the top of your scratch paper and obey it ruthlessly. The most common self-inflicted disaster is spending 90 minutes perfecting one issue and leaving a whole question blank.
3. Read the fact pattern twice. First read: get the story. Second read: annotate. Every proper noun, every date, every stated mental state ("Bob knew," "Alice intended") and every seemingly odd or gratuitous detail is a planted issue. Professors don't waste words — if they tell you the buyer was seventeen, capacity is on the table. If a fact seems weird, it's a trigger.
4. Outline before you write. Spend 15–20% of your time making a bare-bones issue list in the order you'll write them. This prevents the panic-writing spiral and ensures you spot everything before you start burning time on prose.
5. Write in tight IRAC blocks with headers. Use a heading or bold phrase for each issue ("Negligence — Duty and Breach"). This makes it trivial for a tired grader to find and check off your issues against the rubric. Never write one flowing essay; write a stack of discrete, labeled analyses.
6. Argue both sides on close calls. When the facts genuinely cut both ways, say so: "A court could find X because [fact], but Bob will argue Y because [other fact]; the stronger argument is X because..." This is the single highest-value move on a hard issue. The professor built the ambiguity on purpose and is waiting to reward the student who sees both edges of it.
7. When in doubt, spot and move. If you're running out of time, a quick paragraph hitting a real issue is worth far more than a polished paragraph on an issue you already covered. Breadth over depth when the clock is red.

A worked example

Fact fragment: "Dan, angry, threw a rock at Victor intending to scare him. The rock missed Victor but struck Paula, a bystander Dan hadn't noticed, breaking her nose."

A bad answer: "Dan committed a tort. Battery is intentional harmful contact. Dan is liable to Paula."

A strong answer: "Issue: Battery against Paula (transferred intent). Whether Dan is liable for battery to Paula when he intended only to frighten Victor. Rule: Battery requires an intentional act causing harmful or offensive contact. Intent can be satisfied by the doctrine of transferred intent, under which intent to commit one intentional tort (assault) against one person transfers to the completed tort (battery) against a different, unintended victim. Application: Dan threw the rock intending to scare Victor, satisfying the intent for assault against Victor. Because Dan intended an assault and the rock instead caused harmful contact with Paula, transferred intent supplies the intent element for battery against Paula — even though Dan never saw her, since transferred intent does not require intent as to the actual victim. The contact was plainly harmful, breaking her nose. Conclusion: Dan is liable to Paula for battery via transferred intent."

Notice the strong answer never left the facts: "threw the rock," "intending to scare Victor," "never saw her," "breaking her nose" each get pinned to an element. That's the whole game.

The mistakes 1Ls make (and how the grade dies)

• Rule-dumping. Writing everything you memorized about a doctrine without applying it. This feels productive and earns almost nothing. The rule is scaffolding; the application is the building.
• Reaching a firm conclusion and stopping. Students trained to write persuasive essays pick a side and defend it, ignoring the counterargument. On a law exam that leaves half the available points on the table.
• Missing issues by reading passively. Reading the facts like a novel instead of hunting for triggers. Every odd fact is a planted flag.
• Blowing the time budget. Over-investing in the first issue and leaving questions blank. A blank question is a zero no matter how brilliant your first answer was.
• Writing for a reader who already knows the answer. Assuming the professor will "understand what you meant." They grade what's on the page, mechanically, against a checklist. Spell out every step, even the ones that feel obvious.
• Ignoring the call. Analyzing contract issues on a question that asked only about torts. All that work scores zero.

How to prepare so exam day works

Exam skill is built in October, not December. Three things matter most. First, build a usable outline — not a treatise, but a compressed, rule-forward document you could actually reference under pressure (many exams are open-book, and even closed-book, the act of compressing is the learning). Second, take practice exams under timed conditions. Nearly every professor keeps old exams on file; the single highest-return prep activity is writing full timed answers to your own professor's past questions, then comparing to the model answers or sample answers. Reading law is not the same skill as writing it fast, and you don't want the first time you do it to be the real thing. Third, build issue-checklists for each subject — a flow of "if you see these facts, consider these issues" — so that on exam day your spotting is a habit, not an improvisation.

When the skill matters — and when to adapt it

IRAC and issue-spotting are the backbone of nearly every doctrinal 1L exam (Torts, Contracts, Property, Criminal Law, Civil Procedure, Con Law). But watch for variations. Some professors give policy questions ("Should the reasonable-person standard be objective?") where there's no fact pattern to IRAC — those want a structured argument citing competing values and cases, not IRAC. Some give short-answer or multiple-choice sections that test rule recall directly. And some professors explicitly warn against rigid IRAC and want more integrated analysis. Always read the professor's own exam instructions and past exams; they tell you what this specific grader rewards. IRAC is the default, not a law of nature — but on a standard 1L issue-spotter, it's how you win.