5.4 Oral Directions: Sequencing, Conditionals & Drawing Conclusions

5.4 Oral Directions: Sequencing, Conditionals & Drawing Conclusions

[!NOTE] Where the points are actually lost. Capturing the officer's tasks, covered in the previous section, is the mechanical half of Oral Directions. The scored difficulty sits in the other half: the officer speaks tasks in one order but requires them in another, buries conditions inside them, attaches names and times to some but not others, and leaves the reason for an instruction unstated. POST tests all four of those explicitly — the questions cover the "order in which they are to be performed," the "details contained in the call," and the "interpretations and conclusions that may be drawn."

---

Spoken Order Is Not Required Order

Field officers talk the way people talk. They mention the important thing last, back up to add a condition, and put a "but first" in the middle of a sentence. The sequence you must report is the one the hinge words impose, not the sequence of the sentences.

[!TIP] Re-sort in the post-audio window. Do not attempt to reorder while the officer is still talking — you will miss the next task. Capture in spoken order with the hinge word recorded, then use the brief completion period POST provides to renumber the column. A short arrow drawn from row 4 up to row 1 is enough; you are not writing for anyone but yourself, and the notes are never scored.

A short illustration

"Get a supervisor rolling to my location. Before you do that, though, confirm with Records that the restraining order is still active — no point pulling a sergeant out here if it expired last month."

Spoken order: (1) supervisor, (2) confirm with Records. Required order: (1) confirm with Records, (2) supervisor — and the supervisor request is now conditional on the confirmation. A single "before you do that, though" has both reordered the list and attached a condition to it. Items are written on exactly this.

---

Conditional and Negative Instructions

Conditionals are the highest-yield trap on the subtest because the distractors are so clean: the test writer takes the correct action and pairs it with the wrong trigger, or presents it unconditionally.

+-------------------------------------------------------------------------------+
|                    ANATOMY OF A CONDITIONAL DISTRACTOR SET                    |
+-------------------------------------------------------------------------------+
| Spoken: "If the registration comes back stolen, start a tow and a second unit."|
+-------------------------------------------------------------------------------+
| A. Start a tow and a second unit.            <- condition stripped away        |
| B. If the registration is expired, start a   <- correct action, wrong trigger  |
|    tow and a second unit.                                                      |
| C. If the registration comes back stolen,    <- right trigger, wrong action    |
|    notify the watch commander.                                                 |
| D. If the registration comes back stolen,    <- CORRECT: trigger + action      |
|    start a tow and a second unit.               both intact                    |
+-------------------------------------------------------------------------------+

Negative instructions deserve their own mark in your notes. "Do not approach," "hold off," "don't clear him until," "no code three" — these are tasks too, and they are frequently the subject of an item. Write them with a slash or a capital NOT so a hurried glance during the question block cannot read them as positives. The most expensive error on this subtest is answering that a dispatcher should do the very thing the officer said not to do.

---

Detail Items: Attribution Beats Volume

Detail questions ask for a specific name, rank, extension, unit call sign, time or location. Candidates lose these not because they failed to hear the fact but because they recorded it somewhere it cannot be found again. Three habits fix it:

1. Attach, don't append. A time written next to the task it governs ("Ruiz off at 1700" beside the notify-Ruiz row) is retrievable; the same time floating in a margin is not.
2. Record ranks and roles with names. Items routinely offer the right surname with the wrong rank, or the right role attached to a different person. "Det. Ruiz" and "Sgt. Ruiz" are different answers.
3. Distinguish the two locations. Calls commonly contain the officer's current location and a second address — where a suspect went, where a witness lives, where a unit is being sent. Label them; do not assume the only address mentioned is the officer's.

---

Interpretation Items: Answer From the Call, Not From Dispatch Practice

The final question category asks what may be concluded — why an instruction was given, what the officer expects, what the situation amounts to. These reward inference but punish importation.

[!CAUTION] Plausible is not the same as supported. By this point in your preparation you will know a great deal about real dispatch practice: what a supervisor is normally sent to, when a second unit is standard, how evidence is normally protected. On an interpretation item, that knowledge produces attractive wrong answers. The question is what this officer's call supports. If the officer said to hold the technician at the curb and mentioned a lost print last time, the supported conclusion is evidence preservation. If the officer never gave a reason, the supported answer is the one that stays closest to what was said — not the one that sounds most professionally correct.

---

Advanced Worked Call

Simulated radio call (Unit 2-Lincoln-9 to Dispatch): "Dispatch, 2-Lincoln-9, I'm code four at the Fairview Apartments, 2200 block of Ashland. Start me a report number for a residential burglary. Before you do that though, run the name Marcus Delaney, D-E-L-A-N-E-Y, date of birth 3-14-91 — the reporting party says he's the ex-boyfriend and he may have an active protective order. If that order is confirmed active, get me a supervisor and a second unit out here; if it's expired or there's nothing, just the report is fine. Either way, have the crime scene tech call me on my cell before she heads over, I don't want her rolling out if the RP changes her mind about prosecuting. And let Sergeant Whitfield know I'll be tied up past end of watch at 1800."

Capture and re-sort

Spoken order                          Required order (post-audio re-sort)
1. report number, res. burglary   ->  1. run Marcus DELANEY, DOB 3/14/91
2. run DELANEY (BEFORE #1)             (protective order check)
3. IF order active: supv + 2nd unit    2. start report number, res burglary
   IF expired/none: report only        3. IF order ACTIVE -> supv + 2nd unit
4. crime scene tech CALL officer          IF expired/none -> report only
   on cell BEFORE she rolls           4. tech to CALL officer's cell BEFORE
5. advise Sgt. Whitfield: tied up         she responds  [ACTOR: tech]
   past EOW 1800                      5. advise Sgt. WHITFIELD re: past EOW
Loc: 2200 blk Ashland, Fairview Apts | Unit 2-L-9 | code four

Items this call supports

Every one of those five answers came out of the grid, and every one of the traps beside it is built from a specific capture failure: spoken order kept, actor recorded without the instruction, condition dropped, rank not written, real-world reasoning substituted for the call. Fix the capture and the items become mechanical.

---

A Note on Where This Sits in Your Score

Oral Directions is one subtest of eleven, and POST sums the eleven standard scores with equal weight. That cuts both ways. A poor showing here cannot sink an otherwise strong battery — but neither can a strong showing elsewhere buy it back cheaply, and there is no scoring reason to treat this subtest as lower priority than any other. The good news is that it is among the most improvable subtests on the battery, because almost all of its difficulty is a notation problem rather than an aptitude ceiling.