How to Spot the Unsupported Trap on the LSAT
When we flag an answer as Unsupported, it means there was a specific reason that wrong answer looked attractive. The answer sounds plausible, but the text does not give enough support for it. This guide is about catching that move while the choice still feels tempting, then using review to make the pattern easier to notice next time.
What This Trap Means
The answer sounds plausible, but the text does not give enough support for it.
In plain English, Unsupported means the answer is doing something that can feel relevant while still failing the job of the stem. The details change from question to question, but the review habit is the same: slow down, compare the choice to the exact task, and ask what it still fails to prove.
Example
Here is the pattern in a simplified LSAT-style setup. The topic will change, but the underlying move is the part you want to recognize.
Example
Setup: The passage says museum attendance rose after a new advertising campaign began.
Tempting wrong answer: The advertising campaign was the main reason attendance rose.
Why it matters: That is Unsupported because the timing is suggestive, but the passage has not ruled out other reasons attendance increased.
Why It Feels Tempting
It feels plausible because it could be true in the real world, even though the passage does not establish it.
LSAT wrong answers are rarely random. They borrow real language from the stimulus, point at a nearby issue, or describe something that would matter in a different version of the question. That is why this pattern can feel reasonable in the moment even when it does not survive a strict check against the task.
How To Spot It
Use these checks before committing to the answer. The point is to make the suspicious move visible while you still have time to compare choices.
- Separate common sense from textual support.
- Watch for answers that require one extra assumption to work.
How To Beat It
Do not treat the label as something to memorize. Treat it as a cue for what to check next.
During review, find the exact word, comparison, scope shift, or support gap that made the answer tempting. Then rewrite the answer in your own words and state why it fails the stem. That turns the trap from a vague mistake into a repeatable signal.
- For Inference and RC questions, demand proof in the stimulus or passage.
- For other tasks, ask whether the answer has an actual bridge to the argument.
How To Review It In Your Diagnostics
If this pattern is showing up in your diagnostics, start with a small set of missed questions rather than trying to overhaul your whole approach. Look at the answer you picked, write down the feature that made it tempting, and then compare that feature to the reason the credited answer works.
Over time, the percentage matters less than the reaction it trains: pause, name the move, and force the answer back through the exact question stem.
Quick Check
Where exactly did the passage give me enough support for this?