Issue spotting has a reputation as the unteachable part of law school exams, the thing you either see or you don't. The reputation is wrong. Issue spotting is pattern recognition, and pattern recognition is trained the same way everywhere: build an inventory of triggers, expose yourself to patterns repeatedly, and audit your misses.

Students who spot everything are not gifted; they are running a checklist against a fact pattern while everyone else is reading a story. This page is the training program.

What an issue actually is

An issue is a collision between a fact and an element: some detail in the pattern that puts a legal rule genuinely in play. Which means issues live at the intersection of two lists you control. The first is the rule inventory in your head, your outline's checklist.

The second is the fact inventory on the page. Spotting is the act of running one against the other, and it fails for exactly two reasons: the rule was not in your inventory, an outline gap, or the fact never made it into yours, a reading failure. Every miss you will ever log is one of those two, and they have different fixes.

Read like the author, not the audience

The single most useful reframe: exam fact patterns are not found stories, they are engineered documents where every detail was a decision. The professor chose to make the buyer a merchant, chose the neighbor as the news source, chose the ten minute gap before the defendant returned.

When a detail seems gratuitous, a date, a quantity, a relationship, an adjective, the correct response is not to skim past it but to ask what it is doing there, because the honest answer is usually a doctrine. The interrogation habit, why is this fact here, run on every sentence of the pattern, is the core mechanic of spotting, and it is why A students seem to find issues that were invisible: they were reading the same words with a different question.

The five step exam read

First, read the call of the question before the facts, because the call is the scope: analyze all claims and defenses is a different assignment than advise the defendant on jurisdiction, and knowing the assignment filters the entire read. Second, read the pattern once for the story, fast, no pen, just orientation. Third, read it again with a pen, marking every actor, every date, every quantity, every relationship, and every detail that fails the why is this here test.

Fourth, build the inventory before writing a word: for litigation style patterns, a grid of who can sue whom for what, the pairing habit; for transactional patterns, a timeline where every communication gets a legal label. Fifth, run your course checklist down the inventory, your attack outline's top level is literally the spotting tool, and mark each potential issue as heavy, light, or absent.

Only then write. The ten minutes this costs repays itself twice: nothing gets discovered in a panic at minute 150, and the triage of heavy versus light is already done, which is the allocation skill described in what A exams do differently.

Spotting is graded in two tiers

Not every spotted issue deserves analysis, and knowing the difference is part of the score. Issues of analysis are the built fights, where the facts genuinely support both directions; they get the full treatment in IRAC units. Issues of recognition are present but one sided: battery on an admitted punch.

They earn their point in a single sentence that names the element and the fact, and anything more is time transferred from the issues that pay. The B exam failure is symmetrical treatment; the unusual A exam failure is dismissing a built fight in one line because you concluded too fast. The tell for a built fight is fact density: when the professor spent four sentences on the circumstances of one event, the fight is there.

The training program

Build the trigger lists first. For each course, convert your outline's top level into a one page spotting checklist, and annotate each doctrine with its classic fact triggers: statute of frauds, look for oral deals about land, guarantees, or performance beyond a year; personal jurisdiction, look for out of state defendants and internet or stream of commerce sales; felony murder, look for any death during any felony, however accidental. Class hypos are the best trigger source you have, because they are the professor showing you their own patterns.

Then drill spotting as its own exercise, separated from writing. Take a past exam, set fifteen minutes, and produce only the issue inventory, the grid or timeline plus the checklist run. Compare against the model answer's issue list and log every miss in your error log with its cause: outline gap or reading failure.

Ten of these drills cost less time than three full practice exams and train the specific skill faster, though they supplement rather than replace full timed writing, whose protocol is in how to use practice exams. Across drills, watch the miss log for clustering: repeated misses in one doctrine mean an outline repair; misses scattered across doctrines but clustered in long patterns mean a reading discipline problem, and the fix is slowing the third read down.

FAQ

What if I spot an issue but am not sure it is really there?

Name it and size it honestly: one sentence stating why the facts gesture at the doctrine and why it likely fails. A near issue handled in a line signals judgment; a phantom issue given a full IRAC signals the checklist is running you.

How many issues does a typical exam have?

A three hour issue spotter commonly carries eight to fifteen analyzable issues plus a layer of one sentence recognitions, but the range is professor specific and their past exams reveal it. Calibrate to your grader, not to a universal number.

Can issue spotting be improved in the last two weeks?

Yes, faster than any other exam skill, because the fifteen minute drill is cheap and the trigger lists are compact. Two drills a day per weak course, with the miss log driving outline repairs, moves real points in a fortnight.

Written by Ali, Georgetown Law, founder of Lovare Institut.

Book a call