Study guide

8.3 Analysing Scenarios and Tracking Conditions

USA Hire Assessment OPM Federal Clerical and Administrative Hiring Assessment

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: How USA Hire Works

1.1 What USA Hire Is and Which Assessments You Will Take 1.2 From USAJOBS Application to Assessment Invitation 1.3 The Testing Window, Deadlines, and Automatic Ineligibility

2 Chapter 2: Cut Scores, Test-Day Mechanics, and Preparation

2.1 Cut Scores, the Cut-Score Job Series, and Referral 2.2 The Five-Minute Item Clock, RECORD ANSWER, and No Review 2.3 Calculator, Scratch Paper, Devices, and the Testing Environment 2.4 Score Retention, Reuse, and the One-Year Retest Rule 2.5 Official Practice Assessments and Reasonable Accommodation

3 Chapter 3: Occupational Reading — The Core Method

3.1 The Closed-Text Principle and the Five-Minute Reading Method 3.2 Locating Stated Facts, Conditions, and Exceptions 3.3 Vocabulary in Context, Word Parts, and Precise Wording

4 Chapter 4: Occupational Reading — Tables, Application, and Inference

4.1 Reading Tables, Schedules, and Rate Charts 4.2 Applying Written Rules to Specific Situations 4.3 Supported Conclusions vs. Unsupported Assumptions

5 Chapter 5: Occupational Math — Arithmetic and Number Sense

5.1 Arithmetic, Word Problems, and Translating Words into Operations 5.2 Fractions 5.3 Decimals, Money, and Rounding 5.4 Estimation, Calculator Discipline, and Checking Your Work

6 Chapter 6: Occupational Math — Percentages and Proportional Reasoning

6.1 Percentages: Finding the Part, the Whole, and the Rate 6.2 Percent Increase, Percent Decrease, and Reverse Percentages 6.3 Ratios, Proportions, and Unit Rates

7 Chapter 7: Occupational Math — Algebra, Geometry, and Probability

7.1 Basic Algebra 7.2 Basic Geometry and Measurement 7.3 Basic Probability

8 Chapter 8: Occupational Reasoning

8.1 What the Occupational Reasoning Assessment Actually Asks 8.2 Drawing Logical Conclusions from Given Statements 8.3 Analysing Scenarios and Tracking Conditions 8.4 Evaluating Arguments: Assumptions, Flaws, and Support

9 Chapter 9: Occupational Judgment

9.1 The Video Format: Most and Least Effective 9.2 How to Judge Effectiveness 9.3 Recurring Scenario Families and How to Work Them

10 Chapter 10: Occupational Interaction — Format and Personal Effectiveness

10.1 The Untimed Interaction Assessment and Its Response Scales 10.2 Accountability and Self-Management 10.3 Attention to Detail and Learning 10.4 Flexibility and Stress Tolerance

11 Chapter 11: Occupational Interaction — Working With Others

11.1 Customer Service and Interpersonal Skills 11.2 Integrity/Honesty 11.3 Teamwork and Influencing/Negotiating

12 Chapter 12: Other USA Hire Assessments You May Be Assigned

12.1 The Early Career Talent Assessment (ECTA) 12.2 Premium, Supervisory, and Custom USA Hire Assessments

8.3 Analysing Scenarios and Tracking Conditions

Key Takeaways Explain This Topic AI

Scenario items give a situation plus conditions and ask what follows, so the work is tracking conditions rather than manipulating abstract logic.

Build a table of entities against properties and fill in what the conditions establish.

Distinguish what is established, what is ruled out, and what remains undetermined.

A question asking what could be true has a different answer from one asking what must be true.

Facts in the scenario that no condition refers to are usually deliberate distractors.

Last updated: September 2026

8.3 Analysing Scenarios and Tracking Conditions

Quick Summary: OPM's description of the Occupational Reasoning Assessment includes analyze scenarios . These items present a situation with several entities and conditions and ask what follows. They are less about formal logic than about bookkeeping : recording what each condition establishes and, crucially, what it leaves open. OPM's tip to use lists or visuals to organise the information provided is aimed at exactly this.

The three states of any claim

Every claim about a scenario is in one of three states, and keeping them distinct is the whole technique.

  • State Meaning Notation
  • Established The conditions require it ✓
  • Ruled out The conditions forbid it ✗

Undetermined The conditions neither require nor forbid it ?

Most wrong answers on scenario items are claims in the third state presented as though they were in the first. A candidate who does not track the difference will find undetermined options genuinely persuasive, because they are consistent with everything given.

The tracking table

When a scenario involves entities with properties, draw a grid. Entities down the side, properties across the top.

Scenario. Four case files — W, X, Y and Z — are each assigned to exactly one of two teams, Intake or Review. Files assigned to Review are always digitised. W and X are on the same team. Y is on Review. Z is not digitised.

Question. Which must be true?

Set up: File Team Digitised

W ? ?

X ? ?

  • Y Review ✓ (Review -> digitised)
  • Z ? ✗ (given)

Now apply the conditions.

Z is not digitised. Review files are always digitised, so Z cannot be on Review. Z is on Intake .

W and X are on the same team. Undetermined which team, but they match.

Y is on Review , therefore digitised.

Updated: File Team Digitised

W ? (= X) ?

X ? (= W) ?

  • Y Review ✓
  • Z Intake ✗

What must be true? That Z is on Intake, and that Y is digitised. What is undetermined ? Whether W and X are on Intake or Review — the conditions do not settle it, only that they match.

An option saying "W is on Intake" is a could-be-true dressed as a must-be-true. It is perfectly consistent with everything stated, which is precisely what makes it a good distractor.

Chaining conditions to force a result

The Z step above is the characteristic move: a condition about one property (digitised) forces a conclusion about another (team) through a stated rule. Look for these bridges:

Find the rule linking two properties (Review → digitised).

Find the entity where one of those properties is fixed (Z is not digitised).

Apply the contrapositive (not digitised → not Review).

That is Section 8.2's contrapositive doing practical work.

Must be true, could be true, cannot be true

Read the question stem with care; these three demand different answers from the same grid.

  • Stem Correct answer is…
  • Which must be true? Marked ✓ — forced by the conditions
  • Which could be true? Marked ✓ or ? — anything not ruled out
  • Which cannot be true? Marked ✗ — contradicts a condition
  • Which must be false ? Same as cannot be true

A "could be true" question makes undetermined claims correct , which inverts the usual instinct. This is why the stem must be read before the options and again before submitting.

A second worked example

Scenario. A unit schedules three tasks — auditing, filing and training — on three consecutive days, one per day. Training is not scheduled on the first day. Auditing is scheduled the day immediately before filing.

Question. Which must be true?

The pairing condition means auditing and filing occupy consecutive days in that order. Two placements are possible: days 1–2 or days 2–3.

Auditing day 1, filing day 2 → training day 3. Training is not on day 1. ✓ Consistent.

Auditing day 2, filing day 3 → training day 1. But training cannot be on day 1. ✗ Eliminated.

Only one arrangement survives: auditing day 1, filing day 2, training day 3.

Here the conditions determine everything, so every claim is either ✓ or ✗ and nothing is undetermined. Working the small number of possible arrangements to exhaustion is the reliable method when the entity count is low.

The irrelevant-fact trap

As in Section 4.2, scenarios often contain details no condition refers to — a file's date of receipt, an employee's length of service. If no condition mentions it, it cannot force anything. After listing the conditions, cross off any scenario detail that appears in none of them.

Procedure

List the entities and the properties in play.

Draw the grid and enter directly stated facts.

Apply each condition , including contrapositives, and mark ✓, ✗ or ?.

Enumerate possibilities when a condition allows only a few arrangements.

Read the stem — must, could, or cannot — and select accordingly.

Verify that your chosen option matches the marks in your grid rather than your general sense of the situation.