8.3 NCIC-Style Code Matching, BOLOs & Warrant Cross-Checks
Key Takeaways
- CritiCall's official Cross Referencing description covers alphabetic, character-recognition, and numeric searching skills used to respond to written and oral requests for information — the same reasoning that underlies real NCIC, BOLO, and warrant checks.
- A "hit" in the National Crime Information Center (NCIC) is a possible match, not an automatically confirmed one; agencies require hit confirmation with the originating agency before officers act on it as certain.
- Confirmation timelines are commonly split into an urgent tier (about 10 minutes) and a routine tier (about 1 hour), though exact timing is set by each agency's own policy.
- A name match alone is never sufficient for a warrant hit — a second identifier, most often date of birth, is required before treating it as confirmed.
- Partial plate matches on a BOLO require weighing how many characters match, how much uncertainty sits in any unclear position, and whether the vehicle description supports treating it as a probable hit.
Why This Skill Matters Beyond the Test
CritiCall's cross-referencing items do not exist in a vacuum — they are a compressed simulation of judgment calls a working telecommunicator makes many times per shift: running a plate against a lookout list, checking a name against a warrant file, or confirming whether a "hit" in one system truly describes the same person or vehicle flagged in another. CritiCall's official description of the Cross Referencing module states that it "assesses alphabetic, character recognition, and numeric searching skills" while the test taker "responds to both written and oral requests for information," and one of the officially listed abilities the test measures is the capacity to "recognize if bits of information, such as addresses or names, are similar or different." On the job, that same judgment sits underneath every National Crime Information Center (NCIC) query, "Be On the Lookout" (BOLO) check, and warrant confirmation a dispatcher runs.
Because agencies differ in the exact records systems they use, CritiCall does not test agency-specific software — it tests the general reasoning skill those systems all depend on: is this record actually the same person or vehicle I am looking for, or only a similar-looking one? Understanding the real-world stakes behind that judgment makes the abstract cross-referencing items on the test far easier to reason through quickly, because you already know why each detail matters instead of treating it as an arbitrary puzzle.
Core Concepts
NCIC is the Federal Bureau of Investigation (FBI)-maintained national database of wanted persons, stolen vehicles, stolen property, and outstanding warrants that dispatchers query by name, plate, or other identifiers. A hit is a record returned by the query that appears to match the subject or vehicle being checked; it is not automatically treated as confirmed. Because names — and occasionally plates — can coincidentally match a wanted record without being the same subject, agencies require hit confirmation: a follow-up contact with the record's originating agency to verify the record is still active and that the identifying details truly line up before officers act on it as certain. Confirmation timelines are commonly split into an urgent tier (verified within roughly ten minutes) and a routine tier (verified within about an hour); the exact timing is set by each agency's and state's own policy, not by CritiCall.
A BOLO is an internal alert — often naming a specific plate, vehicle description, or suspect description — that has not necessarily been entered into a national database at all. Matching a spotted plate against a BOLO list is a cross-referencing task in miniature: comparing a plate character by character against a shorter, agency-specific list rather than a national one, using the same chunk-and-anchor technique covered in the previous section.
Why name alone is never enough: common names produce false-positive hits routinely. A warrant search on a name like "Michael Smith" run against a national file will very likely return more than one candidate record. Standard practice — and the reasoning CritiCall's cross-referencing items are built to test — is to require at least a second identifier, most often date of birth, and ideally a numeric identifier such as an FBI number or a state identification (SID) number, before treating a name match as confirmed.
| Situation | What to check before treating it as confirmed | Risk if skipped |
|---|---|---|
| Warrant hit on a name | Date of birth, and a second identifier if available | False positive — the wrong person is detained |
| BOLO plate spotted by an officer | Character-by-character match against the exact plate, not just a similar overall appearance | False negative (a real hit is dismissed) or a false positive (an innocent driver is stopped) |
| Partial plate match (one character unreadable or uncertain) | Whether the remaining characters plus vehicle description are distinctive enough to flag as a probable hit | Missing a real hit, or flooding units with false alarms |
| Multiple records under a similar name | Whether aliases share a date of birth or ID number linking them to one true subject | Missing a linked record filed under a different spelling |
Worked Scenario
An officer runs a plate that partially matches a BOLO: four of seven characters are a confirmed match, one character is uncertain (possibly an O or a 0), and two characters do not match at all. Cross-referencing judgment here is not a simple yes-or-no call — it is weighing how many characters are a solid match against how much uncertainty sits in the unclear position, and whether the vehicle description reported alongside the BOLO (color, make, model) supports treating this as a probable hit worth reporting to the officer, versus dismissing it as coincidental. CritiCall's cross-referencing items simulate exactly this kind of partial-match judgment using shorter, cleaner tables than a real BOLO list — but the underlying skill, weighing partial evidence without over- or under-committing, is identical.
Takeaways Recap
Treat every name-only match as unconfirmed until a second identifier lines up, and treat every partial character match as a judgment call about how much uncertainty the remaining evidence can carry — not as an automatic accept or reject.
Why do agencies generally require hit confirmation with the originating agency before officers act on an NCIC warrant hit as certain?
A warrant search on a common name returns three possible matching records. What is the correct next step?