How law school exams actually work.

Most law school exams are three to four hours long, open-book, and consist of one to three hypothetical fact patterns ('hypos') you've never seen before. The professor is not testing whether you memorized their slides or the casebook. They are testing whether you can spot legal issues in a novel set of facts and analyze them in writing using IRAC. The difference is significant: you can know every case assigned in the course and still fail an exam if you can't apply the rules to new facts.

Exams are graded on issue coverage, not word count. A student who spots six issues and analyzes three of them completely will often outscore a student who spots three issues and writes two pages on each. Issue spotting — the ability to read a fact pattern and quickly identify which legal doctrine each fact is designed to trigger — is the single most important exam skill built in law school. It is also the skill that practice alone develops. Reading about contracts does not teach you to spot a contract issue in a tort-heavy fact pattern the way that writing practice answers does.

The practical implication: exam preparation is not the same as class preparation. Briefing cases and following class discussion builds your understanding of the doctrine. Exam preparation is a separate phase — timed writing on unseen fact patterns, self-grading against a rubric, and drilling the rules you're shakiest on until they come automatically under pressure. Most students start this phase too late.

Time management is a graded skill in disguise. Before you write anything, divide your minutes across the questions in proportion to their point weight, then hold the line — a brilliant answer to question one is worthless if it eats the time you needed for question three. The most common way strong students underperform is not weak analysis; it's an unfinished exam. Budget reading and issue-listing time explicitly (often a quarter of the clock), reserve a few minutes at the end, and when a question's time is up, move on even mid-sentence. Issues you never reach score zero, while a thin paragraph on a later issue still earns partial credit.

Know which format you're walking into, because each rewards different preparation. The classic issue-spotter rewards breadth and speed — pack in every triggered issue. A policy question rewards a structured argument that marshals competing rationales, not a rule dump. A short-answer or multiple-choice section (common in Civ Pro and Property) rewards precise rule recall over argument. 'Open-book' rarely means what students hope: there is no time to learn doctrine from your outline mid-exam, so your outline should function as a fast lookup for rules you already know, not a safety net. Get a copy of the professor's past exams early and prepare for the format you'll actually face.

Self-grading is where practice answers turn into improvement. Writing a timed answer and never reviewing it builds speed but not accuracy. After each practice answer, grade yourself against a model or a rubric and ask three questions: which issues did I miss, where did I assert instead of argue, and where did I waste words on an uncontested element? Patterns emerge fast — most students find they consistently miss the same kind of buried issue or routinely under-argue the counterargument — and fixing a recurring pattern is worth more than writing ten more ungraded answers.

The exam-preparation arc across the semester has three distinct phases. In the first half of the semester, your job is understanding — briefing cases, following class discussion, asking questions. In the middle of the semester, shift to synthesis: start your outline and run one practice hypo per week to test whether you can apply what you're learning. In the final two to three weeks, switch to performance: timed full-length exams, self-graded against a model, with rule drilling on whatever the practice reveals as weak. Most students spend the entire semester in phase one and try to compress phases two and three into the final week. That compression is the main reason otherwise well-prepared students underperform — they understand the doctrine but have not yet trained the skill of applying it under pressure.

Past exams are the single best study tool available, and they are often underused. Your professor's old exams — usually on file with the library, the registrar, or a student organization — tell you exactly what format to expect, which combinations of issues this professor likes to create, how much analysis they expect per issue, and whether they prefer you argue both sides or lead with a clear answer. If you can find an exam with a model answer or grading rubric, even better: it shows you how the professor allocates points. Run every available past exam timed, grade it against the model, and make a list of what the professor tests that you have not yet outlined. That list is your exam-prep checklist.

The grading rubric is usually invisible, but you can infer it. Most law school exams are graded by issue — the professor has a list of issues the fact pattern raises, and you get points for spotting and analyzing each. Within each issue, points go to rule accuracy, both-sides analysis, and a clear conclusion. Students who write clean IRAC for contested issues and move on efficiently almost always outscore students who write excellent prose on fewer issues. One useful heuristic: if you have addressed every issue you can find and still have time left, add depth to your most important analysis — but never sacrifice issue coverage to polish a single answer. The student who spots eight issues and writes six clean IRACs beats the student who writes three beautiful essays every time.

Exam-day execution is its own discipline, separate from preparation. Before you write, spend the first two to three minutes reading every question so you know the scope of the whole exam. Then allocate time: if there are three questions worth equal points and you have three hours, each question gets fifty minutes, not ninety for the first and ten for the last two. Start with the question you feel most confident about — a clean first answer builds momentum and ensures you have at least one strong set of points before time pressure builds. When a question's time is up, stop, note in brackets what you would have said ('would have argued proximate cause here — no time'), and move on. Professors often give partial credit for a bracketed point that shows you spotted the issue even if you couldn't develop it.

How you review an exam after it is returned matters as much as how you took it. Read your answer against the model, and for every issue you missed, trace back why: did you not spot the fact that triggered it, did you know the doctrine but not recognize the pattern, or did you run out of time? Each explanation calls for a different fix. Missed facts → practice more issue-spotting drills. Doctrine gap → add it to your outline and flashcard it. Time → practice budgeting on the next exam. Most students read their grade, feel good or bad about it, and learn nothing specific. The students who improve fastest treat every returned exam as a diagnostic, not a verdict.