How to Spot Issues on Law School and Bar Exams

Read the call of the question first because it defines what counts as an issue. The call names the governing subject, the parties whose rights are at stake, and the scope of your answer. A broad call ('Discuss all claims and defenses') invites a wide issue sweep; a narrow call ('Is the search constitutional?') tells you to ignore unrelated issues and go deep on one. Reading the call first turns the fact pattern from a story into a targeted search. It also prevents the common error of writing a brilliant analysis of an issue the question never asked about, which earns little to no credit.

A fact trigger is a specific detail in the prompt that maps to a legal rule, and the second read is where you catch them. Exam drafters do not include facts by accident, so treat each concrete detail as a clue: - A specific date or sequence: statute of limitations, timing, notice, or priority. - 'Orally' or 'over the phone': Statute of Frauds or parol evidence. - A signature without reading or under pressure: mistake, duress, unconscionability, duty to read. - A death, injury, or threat: homicide, wrongful death, survival, duty and causation. - An out-of-court statement offered to prove the truth of the matter asserted: hearsay and its exceptions. The discipline is to read the facts twice: once for the narrative, once trigger-by-trigger. Underline or list each trigger with the rule it implicates so no detail goes unspotted.

Most exam fact patterns are deliberately multi-issue, so map every party pairing to surface hidden claims. List each plaintiff against each defendant, each charge against each defendant, and each contract obligation against each promisee. This grid forces you to consider relationships a single read overlooks, such as agency or partnership liability for an employee's act, co-conspirator or accomplice liability among several actors, or a defense available against one party but not another. When the same fact supports multiple theories (for example, one act giving rise to both battery and a related crime), note each separately. Treating the pattern as a web of claims rather than a single dispute is what separates high-scoring answers from incomplete ones.

A subject checklist is your safety net against the issue you almost missed. After your trigger-based pass, run your spotted issues against a memorized framework for the tested area so you confirm coverage of every element and likely defense. For a negligence claim, walk duty, breach, causation (actual and proximate), and damages, then defenses like comparative fault and assumption of risk. For a contract, walk formation, defenses to formation, terms, performance, breach, and remedies. Checklists work because they convert recognition (which can fail under time pressure) into a deliberate sweep. Build one short checklist per high-frequency subject and run it on every essay in that subject.

Once issues are spotted, organize them before writing by converting each into an IRAC block. Issue spotting and issue analysis are different skills: spotting names the questions, IRAC answers them. Order your spotted issues so threshold questions (jurisdiction, admissibility, justiciability) come before merits, and so dispositive or heavily weighted issues lead. Give each spotted issue its own labeled paragraph; a grader scanning for credited issues should be able to find each one fast. Even a thinly analyzed issue earns more than an unspotted one, so it is usually better to name every legitimate issue briefly than to over-develop one and miss three. For the full analytical framework, pair this method with an IRAC writing guide.