8.3 Policy-Style Questions

Treat A Policy As A Map Of Conditions

A policy-style question gives a written rule and a specific case, then asks what the policy requires. This is the most job-realistic deductive format, because officers and corrections staff apply written policies daily. IOS frames the on-the-job skill exactly this way: reading statutes, ordinances, and standard operating procedures and applying them to the situation at hand. On the test, the policy is printed in the prompt — you supply none of it from memory.

The first task is to identify every required condition. Some rules have a single condition; many have several joined by "and." When a rule lists conditions with "and," all of them must be satisfied before the result follows. Meeting three of four is not enough. When conditions are joined by "or," satisfying one is generally enough — but read whether the rule means "either" or "at least one," because that changes the analysis.

Worked Example: A Multi-Condition Rule

Policy: An officer may conduct a vehicle inventory search only when all of the following are true: (a) the vehicle has been lawfully impounded, (b) the search follows standardized department procedure, and (c) the officer documents the inventory on the approved form. Facts: Officer Cole's vehicle was lawfully impounded and she followed standardized procedure, but she did not complete the approved inventory form.

Reasoning: The rule joins three conditions with "and," so an inventory search is authorized only when all three are met. Conditions (a) and (b) are satisfied; condition (c) is not. Therefore the necessary conclusion is that the inventory search does not satisfy policy as conducted. A trap answer might say "the search is valid because the vehicle was lawfully impounded" — true as to one condition, but the rule requires all three.

Worked Example: An Exception Clause

Policy: Visitors must pass through the metal detector before entering the secure area, unless they are sworn law-enforcement officers presenting valid credentials. Facts: A sworn deputy presents valid credentials and asks to bypass the metal detector. A civilian contractor with a vendor badge makes the same request.

Reasoning: The exception is narrow — it covers sworn law-enforcement officers presenting valid credentials and no one else. The deputy fits the exception, so she may bypass the detector. The civilian contractor does not fit the exception (a vendor badge is not sworn-officer credentials), so the main rule controls and the contractor must pass through the detector. The two cases get opposite answers from the same policy because one falls inside the exception and one does not. A trap answer would extend the exception to anyone with an official-looking badge.

Use this policy checklist:

• State the main rule and its required result.
• List every condition; note whether they are joined by 'and' or 'or'.
• Identify any exception and read its exact limits.
• Match the specific facts to the conditions and exception precisely.
• Reject choices that satisfy only some 'and' conditions.
• Reject choices that stretch an exception beyond its wording.

Policy questions also test the discipline to resist convenience and sympathy. The sympathetic outcome for a candidate, an inmate, or a visitor is irrelevant if the policy's conditions are not met. Apply the rule as written; if an answer depends on a condition the policy does not contain, it is not a necessary deduction.

Ranked Rules, Definitions, And Procedural Order

Some policy items add a wrinkle: the prompt supplies more than one rule, and you must decide which one governs. When rules could conflict, look for ordering language — "notwithstanding," "except as provided in," "this rule takes precedence," or a numbered priority. The higher-priority rule controls the case even if a lower rule seems to point the other way.

Worked example. Rule A: "Personal property is returned to an arrestee at release." Rule B: "Notwithstanding Rule A, any item held as evidence is not returned until the case is closed." Fact: "At release, the arrestee requests a phone that has been logged as evidence in an open case." Rule B's "notwithstanding" language makes it the controlling rule, so the forced conclusion is that the phone is not returned at release. Rule A would have suggested the opposite, which is exactly the trap.

Policy prompts also frequently provide definitions you must apply literally. If a prompt defines a "business day" as Monday through Friday excluding holidays, then a deadline of "three business days" cannot be satisfied by counting a weekend. Plug the supplied definition in mechanically; do not substitute the everyday meaning of the word.

Procedural order is another tested dimension. If a policy says an officer must first secure the scene, then photograph evidence, then collect it, a fact pattern in which evidence was collected before photographs were taken violates the order — and a question asking 'what was done improperly' is answered by the out-of-sequence step. Read ordered procedures as a chain in which each step is a precondition for the next.

Combining these habits — spotting overrides, applying supplied definitions literally, and respecting procedural order — lets you handle the more elaborate policy items without ever importing a rule the prompt did not give you.