8.1 Applying Rules To Facts

What Deductive Reasoning Measures

Deductive reasoning is the ability to take a general rule and apply it to a specific situation to reach a conclusion that is logically certain. The CJBAT, developed by Industrial/Organizational Solutions (IOS) and delivered through Pearson VUE for Florida criminal-justice academy entry, lists deductive reasoning among the cognitive competencies in Section III, which is administered as one timed block covering Written Comprehension, Written Expression, Inductive Reasoning, and Deductive Reasoning together.

IOS describes this skill as applying general rules to specific problems to produce logical answers. On the job, an officer uses it when reading Florida Statutes, county ordinances, agency policies, legal bulletins, and standard operating procedures, then applying that written rule to the case in front of them. The test recreates that task in miniature: it gives you a rule and a set of facts, then asks what conclusion follows.

The direction of reasoning is the defining feature. Deduction moves from the general to the specific — from a broad rule down to one particular case. (Inductive reasoning, tested in the next chapter, moves the other way, from specific observations toward a general pattern.) Keeping these straight matters, because the same passage can support a valid deduction and an invalid guess.

The General-To-Specific Test

A conclusion is a valid deduction only if it must be true whenever the rule and facts are true. Consider a sample rule and fact set written in CJBAT style:

Rule: A citation may be issued only if the officer personally witnessed the violation. Fact: Officer Reyes did not personally witness the violation; a bystander reported it afterward.

The deduction: Officer Reyes may not issue a citation for that violation. That conclusion is forced by the rule — the single required condition (personally witnessed) is not met, so the permitted result (issue a citation) cannot follow. An answer saying "Reyes should issue the citation because a violation occurred" sounds reasonable but is not supported, because the rule conditions the citation on personal observation, not on whether a violation happened.

Worked Example

Rule: Department policy states that any firearm taken into evidence must be logged within 24 hours of seizure and that an unlogged firearm cannot be released from the property room. Facts: Officer Tan seized a firearm at 9:00 a.m. Monday. It is now 8:00 a.m. Wednesday and the firearm has not been logged. A detective requests its release.

Reasoning: The policy has two parts. Part one (log within 24 hours) was violated — roughly 47 hours have passed with no log entry. Part two is the controlling rule for the question: an unlogged firearm cannot be released. The firearm is unlogged. Therefore the necessary conclusion is that the firearm cannot be released to the detective. Notice we do not need to decide what discipline Officer Tan faces or whether the evidence is admissible — the rule only addresses release, so the deduction stays there.

This discipline — answering exactly what the rule controls and nothing more — is the heart of the skill. Use this checklist on every item:

• Restate the rule in if/then form.
• List only the facts the prompt provides.
• Confirm every required condition is satisfied (or note which is not).
• Choose the conclusion that must follow.
• Reject any answer that only might be true.
• Reject any answer that relies on outside law or experience.

Because IOS says no prior criminal-justice experience is required, treat the police or corrections setting as flavor. The badge on the scenario does not give you extra rules — only the printed rule does. The candidate who reads the rule precisely and refuses to add anything will reliably out-score the candidate who reasons from what an agency "probably" does.

A Second Worked Example, And Why Necessity Beats Plausibility

Deductive items reward a specific mental move: hold the rule fixed, then ask whether the answer is forced rather than merely reasonable. A second example makes the difference concrete.

Rule: A visitor pass is issued only to a person who is on the pre-approved visitor list and who shows valid photo identification. Facts: Mr. Alvarez is on the pre-approved visitor list. He left his wallet at home and has no identification with him today.

The rule joins two requirements: being on the list and showing valid photo ID. Mr. Alvarez satisfies the first but not the second. Because both are required, the forced conclusion is that Mr. Alvarez may not be issued a visitor pass today. A plausible-sounding distractor — "He can be admitted because staff recognize him" — adds a fact (staff recognition) the rule never mentions. Recognition is not on the list of requirements, so it cannot satisfy the rule. The lesson repeats: the conclusion must follow from the stated conditions, not from what feels fair or workable.

This is why the exam frames deduction around the word must. Three flavors of answer commonly appear, and only one is correct:

• Must be true — forced by the rule and facts. This is the deductive answer.
• Could be true — consistent with the facts but not forced. Tempting, but wrong for a deduction.
• Cannot be true — contradicts the rule or a stated fact. Eliminate on sight.

When you slot each option into one of these three buckets, the correct choice usually announces itself. The skill is not raw intelligence; it is the patience to verify that an answer is required, not just attractive. Across Section III you will see this structure again and again — a short rule, a few facts, and four choices engineered so that the most natural-sounding one is frequently the trap. Train yourself to distrust 'reasonable' and trust 'required,' and these items become some of the most reliable points on the test.