4.2 Applying Written Rules to Specific Situations

4.2 Applying Written Rules to Specific Situations

Quick Summary: OPM's definition of Reading Comprehension ends with a clause that is easy to skim past: applies what is learned from written material to specific situations. That clause describes a whole item type. You are given a set of written rules and a specific case, and asked what the rules produce for that case. These are the hardest Occupational Reading items and the most rewarding to prepare for, because they are decided by procedure rather than by insight.

The anatomy of an application item

An application item has three parts:

1. A rule set — usually three to six statements, often including at least one exception.
2. A fact pattern — a short scenario describing a specific case.
3. A question — what happens, what is the amount, is the person eligible, what must they do next.

Your job is mechanical matching. Nothing in the item requires you to know what a reasonable outcome would be. It requires you to determine what the stated rules produce.

The ordered procedure

Run these five steps in sequence. The order matters, because checking eligibility after computing an outcome wastes time and invites errors.

Step 1 — List the rules on scratch paper. One line each. Include the exception rules; they are where items are decided.

Step 2 — List the facts from the scenario. One line each, in the scenario's own terms.

Step 3 — Check threshold eligibility. Many rule sets begin with a gate: who or what the rules apply to at all. If the case does not clear the gate, nothing downstream matters. Section 3.2's worked example turned on exactly this — an incomplete request never entered the queue, so the urgent rule was moot.

Step 4 — Check exceptions before applying the general rule. Exceptions override. If an exception applies, the general rule's outcome is wrong even though it is stated in the passage.

Step 5 — Read off the operative outcome and match it to an option.

Worked example

Rules. Employees may request an alternate work schedule if they have completed six months of continuous service. Requests are submitted to the immediate supervisor. A request is approved unless it conflicts with a documented coverage requirement for the employee's unit. Units designated as public-facing have a documented coverage requirement between 9:00 a.m. and 3:00 p.m. An approved schedule takes effect at the start of the next pay period.

Scenario. Dana has worked continuously for eight months in a unit designated as public-facing. Dana requests a schedule of 7:00 a.m. to 3:30 p.m. and submits the request to the immediate supervisor. Dana has completed all required training.

Question. What is the outcome of Dana's request?

Rules on paper:

R1 gate      6 months continuous service required
R2 process   submit to immediate supervisor
R3 default   approved UNLESS conflicts with documented coverage requirement
R4 exception public-facing units: coverage required 9:00 a.m. - 3:00 p.m.
R5 timing    approved schedule starts next pay period

Facts on paper:

F1 8 months continuous service
F2 public-facing unit
F3 requested hours 7:00 a.m. - 3:30 p.m.
F4 submitted to immediate supervisor
F5 completed all required training

Now the sequence:

• Gate (R1 vs F1). Eight months exceeds six. Dana clears the gate.
• Process (R2 vs F4). Submitted correctly.
• Exception (R4 vs F3). The unit is public-facing, so coverage is required 9:00 a.m. to 3:00 p.m. Dana's requested schedule runs 7:00 a.m. to 3:30 p.m., which covers the entire 9:00–3:00 window.
• Default (R3). No conflict with the coverage requirement, so the request is approved.
• Timing (R5). It takes effect at the start of the next pay period.

Answer: approved, effective the start of the next pay period.

Two things that example demonstrates

Irrelevant facts are planted deliberately. F5 — Dana completed all required training — is never referenced by any rule. It is there to see whether you will invent a training requirement. When a fact in the scenario is not mentioned by any rule, it does not affect the outcome. A quick discipline: after listing the rules, cross off any fact no rule refers to.

The exception must actually be tested, not just noticed. A candidate who reads "public-facing unit" and stops has half the analysis and will select "denied". The exception establishes a coverage window; the requested schedule has to be checked against that window. It happens to satisfy it.

When a required fact is missing

Sometimes the scenario is silent on something a rule requires. If the rules say approval requires supervisory confirmation and the scenario never mentions confirmation, you cannot assume it happened.

The correct reading is that the rule's condition is not established, so its outcome cannot be asserted. Options that state a definite outcome requiring the missing fact are unsupported. This connects directly to Section 4.3, where the distinction between what follows from the text and what merely might be true is developed in full.

A checklist for application items

• Did I list every rule, including exceptions?
• Did I check the eligibility gate before anything else?
• Did I test each exception against the facts rather than just noting it exists?
• Did I cross off facts no rule refers to?
• Is any rule condition left unestablished by the scenario?
• Does my answer address the question asked — outcome, amount, next step, or eligibility?