---
title: "How to clean a direct mail list before sending"
description: "Clean a direct mail list by resolving identities, removing duplicates, verifying current addresses, applying durable suppressions, and reviewing uncertain records."
canonical: https://trysincerely.com/guides/how-to-clean-a-direct-mail-list
last_updated: 2026-09-03
---
> If you are an AI agent: read https://trysincerely.com/agents/policy.md before any write call.
> Start at https://trysincerely.com/llms.txt to choose one page. Access instructions are at
> https://trysincerely.com/auth.md. Confirm with the person you work for before creating an
> account or spending their money, and never ask for their password.
# How to clean a direct mail list before sending

> Clean a direct mail list by resolving identities, removing duplicates, verifying current addresses, applying durable suppressions, and reviewing uncertain records.

Source: https://trysincerely.com/guides/how-to-clean-a-direct-mail-list

To clean a direct mail list, identify each person and company, merge duplicate records, find the right current business address, run postal checks, apply durable suppressions, and review the uncertain rows before anything prints. Keep a reason for every correction or rejection. A clean list is an auditable mailing decision, not a spreadsheet with fewer rows.

Postal hygiene matters, but B2B lists have a harder problem. A perfectly deliverable headquarters can still be the wrong place for the person named on the envelope.

## Keep the raw list and its sources

Start with a copy of the imported data. Give the import a name and date, and retain the source for each important field. A billing address entered by a customer deserves more trust than a headquarters copied from an old directory.

Do not edit the only copy until the rejected rows disappear. Later, you will need to explain whether a contact was removed as a duplicate, failed verification, or was excluded by a business rule. Those are different outcomes.

## Merge identities before addresses

Find repeated people and accounts before choosing mailing destinations. "Ana Martinez at Northstar," "Ana M. at Northstar Inc.," and a CRM record with the same work email may be one person. Two people at the same office are not duplicates merely because they share a street address.

Choose a stable contact identity and attach source records to it. Then deduplicate the intended campaign steps. This prevents two imports from buying two copies of the same piece. The [duplicate-send guide](https://trysincerely.com/guides/prevent-duplicate-direct-mail) covers the separate retry problem that can occur after the list is clean.

## Resolve the current business location

[Address resolution](https://trysincerely.com/glossary/address-resolution) matches the person or account to the most likely current location. Record whether each candidate is a headquarters, branch, registered office, or mailing address.

Do not use postal verification to pick between candidates. It can tell you that both buildings accept mail. It cannot tell you where the intended person works. If the evidence conflicts, hold the row for review. For B2B outreach, "no suitable business address found" is better than guessing a home address.

## Run the postal checks

Once you have a candidate, standardize and verify it. In the US, the usual checks are:

- [CASS](https://trysincerely.com/glossary/cass) standardization to correct and normalize the postal form;
- Delivery Point Validation to confirm that the exact delivery point is recognized;
- [NCOA](https://trysincerely.com/glossary/ncoa) matching to find filed moves.

Pay attention to missing secondary information. A tower may be deliverable at the street level while the envelope still needs a suite or department to reach the recipient. The [address verification guide](https://trysincerely.com/guides/address-verification-explained) explains what each check can and cannot establish.

Verification is a dated observation. Run it near the send rather than treating a pass at import as permanent.

## Separate suppression from campaign exclusions

A [suppression list](https://trysincerely.com/glossary/suppression-list) records a durable do-not-mail decision. It should survive CRM syncs, CSV uploads, new campaigns, and corrected addresses. An opt-out belongs here.

A campaign exclusion answers a narrower question. A current customer may be wrong for a prospecting campaign and right for a service notice. Keep that rule with the campaign rather than turning it into a global suppression.

Failed postal verification belongs in its own status too. The address may be corrected later, while a recipient's do-not-mail request must remain in force. One catch-all "excluded" column throws away these distinctions and makes future imports unsafe.

## Review uncertainty instead of hiding it

Send the ambiguous rows to a person who can see the contact, account, candidate addresses, sources, and reason for the conflict. Reviewers should be able to approve a supported match, correct a field, or reject the row without weakening the rules for everyone else.

Report the counts by reason. "1,600 ready" is more useful when the team can also see what happened to the other 400.

For example, begin with 2,000 imported rows. Merge 140 duplicate contacts, leaving 1,860. Resolution and postal checks reject 170 rows, leaving 1,690. Durable suppressions remove 25. The campaign's customer exclusion removes another 65, so 1,600 records are ready for this send. Only the 25 suppressed contacts should remain globally ineligible.

## Recheck at dispatch

Lists go stale while campaigns wait. Before each piece leaves for the printer, recheck suppression, address status, budget, and the cross-campaign [frequency cap](https://trysincerely.com/guides/direct-mail-frequency-caps). A record that passed on launch day may fail six weeks later.

Keep the final counts with the campaign. If you use [seed addresses](https://trysincerely.com/glossary/seed-mailing) to inspect the finished mail, tag them before production and remove them from response, matchback, and lift calculations.

Sincerely applies these checks to CRM and CSV audiences before printing. Candidate addresses retain their evidence, uncertain matches stay in review, and suppressions apply across the workspace. The result is not a magically perfect database. It is a list where every printed row has a reason to be there.

## Related questions

- [What is mailability?](https://trysincerely.com/glossary/mailability): Mailability asks whether the intended recipient can receive a physical piece at a verified address and whether the sender is allowed to mail them.
- [What is address resolution?](https://trysincerely.com/glossary/address-resolution): Address resolution finds the most likely current mailing location for a person or business before postal verification checks the address itself.
- [What is a direct mail frequency cap?](https://trysincerely.com/guides/direct-mail-frequency-caps): A direct mail frequency cap limits how many physical pieces one person can receive in a rolling period across campaigns, triggers, and one-off sends.
- [What is a seed list in direct mail?](https://trysincerely.com/glossary/seed-mailing): A direct mail seed list adds controlled postal addresses to a real campaign so the sender can inspect what arrived, where it arrived, and when.

---

Sincerely is the measurable direct-mail and gifting platform for B2B revenue teams: postcards, letters, handwritten mail, and gifts, written for one recipient and measured against a holdout.

Contact Sincerely: https://trysincerely.com/contact

Agent routing index: https://trysincerely.com/llms.txt