Free CritiCall Dispatcher Exam Flashcards

Call summarization means condensing a caller's account into the essential dispatch facts (who, what, where, when, weapon/vehicle) — not writing down everything said word for word. CritiCall's summarization modules score whether you captured the operationally critical facts, not writing speed.

Location, before anything else. If the call drops, transfers, or the caller can't continue, responders can still be sent to a confirmed location. Every other detail (nature of the call, suspect description, etc.) is gathered only after the address is locked in.

Accuracy naturally drops when a task is split between two channels — for example, typing CAD notes while listening to a caller. CritiCall's multitasking modules are scored expecting this trade-off, so the goal is minimizing errors under split attention, not eliminating the slowdown entirely.

When an officer keys up with an emergency (e.g., 'shots fired' or 'need help') while you're mid-entry on an unrelated phone call, the radio traffic takes precedence — officer safety on an active radio transmission outranks routine data entry on a call already in progress.

Spelling names and plates letter-by-letter over noisy audio invites errors (e.g., 'B' and 'D' sound alike). The standard fix is the NATO phonetic alphabet (Alpha, Bravo, Charlie...) to confirm each letter unambiguously before it's entered into CAD.

Paraphrasing the address back to the caller ('You're at 400 Oak Street, is that right?') catches transcription errors before dispatch, rather than after units are already en route to the wrong place. This active-listening check is faster than a correction call later.

When several 911 lines ring at once, the correct action is a brief triage — determine which caller has the most time-critical emergency — rather than answering strictly in the order the calls arrived. A held caller reporting a minor issue is lower risk than an unanswered caller reporting a life threat.

If a 911 call drops mid-conversation, the dispatcher calls back immediately using the number captured by ANI (Automatic Number Identification) rather than waiting for the caller to redial — seconds matter, and the caller may be unable to call back themselves.

CritiCall's multitasking modules interleave on-screen prompts (alerts, secondary data requests) with an active audio call. The tested skill is triaging which prompt to act on immediately versus which can wait until the call wraps up, without losing track of the caller.

A consistent note structure — who, what, where, when, weapon/vehicle — lets a dispatcher capture a chaotic call in a scannable order instead of a wall of text. Structured notes are faster to read back and less likely to omit a critical fact under time pressure.

Entering data in short bursts between pauses in caller speech — rather than typing continuously while the caller is talking — reduces the chance of missing a spoken detail. The tested skill is timing your typing to gaps in the conversation, not typing nonstop.

When multiple calls compete for dispatch, threat-to-life always outranks property-only or informational calls, regardless of which call came in first. A report of a person not breathing is dispatched ahead of a call about a broken window, even if the window call arrived first.

A crime happening right now (in-progress) is prioritized above a report of something that already occurred (a 'cold' report), because in-progress calls carry ongoing risk to victims, witnesses, or responding units. A cold burglary report can wait; an active break-in cannot.

Any mention of a weapon (firearm, knife, or vehicle used as a weapon) escalates a call's priority level, even if the described act itself sounds minor. Weapon involvement changes the responding units' approach (staging, backup) before they can act, so it must be flagged immediately.

When two calls appear equally severe, the one with higher risk to the responding officer or medic is dispatched first — for example, a domestic disturbance with an unknown weapon status over a routine welfare check with no reported risk indicators.

For medical calls, life-saving pre-arrival instructions (like starting CPR or applying pressure to a wound) are given before continuing to gather non-critical background details. Getting the caller acting to save a life outranks finishing the intake questionnaire.

When a caller can't confirm key details (exact injury, whether a suspect is still on scene), the dispatcher sends the higher level of response the situation could reasonably require, rather than waiting to clarify — units can always be downgraded en route, but a delayed dispatch can't be undone.

A single incident (e.g., a car crash with injuries) often requires notifying more than one discipline. The tested skill is recognizing all agencies a call touches — not just the first one that comes to mind — so a fire/EMS response isn't missed on a call that sounds like 'just' a police matter.

Before assigning a new unit to a call, check whether a unit is already assigned to that address or incident. Dispatching a second unit to a call that's already covered wastes coverage elsewhere and can create confusion about who has scene responsibility.

A call describing several injured people is prioritized and resourced differently than a single-victim call of the same type — it may require multiple medic units and an early request for additional resources, not just the standard one-unit response.

On a standard city grid, streets running one direction (e.g., east-west) are typically named 'Streets,' while the perpendicular set (north-south) are 'Avenues' or numbered. Knowing which axis a name belongs to lets you find an intersection without scanning the whole map.

Address numbers usually increase in one direction from a baseline (e.g., a central street or the city limit), and each 'block' spans roughly 100 numbers. Knowing the block-to-street relationship lets you estimate an address's location even without seeing the exact building.

The geometrically shortest path on a map isn't always usable — a one-way street running the wrong direction forces a detour. Map-reading items test whether you factor in street restrictions, not just straight-line distance, when picking a route.

Many cities split addresses into quadrants (e.g., 400 NE Main St. vs. 400 NW Main St.) that can be blocks apart despite an identical street number and name. Missing the quadrant label is a common way to send a unit to the wrong side of the city entirely.

When a caller can't give an exact address (common for callers on foot or in unfamiliar areas), the fallback is the nearest cross-streets or a landmark, converted to an approximate address range — this is faster to relay to units than an unresolved 'somewhere near here.'

Older paper map books and some CAD map overlays locate an address using a page number plus a letter/number grid cell (e.g., 'Page 42, D-3') rather than GPS coordinates. Reading these correctly means matching the row letter and column number to the printed grid, not guessing by eye.

The unit dispatched to a call should be the one closest by travel distance/direction, not simply the lowest-numbered or first-listed unit in the CAD roster. Picking by proximity minimizes response time; picking by list order can send a unit across town unnecessarily.

Typing scores are based on net WPM — gross words typed minus a penalty for errors — not raw typing speed. A dispatcher who types fast but sloppy can score below one who types slower but clean, since CAD errors can send responders to the wrong location.

The letter 'O' and the number '0,' and the letter 'I' and the number '1,' are among the most frequently mis-keyed character pairs in CAD data entry, especially in plates and case numbers. Data-entry modules deliberately include these look-alikes to test careful character-by-character entry.

ANI/ALI (Automatic Number/Location Identification) fields are populated automatically from the phone system and are generally reliable, while narrative and detail fields are typed by the dispatcher and carry human error risk. Knowing which fields to double-check saves time versus re-verifying data the system already captured correctly.

CAD systems mix open narrative fields (typed freely) with coded/dropdown fields (selected from a fixed list, like call-type codes). Coded fields exist specifically to prevent inconsistent spelling or phrasing from breaking searches and reports later.

Standard practice is to amend or supplement an incorrect CAD entry with a corrected note, not delete the original entry outright — CAD logs typically function as a legal record, and unexplained deletions undermine the audit trail for later investigations or court testimony.

Agencies set a single standard format for entering phone numbers, dates, and similar fields (e.g., digits only, no dashes) so CAD searches and cross-system lookups work consistently. Entering the same data in inconsistent formats can cause records not to match during a later search.

Data-entry modules are sometimes scored while a simulated call plays in the background, testing whether accuracy holds up under a competing audio channel — not just typing speed measured in silence, which doesn't reflect real call-taking conditions.

Cross-referencing means matching a single piece of information (a name, plate, or phone number) across two or more separate lookup tables to confirm they point to the same record. It's tested because dispatchers routinely reconcile CAD, warrant, and DMV data that don't share one unified database.

License-plate and ID comparison tasks are built around characters that look alike at a glance — 8 vs. B, 5 vs. S, 2 vs. Z. The tested skill is comparing character-by-character rather than eyeballing the overall shape of the string, which is how these near-matches slip through.

A BOLO (Be On the Lookout) plate match is rarely a perfect string match — dispatchers must judge whether a partial or near match (e.g., missing one digit) is close enough to flag, balancing the risk of a false alarm against missing a real hit.

A name alone is not enough to confirm a warrant match — common names produce false hits. Cross-referencing a warrant requires matching name AND date of birth (and often additional identifiers) together before treating a subject as the wanted person.

The same individual can appear under different name spellings or aliases across separate systems. Cross-referencing tasks test whether you can trace a shared identifier (like a DOB or ID number) linking apparently different names back to one subject.

Flagging a match that isn't real (false positive) sends resources on a wrong lead; missing a real match (false negative) lets a legitimate hit go unnoticed. Cross-referencing modules score both error types, so guessing quickly to save time increases one risk while rushing carelessly increases the other.

Recalling a long string of facts (address, name, description) is more accurate when grouped into small chunks of 3-4 items rather than trying to hold everything as one long list. This is why structured call-note formats (who/what/where/when) work better than free recall.

In memory-recall exercises, the first and last facts given tend to be remembered best, while details in the middle of a sequence are most likely to be forgotten. Deliberately re-checking the middle of a caller's account guards against this natural memory gap.

Writing down recalled details immediately after audio playback preserves more accuracy than trying to recall them after a delay or after handling another task first — memory of spoken detail decays quickly, especially under the interruption of a busy dispatch floor.

Suspect descriptions are recalled and relayed in a consistent order — sex, race, approximate age, height/build, clothing, distinguishing features — so nothing is skipped and responding units can scan for a match quickly rather than parsing an unordered list.

When a name or word was spelled letter-by-letter during a call, recall accuracy is tested by reproducing the exact spelling given — not a phonetically 'close enough' version — since a single wrong letter can cause a CAD or warrant search to miss the correct record.

Reading modules test picking the version of a sentence that states one clear meaning versus a version that could be read two different ways (an ambiguous pronoun or unclear modifier). Ambiguous CAD narrative can mislead a responding unit or a later reviewer of the call.

Proofreading items test whether a typed CAD entry matches what was actually dictated, character by character — not whether the entry merely sounds plausible. A transposed digit or dropped word can pass a casual read but fail a careful comparison.

CAD systems expect consistent abbreviations for street types (St., Ave., Blvd., Rd.) rather than inconsistent spelling-out or shortening. Using the agency's standard abbreviation prevents duplicate or mismatched address records in the system.

Reading comprehension items often bury one operative rule inside a longer policy paragraph. The tested skill is identifying which sentence actually governs the decision (e.g., an exception clause) rather than summarizing the whole passage generally.

Spelling/proofreading items include commonly confused words (e.g., 'their/there,' 'to/too') embedded in otherwise correct sentences. Catching these requires reading for meaning and usage, not just scanning for obviously misspelled words.