3.3 Address and Record Comparison

Address and Record Comparison

Clerical professionals frequently manage databases containing multi-field customer or resident records. A complete record typically includes a combination of names, street addresses, cities, states, ZIP codes, and sometimes account or phone numbers. Verifying these multi-field records requires high cognitive flexibility, as you must switch between scanning text, numbers, and standardized abbreviations.

In a civil service exam, you will be presented with tables of records and asked to determine if they are identical or to identify specific discrepancies. This section breaks down the anatomy of addresses, explains how standard abbreviations are tested, and teaches systematic strategies for validating multi-field records.

---

1. The Anatomy of an Address and Standard Abbreviations

When human eyes read an address, they automatically resolve minor abbreviations. If you see 123 Elm St. on one sheet of paper and 123 Elm Street on another, your brain immediately recognizes that both represent the same physical location. However, in clerical comparison and database indexing, these are mismatches. You must treat every character, period, and abbreviation as a unique string.

Street Suffixes

Examiners frequently exploit the difference between fully spelled words and their abbreviated counterparts.

• Common Suffixes: Street (St.), Road (Rd.), Avenue (Ave.), Boulevard (Blvd.), Court (Ct.), Drive (Dr.), Lane (Ln.), Parkway (Pkwy.), Terrace (Ter.).
• Exam Trap: 456 Oak Ave. and 456 Oak Avenue are mismatches. Ensure you verify whether a period is present (e.g., St. vs. St).

Directional Prefixes and Suffixes (Directionals)

Directionals indicate cardinal directions before or after the street name. A mismatch in a directional changes the physical location entirely.

• Pre-directionals: 100 North Broadway vs. 100 N. Broadway (mismatch in spelling).
• Post-directionals: 500 2nd Ave. SW vs. 500 2nd Ave. S.W. (mismatch in punctuation).
• Directional Swaps: 100 E. Main St. vs. 100 W. Main St. (mismatch in direction, representing locations miles apart).

---

2. Secondary Unit Designators and Apartment Numbers

Secondary units include apartments, suites, rooms, units, and floors. These details are critical for mail delivery and emergency services.

Suffix vs. Unit Number

The designation of the unit must match in both spelling and placement:

• Apartment (Apt.), Suite (Ste.), Unit, Room (Rm.), Floor (Fl.), Number (#).
• Placement Variations: 888 Broadway Apt. 3B vs. 888 Broadway #3B (mismatch due to designator).
• Missing Units: 102 Cherry Ln. vs. 102 Cherry Ln. Unit 4 (mismatch due to omission).
• Hyphenated Units: 12-A Maple Rd. vs. 12 Maple Rd. Apt. A (mismatch due to formatting structure).

---

3. ZIP Codes and State Abbreviations

ZIP codes and state fields are highly structured, making them prime targets for exam questions.

State Abbreviations

The United States Postal Service (USPS) uses standard two-letter state abbreviations. However, exams may mix these with older abbreviations or swap similar-looking codes.

• Similar Two-Letter Codes: MA (Massachusetts) vs. ME (Maine), MI (Michigan) vs. MN (Minnesota), MS (Mississippi) vs. MO (Missouri), AK (Alaska) vs. AR (Arkansas).
• Spelling Variations: TX vs. Tex. vs. Texas.

ZIP and ZIP+4 Codes

ZIP codes are numeric strings, usually 5 digits, but can be 9 digits (ZIP+4).

• Omission of ZIP+4: 90210 vs. 90210-4109 (mismatch).
• Transpositions within ZIP: 02138 (Boston, MA) vs. 02318 (mismatch). Note that transposing numbers in a ZIP code can route mail to an entirely different state.

---

4. Multi-Line Address Records

In some databases, addresses are split into multiple lines (e.g., Address Line 1 for street address and Address Line 2 for apartment/suite). When comparing multi-line records, ensure that the fields have not been merged or shifted. For example, a record with Apt. 5 on Line 2 is not an exact match to a record where Apt. 5 has been appended directly to Line 1 (e.g., 123 Main St. Apt 5 on a single line). While the physical address is the same, the database schema treats them as distinct formats.

---

5. Systematic Methods for Multi-Field Record Comparison

When comparing database tables where each row contains 4 to 6 columns of information (e.g., Name, Address, City, State, ZIP), reading the entire row at once is inefficient. Instead, use these industry methods:

1. Field-by-Field Isolation (Vertical Scanning): Instead of comparing Row 1 of Column A to Row 1 of Column B, scan down a single column first. For example, look at the ZIP code column for all records. It is much easier to scan a vertical list of 5-digit numbers to find mismatches than it is to read full horizontal rows. Once you verify the ZIP codes, move to the States, then the Street Names, and finally the names of the individuals.
2. Verify the Shortest and Most Numeric Fields First: Numeric fields (ZIP codes, house numbers) have fewer characters and are easier to compare than long text fields (names, street names). If you spot a mismatch in a ZIP code, you can immediately mark the entire record as a mismatch without wasting time reading the street address.
3. The "Pointer" Technique: Use a blank card or sheet of paper to block out all other rows except the one you are evaluating. This prevents your eyes from drifting to neighboring rows, which is a major cause of errors under exam stress.
4. Confirm Capitalization and Punctuation Separately: Once you confirm that the letters and numbers match, do a quick pass specifically looking at punctuation (periods, commas, hyphens) and capitalization.