8.1 Alphabetic & Numeric List Searching

Why This Module Is on the Test

CritiCall's official list of abilities explicitly includes "Identify written information provided on lists (such as finding a name on a list from an alphabetically-sequenced telephone book)" — one of the plainest, most literal skill descriptions in the entire test battery. This is not a euphemism; you will genuinely be timed on how fast and accurately you can find one specific entry in a printed-style list. On the job this maps to hunting through a paper or on-screen roster, an alphabetized hazmat placard guide, a mutual-aid contact sheet, or a directory of business names when a caller can only give you a name and no address.

The skill sounds trivial until it is timed and paired with distractors: two or three similarly spelled names sitting one line apart, entries that break "obvious" alphabetization rules, or a numeric list where you must scan by value rather than by position on the page. CritiCall scores both speed and accuracy on these items, and a wrong-line answer counts the same as a blank one — there is no partial credit for finding the right neighborhood of the list.

Core Rules of List Searching

Two sorting conventions show up on the test and on the job, and mixing them up costs time:

Letter-by-letter alphabetization ignores spaces and punctuation and compares the string as one continuous run of characters. Under this system, "MacDonald" sorts as one word, and where "Mac Donald" (written as two words) falls relative to it depends on whether the space is skipped or treated as a character.

Word-by-word alphabetization treats each space-separated word as its own sorting unit, so a two-word name is compared word-first rather than as one long string. Most CritiCall-style directories use a flattened, letter-by-letter convention similar to a printed phone book, but the test does not announce which rule is in use — you infer it from the first few entries you see and then apply it consistently rather than assuming.

Numeric lists (case numbers, unit numbers, zip codes) sort strictly by value, but three details commonly trip up a fast scan:

• Leading zeros. "0452" and "452" represent the same number, but a list that treats entries as fixed-width text strings may place them differently than a list that sorts by pure numeric value.
• Numbers as name prefixes. "1st Street" is frequently alphabetized as if spelled out ("First Street," filed under F), not under the digit "1" — a convention borrowed directly from printed phone books and city directories.
• Mixed alphanumeric codes. As plain text, "A-12" can sort before "A-2" because the character "1" is compared before "2" at the second position, even though 12 is numerically larger than 2. Treat mixed letter-and-number codes as text strings unless you are told otherwise.

Search Strategy: Anchor and Narrow

The fastest accurate method is a two-stage anchor-and-narrow scan, not a top-to-bottom read of every line:

1. Jump to the block. Use the first letter (or first two letters, for a long list) to jump directly to the approximate location — the way you would flip a phone book open near "R" rather than starting at "A" and reading forward.
2. Narrow within the block. Once inside the right first-letter block, scan only the second and third letters to close in on the exact entry, watching for near-duplicates that share the same opening letters.
3. Confirm with a second identifier. If two entries share a last name, use the first name, a middle initial, or another visible field (address, phone number, unit number) to pick the correct line. Never select an entry based on the last name alone when more than one similar entry is visible.

Worked Scenario

A caller says, "This is Roberta Ashworth, calling about my neighbor's dog." You need her address from an alphabetized resident directory that shows, in this order: Ashworth, Rachel; Ashworth, Robert; Ashworth, Robert J.; Ashworth, Roberta. All four entries cluster within a few lines of each other. The correct line is the exact match, "Ashworth, Roberta" — not "Ashworth, Robert" (missing the trailing "a") and not "Ashworth, Robert J." (a different person carrying a middle initial). This is the exact trap the module is built around: a fast reader who stops at the first "Ashworth, Robert—" match grabs the wrong line and enters the wrong address into the call.

The same logic applies to numeric lists. If you are asked to find case number "A-204" in a list that also contains "A-024," "A-240," and "A-2004," the only safe method is comparing the full string character by character rather than trusting a glance at the first digit or two.

Takeaways Recap

List-searching items reward a deliberate, two-stage scan over a fast, confident guess, and the test is specifically built to punish candidates who stop at the first plausible-looking match.