The GMAT Focus edition ships with a Reasoning sub-section that asks candidates to read a short business case and pick the response that strengthens, weakens, draws out, or resolves a tension inside it. That item family is the Evaluating Business Scenarios prompt, and it sits at the meeting point of verbal reasoning, data interpretation, and managerial judgement. Because each question presents roughly 80 to 120 words of narrative before the stem, candidates who treat it as a reading-comprehension item tend to over-read; candidates who treat it as a logic puzzle tend to under-read. The families that succeed treat the prompt as a tiny argument with a load-bearing claim, an unstated assumption, and a request that the test-taker do something surgical to it. Knowing the request before you read the case is what separates a 645 candidate from a 705 candidate on this single item type.
Across a full GMAT Focus sitting, the Evaluating Business Scenarios family accounts for a meaningful slice of the Reasoning section, and it pulls double weight because every missed item both costs raw points and inflates the standard error of the candidate's overall ability estimate. The exam format delivers these prompts inside the standard 45-minute Reasoning block, in line with the same adaptive pacing that governs the other Reasoning families. The four reading moves that follow are designed for working under that time pressure, not for an untimed textbook drill.
What the stem is actually asking you to do
Every Evaluating Business Scenarios item has a recognisable shape, and the shape is governed entirely by the stem, not the case. Most candidates read the case first and only skim the stem; that habit costs roughly one in five of these items at the 600-band level. The first reading move is therefore the simplest: stop, lift your eyes to the stem, and identify the verb the test-writer has chosen. Six verbs appear with predictable frequency.
- Most likely — the request is a forward inference from the case, anchored to a stated fact plus one piece of unstated information.
- Most useful — the request is a meta-evaluation of the case itself, asking which new fact would best test the argument.
- Which response — the request is a managerial or stakeholder action, asking what the decision-maker should do given the case.
- Which explanation — the request is a counterfactual, asking how to reconcile an apparent contradiction between two facts in the case.
- Would most strengthen / weaken — the request is a tactical attack on the argument, asking which answer choice moves the conclusion closer to or further from validity.
- Would most justify — the request is a logical underpinning, asking which answer choice is the missing premise of the argument.
Once the verb is fixed in your head, the case becomes a directed target. A "most likely" stem is asking for a probable outcome, not a true statement. A "would most weaken" stem is asking for a defeater, not a counterexample in the abstract sense. For most candidates, the single largest gain on this family is internalising this distinction: a true statement and a useful statement are not the same target, and conflating them costs a question on roughly 25 to 30 per cent of items at the 605 to 635 band. The verb also tells you what to ignore. A "which response" stem can usually skip the second paragraph of the case entirely; the answer is about action, not about whether the action is theoretically justified.
To train this move, copy any practice Evaluating Business Scenarios item into a spreadsheet and label the verb. After 15 items, the pattern is unmistakable. After 30, you will catch yourself silently naming the verb before you finish reading it, and that sub-vocalisation is the foundation of a 7-to-9-second time save on every item in this family.
The four-part argument sketch that holds the case together
Reading the case is the second move, and the most efficient way to read it is to draw a four-part argument sketch before you look at the answers. The four parts are: context, claim, support, and gap. The context is the company, the time horizon, and the constraint. The claim is the sentence that, if removed, would collapse the case. The support is whatever evidence the case offers for that claim, and the gap is the assumption the writer is hoping you will not notice. Most candidates skim the context, under-read the claim, ignore the support, and never even reach the gap. Reversing that order — claim first, support second, gap third, context last — is the second reading move.
In practice, the claim is almost always the last sentence of the first paragraph or the first sentence of the second paragraph. It is a sentence with a verb, a subject, and a load-bearing noun. The support is usually one sentence in the case; if you find more than one, the case is signalling that the claim is contested, and the gap will be the missing link between the two pieces of support. The gap is the assumption that connects the support to the claim, and it is the single best place to attack a "would most weaken" stem. For a "would most strengthen" stem, you are looking for the answer that fills the gap with a specific, testable fact, not with a generic endorsement.
For most candidates, the sketch takes 25 to 35 seconds the first time, dropping to 15 to 20 seconds after a dozen items. The investment is worth it because the sketch gives you a place to park the case in your head. Without it, the case fades by the time you reach answer choice D, and a 50-second item becomes a 110-second item. With it, you can answer the question without re-reading the case at all, which is the test-taker's true goal on this family.
Stem shapes and the answers they invite
Every Evaluating Business Scenarios stem fits one of three shapes, and each shape has a characteristic family of wrong answers. The shapes are single-claim, dual-claim, and action-pivot. The single-claim stem is the most common: the case makes one claim, the stem asks the test-taker to do something to that claim, and the four wrong answers each attack a different part of the case that the stem is not asking about. The dual-claim stem is rarer but more lethal: the case makes two claims, the stem targets the relationship between them, and three of the wrong answers are true statements about one claim in isolation. The action-pivot stem presents a case and asks what the decision-maker should do, and the wrong answers are usually general principles that the candidate has to recognise as inapplicable to the specific constraint of the case.
- Single-claim signature — "which of the following would most strengthen the argument". The wrong answers are usually consistent with the case but not actually load-bearing on the claim.
- Dual-claim signature — "which of the following best explains why both statements can be true". The wrong answers choose one side of the case and ignore the other.
- Action-pivot signature — "which response should the manager most likely take". The wrong answers sound reasonable in the abstract but violate one constraint stated in the case.
The single-claim shape is forgiving because the test-taker can confirm the claim before reading the answers. The dual-claim shape is unforgiving because the candidate has to hold both claims in working memory at once; if you have not sketched the case, you will forget the second claim by the time you reach choice C. The action-pivot shape is unforgiving for a different reason: it tests whether the candidate can read a constraint, not just a claim. In my experience, the action-pivot is the shape where strong verbal candidates lose the most points, because they read for the action and skip the constraint. A 30-second underline of every stated constraint is the single best insurance policy for this shape.
Common pitfalls and how to avoid them
Three pitfalls account for the majority of avoidable errors on this family. The first is reading the case instead of the stem. The second is treating a true statement as a useful statement. The third is choosing the answer that the case makes you want to choose, rather than the answer that the stem is actually requesting. All three are behavioural, not intellectual, and they yield to targeted drill.
- Pitfall 1 — Over-reading the case. Candidates spend 50 seconds reading 100 words because they want to be thorough. The case rarely contains more than one load-bearing fact. Mark it, move on, return to the stem.
- Pitfall 2 — Confusing true with useful. A true statement is one that does not contradict the case. A useful statement is one that does the work the stem is requesting. The exam format rewards useful, not true.
- Pitfall 3 — Answering the writer, not the stem. The case is often written in a sympathetic voice, and the candidate's instinct is to endorse the writer's framing. The stem is deliberately written to test whether the candidate can stand outside that framing.
The remedy for all three is the same: a 10-second pause after reading the stem, a 5-second pause after sketching the case, and a 3-second pause before selecting an answer. Those pauses feel wasteful, but they convert a 60-second rushed item into a 75-second deliberate item, and the deliberate item has a measurably higher hit rate. The exam format permits that 15-second margin; the Reasoning section's per-item budget is roughly 95 seconds, and the time is rarely the binding constraint on this family.
A short comparative table of the three stem shapes
The table below summarises the three stem shapes introduced above, with the verb signature, the typical wrong-answer pattern, and the tactic that most reliably converts the shape into a correct answer. It is intended as a working reference for the final review pass of any preparation block, not as a substitute for timed drill.
| Stem shape | Typical verb | Wrong-answer pattern | Reliable tactic |
|---|---|---|---|
| Single-claim | Strengthen / weaken / justify | Consistent with the case but not load-bearing | Re-state the claim in your own words; only an answer that touches the claim counts |
| Dual-claim | Best explains / most likely reason | True about one claim, silent on the other | Sketch both claims; reject any answer that does not mention both |
| Action-pivot | Should the manager / which response | Reasonable in the abstract, violates a stated constraint | Underline every stated constraint; reject any answer that breaks one |
Notice that the reliable tactic is the same shape in every row: identify the test-writer's target before evaluating any answer. This is the test-preparation principle that lifts Evaluating Business Scenarios from a verbal item into a structural item, and it generalises to roughly a third of the Reasoning section once the candidate internalises it.
Two worked examples of the reading moves in action
The first example is a single-claim case. A regional airline notes that it added two daily flights between two mid-size cities in the last quarter, that load factor on the new flights averaged 71 per cent, and that overall revenue on the route rose by 12 per cent. The case concludes that the additional flights were financially justified. The stem asks which of the following would most strengthen the argument. The reading moves play out in this order: the verb is "strengthen", the claim is the last sentence, the support is the 71 per cent and 12 per cent figures, and the gap is the assumption that the new flights did not cannibalise the existing flights. The correct answer will show that pre-existing flights retained their load factor after the new flights were added. The wrong answers will be true — 71 per cent is a respectable load factor, 12 per cent revenue growth is a respectable number — but they will not touch the cannibalisation gap. A candidate who reads the case without sketching it will see those respectable numbers and pick a respectable-sounding answer, losing the item to a true-but-not-useful choice.
The second example is a dual-claim case. A consumer-electronics retailer reports that its average ticket size rose by 8 per cent year over year, while its conversion rate fell by 3 per cent over the same period. The case concludes that the new merchandising plan, which emphasised premium product placement, was a success. The stem asks which of the following best explains why both the rise and the fall could be evidence of a successful plan. The reading moves: the verbs are "best explains" and "both", the first claim is the rise, the second claim is the fall, and the gap is the missing link that a single merchandising plan could produce both effects. The correct answer will argue that fewer visitors entered the store, but those who did were steered toward higher-margin items, so the average ticket rose and the conversion rate fell. The wrong answers will pick one side of the case — celebrating the rise as a win, or lamenting the fall as a loss — and will not address the dual-claim structure. A candidate who has not sketched both claims will, by choice C, have forgotten the fall, and will select a single-direction answer that the stem is not requesting.
Across both examples, the scoring implication is the same: the preparation strategy that yields the largest gain is not vocabulary drill, not timing drill, but argument-sketches drill. A candidate who can sketch 25 cases in a single sitting will see the dual-claim shape, recognise the action-pivot shape, and stop confusing the true with the useful. That is the scoring difference between a 645 candidate and a 705 candidate on this family, and the rest of the Reasoning section tends to follow.
How to integrate this family into a six-week preparation strategy
The Evaluating Business Scenarios family responds to a specific kind of practice. A candidate who drills 200 mixed Reasoning items will improve on average across the section, but a candidate who drills 60 Evaluating Business Scenarios items in a single block, while labelling the verb and sketching the argument for each, will improve disproportionately on this family. The reason is that the family is structurally narrow: there are six verbs, three shapes, and a small inventory of wrong-answer patterns. Drilling in a focused block forces the candidate to internalise that inventory, and the inventory is what generalises to test day.
A workable six-week block runs like this. In weeks one and two, the candidate completes 10 items per day, spends the first half of each session labelling the verb and sketching the case, and reviews every wrong answer against the pitfall taxonomy above. In weeks three and four, the candidate drops the labelling and the sketch, but logs a single sentence on the most likely pitfall that they would have hit. In weeks five and six, the candidate completes full-length timed Reasoning sections and tracks the per-family hit rate. A candidate who moves from a 55 per cent hit rate on Evaluating Business Scenarios in week one to a 75 per cent hit rate in week six is a candidate who will see a meaningful lift in their overall Reasoning score, because the family is large enough to swing the section's raw score by 2 to 3 points, which is the difference between one score band and the next.
What to do when none of the answers look right
Every candidate eventually meets an Evaluating Business Scenarios item where the four answers all look slightly off, and the case is not pointing to a clear winner. The default reaction is to pick the answer that the case is most sympathetic to, and that reaction is the one that loses the item. The better move is to re-read the stem and look for the one constraint you may have ignored. In my experience this usually resolves the question within 20 seconds: the constraint is almost always a word like "most", "likely", or "first", and the answer that violates it is the answer you were about to pick. The test-preparation principle is that a question with no clean answer is a question whose constraint you have not yet found.
For most candidates, the safe move on a stuck item is to pick the answer that addresses the test-writer's target, even if it does not address every detail of the case, and to flag the item for review. Under timed conditions, the cost of spending 40 extra seconds on a stuck item is higher than the cost of a 25 per cent chance of being wrong, because the time is borrowed from the next three items, where the candidate's expected value is higher. The exam format's adaptive design punishes inconsistency, and the disciplined move is to accept the 75 per cent answer and move on, returning to the item only if the section's remaining budget allows.
Conclusion and next steps. The Evaluating Business Scenarios family rewards candidates who treat the case as a small argument, the stem as a directed request, and the answer choices as a small inventory of consistent-but-not-load-bearing wrong answers. A six-week preparation strategy built around labelled verbs, four-part argument sketches, and pitfall-aware review will move most candidates from a 55 per cent to a 75 per cent hit rate on the family, which is the difference between a steady 645 and a defensible 705 on the GMAT Focus. TestPrep İstanbul's diagnostic assessment is a natural starting point for candidates who want a sharper preparation plan on Evaluating Business Scenarios specifically, and for tutors building a section-level plan around the Reasoning block.