LSAT RC Wrong-Answer Types: How the Test Builds the Four Wrong Choices

Every LSAT Reading Comprehension question has one credited answer and four wrong ones — and the four wrong ones were engineered, not thrown in. The test writers know exactly which misreadings are tempting, and they build choices to catch each of them. Learning those recurring shapes turns elimination from a feeling into a process.

The anchor for all of it is simple: a correct RC answer maps to a specific sentence (or a tight cluster of sentences) in the passage. If you cannot point to the textual support, be suspicious. Most wrong-answer types are designed to feel supported while quietly lacking that anchor.

These shapes repeat across passages and question types. You do not need to label every wrong answer, but recognizing the pattern speeds up elimination.

The two that catch the most points are "too extreme" and "half-right." Extreme wording is easy to overlook when the underlying idea is correct, and half-right answers exploit the fact that you stop reading once the opening matches what you expected.

The single biggest upgrade to RC elimination is refusing to cut an answer on gut feel. "I don't like how it sounds" is not a reason; it is a placeholder for a reason you have not found yet. For every answer you eliminate, you should be able to name the specific problem: too strong, distorts the detail, not in the passage, answers the wrong question.

This discipline does double duty. It makes your eliminations reliable, and it exposes the moments when you are guessing — which are exactly the moments to slow down and return to the text rather than commit.

Before you select an answer, find the sentence that proves it. The credited answer to a Reading Comprehension question is almost always traceable to direct evidence — a specific phrase you can put your finger on. If you cannot locate that phrase, you are probably looking at the wrong answer.

Run the check in both directions. If you can support a choice with a clear sentence, that is a strong signal it is correct. If your support is vague — "the passage kind of implies this overall" — treat the answer with suspicion, because most wrong answers are built to survive a vague impression and fail a specific one.

Suppose a passage argues that a historical reform "contributed to, though did not single-handedly cause," a rise in literacy, and a question asks what the author would most likely agree with.

(A) "The reform was the primary cause of rising literacy." — Too extreme and a detail distortion; the passage explicitly says it was not single-handed. Cut, with a reason. (B) "The reform had no measurable effect on literacy." — Reversal; the passage says it contributed. Cut. (C) "The reform was one of several factors in rising literacy." — Matches "contributed to, though did not single-handedly cause." Point to that sentence: this is the answer. (D) "Literacy would have risen at the same rate without the reform." — Out of scope; the passage never makes that counterfactual claim. Cut. (E) "The reform improved literacy more in cities than in rural areas." — True-but-unresponsive at best, and likely not in the passage; it answers a question that was not asked. Cut.

Every elimination had a named reason, and the winner had a sentence behind it. That is the whole method.

The most common RC error is choosing the answer that echoes the passage's vocabulary or tone without checking what it actually claims. Detail-distortion traps are built precisely for this: they recycle real words from the text in a slightly wrong arrangement, so they feel familiar and safe.

Beat it by verifying meaning over wording. An answer that reuses the passage's phrases can still reverse a relationship or overstate a hedge. Ask what the sentence asserts, match it to specific evidence, and let the answer that survives that test win — not the one that simply sounds the most like what you just read.