The Law School Exam Guide
Law school exams feel impossible until you realize they all follow the same pattern. Your job is the same every time: spot the issues buried in the facts, run each one through a framework, and spend your time where the points are.
This guide covers the IRAC structure, a routine for finding issues so you stop missing them, and a calculator that turns any exam into a minute-by-minute plan. None of it is complicated once you see how the pieces fit.
How to use IRAC
Take every issue you spot and run it through the same four steps. Graders give points for structure, so make the issue, the rule, how you apply the facts, and your conclusion easy to find. A grader skimming fast should be able to see all four at a glance.
Issue
Name the legal question the facts raise.
- Frame it as a yes-or-no question
- Use the legal term of art
- One issue per IRAC block
Pitfall: Writing a fact summary instead of a legal question.
Rule
State the governing law and its elements.
- Lead with the black-letter rule
- Break it into elements or factors
- Note majority vs. minority splits
Pitfall: Dumping every rule you memorized, relevant or not.
Application
Map the facts onto each element, for both sides.
- Use "because" plus a specific fact
- Argue the counterargument too
- This is where the points live
Pitfall: Stating a conclusion without the "because."
Conclusion
Resolve the issue, briefly.
- Pick the stronger side
- One or two sentences
- It is fine to say "a court likely..."
Pitfall: Spending more time here than on Application.
IRAC in a single paragraph
Here is what IRAC looks like in practice, on two different subjects. Notice how short the Issue, Rule, and Conclusion are, and how the Application carries the weight.
Issue. Whether Dan committed battery when he pulled the chair out from under Pam.
Rule. Battery is an intentional act that causes a harmful or offensive contact with the plaintiff's person. Intent is satisfied if the defendant acted with purpose or knew the contact was substantially certain to result, and the contact need not be skin-to-skin.
Application. Dan acted intentionally because he deliberately moved the chair knowing Pam was about to sit. Even if he meant it only as a prank, intent transfers to the contact that followed, and substantial certainty is met because a person sitting on a removed chair will almost certainly hit the floor. The floor contact is harmful because Pam was injured, and contact through the ground she expected to support her still counts as contact with her person.
Conclusion. A court would likely find Dan liable for battery.
How to spot issues
You cannot analyze an issue you never saw, and missed issues are where most points disappear. Issues hide in the facts. The skill is learning to see the trigger and the issue it raises, then working through your attack outline so nothing slips by.
Fact trigger, then issue
Certain facts are red flags. When you see one, a specific doctrine should jump to mind. Here are some of the most common pairings:
| When you see... | Check for... |
|---|---|
| A surprising or unforeseeable injury | Proximate cause / scope of liability |
| A promise with nothing given in return | Consideration / promissory estoppel |
| "As is," a disclaimer, or a form contract | Warranties, unconscionability, §2-207 |
| A bystander who witnesses harm | NIED / IIED standing |
| Someone acting under a mistaken belief | Mistake, consent, self-defense privilege |
| A deadline, "open for," or a revoked promise | Offer, option, revocation, mailbox rule |
The four-pass method
Read fast for the story
Who wants what from whom, and what went wrong? Get the shape of it before anything else.
Read slow with your attack outline
Run every pair of parties against each cause of action so you do not skip a relationship.
Mark every triggering fact
Each fact is in the hypo for a reason. If it is on the page, it probably belongs in your Application.
Outline before you write
List the issues in the order you will address them, with a minute budget next to each.
If a fact never shows up anywhere in your analysis, you probably missed an issue. Go back and ask why the professor put it there.
Exam time-management calculator
Enter your exam length and give each question its point value. The calculator sets aside time to read and review, splits the rest by points, and builds a clock schedule if you add a start time. Running out of time on the last question is the most common avoidable way to lose points, and a plan fixes it.
| Question | Points | |
|---|---|---|
| Phase | Points | Share | Minutes | Outline / Write | Clock window |
|---|---|---|---|---|---|
| Read & plan | — | — | 15 | — | — |
| Essay 1 (Torts) | 35 | 35% | 54 | 11 / 43 min | — |
| Essay 2 (Contracts) | 35 | 35% | 54 | 11 / 43 min | — |
| Multiple choice (25 Q) | 30 | 30% | 47 | 9 / 38 min | — |
| Final review | — | — | 10 | — | — |
The Outline / Write split reserves about 20% of each question for spotting issues and sketching your IRAC order before you start drafting.
Exam-day checklist & common mistakes
Exam-day checklist
- Skim the whole exam and the point totals first, then build your time plan before you write a word.
- Answer the highest-point question first, while you are fresh.
- Use a header for each issue so the grader can find your points fast.
- When the clock hits a question's limit, conclude and move on.
- Save the buffer for re-reading the actual call of each question.
Common ways students lose points
- Rule-dumping. Pages of memorized law with no facts attached earns almost nothing.
- Skipping the weak side. Strong answers argue both parties before concluding.
- Burying the issue. With no header or signpost, the grader cannot award points they cannot find.
- Running out of time. A half-answered last question is the most common avoidable loss.
- Answering the wrong call. "Discuss Dan's liability" is not "discuss everyone's."