Law school exam writing is a distinct skill that differs fundamentally from other forms of legal writing. Unlike a memo or brief, which rewards thoroughness and polish, an exam answer rewards speed, issue-spotting, and efficient analysis. Most law school exams are time-pressured exercises designed to test whether you can identify the legal issues hidden in a complex fact pattern and apply the relevant rules under timed conditions. Your professor is not looking for elegant prose — they are looking for evidence that you can think like a lawyer under pressure.
The IRAC method (Issue, Rule, Application, Conclusion) is the backbone of exam writing, but simply knowing the acronym is not enough. The key to a high-scoring exam answer is the Application section — the analysis that bridges the gap between the abstract rule and the specific facts. Students who state the rule and jump to a conclusion without showing their analytical work consistently underperform. The application is where you demonstrate the critical thinking your professor spent the semester teaching you.
Time management is arguably as important as substantive knowledge. A brilliant analysis of the first issue is worthless if you run out of time and miss three other issues. Most professors allocate roughly equal points per issue, which means the marginal value of each additional issue you spot is much higher than additional depth on an issue you have already covered. When in doubt, move on to the next issue.
Document Structure
Issue Spotting
Identify every legal issue raised by the fact pattern.
Read the entire fact pattern once quickly, then read it again slowly, underlining facts that trigger legal issues. Every fact is there for a reason — if a detail seems irrelevant, you may be missing an issue. Use the exam's point allocation (if provided) to gauge how many issues the professor expects you to find.
Rule Statement
State the legal rule that applies to each issue concisely and accurately.
State rules from memory — you will not have time to look them up. Include all elements of the rule, not just the definition. If there is a majority and minority rule, state both and note which applies in the relevant jurisdiction. If the professor emphasized a particular formulation of the rule, use that formulation.
Application
Apply the rule to the specific facts in the exam to argue both sides.
This is where exams are won or lost. Do not just state a conclusion — walk through how each element of the rule applies to the specific facts. Argue both sides: 'Plaintiff will argue X because [specific fact]; however, Defendant will counter that Y because [specific fact].' Use the exact facts from the hypothetical, not generic analysis.
Conclusion
State your conclusion on each issue and explain which side has the stronger argument.
Your conclusion does not need to be 'right' — professors want to see your reasoning, not your prediction. Pick the side with the stronger argument, state your conclusion in one sentence, and move on. Do not agonize over close calls — that time is better spent on the next issue.
Policy (If Relevant)
Address policy considerations when the professor has signaled they are important.
Some professors love policy arguments; others think they are a waste of exam time. Know your professor. If policy is relevant, a brief mention of the underlying policy rationale can add depth to a close analysis. For example: 'This result is consistent with the policy of deterring manufacturers from placing defective products in the stream of commerce.'
Do's and Don'ts
Do
- Allocate your time based on point values — spend 30 minutes on a 30-point question, not 60 minutes
- Spot every issue first, then analyze each one — missing an issue entirely costs more than a shallow analysis of one you found
- Argue both sides of every close issue — professors want to see that you can identify arguments on both sides
- Use the exact facts from the hypothetical in your application — generic analysis scores poorly
- Write an IRAC paragraph for every issue you spot, even if your analysis is brief
- Use headings to organize your answer so the grader can find each issue quickly
Don't
- Do not spend all your time on the first issue and run out of time for the rest — breadth matters more than depth
- Do not recite the rule without applying it — stating the rule earns partial credit at best
- Do not write a conclusion without analysis — 'Defendant is liable for negligence' with no IRAC earns almost no credit
- Do not ignore facts that seem to cut against your conclusion — address them and explain why they do not change the outcome
- Do not write an introduction or conclusion that restates the question — jump straight into the analysis
- Do not spend time on penmanship or polished prose — substance beats style on every exam
Before & After Examples
Before
Battery is the intentional harmful or offensive touching of another person. Here, Dave hit Pat. Therefore, Dave committed battery.
After
The issue is whether Dave committed battery against Pat when he shoved Pat during the argument at the restaurant. Battery requires: (1) an intentional act; (2) that causes harmful or offensive contact; (3) with the plaintiff's person. First, Dave's shove was intentional — he deliberately extended his arms and pushed Pat, which satisfies the intent element. Dave may argue he was merely gesturing, but the fact that Pat was knocked backward into a table suggests force consistent with an intentional push, not an accidental gesture. Second, the contact was harmful — Pat sustained a bruised hip and a cut on his forearm from the broken glass. Even if the injuries were minor, any contact that causes bodily harm satisfies this element. Third, the contact was with Pat's person — Dave's hands made direct contact with Pat's chest. Dave will likely argue provocation (Pat called Dave a liar), but provocation is not a defense to battery, though it may reduce damages. Conclusion: Dave is likely liable for battery because all three elements are satisfied, and provocation does not negate the intentional tort.
The improved version identifies the issue with specific facts, states all elements of the rule, applies each element to specific facts from the hypothetical, argues both sides, addresses a potential defense, and reaches a reasoned conclusion. The weak version recites the rule and jumps to a conclusion without any analysis of the specific facts.
Before
There might be a negligence issue here. Negligence requires duty, breach, causation, and damages.
After
Issue: Whether the restaurant owed a duty of care to Pat as a business invitee and breached that duty by failing to intervene in the altercation. A commercial establishment owes its business invitees a duty of reasonable care to maintain safe premises, including a duty to protect against foreseeable criminal or tortious acts by third parties. Restatement (Second) of Torts Section 344. Application: The restaurant knew Dave and Pat were arguing loudly for ten minutes before the shove occurred. A reasonable business owner would have intervened — by asking the parties to leave or calling security — before the situation escalated to physical contact. The restaurant will argue that the shove was sudden and unforeseeable, but the ten-minute escalation period suggests the restaurant had notice that the situation was becoming dangerous. Conclusion: The restaurant likely breached its duty because it had ample notice of the escalating confrontation and failed to take any action.
The improved version spots a less obvious issue (premises liability), states the specific rule with authority, applies the rule to the specific facts (ten-minute argument, failure to intervene), argues both sides, and reaches a conclusion. The weak version spots the issue but stops at the rule statement without any application.
Common Mistakes to Avoid
Spending too much time on the first question and running out of time for later questions that carry equal or greater weight
Stating the rule without applying it to the specific facts — the 'rule dump' approach earns minimal credit
Missing issues because you started writing before reading the entire fact pattern carefully
Arguing only one side of a close issue instead of showing you can see both perspectives
Writing a long introduction that restates the question rather than jumping immediately into IRAC analysis
Ignoring facts in the hypothetical that seem unfavorable — professors put those facts there to test your ability to address counterarguments
Failing to allocate time proportionally to point values, resulting in brilliant analysis of minor issues and nothing on major ones