What is the grader actually rewarding?
Most law professors grade issue-spotter exams against a checklist. Each issue is worth points, and within each issue, points attach to identifying the rule, identifying the sub-elements in dispute, and matching each element to the facts that trigger or defeat it. A sentence like "Dana was negligent" earns nothing. A sentence like "Dana looked away from the road for roughly four seconds while traveling 55 mph, covering more than 300 feet blind" earns a point because it does work on the breach element.
This is why the conclusion rarely matters. On a well-drafted exam, the close questions are deliberately close — the facts are built so a competent student could argue either way. The professor wants to see that you know the question is contestable and can articulate both sides. Say so out loud: "This is a close call because..." then give the strongest argument for each party and pick one.
Grading practice does vary. Some professors use a strict point-per-issue rubric; others read holistically and reward organization and judgment; a few weight policy discussion heavily. This variation is driven almost entirely by the individual professor, not the school or the subject. The fix is the same everywhere: get old exams and any model answers or grading memos from the professor, and read what they actually rewarded.
How should you spend the clock?
Convert points to minutes. If a three-hour exam has a 60-point question and a 40-point question, you have roughly 108 minutes and 72 minutes. Write those wall-clock stop times on your scratch paper before you start and honor them. Abandoning a question mid-sentence to start the next one costs less than finishing beautifully and leaving forty points untouched.
Spend the first 20 to 25 percent of each question's time reading and outlining. Read the call of the question first — "Discuss Perez's claims against Dana only" is a hard limit, and discussing Dana's claims against Perez earns zero. Then read the fact pattern twice: once for the story, once with a pen, marking every fact that seems planted. Dates, dollar amounts, ages, states, oral versus written, who spoke first — these are there for a reason.
Then build a two-minute outline: a list of issues in the order you will write them, with a two- or three-word note about the key fact for each. Writing without this outline is the most common cause of a disorganized answer that repeats itself and misses issues sitting in the last paragraph of the hypothetical.
What does a good IRAC paragraph look like?
Use a bolded heading naming the issue, then keep the rule short and the application long. A serviceable ratio is one or two sentences of rule to five or more sentences of application.
Here is the shape:
"Breach. A defendant breaches when she fails to act as a reasonable person under the circumstances; under the Carroll Towing formulation, breach exists where the burden of precaution is less than the probability of harm multiplied by its gravity. Dana's burden was trivial — setting the phone down costs nothing. The probability of harm was substantial: she was in stop-and-go traffic on a four-lane road at rush hour, where the car ahead can brake without warning. The gravity is severe, as a rear-end collision at 40 mph routinely causes serious injury. Dana will argue she glanced down only at a red light and that the statute she violated is a minor infraction, but she admitted looking away as traffic began to move. B is far less than P times L, and a jury would likely find breach."
Notice that every sentence in the application contains a fact from the hypothetical. If a sentence in your answer could have been written before you read the fact pattern, it is probably not earning points. Notice also that the counterargument is specific — it uses Dana's own facts rather than a generic "however, the defendant may disagree."
How do you find issues you would otherwise miss?
Memorize an attack outline — a bare checklist of the course's doctrinal structure that you can reproduce on scratch paper in three minutes. For torts, that might be: intentional torts, defenses, negligence (duty, breach, causation, damages), defenses to negligence, strict liability, products, vicarious liability, damages. For civil procedure: personal jurisdiction, subject matter jurisdiction, venue, Erie, service, pleading, joinder, discovery, summary judgment, preclusion. Run the fact pattern against the list rather than trusting recall.
Then run a second pass by party. For each named character, ask what claims they have and against whom, and what defenses they hold. Fact patterns hide issues in secondary characters — the employer, the bystander, the second buyer.
Treat every specific detail as a flag. A defendant who is seventeen raises capacity or minority. A conversation about land raises the Statute of Frauds. A defendant incorporated in Delaware with a plant in Ohio raises citizenship for diversity. Professors do not write ages and states by accident.
How much law should you state, and do you need citations?
State the rule at the level of generality the issue requires, then break out only the disputed element. If duty and damages are obvious and breach is contested, dispose of duty and damages in one sentence each and spend your words on breach. Writing a full page on an uncontested element while ignoring a contested one is a classic way to score in the middle of the curve.
You almost never need Bluebook citations on an exam. Case names alone are fine and often expected: "under International Shoe," "as in Palsgraf," "the Hadley v. Baxendale limitation on consequential damages." No reporters, no pincites, no italics — nobody is grading citation form. Rule and statute numbers should be given as numbers: Rule 12(b)(6), Rule 56, UCC § 2-207, Federal Rule of Evidence 403.
Cases matter most when you use them analogically. "The contacts here are weaker than in World-Wide Volkswagen, where the car merely arrived in Oklahoma through the unilateral act of the buyer" is worth more than dropping a case name as decoration.
If your professor taught a split — majority versus minority rule, Restatement versus common law, an approach the professor personally criticized — flag it and resolve it under both. That is usually a scored line on the rubric.
What loses the most points?
The three biggest losses are running out of time, restating facts without connecting them to rules, and burying the analysis in unbroken prose. Fix the third by using headings and short paragraphs; a grader reading her hundredth exam at 11 p.m. should be able to see your structure at a glance.
Other reliable point-killers:
- Writing an introduction that summarizes the facts. Start with the first issue.
- Inventing facts. Say "if Dana in fact knew of the defect, then..." rather than asserting she knew.
- Refusing to conclude. Pick a side after arguing both; "it could go either way" with no resolution loses a point on many rubrics.
- Ignoring the call of the question, including word limits and instructions to argue for one party rather than analyze neutrally.
- Spending twenty minutes on a policy digression the question did not ask for.
How do you practice this before the exam?
Write full, timed answers to at least three past exams per course, ideally your professor's own. Reading a model answer without having written one first teaches you almost nothing, because recognition feels like competence and is not. The point of practice is discovering which rules you cannot state under pressure.
After each practice answer, self-grade against the model or grading memo and keep a running list of what you missed. Most students find the same two or three failure modes repeating — always missing consideration, always forgetting to check subject matter jurisdiction — and those are fixable with a checklist.
Also practice the mechanics. Know whether the exam is closed book, open book, or open outline, whether it is on Examplify or Exam4, and whether the software locks your computer. If it is closed book, your attack outline has to live in your head. If it is open book, the marginal value of a 90-page outline is near zero; build a five-page attack outline you can actually navigate in ninety seconds.