How To Do Verbal Reasoning

The actual process most people get wrong

Verbal reasoning isn't about being smart. It's about following a narrow set of constraints under time pressure, and the moment you start bringing outside knowledge into the equation you're already failing. I spent years grading these tests across multiple hiring pipelines and psychometric providers, and the difference between someone who scores well and someone who doesn't is almost never raw intelligence. It's discipline. Start with the passage. Not the question. Most test-takers flip straight to the question stem and then go hunting for evidence, which means they carry a preconceived answer into the text. The passage will contain distractors — plausible-sounding statements that are subtly unsupported. If you read the question first, your brain latches onto those distractors as confirmation bias waiting to happen. Read the passage once, note what it actually claims and what it leaves ambiguous, then look at the options. The core mechanic in every verbal reasoning test — whether it's the UKCAT, the Watson Glaser, the SHL verbal section, or LSAT reading comprehension — is the same three-way split: true, false, or cannot say. People treat these as obvious, but they're not. "Cannot say" is the hardest category because it requires you to admit ignorance with confidence, which feels counterintuitive when you've been trained your whole life to pick an answer and move on.

Here's where the real work starts. A statement is "true" only if it follows logically from the information given. Not probably true. Not reasonable. Logically entailed. If the passage says "X contributed to the decline," you cannot conclude "X caused the decline." Contributing is a subset of causation, and the test will absolutely include that as a trap option. Similarly, if the passage discusses a single study, any option generalizing to "researchers agree" or "studies show" is automatically unselectable unless the passage itself makes that broader claim. I ran into a particularly nasty edge case last year with a SHL-style assessment where the passage described a policy being "under review by the committee." The question asked whether the policy had been rejected. Half the candidates marked "false" because in everyday language, something under review isn't rejected. But strictly speaking, "under review" simply means no decision has been communicated yet. The policy could have been quietly shelved, formally rejected, or actively under consideration. The only defensible answer is "cannot say." I watched experienced candidates lose marks on this exact type of question because they applied conversational implicature instead of formal logical analysis. The workaround I started teaching was to literally paraphrase the passage in your head using the most boring, most restricted interpretation possible before touching the answer choices. Strip every modal qualifier. Remove every implication. What is left is what you're allowed to use.

Logical structure matters more than vocabulary

Many test-takers try to muscle through verbal reasoning by recognizing key terms or matching phrases between the passage and the options. This strategy collapses as soon as the questions move beyond simple comprehension into inference and assumption identification. Watson Glaser critical thinking questions, for example, ask you to identify arguments that "strongly support" or "weakly support" a conclusion, or to spot assumptions that the argument takes for granted. These require you to map the logical skeleton of the passage, not its vocabulary. A strong argument is one where the conclusion follows necessarily or near-necessarily from the premises. A weak argument is one where the conclusion goes significantly beyond what the premises justify. The distinction matters because the test will present you with arguments that are emotionally compelling, socially desirable, or intuitively correct — and all of those qualities are irrelevant. An argument can be morally right and logically weak at the same time. I've seen candidates mark "strong support" on an option simply because they agreed with the conclusion, which is the exact error the test is designed to catch. The practical fix is to separate the evaluation from the endorsement. Before you assess any argument, ask yourself whether you personally believe the conclusion. If yes, force yourself to write down three reasons it could be wrong. This takes about ten seconds and dramatically reduces confirmation bias in your scoring. It's a small mechanical step, but in my experience it shifts average scores by roughly a full band level on standardized instruments, which is the difference between passing and failing on many corporate screening cutoffs.

Common failures and what to do about them

The most frequent mistake I see is speed-reading without retention. Candidates rush through the passage in two minutes, then spend four minutes re-reading individual sentences while trying to answer questions. This is inefficient because the first read was superficial and the second read is panicked. A better allocation is roughly three minutes for an initial careful read with light annotation, two minutes for question analysis, and two minutes per question. You're not trying to memorize the passage. You're building a mental map of claims, scope, and logical relationships so you can return to the right section quickly. Another failure mode is treating all verbal reasoning tests as the same format. The LSAT logical reasoning section operates on formal logic with conditional statements and flaw identification. The UKCAT verbal reasoning section is closer to reading comprehension with true/false/cannot say. The GMAT critical reasoning section mixes assumption, strengthen, weaken, and inference questions in a single passage. The strategies overlap but aren't interchangeable. Preparing for one without recognizing the structural differences of another will cost you time and accuracy. Spend at least two hours analyzing the specific format you'll be facing before doing practice questions. There's also the issue of time pressure creating cascade failures. When you miss one question because you overthought it, you tend to rush the next three, which generates more errors and further panic. The realistic approach is to accept that you will not answer every question correctly and plan your pacing accordingly. On a standard 25-question verbal section with 30 minutes allocated, that's 72 seconds per question including the passage. If a question consistently eats more than two minutes, mark it and move on. You're trading one point for the chance to secure three or four easier points later in the section.

Resources and practice strategy

The most reliable free practice material comes from the test publishers themselves. SHL, Kenexa, UBS, and Cambridge Assessment all publish sample tests on their websites. These are closer to the actual instrument than any third-party prep book because the wording conventions, distractor patterns, and difficulty calibration come directly from the item banks. Third-party materials often overcomplicate the explanations or introduce strategies that don't transfer to the actual test format. For paid resources, the Watson Glaser prep guides from Critical Thinking Company are the standard reference, and the LSAT prep from Manhattan Prep or Powerscore covers the logical reasoning depth most other tests don't require but that will make easier tests feel straightforward by comparison. The tradeoff is time investment. LSAT-level preparation takes 40 to 80 hours for meaningful score improvement, which is overkill if you're only preparing for a single corporate assessment. Match the preparation depth to the test you're actually taking. One final point that nobody emphasizes enough: verbal reasoning performance is sensitive to fatigue and reading speed. If you're not a fast reader, practice timed reading with non-fiction material — journals, policy documents, technical reports — for at least two weeks before the test. This isn't about building general reading ability. It's about training your eyes to track claim structure under time constraints rather than narrative flow. The improvement is measurable. Most candidates who do this see their effective reading speed on dense passages increase by 30 to 40 percent within three weeks, and the comprehension loss that normally accompanies speed increases is minimal if you're focusing on argument structure rather than details.