Inference & Application Questions in RC
What You Need to Know
Inference & Application questions in LSAT Reading Comprehension test whether you can go beyond exact quoted lines without going beyond the passage.
- Inference (Most Strongly Supported) questions: what must (or is best) supported by the passage, even if not stated verbatim.
- Application questions: take an idea/principle/attitude from the passage and ask how it would play out in a new situation.
Why this matters: these questions are where LSAT writers punish “sounds right” reading. The right answer is provable from the passage’s logic, not just consistent with it.
Core rule (the whole game)
Inference/Application answers must be supported by the passage’s text + reasoning.
- If an answer needs a new assumption, it’s out.
- If an answer could be true but doesn’t have to be true, it’s out (unless the stem is “could be true,” which is rarer in RC).
Common stems to recognize fast
Inference:
- “Which of the following is most strongly supported?”
- “The passage implies which of the following?”
- “It can be inferred that …”
- “The author’s discussion suggests that …”
Application:
- “The author would be most likely to agree that in situation X …”
- “Which scenario is most analogous to …?”
- “Which of the following best exemplifies the principle described?”
- “Based on the passage, how would the author evaluate …?”
Critical reminder: In RC, “most strongly supported” means best-proven, not most exciting. Pick the boring answer you can actually justify.
Step-by-Step Breakdown
A. Inference (Most Strongly Supported) method
Classify the inference type
- Local inference: tied to a specific paragraph/claim (often easiest to prove).
- Global inference: about the passage’s overall argument, purpose, tone, or comparative structure.
Predict the “support zone” before hunting
- Ask: “What part of the passage would have to contain proof for this?”
- If you can’t name a zone, you’re at risk of chasing vibes.
Rephrase the relevant lines into a plain-language claim
- Strip qualifiers carefully (some matter).
- Keep track of who believes what (author vs. critics vs. researchers).
Pre-phrase a safe inference
- Think: “What is the smallest thing that must be true if those lines are true?”
- Safer inferences usually:
- restate with synonyms,
- combine two nearby claims,
- apply a stated generalization to a described case.
Use the “Proof, not Plausible” answer test
- For each choice, demand a textual warrant.
- If you can’t point to support, eliminate—even if it feels consistent.
Prefer weaker language when support is limited
- If the passage supports “sometimes,” eliminate answers claiming “always.”
- If the author hedges, the correct answer hedges.
Confirm the winner is the best-supported among remaining
- On “most strongly supported,” multiple choices can be consistent; choose the one with the clearest, most direct support.
B. Application method (principle/attitude → new case)
Identify what you’re applying
- Is it a principle (“If X, then Y”), a criterion (“good research must do A”), an evaluation standard, or an author attitude?
Extract the passage rule in IF–THEN form (even if unstated)
- Translate:
- “The author criticizes studies that rely solely on self-reports” →
- IF a study relies solely on self-reports, THEN the author would find it methodologically weak.
- Translate:
Underline the trigger conditions and the outcome
- Triggers: what must be present for the rule to apply.
- Outcome: what the author would conclude/approve/disapprove.
Map each answer choice to the rule
- Ask two questions:
1) “Does this scenario satisfy the trigger?”
2) “If yes, does the scenario produce the predicted outcome?”
- Ask two questions:
Watch for near-miss triggers
- LSAT loves options that look similar but miss one required element.
Choose the option with the tightest match (not the loudest resemblance)
- Correct application answers feel like:
- “Yep, that’s the same structure,” not “same topic.”
- Correct application answers feel like:
Mini worked walkthroughs (annotated)
Walkthrough 1 (Inference)
Passage says:
- “Several early studies reported an effect, but later studies with larger samples failed to replicate it.”
Safe inference:
- Larger-sample later studies cast doubt on the reliability of the early reported effect.
Answer choice check:
- “The effect does not exist” = too strong (not proved).
- “Early studies were fraudulent” = new assumption.
- “Replication attempts did not confirm the effect” = directly supported.
Walkthrough 2 (Application)
Passage principle:
- “Policies that reduce traffic congestion are most effective when they change incentives rather than merely providing information.”
Rule:
- IF a policy changes incentives, THEN it’s likely more effective than info-only campaigns.
Correct application answer will describe:
- congestion policy with pricing/penalties/benefits (incentives), not just ads or signage.
Key Formulas, Rules & Facts
A. Inference vs. Application: quick compare
| Question type | What it asks | Your job | What “right” looks like |
|---|---|---|---|
| Inference / MSS | What the passage implies or supports | Prove a claim from text + logic | Most provable option (often modest/hedged) |
| Application | How the passage’s idea would apply in a new case | Extract a rule/attitude and match structure | Best structural match to the passage’s principle/standard |
B. The support standard (how strict to be)
| Stem language | Support level you need | Practical meaning |
|---|---|---|
| Must be true / inferred / implies / MSS | Very high | Treat like LR Must Be True: deduce from passage |
| Most likely / best supported | High, but comparative | Pick the option with strongest textual footing |
| Would the author most likely agree | High | Must match author’s explicit view + tone/criteria |
| Best exemplifies / most analogous | High | Match relationship pattern, not surface topic |
C. High-yield “valid inference” moves
- Synonym / paraphrase: passage says “rare” → answer says “infrequent.”
- Combine two statements: A causes B; B increases C → A increases C (if no blockers/qualifiers).
- Category-to-member: “All X have Y” + “Z is an X” → “Z has Y.”
- Member-to-category (careful): “This X has Y” → cannot infer all X have Y.
- Qualified extension: “Often/typically tends to” allows a weak general inference, not a universal one.
D. High-yield “application” mapping cues
- Criteria/standard: “good,” “successful,” “legitimate,” “reliable,” “sound,” “adequate,” “problematic.”
- Causal claims: “because,” “leads to,” “results in,” “accounts for.”
- Comparisons: “more than,” “rather than,” “unlike,” “similar to.”
- Recommendations: “should,” “ought,” “policy should,” “best approach.”
If you can’t restate the passage’s relevant principle in one sentence, you’re not ready to apply it.
Examples & Applications
Example 1: Local inference (quantifier trap)
Passage snippet:
- “Some historians argue that the treaty’s economic clauses mattered more than its territorial clauses; others argue the opposite.”
Question: Which is most strongly supported?
- Correct inference: Historians disagree about whether economic or territorial clauses were more important.
- Common trap answers:
- “Most historians agree…” (unsupported).
- “The treaty’s economic clauses were more important” (author hasn’t endorsed either side).
Key insight: When the passage reports a debate, you can usually infer the existence of disagreement, not who’s right.
Example 2: Global inference (author’s stance)
Passage snippet:
- “While the new method is elegant, its accuracy in messy real-world conditions remains unproven.”
Strongly supported:
- The author is cautiously skeptical about real-world performance.
Trap answers:
- “The author rejects the method as useless” (too strong).
- “The author believes the method is already proven accurate” (contradicts).
Key insight: Tone words like “while,” “elegant,” “remains unproven” often signal qualified approval + a reservation.
Example 3: Application (criterion-based)
Passage principle:
- “For an archaeological claim to be convincing, the artifact’s context must be well documented; isolated artifacts are weak evidence.”
Question: Which scenario would the author find most convincing?
- Correct: An artifact discovered in situ with clear stratigraphic records and chain of custody.
- Traps:
- A spectacular artifact bought from a dealer with unknown origin (isolated).
- Multiple photos of an artifact but no site records (documentation gap).
Key insight: Application hinges on trigger conditions (“context well documented”), not “artifact is cool.”
Example 4: Application (analogy/structure)
Passage idea:
- “Regulating an industry using outdated metrics can misclassify innovation as noncompliance.”
Correct analogous scenario will share the structure:
- Rule uses an old metric → new behavior doesn’t fit → wrong classification.
Trap analogies:
- Same topic (regulation) but no outdated metric.
- Outdated metric exists but it correctly classifies the new behavior (no misclassification).
Key insight: “Analogous” = same logical relationship, not same subject area.
Common Mistakes & Traps
Mistake: Treating ‘most strongly supported’ as ‘most reasonable’
- What goes wrong: you pick the answer that fits your world knowledge.
- Why wrong: LSAT wants textual proof, not realism.
- Fix: Ask, “Where is this in the passage?” If you can’t point, cut it.
Mistake: Over-inferring from an example
- What goes wrong: passage gives one case; you infer a universal rule.
- Why wrong: a single instance doesn’t justify “all/most.”
- Fix: Match quantifiers: example → at most “can” or “sometimes,” unless passage generalizes.
Mistake: Missing scope limits (time, group, conditions)
- What goes wrong: passage says “in early 20th-century France,” answer says “in Europe” or “today.”
- Why wrong: scope expansion is a classic wrong-answer engine.
- Fix: Track who/when/where; eliminate answers that broaden or shift.
Mistake: Confusing who holds the view (author vs. others)
- What goes wrong: passage reports critics; you attribute their opinion to the author.
- Why wrong: RC often includes multiple viewpoints.
- Fix: Label margins mentally: A = author, C = critics, R = researchers.
Mistake: Ignoring hedges and intensity
- What goes wrong: passage says “may,” answer says “will”; passage says “some,” answer says “most.”
- Why wrong: the LSAT tests sensitivity to qualifiers.
- Fix: Prefer answers with the same strength level as the passage.
Mistake: In application, matching topic instead of structure
- What goes wrong: you pick the answer about the same field, not the same logic.
- Why wrong: application/analogy is about relationships.
- Fix: Write the rule as IF–THEN; choose the option that satisfies it.
Mistake: Falling for ‘extreme language’ when the passage is moderate
- What goes wrong: “never,” “always,” “completely,” “only” sneaks in.
- Why wrong: RC passages usually support nuanced claims.
- Fix: Extreme can be right, but only if the passage is extreme. Demand proof.
Mistake: Choosing an answer that is true in general but irrelevant
- What goes wrong: answer is factually true but not supported/required by this passage.
- Why wrong: LSAT is closed-universe.
- Fix: Ask, “Does the passage commit to this?” Not “Is this generally true?”
Memory Aids & Quick Tricks
| Trick / mnemonic | What it helps you remember | When to use it |
|---|---|---|
| “Prove it or lose it” | Inference answers need evidence, not vibes | Any MSS/inferred/implies question |
| UDI: Up–Down–In | Wrong answers often go Up in strength, Down to a subset/example, or In a new idea | Eliminating answer choices fast |
| IF–THEN extraction | Turns a fuzzy passage idea into a checkable rule | Application/principle questions |
| Trigger–Outcome check | Confirms the scenario actually activates the rule and yields the predicted evaluation | Application + analogy |
| “Same structure, not same subject” | Prevents topic-matching traps in analogy questions | Most analogous / best exemplifies |
| Qualifiers = guardrails | “Some/many/often/may” restrict what you can infer | Inference and author-attitude |
Quick Review Checklist
- Inference = prove from passage; don’t import outside facts.
- On most strongly supported, pick the choice with the clearest textual warrant, even if it feels mild.
- Track scope (who/when/where/conditions) and strength (some vs. most; may vs. will).
- Separate author’s view from other viewpoints the author reports.
- For application, convert the relevant idea into an IF–THEN rule.
- In application/analogy, match logical structure (trigger + outcome), not topic.
- Eliminate answers that add new causes, reverse relationships, or overgeneralize from examples.
You’ve got this: be ruthless about proof, and these questions become predictable.