7.1 Problem-Solving Format: Scenarios and Follow-Up Questions
Key Takeaways
- Section B: Police Problem-Solving presents 30 questions built from short written scenarios or simple maps, and a single scenario is often followed by more than one four-option question drawing on the same shared facts
- Read the full scenario once, start to finish, and extract the who/what/where/when/task facts before you look at any of the four answer options
- When one scenario supports multiple linked questions, the fact base you build for the first question carries over to every later question tied to that scenario, so re-deriving it from scratch each time wastes time you do not have
- Reading answer options before finishing the scenario invites anchoring - a plausible-sounding option can quietly reshape your memory of what the scenario actually said
- Each linked question usually tests a different angle on the same facts - priority of action, a specific detail, or a map/direction question - so the correct answer depends on exactly what that individual stem asks, not on the scenario in general
Problem-Solving Format: Scenarios and Follow-Up Questions
Quick Answer: Section B presents 30 questions built from short written scenarios or simple maps. A single scenario is frequently followed by more than one four-option question, all drawing on the same underlying facts. The reliable approach is to read the scenario once, all the way through, and pull out the who/what/where/when/task facts before glancing at any option - then reuse that same fact base for every question tied to that scenario, rather than starting over each time.
How a Section B Item Is Actually Built
Every Section B item begins with a stimulus - either a short paragraph describing an incident, or a simple diagram showing streets, an intersection, or the relative positions of people and vehicles. That stimulus is followed by a question stem and four candidate answers. What makes Section B feel different from Section A is that the stimulus is frequently reused: one scenario paragraph can sit above two or three separate questions, each asking about a different piece of the same situation, before the next scenario begins.
| Element | What appears | What you do with it |
|---|---|---|
| Scenario | A paragraph describing an incident, or a simple map | Read it fully once before looking at any option |
| Question stem | One specific task tied to the scenario | Identify exactly what this particular question is asking |
| Four options | Candidate responses, facts, or directions | Compare each one against the facts you already extracted |
Because the scenario is shared, a common and costly mistake is treating every question underneath it as a fresh puzzle and re-reading the whole paragraph from the top each time. That habit burns seconds you cannot get back on a test averaging roughly 28 seconds per item across the whole exam. The scenario does not change between linked questions - only the specific thing being asked about it changes.
What a Multi-Question Scenario Group Actually Tests
When a single scenario supports more than one question, the questions are rarely asking the same thing twice in different words. Instead, each one usually targets a different skill layered on top of the identical facts.
| Question angle | Example of what it asks | Skill it is really testing |
|---|---|---|
| Priority of action | What should the officer do first, given everything described | Judgment and sequencing |
| Detail recall or contradiction | Which statement is NOT supported by the scenario | Careful, literal reading |
| Map or direction | Which route, direction, or location matches the scenario | Spatial reasoning |
| Applying a stated rule | Given a short rule in the scenario, which action follows it | Rule application |
Recognizing which angle a specific stem is testing matters, because an answer that would be correct for a "what should happen first" question can be entirely wrong for a "which detail is missing" question built on the exact same paragraph. Reading the question stem carefully, every single time, is not optional busywork - it is the difference between answering the question that was actually asked and answering a question you assumed was being asked because it resembled the last one.
The Trap of Reading Options Before Finishing the Scenario
Under time pressure, it is tempting to skim the first sentence or two of a scenario and then jump straight to the four options, hoping the options themselves will clarify what matters. This backfires more often than it helps, for a specific reason: the wrong options in Section B are usually written to sound reasonable on their own. An option that says "the officer should immediately enter the building to check for the alarm's source" reads as confident and plausible in isolation - it only becomes clearly wrong once you have registered a detail earlier in the scenario, such as the door already standing open with no sign of forced entry, or a witness reporting movement inside. Read the options before that detail has registered, and the confident-sounding wrong option can quietly overwrite the more cautious, correct reading of the scene in your mind. This is anchoring, and it is one of the most reliable ways to convert an easy scenario into a missed question.
The fix is procedural, not a matter of willpower: finish reading the entire scenario, build your fact base, and only then look at the four options - treating each option as a claim to verify against the facts you already have, rather than as a hint about what the facts might be.
A Five-Category Fact Extraction Framework
Before looking at any option, sort what the scenario tells you into five categories. This does not need to be written out - assume a bare desk, since eProctor does not permit papers by default - but running the five categories explicitly in your head forces a complete first pass through the facts instead of a partial one.
| Category | What to capture | Why it matters |
|---|---|---|
| Who | People and roles present (caller, witness, officer, subject) | Determines whose account or position is being described |
| What | The core event or events, in the order given | Determines what actually happened, not what is implied |
| Where | Locations and relative positions | Needed for map items and for judging feasibility of actions |
| When | Times, sequence words, and elapsed intervals | Needed for ordering events and timing-based questions |
| Task | What the scenario or the officer is explicitly being asked to accomplish | Anchors which details are relevant to the question that follows |
Worked Example: Applying the Framework
Consider an original scenario built the way a Section B item might present one: "At 6:50 p.m., a store clerk calls to report that a customer knocked over a display rack and left without paying for two items, walking east on Birch Street toward the plaza. The clerk did not see a vehicle and did not see a weapon. Two minutes later, a second call reports a man matching that description now walking calmly along the same block."
Applying the framework before touching any options:
- Who: the clerk (caller/witness), the customer/subject, a second caller
- What: a theft of two items and a knocked-over display; no weapon seen; subject now walking calmly
- Where: Birch Street, heading east toward the plaza
- When: 6:50 p.m., with a second, consistent report two minutes later
- Task: whatever the specific question below the scenario actually asks - for example, the most appropriate response, or the most likely current location
With the fact base built, a question asking for the most appropriate immediate response can be evaluated directly: any option describing an armed, high-risk confrontation is inconsistent with "no weapon seen" and "walking calmly," while an option matching a calm, low-risk approach and a description broadcast to other units fits the extracted facts. A different question attached to the same scenario - say, one asking which direction to search first - can reuse the identical "Where" and "When" facts without rebuilding them, because they were already captured on the first pass.
Why Reuse, Not Repetition, Wins on Pace
The practical payoff of this method shows up most clearly on the second and third questions in a linked group. The first question in a scenario group typically costs more time, since it requires the full read-and-extract pass. Every subsequent question tied to that same scenario should cost noticeably less time, because the fact base is already built - the only new work is understanding what the new stem is asking and checking the four options against facts you already have on hand. Test-takers who instead reread the full paragraph from scratch for every linked question are effectively paying the full reading cost multiple times over for the same scenario, which is exactly the kind of pacing leak that turns a manageable 30-question section into a rushed one. Because you should not count on having scratch paper, practise holding that fact base in working memory: read once, sort the facts into the five categories mentally, and reuse them across every question tied to that scenario.
How is a single Police Problem-Solving scenario typically used across the questions built on it?
Why is it recommended to finish reading a scenario completely and extract its facts before looking at any of the four answer options?
A caller reports that a man wearing a green jacket knocked over a mailbox on Birch Street at 6:15 p.m. and walked north toward the plaza. Which single additional fact, if it were added to this scenario, would most likely change which response option is correct?
A scenario is followed by three separate linked questions. After correctly extracting the facts for the first question, what is the most efficient approach for the second and third questions attached to that same scenario?