8.2 Character Comparison & Perceptual Ability

Why This Module Is on the Test

CritiCall's official test-description list names this module "Perceptual Ability," defined as the "ability to compare job related letter/number sequences" with "aptitude at eliminating similar and potentially confusing sequences." In plain terms: can you tell, at speed, whether two alphanumeric strings are truly identical or only look identical? License plates, Vehicle Identification Numbers (VINs), case numbers, and address numbers are exactly the kind of string where a single swapped character sends a patrol unit to the wrong address or clears the wrong vehicle from a lookout list. This module isolates that one skill — precise visual or aural encoding of a short string — away from any surrounding scenario, so it rewards a specific technique far more than general reading speed.

Depending on the exact item format your hiring agency selects, you may be shown a reference string on screen and asked to pick which of several candidate strings matches it exactly, or you may hear a string read aloud once and be asked to identify or re-enter the matching string from what you retained. Both formats test the same underlying skill: encoding a short string character by character rather than by its overall shape or general "feel."

Core Terms and the Confusable-Character Table

The single biggest cause of missed items is shape-matching — glancing at a string and judging "yes, that looks like the reference" based on its overall silhouette instead of checking each character in turn. Item writers deliberately build wrong answers around characters that look or sound alike:

A second common error type is transposition — two correct characters swapped in position (for example, "8747936" written as "8747396"). A third is insertion or omission of a single character, which shifts everything after it out of alignment (for example, "GH4T-90BX" versus "GHA4T-90BX," where one extra letter pushes the rest of the string one position to the right even though most individual characters are technically present somewhere in the string).

The Chunk-and-Anchor Technique

Reading a seven-to-ten-character string all at once and trusting your overall impression is the most common way candidates lose points on this module. The reliable method instead is:

1. Break the string into chunks of three or four characters, the way you would naturally read a phone number, and compare one chunk at a time rather than the whole string at once.
2. Compare position by position within each chunk — ask "is character one the same as character one?" rather than "does this chunk look about right?"
3. Treat letter/number ambiguity as a flag, not a guess. Whenever a character could plausibly be read either way (O/0, I/1, S/5), slow down specifically at that position rather than re-reading the whole string.
4. Confirm left to right only once. Re-scanning back and forth increases the chance of losing your place — you can end up re-confirming one position twice while skipping another entirely.

Worked Scenario

Reference plate: 8KJW2Q5. Candidate options are 8KJW2O5, 8KJW2Q5, 8KIW2Q5, and 8KJVV2Q5. Chunking the reference as "8KJ / W2Q / 5": the first candidate substitutes the number 0 for the letter Q in the sixth position; the third candidate substitutes the letter I for J in the third position; the fourth candidate inserts an extra V, shifting the remainder of the string out of alignment. Only the second candidate, 8KJW2Q5, matches every position exactly. A candidate who reads by overall shape rather than by position is precisely the one most likely to accept 8KJW2O5 as a match, because the silhouette of that string barely changes with an O substituted for a Q.

Common Traps

• Trusting length alone. Two strings of the same length are not automatically the same string — insertion/omission pairs are specifically designed to have matching or near-matching lengths.
• Anchoring only on the first few characters. Many wrong-answer strings are constructed to match the reference exactly at the start and diverge only in the middle or end.
• Rushing the ambiguous character types (O/0, I/1, S/5) instead of slowing down at exactly those positions.

Audio-Based Items and Phonetic Confusion

When a string is read aloud instead of shown on screen, a second layer of confusion sits on top of the visual look-alikes: letters that sound alike. "B," "D," "P," "T," and "V" are frequently misheard for one another over a headset, and "M" and "N" are easily confused in fast speech. Agencies solve this operationally by spelling critical characters with a phonetic alphabet ("Bravo" instead of just "B") when confirming information back to a caller — but during the test itself you must rely on careful listening, since the audio is typically plain letters and numbers, not phonetic code words. If you are unsure whether you heard a "B" or a "D," treat that position the same way as an ambiguous O/0 on screen: flag it and do not guess.

Takeaways Recap

Speed on this module comes from a disciplined chunk-by-chunk, position-by-position comparison, not from reading faster; accuracy is what the score actually measures.