Data Quality & Postal Records · THE NO-PANIC PLAN
Normalize U.S. postal address records without losing unit details
A standardized address can be easier to sort and print, but formatting does not prove that a person lives at the address or that mail will reach them. This workflow covers U.S. postal-address records only. It preserves the source data, applies USPS formatting guidance, checks a limited sample through official lookup, and keeps ambiguous or international records for review instead of guessing. Use an approved process for bulk address verification; do not upload a customer list to a public lookup or formatter without authority and privacy review.
MISSION Standardize a U.S. address dataset for a defined mailing purpose while preserving original values, apartment or suite details, unresolved exceptions, and the limits of address verification.
Standardize the U.S. address fields and keep uncertain records in a review queueTHE REAL-WORLD BIT
What happens outside this browser tab?
Define the mailing purpose and U.S. scope; preserve a read-only original and profile address fields; parse street, unit, city, state, and ZIP into explicit columns; standardize output against USPS Publication 28; use official lookup only for appropriately authorized individual checks; review PO Box, rural route, Puerto Rico, military, missing-unit, and international exceptions; deduplicate only exact, policy-approved matches; then compare counts and samples and export both the standardized data and an exception report.
YOUR CHECKLIST, WITH FEWER DRAMATIC SIGHES
One step at a time.
Follow the order below. If a step names a Nirmion tool, its link is right there with it.
- 01
Define what the address records will be used for
Write down the intended output, such as formatting a permissioned U.S. mailing list for a specific fulfillment or correspondence task. Identify who owns the source file, the system of record, the date received, and which records are in scope. Keep the country as an explicit field and route non-U.S. records to the appropriate country-specific standard rather than applying USPS rules to them. Limit processing to data you are authorized to use; a correctly formatted postal address does not establish a person's identity, current residence, customer relationship, or consent for marketing. Record the decision criteria before editing so cleanup does not silently change how the list is used.
- 02
Preserve the original and inspect the address columns
Save an unchanged, access-controlled copy of the input and work on a separate version. Record the file name, date, row count, and relevant column names. Check whether the data stores recipient, delivery line, unit, city, state, ZIP Code, country, and notes in separate fields or mixes several values into one cell. Identify blanks, invalid state abbreviations, ZIP values stored as numbers, misplaced unit labels, line breaks, and records with multiple addresses. Keep leading zeros in ZIP Codes by treating them as text. Microsoft Power Query can help import and transform tabular data repeatably; keep the original query steps and output counts so another reviewer can understand what changed.
- 03
Parse fields and mark uncertain records instead of guessing
Separate recipient or organization, delivery address, secondary unit, city, state, ZIP Code, and country into distinct fields. Preserve apartment, suite, floor, room, building, rural-route, and PO Box information exactly as received before applying a USPS designator. When a value could refer to either a street name or unit, or two rows have conflicting unit numbers, do not infer the intended address from a nearby record. Use an exception status such as missing unit, multiple candidates, non-U.S. address, or source conflict and send it to the data owner. USPS Publication 28 defines U.S. delivery-address components and standardized output; it is not a license to invent missing address facts.
- 04
Apply USPS formatting and preserve a before-and-after value
Use the current USPS Publication 28 for delivery-line order, street suffixes, directional abbreviations, secondary unit designators, PO Box, rural route, and special address formats. Keep the source address in its original columns and write a standardized result to new columns, with a change note or rule version. The Address Formatter and Postal Code Formatter can format a small, authorized input locally; they do not perform a USPS database match. Do not drop an apartment or suite because a shorter line looks cleaner, and do not convert an unfamiliar rural, military, Puerto Rico, or organization address to a standard street pattern without source evidence.
- 05
Use official ZIP lookup only for limited, authorized checks
For an address you are permitted to check, use USPS ZIP Code Lookup to compare the entered street address, city, and state with the returned ZIP information. Enter records individually when appropriate; do not paste a bulk list containing personal information into a public web form. USPS explicitly says a ZIP Code result does not confirm that a person or company is at an address. It is also not proof of a deliverable recipient, consent to contact, or current occupancy. If you need bulk matching or delivery-point validation, use an authorized USPS Address Information System product or licensed service and review the service's data-use and privacy terms with the data owner.
- 06
Review duplicate candidates and special address cases
Compare normalized address fields to find exact duplicates, but do not merge records solely because they share a building, street address, ZIP Code, or organization. Two apartments at the same building are different delivery locations; one household may also have multiple authorized recipients. Use the business rule approved by the data owner to decide whether records represent duplicate rows, separate people, forwarding addresses, or mailing preferences. Keep postal boxes, rural routes, military addresses, Puerto Rico and other special formats in the relevant USPS category. Document every merge, split, unresolved conflict, and excluded international record in an exception report.
- 07
Check the output and publish the exception report with it
Compare input and output row counts, count each exception type, and sample records from every format group, including apartments, PO Boxes, rural routes, and ZIP Codes with leading zeros. Check that no unit, recipient, country, or source value disappeared, and confirm that each change follows the selected rule. A second reviewer should resolve high-impact corrections against the source system before the standardized file is used for mail. Export the standardized output, the unchanged source reference, the transformation notes, the check date, and the exception queue to approved storage. Restrict access, follow the organization's retention policy, and do not describe the result as identity or occupancy verification.
THE HELPER CREW
Tools for the fiddly bits.
These are the currently published Nirmion tools matched to this guide. Open a tool page for its accepted inputs and limits.
RECEIPTS, PLEASE
Sources & review notes
Each source is linked to the steps it supports. Open it to check its scope and current guidance.
Source checked 2026-10-10