LSATLSAT conclusionmain conclusionargument structure

How to Find the LSAT Conclusion When There Are No Indicator Words

When "therefore" and "thus" are missing, finding the conclusion gets harder. Use the Why Test and the Therefore Test to identify the main point in any LSAT argument.

Verbloom
LSAT guides · built by a 178 scorer
8 min read

When the easy signposts disappear

Indicator words like "therefore," "thus," and "so" make the conclusion easy to spot — when they are there. The trouble is that many of the hardest Logical Reasoning stimuli leave them out entirely, or sprinkle them around premises to bait you. When the signposts vanish, you need a method that works on meaning rather than punctuation.

The answer is to stop hunting for words and start asking about roles. The conclusion is the claim the author is trying to get you to accept; the premises are the reasons offered in its support. Two quick tests reveal which is which.

The Therefore Test and the Why Test

The Therefore Test: take the two statements you are deciding between and mentally place "therefore" between them, in both orders. "A, therefore B" versus "B, therefore A." Only one direction makes sense as reasoning — and the statement that lands after "therefore" in the sensible version is the conclusion.

The Why Test: pick the statement you suspect is the conclusion and ask "why should I believe this?" If the other statements answer that question, you have found the conclusion, because premises exist to answer "why." If asking "why" about your candidate leads nowhere and the other statement is the one being supported, you picked a premise by mistake.

Both tests do the same job from different angles: they force you to check the direction of support. The conclusion is always the claim being supported, never the one doing the supporting.

The conclusion is what the author wants you to believe

A conclusion is not defined by its position or its tone. It is not necessarily the last sentence, and it is not necessarily the most opinionated-sounding line. It is whatever the rest of the argument is built to support.

This is worth repeating because two habits mislead people. The first is grabbing the final sentence — but authors often state the conclusion early and spend the rest of the stimulus defending it. The second is grabbing the most strongly worded claim — but a vivid premise can sound more like an opinion than the actual main point does.

Anchor on function. Ask which single statement everything else is there to justify. That statement is the conclusion even if it sits in the middle and reads modestly.

Watch for buried and disguised conclusions

Conclusions hide in a few predictable disguises. A recommendation ("the city should adopt the plan") is often the conclusion, with the surrounding facts as support. A prediction ("enrollment will rise next year") and a value judgment ("this approach is misguided") play the same role. When you see a recommendation, forecast, or evaluation, test it first — it is frequently the main point.

Conclusions also get buried mid-paragraph, tucked between premises so the last sentence is actually a premise or an elaboration. And watch for the counter-premise setup: "Some argue X. But the evidence shows Y." The clause after "but" is usually the conclusion, and X is a view the author is rejecting.

Worked example

Stimulus, no indicators: "A city that wants to cut traffic should invest in public transit rather than wider roads. Wider roads attract more drivers, which fills the new capacity within a few years. Transit, by contrast, removes cars from the road for good."

Apply the Why Test to the first sentence: why should I believe the city should invest in transit? Because wider roads just fill back up, and transit permanently removes cars. The other two sentences answer "why" — so the first sentence is the conclusion, even though it has no "therefore" and the supporting reasons come afterward.

Confirm with the Therefore Test: "Wider roads fill back up and transit removes cars for good, therefore the city should invest in transit" reads as sound reasoning; the reverse does not. Same answer, double-checked.

The common mistake: defaulting to the last or loudest sentence

Under time pressure, students reach for shortcuts: the last sentence, or the one that sounds most like an opinion. Both fail regularly, because the LSAT writes stimuli specifically to punish those shortcuts — conclusions are routinely placed first or in the middle, and premises are often phrased forcefully.

Replace the shortcut with a five-second check. Before you commit, run the Why Test on your candidate conclusion. If the rest of the stimulus does not answer "why believe this," you have the wrong sentence. That one habit catches most conclusion-identification errors.

Frequently asked questions

How do I find the conclusion when there is no "therefore" or "thus"?

Use the Why Test: pick a candidate and ask "why should I believe this?" If the other statements answer that question, your candidate is the conclusion. The Therefore Test — inserting "therefore" between the statements to see which direction makes sense — confirms it.

Is the conclusion always the last sentence?

No. Authors frequently state the conclusion first or in the middle and place supporting premises afterward. Position does not determine the conclusion; function does — it is the claim everything else supports.

Can a recommendation or prediction be the conclusion?

Yes, often. Recommendations ("should"), predictions ("will"), and value judgments ("is misguided") are common conclusion forms. When you see one, test it first — the surrounding facts are usually its support.

What about "Some people argue X, but Y" structures?

The clause after "but" is usually the author's conclusion, and X is a competing view the author is arguing against. Do not mistake the opposing view for the main point.

Related Verbloom guides

Sources

Want LSAT logic to feel visual?

Verbloom turns argument structure into short visual lessons, drills, and explanations built for actual score movement.

About·Privacy·Terms·Contact
Featured on FoundrList