Study guide
5.3 Reading Tables, Bar Graphs & Pie Charts for Trend Conclusions
National Criminal Justice Officer Selection Inventory NCJOSI²
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: NCJOSI Overview, Test Mechanics & Pacing Strategies
1.1 Exam Architecture: Cognitive vs. Non-Cognitive Structure, Administration & Scoring 1.2 Test Pacing Tactics (150 Minutes for 200 Items), Time Management & Guessing Strategies 1.3 Hiring Agency Standards: Cut Scores, Civil Service Banding, Background Checks & Polygraph Integration
2 Chapter 2: Verbal Comprehension & Police Document Analysis
2.1 Reading Police Department Policies, Standard Operating Procedures (SOPs), & Directives 2.2 Factual Extraction from Incident Reports, Affidavits, & Witness Statements 2.3 Critical Inference, Identifying Implicit Details, & Avoiding Assumptions in Investigations
3 Chapter 3: Verbal Expression, Grammar & Police Report Mechanics
3.1 Police Vocabulary, Common Confusables, & High-Frequency Spelling in Law Enforcement 3.2 Sentence Structure, Syntax, Modifiers, & Active Voice in Official Documentation 3.3 Punctuation, Capitalization, Pronoun Case, & Mechanical Accuracy in Field Notes
4 Chapter 4: Deductive Reasoning & Policy Application
4.1 Applying Legal Rules, Statutory Thresholds, & Probable Cause Standards 4.2 Conditional Logic (If/Then, Modus Ponens, Modus Tollens) in Officer Decision-Making 4.3 Syllogisms, Categorical Logic, & Valid Deductions Under Pressure
5 Chapter 5: Inductive Reasoning, Pattern Recognition & Graph Interpretation
5.1 Trend Identification & Connecting Elements Across Disparate Incident Scenarios 5.2 Modus Operandi (MO) Analysis & Criminal Pattern Synthesis 5.3 Reading Tables, Bar Graphs & Pie Charts for Trend Conclusions
6 Chapter 6: Problem Sensitivity & Situational Hazard Recognition
6.1 Identifying Imminent Operational Hazards, Scene Inconsistencies, & Red Flags 6.2 Officer Safety Traps, Ambush Awareness, & Tactical Discrepancy Detection 6.3 Prioritizing Calls for Service & Emergency Dispatch Triage
7 Chapter 7: Spatial Orientation, Map Reading & Route Planning
7.1 Compass Bearings, Cardinal Directions, & Grid Reference Navigation 7.2 Route Optimization, One-Way Street Systems, & Dead-End Avoidance Under Emergency Driving 7.3 Spatial Relation Puzzles, Floor Plans, & Tactical Interior Building Clearing Navigation
8 Chapter 8: Information Gathering, Selective Attention, Flexibility of Closure & Visualization
8.1 Information Gathering: Sequencing Statements & Linking Witness Accounts 8.2 Selective Attention: Matching Letter, Number & Symbol Strings Exactly 8.3 Flexibility of Closure: Finding a Known Shape Hidden in a Figure 8.4 Visualization: Recognizing a Person or Object After It Changes
9 Chapter 9: Applied Mathematics (Original NCJOSI Mathematical Reasoning)
9.1 Hand Arithmetic, Decimals, Fractions, & Percentages (No-Calculator Mechanics) 9.2 Speed, Distance, Time, & Accident Skid-Mark Calculations 9.3 Geometry in Field Operations: Perimeter, Area, & Crime Scene Tape Cordoning 9.4 Law Enforcement Resource Allocation, Shift Scheduling, & Payroll Overtime Math
10 Chapter 10: Section II Non-Cognitive (Integrity) Measure
10.1 Section II Explained: 120 Agreement-Scale Statements, Scoring & Honest Responding 10.2 Anti-Social Behaviors & Rule Compliance: Gratuities, Dishonesty, & Off-Duty Conduct 10.3 Orderliness & Diligence: Conscientiousness, Follow-Through & Accurate Records 10.4 Socialization, Community Policing, De-escalation & Duty to Intervene 10.5 Positive Outlook: Optimism, Resilience & Recovering from Stress
5.3 Reading Tables, Bar Graphs & Pie Charts for Trend Conclusions
Key Takeaways Explain This Topic AI
IOS states that NCJOSI² inductive items give tables of information, bar graphs or pie graphs and ask for general conclusions.
IOS's sample uses a bar graph of daily calls over three weeks and asks for the fewest-call day and the largest increase from week 1 to week 3.
Read the title, units, axis scale and legend before comparing bars, because a mislabeled series is the fastest route to a wrong answer.
A pie chart shows shares of one total; multiply the share by the total to get a count, and never compare raw slices across pies with different totals.
To judge whether a strategy worked, compare the change where it was used with the change where it was not, and avoid claiming proof of cause.
Last updated: October 2026
Note
ExamFinch provides this independent study guide to help prospective law enforcement officers prepare for the National Criminal Justice Officer Selection Inventory (NCJOSI). ExamFinch is an independent educational publisher and is not associated with, affiliated with, or endorsed by Industrial/Organizational Solutions (IOS) or any municipal civil service commission.
What IOS Says These Items Look Like
The IOS study guide describes the NCJOSI² inductive reasoning items in one sentence: you will be given tables of information, bar graphs or pie graphs and asked to make general conclusions based on them. It frames the questions as "What trends do you notice? Have specific strategies been successful or unsuccessful?"
IOS's sample shows a grouped bar graph titled Number of Calls Received Daily , with one bar per week (Week 1, Week 2 and Week 3) for each weekday from Monday to Friday. Its two sample questions ask:
When were the fewest calls received? (a single smallest value)
Which day of the week saw the largest increase between Week 1 and Week 3? (the biggest difference between two series)
The bars you compare and the arithmetic you need are simple. Most errors come from reading the wrong bar, the wrong week or the wrong direction of change. The method below prevents that.
The Five-Step Reading Order
Use the same order on every table or graph, before you look at the answer choices:
Title : What is being counted, and over what period? ( calls per day , burglaries per quarter , percent of arrests )
Units : Are values raw counts, percentages, dollars or rates per 1,000 residents? Never mix units in one comparison.
Axis scale : Where does the vertical axis start, and what is the interval between gridlines? A bar graph that starts at 4,000 instead of 0 makes small differences look huge.
Legend : Which color or shading is which series (Week 1, Week 2, District A)? Point at the legend, then at the bar.
The question's exact comparison : Is it asking for a largest value , a smallest value , a largest increase , a decrease , a total or a share ?
Tip
Write the comparison as a tiny formula in the booklet margin before reading the options, for example "W3 minus W1, each day, biggest positive." This stops you from answering the question you expected instead of the one asked.
Worked Example 1: Grouped Bars and "Largest Increase"
Suppose a bar graph shows traffic-crash reports for one city over two months. Read off the values into a quick table:
- Day March April Change (April minus March)
- Monday 42 47 +5
- Tuesday 38 52 +14
- Wednesday 45 41 −4
- Thursday 50 58 +8
- Friday 61 66 +5
Most crashes in a single bar: Friday in April (66).
Fewest crashes in a single bar: Tuesday in March (38).
Largest increase from March to April: Tuesday (+14), even though Tuesday never has the tallest bar.
Only decrease: Wednesday (−4).
The trap here is choosing Friday for "largest increase" because Friday's bars are tallest. Height and change are different questions.
Percentage Change
Some items ask for a percentage increase. Use the original value as the denominator:
Percent change = New − Old Old × 100 \text{Percent change} = \frac{\text{New} - \text{Old}}{\text{Old}} \times 100 Percent change = Old New − Old × 100
Tuesday: 52 − 38 38 × 100 ≈ 36.8 % \frac{52 - 38}{38} \times 100 \approx 36.8\% 38 52 − 38 × 100 ≈ 36.8% . Thursday: 58 − 50 50 × 100 = 16 % \frac{58 - 50}{50} \times 100 = 16\% 50 58 − 50 × 100 = 16% . Tuesday has both the largest raw increase and the largest percentage increase here, but that is not always true: a small base can produce a large percentage from a small raw change.
Worked Example 2: Pie Charts
A pie chart shows how one total is divided. Suppose a pie chart shows the 1,200 calls for service handled by one shift in a month:
- Call Type Share of Total Count (Share × 1,200)
- Traffic 30% 360
- Disturbance 25% 300
- Theft 20% 240
- Alarm 15% 180
- Medical assist 10% 120
- Total 100% 1,200
Typical questions and how to answer them:
"How many theft calls were there?" 0.20 × 1,200 = 240 0.20 \times 1{,}200 = 240 0.20 × 1 , 200 = 240 .
"How many more traffic calls than alarm calls?" ( 30 % − 15 % ) × 1,200 = 0.15 × 1,200 = 180 (30\% - 15\%) \times 1{,}200 = 0.15 \times 1{,}200 = 180 ( 30% − 15% ) × 1 , 200 = 0.15 × 1 , 200 = 180 .
"Which two categories together make up more than half of all calls?" Traffic + Disturbance = 55%.
Warning
If two pie charts have different totals (for example, 1,200 calls on day shift and 800 on night shift), a bigger slice does not mean a bigger count. 25% of 800 is 200, which is fewer than 20% of 1,200 (240). Convert each slice to a count before comparing across pies.
Worked Example 3: "Was the Strategy Successful?"
IOS specifically mentions questions about whether strategies were successful. The key is comparison. Suppose a table shows residential burglaries before and after a foot-patrol program:
- District Program? Year 1 Year 2 Change Percent Change
- A Yes 120 84 −36 −30%
- B No 110 105 −5 about −4.5%
- C Yes 90 81 −9 −10%
What the data supports :
Burglaries fell in both program districts by a larger percentage than in the district without the program.
District A had the largest drop in both count (−36) and percentage (−30%).
What the data does not support :
"The program caused the drop." Other changes could explain it; one year of numbers shows association, not proof.
"Burglaries will keep falling next year." The table says nothing about the future.
"District C's program failed." Its burglaries still fell more than District B's, just less than District A's.
The best answer to a strategy question usually sounds like the first list: specific, comparative and no stronger than the numbers allow.
Common Errors on Table and Graph Items
- Error Example Prevention
- Wrong series Reading the Week 2 bar when the question asks about Week 3 Touch the legend, then the bar
- Height vs. change Picking the tallest bar for "largest increase" Compute each difference
- Wrong direction Treating a decrease as an increase Always compute later minus earlier
- Truncated axis Assuming a bar twice as tall means twice as many Read the actual values from the scale
- Share vs. count Comparing percentages from pies with different totals Convert shares to counts first
- Overreach Choosing "proves" or "always" conclusions Prefer the most limited answer the data supports