Study guide
8.5 Diagramming Simple Conditions
CJBAT Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Orientation To The Florida BAT/CJBAT
1.1 BAT and CJBAT Naming 1.2 FDLE/CJSTC Purpose 1.3 Law Enforcement vs Corrections Tracks 1.4 Exemptions and Who Still Needs the Test 1.5 ATMS Official-Result Concept 1.6 Study Plan Overview
2 Registration, Fees, ID, And Test-Site Rules
2.1 Pearson VUE Account and BAT Candidate ID 2.2 $39 Fee and Non-Refundable Rules 2.3 Florida-Only Testing 2.4 Cancellation, Rescheduling, Absence, and Weather 2.5 Two-ID Requirement and Matching Legal Name 2.6 Test-Room Policies and Misconduct
3 Exam Structure, Timing, Passing, And Retakes
97 Total Items And 1.5 Hours Section I Timing And Role Section II Picture-Memory Timing Section III One-Hour Cognitive Section Passing Rule, Pass/Fail Results, And ATMS Score Validity And Retake Limits
4 Behavioral Attributes And Professional Judgment
Official Scope Of Behavioral Attributes Integrity And Honesty As Study Themes Professionalism And Public Trust Interpersonal Judgment In Scenarios Self-Control, Adaptability, And Dependability Avoiding Extreme Or Self-Serving Choices
5 Memorization And Visual Recall
What Section II Measures One-Minute Picture Review Strategy Detail Categories: People, Vehicles, Location, Direction, Sequence Chunking And Mental Labeling Avoiding Invented Details Timed Recall Drills
6 Written Comprehension
Reading Only The Provided Passage Main Idea And Detail Questions Sequence, Inference, And Purpose Law-Enforcement And Corrections Context Without Outside Assumptions Eliminating Unsupported Choices Pacing Within Section III
7 Written Expression
7.1 Clear Sentences In Section III 7.2 Grammar And Subject-Verb Agreement 7.3 Punctuation And Complete Thoughts 7.4 Pronoun And Modifier Clarity 7.5 Report-Style Precision 7.6 Choosing The Least Ambiguous Wording
8 Deductive Reasoning
8.1 Applying Rules To Facts 8.2 If/Then And Must/May Logic 8.3 Policy-Style Questions 8.4 Separating Stated Facts From Assumptions 8.5 Diagramming Simple Conditions 8.6 Common Trap Answers
9 Inductive Reasoning
What Inductive Reasoning Measures Patterns, Trends, And Hypotheses Evidence-Based Conclusions Avoiding Overgeneralization Comparing Cases And Details Mixed Practice Strategy
10 Law Enforcement And Corrections Scenario Differences
Selecting CJBATLEO Vs CJBATCO Law Enforcement Contexts Corrections Contexts Same Abilities, Different Setting No Previous Experience Required Using Only Provided Materials
11 Full-Length Practice Strategy And Remediation
Building A Realistic Practice Frame Timed Blocks And Pacing Records Diagnostics After A Full Practice Session Remediation Cycles By Competency Retake Rules And Study Decisions From Practice To The Next Official Step
12 Final Review And Test-Day Readiness
Final-Week Review Plan ID Confirmation And Arrival Checklist Test-Room Rules And Misconduct Pacing And Stress Control On Test Day Results, ATMS, And Score Validity Route Review And Next Steps
8.5 Diagramming Simple Conditions
Key Takeaways Explain This Topic AI
A diagram is a fast, compact version of a rule that keeps conditions and results organized while you compare answer choices.
Arrows capture if/then direction; checklists capture multi-condition 'and' rules; columns separate categories or tracks.
Because deductive reasoning shares the Section III timer, a diagram must be quick — a few symbols, not a full chart.
A diagram must preserve the rule exactly; if your diagram and the prompt disagree, the prompt always wins.
Diagrams especially help with chained conditions, where one rule's result becomes another rule's condition.
Last updated: June 2026
Turn Rules Into Small Maps
A diagram is a short visual version of a rule — an arrow, a checklist, or a two-column note. Its only purpose is to keep the rule from slipping out of mind while you weigh four answer choices. It is not art, and it is not an official source; it is a memory aid that must mirror the rule precisely.
Deductive Reasoning shares the Section III time block with Written Comprehension, Written Expression, and Inductive Reasoning. Because that time is shared, your diagram must be fast . If sketching it takes longer than carefully rereading the item, skip it. Most CJBAT rules need only a few symbols.
Three Quick Diagram Forms
Arrows capture if/then direction. For a rule like "If a report is incomplete, the supervisor returns it," write: incomplete report -> supervisor returns it . The arrow points one way, reminding you not to reverse the rule (returning a report does not prove it was incomplete).
Checklists capture multi-condition "and" rules. For "An officer may release evidence only if it is logged, photographed, and signed out," draw three boxes: [ ] logged [ ] photographed [ ] signed out . The release is authorized only when all boxes are checked.
Columns capture separate categories or tracks. When a rule treats two groups differently, a side-by-side note prevents you from carrying a condition into the wrong group.
Rule type Diagram form Quick example
If/then A -> B Incomplete report -> returned.
Either condition A or B -> C Late OR no ID -> not admitted.
Multiple requirements Checkboxes Logged, photographed, signed out.
Separate categories Two columns LEO scenario vs corrections scenario.
Chained conditions A -> B -> C Failed test -> remediation -> retest.
Worked Example: Chaining Conditions
Some items hide a chain , where the result of one rule becomes the condition of the next. Diagramming the chain prevents you from skipping a link.
Rules: (1) If a recruit fails the physical assessment, the recruit is assigned to remediation. (2) If a recruit completes remediation, the recruit may attempt the reassessment. (3) Only a recruit who passes the reassessment continues to the next phase. Facts: Recruit Owens failed the physical assessment and completed remediation. The prompt does not say whether Owens passed the reassessment.
Diagram the chain: failed -> remediation -> (complete) -> may reassess -> (pass) -> next phase . Owens has moved along the chain to may attempt the reassessment . But the final link — passing the reassessment — is not established by the facts. So the only supported conclusion is that Owens may attempt the reassessment ; you cannot conclude Owens continues to the next phase, because the prompt never says he passed. The diagram makes the missing link obvious.
Diagram carefully:
Keep the original rule's wording in mind beside your sketch.
Draw arrows only in the direction the rule states.
Use checkboxes when every condition must be met.
Use columns when categories or tracks differ.
For chains, draw every link and stop where the facts stop.
Add no facts to the diagram that the prompt did not give.
If your diagram seems to conflict with the prompt, the prompt controls — redraw the diagram, don't bend the rule. A good diagram is simply the rule preserved in a smaller, faster form.
Grids For 'Who-Gets-What' And Truth Tables For Yes/No
Two more diagram forms handle the trickier deductive items efficiently. The first is a grid (matching) chart for prompts that distribute several outcomes across several people, items, or categories. The second is a mini truth check for prompts that hinge on a single condition being met or not.
Use a grid when a prompt assigns attributes. Suppose three recruits are each assigned to one station, and the rules say "Adams is not at the range," "Brooks is at the classroom," and "each recruit is at a different station." A small three-by-three grid lets you mark Brooks at the classroom, eliminate the classroom for Adams and Carter, mark Adams off the range, and deduce by elimination that Adams is at the gym and Carter is at the range . Without the grid, holding three constraints in memory invites error; with it, the answer falls out mechanically.
- Range Classroom Gym
- Adams No No Yes
- Brooks No Yes No
- Carter Yes No No
Use a quick yes/no check when a prompt turns on whether one condition holds. Lay the condition against the result: if the condition is met, mark the result that follows; if it is not, mark that the result is not triggered. For "a pass is valid only if signed," an unsigned pass is simply invalid — one line of reasoning, no chart needed.
A short menu of when to use each tool:
Arrow — a single if/then rule; track direction.
Checklist — one rule, several 'and' conditions.
Columns — two categories or tracks treated differently.
Chain (A->B->C) — results that feed into later conditions.
Grid — several outcomes matched across several subjects.
Yes/No check — one condition decides one result.
The meta-rule for all of them is the same: a diagram only ever records the prompt's information in a more scannable shape. It never adds, never reverses, and never outranks the printed rule. Choose the lightest tool that fits the item, draw it in seconds, and let it carry the constraints so your attention stays on selecting the conclusion that must follow. Under the shared Section III clock, the candidate who diagrams efficiently spends thinking time on the logic rather than on re-reading the same constraints three times.