4.3 Multi-Rule Scenarios & Constraint Stacking

Multi-Rule Scenarios & Constraint Stacking

Harder Applying Facts items on Exam #45-857 stack two or more printed rules in one stem. Your job is not to invent a "safety first" hierarchy from real-world policing. Your job is to evaluate each printed rule's conditions, then select the action that satisfies every applicable mandatory duty—and only those duties.

This section trains a stacking method, worked multi-rule scenarios, a scratch-paper constraint table, and the failure modes that steal points from candidates who read quickly but apply loosely.

Why Stacking Feels Harder Than Single-Rule Items

Single-rule items punish one mistake: missing an exception, misreading may vs must, or importing outside knowledge. Stacked items punish partial compliance: you correctly apply the vivid rule (often the safety-sounding one) while skipping a quieter second duty (notification, vouchering, radio restriction, escort count). The attractive wrong answer is usually the one that "mostly" follows the spirit of the stem.

OCA still requires the same discipline: all information needed is in the question. Real Penal Law elements, academy slogans, and "what a sergeant would want" are irrelevant unless printed.

Stacking Method (Four Steps)

1. Separate the rules. Number them R1, R2, R3 exactly as printed—even if they appear in one paragraph.
2. Evaluate each rule independently against a scenario checklist (who, where, when, what, documents, sequence).
3. Resolve interactions only using printed hierarchy language (notwithstanding, except when, after notifying, only if, unless).
4. If no hierarchy is printed, choose the option that satisfies all applicable mandatory rules and does not invent a tie-breaker.

Independent Evaluation Checklist

For each rule, ask:

• Does the scenario trigger this rule at all?
• If triggered, is the duty mandatory (must) or permissive (may)?
• Does any printed exception apply with all of its conditions present?
• What actions does this rule block?

Only after each rule has a Y/N trigger call should you look at answer choices.

Worked Stack A — Custody Movement + Radio Rule

R1 (given): "When moving a custody defendant through a public corridor, two officers must escort the defendant; one leads and one follows."
R2 (given): "Officers must not transmit defendant names over unencrypted radio."
Situation: One officer is available; sergeant radios "Bring Smith to Part B now."

Application:

A correct option typically waits for a second officer and uses a non-name descriptor or a landline/secure channel if the printed policy provides one. An option that moves alone "because the sergeant ordered speed" violates R1 unless R1 contains an emergency exception (it does not here). An option that broadcasts the name again to "confirm" violates R2. Releasing the defendant to walk alone invents a third policy that was never printed.

Teaching point: Urgency language in a radio call is not a printed exception to a two-officer escort rule.

Worked Stack B — Visitor Property + Evidence Tagging

R1: "Prohibited items found at screening must be refused entry or secured per the visitor's choice to discard or return to vehicle."
R2: "Any item that is potential evidence of a crime discovered at screening must be vouchered and the sergeant notified before the visitor leaves the checkpoint."
Situation: Screening finds an unlabeled pill bottle and a folding knife; visitor says "toss the knife, I'll keep the pills in my pocket." The stem states officers reasonably believe the pills are illicit.

Application:

• Knife → prohibited item → discard/return pathway under R1 (visitor may choose discard).
• Pills → potential evidence per the stem's belief language → R2 controls: voucher + sergeant notify before the visitor leaves.
• Visitor preference cannot override R2 when R2's condition is met.
• Letting the visitor trash both and enter immediately fails R2.
• Pocketing the pills fails R2.
• Automatic arrest based on "real Penal Law" is outside knowledge unless the printed rules require it.

Worked Stack C — Location Scope + Notification Hierarchy

R1: "Inside a courtroom in session, officers must seize recording devices used without a written judicial order and notify the sergeant immediately."
R2: "In public lobbies, officers must direct persons to stop recording and issue one warning before any seizure; notify the sergeant only if recording continues after the warning."
Situation: A person records on a phone in the lobby; stops after one warning.

Application: R1's courtroom seizure duty is not triggered—the location is lobby. R2 is triggered: warning already issued and recording stopped → no seizure and no sergeant notification under the printed lobby rule. The wrong answer often applies the stricter courtroom rule because seizure "feels right." That is a scope shift, not stacking skill.

Constraint Table (Build This on Scratch Paper)

If an answer choice performs a blocked action or skips a mandatory action, eliminate it—even if it would be smart in real life. If two rules both trigger and no hierarchy is printed, the surviving choice must satisfy both columns' mandatory actions.

Timing Tip for Stacked Items

Spend your first 20–30 seconds outlining the table above. Candidates who jump to choices often pick a response that satisfies the emotionally salient rule while violating a quieter clerical/notification rule printed second. Thirty seconds of structure is cheaper than a wrong click you never revisit.

Common Stack Failures (Tag Your Practice Misses)

Practice Prescription

Write pairs of odd, specific rules (even unrealistic ones). Build scenarios that tempt you to satisfy only the dramatic rule. Force a full constraint table before choosing. The exam rewards candidates who can hold two printed duties in working memory without blending them into a vague professional instinct.

Stacking is not "more law." It is more careful reading under time pressure—still using only the rules OCA prints in the stem.