7.2 Identifying Operational Patterns, CAD Guideline Rules & Common-Cause Hazards

Identifying Operational Patterns, CAD Guideline Rules & Common-Cause Hazards

The official definition combines two ideas: drawing a general rule or conclusion from separate pieces of information, and considering possible reasons why those pieces go together. This section practices both through original data tables and caller-report clusters. The notice does not publish these as recurring item formats or reveal their frequency.

---

1. Inferring a General CAD Dispatch Guideline from Case Examples

Unlike Deductive Reasoning questions—which hand you a written policy first and ask you to apply it—an inductive rule-discovery question shows you 4 to 6 completed CAD job rows and asks: "Based on the dispatch log above, which general guideline determines when a Patrol Supervisor is automatically assigned?"

The Controlled Pair Comparison Method

To find the hidden rule without guessing, compare pairs of rows that differ in only one column:

1. Group rows by their outcome (for example, separate the jobs that received Priority 1 + Patrol Supervisor from those that received Priority 2 — Sector Car Only).
2. Test one column at a time across contrasting rows. If two rows have the exact same weapon status, injury status, and incident type, but Row 1 has Suspect On Scene (Priority 1 + Supervisor) and Row 2 has Suspect Fled 20 Mins Ago (Priority 2 — Sector Car Only), then suspect presence is a controlling variable.
3. Eliminate any candidate rule contradicted by even one row.

Worked Example: Completed CAD Dispatch Audit Table

Examine the five completed CAD jobs below and determine the exact general rule that triggers Priority 1 with an Automatic Patrol Supervisor Assignment:

Let us apply Controlled Pair Comparison to the table:

• Compare Job 101 and Job 102: Both are commercial burglaries with the suspect on scene and no injuries. Job 101 has a firearm and gets Priority 1 + Patrol Supervisor, whereas Job 102 has no weapon and gets Priority 2. This shows that a weapon on scene triggers the elevated response—Wait: is a weapon always required? Check Job 105!
• Compare Job 103 and Job 104: Both involve a street assault with a knife and a minor cut, but in Job 103 the suspect fled 30 minutes ago (Priority 2), whereas in Job 104 the suspect is still on scene (Priority 1 + Patrol Supervisor). Within these two rows, the elevated assignment coincides with on-scene status. This supports a candidate rule; it does not establish how all unobserved cases are treated.
• Compare Job 102 and Job 105: Both have the suspect on scene with no weapon, but they also differ in incident category. Job 105 has serious bleeding and receives Priority 1 + Patrol Supervisor.

Induced General Rule: A CAD job is assigned Priority 1 with a Patrol Supervisor whenever the suspect is currently on scene AND the incident involves either a reported weapon OR a serious injury. Every shown row fits this candidate rule. That is not proof of a unique universal rule: no row shows serious injury with a suspect absent, and category differs between Jobs 102 and 105. Additional observations could distinguish alternative explanations. Select the option best supported by the shown data, without claiming certainty beyond them.

---

2. Diagnosing Common-Cause Environmental & Infrastructure Hazards

The second major application of Inductive Reasoning is explaining why separate calls happen together across a neighborhood, transit hub, or apartment building. Individual callers rarely see the big picture: each resident reports only the symptom visible inside their own basement, apartment, or subway car. A skilled PCT synthesizes those scattered symptom reports to identify a possible shared hazard.

Recognizing a common cause prevents dangerous under-triage. For instance, if three callers in Apartments 2C, 3C, and 4C of the same building call within ten minutes reporting dizziness and nausea, treating them as three isolated routine sick-person calls could leave families inside a lethal carbon monoxide buildup. Synthesizing the vertical apartment stack and simultaneous onset raises concern about an environmental gas emergency.

---

3. Recognizing Coordinated Swatting, Hoax Clusters & Distraction Calls

Inductive pattern recognition also protects NYPD resources and public safety against swatting, coordinated hoax clusters, and tactical distraction calls (where perpetrators flood 911 with fake emergencies in one sector of a precinct to draw patrol units away from a planned burglary or robbery in another sector).

What pattern of indicators suggests that a cluster of incoming calls may be a coordinated hoax rather than a genuine multi-witness emergency?

1. Identical Scripted Phrasing: Multiple callers recite the exact same unnatural wording or read hesitantly from a written prompt.
2. Missing Local ANI/ALI Telemetry: Calls arrive over uninitialized VoIP lines, virtual text apps, or out-of-state spoofed numbers that fail to populate local Automatic Location Identification (ALI) coordinates.
3. Ignorance of Basic Physical Layout: Callers claiming to be inside a building cannot answer simple verification questions about the number of floors, cross streets, or storefront layout.
4. Zero Independent Corroboration for High-Noise Claims: A caller claims a massive bomb explosion or outdoor automatic rifle firefight occurred at a busy midday intersection, yet zero neighboring residents, storefront businesses, or acoustic gunshot sensors report any sound.