7.2 Coding and Clerical Operations With Letters and Numbers
Key Takeaways
- Coding questions give a key that translates information, such as letters to number ranges or words to abbreviations, and ask you to apply it accurately.
- Read the key once carefully, confirm the direction of translation, and watch for ranges that overlap at their boundaries.
- Operations with letters and numbers may combine counting, comparing, and alphabetizing a group of symbols, so identify the exact task before scanning.
- Translate easy items first, then return to items that need a key re-check, which prevents the key-lookup bottleneck from slowing the whole section.
- Most coding errors come from misreading the key, using the wrong direction, or missing a boundary condition rather than from arithmetic.
What Coding Tests
A coding question supplies a key and asks you to translate information using it. The key might assign a letter to a number range, replace a word with an abbreviation, or convert a date or location into a file code. The exam is checking whether you can apply a written rule precisely, not whether you can memorize anything. The key is always given.
Government offices code data constantly: routing files by region code, assigning category letters to claim amounts, or converting account types into short labels. The skill is the same in every case. Read the rule, confirm its direction, and apply it without drifting into what you assume the rule should say.
Read the Key Before the Items
Spend the first few seconds on the key itself. Identify what is being translated and in which direction. A key that converts words to codes is not the same as a key that converts codes to words, and items often test both directions in the same set.
| Key element | Question to ask | Common slip |
|---|---|---|
| Direction | Am I going from word to code or code to word? | Translating the wrong way |
| Ranges | Where does each range start and end? | Boundary value placed in the wrong band |
| Exceptions | Does any value have a special code? | Applying the general rule to an exception |
| Multiple fields | Does the final code combine several parts? | Coding only one field and stopping |
Worked Example: Range Coding
Suppose claim amounts are coded by this key: amounts from $0 to $99 get code A, $100 to $499 get code B, $500 to $999 get code C, and $1,000 or more get code D. Code a $500 claim.
The trap is the boundary. Five hundred is the start of the C band, not the top of the B band, so the correct code is C. Boundary values decide many coding items. Underline the first and last number of each range and check whether the rule says "up to" or "and over" before you commit.
Worked Example: Word-to-Code Translation
A mail unit uses this key: North = 1, South = 2, East = 3, West = 4, and adds the letter R for a rush item. A rush package going South should be coded 2R. The error to avoid is coding only the direction and forgetting the rush flag, or reversing it to R2 when the key specifies the number first.
Operations With Letters and Numbers
Some subtests ask you to work on a group of letters and numbers: count how many digits appear, compare two groups, or place items in order. The first move is always to name the exact task, because the symbols look similar whether you are counting, comparing, or alphabetizing.
| Task signal | What to do | Watch for |
|---|---|---|
| How many ... | Count only the requested symbol type | Mixing letters with digits |
| Which group is larger or different | Compare position by position | Stopping before the last character |
| Put in order | Apply the stated ordering rule | Numbers before or after letters as specified |
| Which does not belong | Find the shared rule, then the exception | Choosing the least familiar item by feel |
Worked Example: Counting
In the group 4K9P2M7, how many characters are digits? Read each symbol: 4 is a digit, K is a letter, 9 is a digit, P is a letter, 2 is a digit, M is a letter, 7 is a digit. That is four digits. Counting only what the question names prevents the common error of returning the total length, seven.
Efficient Section Strategy
The key-lookup step is the bottleneck on coding sections. Each glance back at the key costs time. Reduce lookups with a two-pass approach.
- First pass: translate every item you can code from memory of the key after one careful read.
- Mark any item that needs a fresh key check rather than stopping the whole section.
- Second pass: handle the marked items together, so you re-read the relevant part of the key once for several questions.
- Confirm direction and boundaries on the marked items, where mistakes cluster.
This order keeps you moving and groups the slow lookups. It also concentrates your careful checking on boundary and exception items, which is where most coding points are lost.
Where Coding Points Are Lost
Coding errors are rarely arithmetic. They come from misreading the key, translating in the wrong direction, dropping one field of a multi-part code, or placing a boundary value in the wrong range. Build a quick self-check: does the code match the key direction, did I include every required field, and did I test the boundary? Those three checks catch most planted errors.
A Quick Self-Check Routine
Apply a three-question check to any coded answer before marking it. First, direction: did I translate the way the item asked, word to code or code to word? Second, completeness: if the final code combines several fields, did I include all of them in the right order? Third, boundary: if a value sits at the edge of a range, did I read whether the rule says up to or and over? Running these three checks costs only a second or two and removes the errors that cluster on multi-field and boundary items, which is exactly where coding sections are won or lost.
A key codes amounts as follows: $0-$99 = A, $100-$499 = B, $500-$999 = C, $1,000 and over = D. What code applies to a $999 amount?
On a coding subtest, what is the most efficient way to handle the time cost of looking back at the key?