5.3 Frequency & Probability Determination

Why Frequency and Probability Determination Is Tested

CritiCall's official Frequency of Information/Probability Determination module measures the applicant's capacity to "choose the most likely solution based on information provided," applying probability principles and filtering out irrelevant data. This is a distinct skill from the deterministic arithmetic in Sections 5.1 and 5.2 — instead of computing one correct number, these items ask you to weigh incomplete or partial information and select the answer that is best supported by the data given, not the one that "feels" most dramatic. The skill maps directly onto real dispatch work: a caller who disconnects mid-sentence, a vague description, or a repeat address with a known history all require a dispatcher to reason about what is probably happening before more information arrives, without ever having full certainty.

Core Concepts

• Base rate / historical frequency: a known proportion of past events (for example, "12% of calls from this block are medical") used to estimate the likely category of a new, similar event.
• Proportion projection: applying a known percentage to a new volume of calls to estimate an expected count — mechanically similar to Section 5.1's percentage math, but framed as a forecast rather than a fixed total.
• Most-likely-solution reasoning: choosing the option best supported by the facts given, while accepting that no option is provable with certainty from partial information. CritiCall explicitly frames this as picking the most likely answer, not the only possible one.
• Irrelevant-information filtering: many items embed extra facts (names, side details, unrelated numbers) that do not affect the correct probability calculation — part of the skill being tested is recognizing which numbers matter.

Worked Examples

Example 1 — Proportion Projection. "A communications center logs 8,400 calls in a typical month. Historically, 12% of all calls are structure fires. If that pattern holds, about how many of the next 350 calls would you expect to be structure fires?"

• Step 1: Identify the relevant numbers — the 12% rate and the 350-call volume (the 8,400 monthly total is background, not needed for this specific projection).
• Step 2: Apply the rate — 350 × 0.12 = 42 structure fires expected.

Example 2 — Filtering Irrelevant Information. "Dispatcher Alvarez has worked the day shift for six years. Of the last 60 calls logged from Maple Street, 9 were reported as gas odors, and all 9 were later confirmed as actual gas leaks by the utility company. Based on this frequency, if 20 new calls come in reporting a gas odor from a similar area, about how many would you expect to be confirmed leaks?"

• Step 1: Alvarez's tenure and day-shift assignment are irrelevant to the calculation.
• Step 2: The confirmed-leak rate is 9 ÷ 60 = 15%.
• Step 3: 20 × 0.15 = 3 expected confirmed leaks — but because gas-odor calls carry a life-safety risk regardless of historical confirmation rate, every one is still dispatched; the frequency informs staffing and trend analysis, not whether to respond.

Example 3 — Most-Likely-Solution Reasoning. "Of the last 50 hang-up 911 calls placed from residential landlines in a given service area, 40 were confirmed accidental (butt-dials or a child playing with a phone) and 10 were confirmed emergencies requiring a response. A new hang-up call comes in from a residential landline in the same area with no further information available. Which action is best supported by this frequency data?" The statistically common outcome (80% accidental) does not eliminate the possibility of an emergency; the most defensible action combines the probability data with dispatch protocol — attempt a callback and send a unit to check welfare, rather than closing the call on the strength of the base rate alone. This example illustrates the core exam skill: frequency data shapes the most likely explanation, but a probability determination item still expects you to weigh that likelihood against the cost of being wrong, not to treat the majority outcome as a certainty.

Realistic Exam Scenario

A CritiCall-style item might read: "In the past 30 days, a dispatch center handled 900 calls. Of those, 60 involved a reported weapon. Of the next 45 calls expected today, how many would historical frequency suggest will involve a reported weapon?" Working the proportion: 60 ÷ 900 = 6.67%; 45 × 0.0667 ≈ 3 calls. The correct multiple-choice answer will be the nearest whole number consistent with that rate, and distractor options typically include a number derived from misapplying the wrong base (for example, using 60 ÷ 45 instead of 60 ÷ 900).

Common Traps

• Confusing frequency (a raw count) with probability (a proportion). "9 confirmed leaks" is not the same fact as "15% of gas-odor calls are confirmed leaks" — know which one a question is asking you to compute or use.
• Treating "most likely" as "certain." These items never offer an option that is provably true from the data alone; the task is to rank plausibility, not to prove a fact.
• Anchoring on a vivid but rare scenario instead of the statistically common one when the question is purely asking for the frequency-based projection.
• Ignoring an explicitly stated rate in favor of an assumed or remembered "typical" percentage — always use the number the item actually gives you.

Quick Takeaways

• CritiCall's Frequency of Information/Probability Determination module asks you to select the most likely answer from partial information, not to prove a certainty.
• Proportion projection (rate × new volume) is the core calculation behind most frequency items — identify the rate and the volume the question is actually asking about.
• Items commonly embed irrelevant details (names, tenure, unrelated totals); extract only the numbers the specific question needs.
• A low historical probability of an emergency does not eliminate dispatch protocol obligations — probability informs judgment, it does not replace safety-first response rules.
• Watch for distractor answers built from the wrong denominator (using the sample count instead of the full historical total, or vice versa).