Email List Hygiene Checklist for Outbound Campaigns

Email list hygiene is the process of keeping an outbound audience accurate, relevant, and safe to use over time. Before a campaign, clean the data, verify address signals, review recipient fit, reconcile suppressions, and record who approved the final audience. Verification alone is not list hygiene, because a technically reachable address can still be irrelevant, role-based, disposable, unsubscribed, or already suppressed.

The checklist

1. Establish provenance and ownership

Write down where the list came from, when it was collected or exported, what audience it represents, and who owns the decision to use it. A list with no source cannot be investigated when a row looks wrong. It also encourages accidental reuse for a campaign that was never intended by the original collection context.

Do not treat a purchased or scraped list as clean because it came from a recognizable vendor. The Google sender guidelines emphasize sender responsibility for message quality and recipient response; technical checks do not replace a defensible audience process.

2. Normalize the file

Trim leading and trailing whitespace, standardize column names, preserve UTF-8 text, and decide how blanks will be handled before import. Deduplicate on a normalized email key, but preserve the original value and source row for auditability. Check that personalization fields render naturally; a clean address with a broken name merge is still a poor recipient experience.

The existing RepMail guide to CSV formatting covers practical import failures. Use it alongside this checklist rather than assuming that a technically parseable CSV is ready for outreach.

3. Classify address signals separately

Run or record the available checks, but keep their meanings distinct. Syntax answers whether the value has a plausible email format. Domain checks answer whether routing information exists. Mailbox checks may provide stronger or weaker evidence. A catch-all result means the mailbox is unresolved; a disposable flag describes likely temporary use; a role flag describes a shared function; unknown means the available evidence did not support a conclusion.

Do not collapse these outcomes into a single “good” column. The verification status model gives a practical schema for retaining the difference.

4. Review fit and context

Confirm that each retained row belongs to the campaign’s intended audience. Check company, role, geography, use case, source context, and freshness. A valid address at the wrong company is not a good lead. A role address may be appropriate for a functional message but wrong for individual personalization. A catch-all address may need human review rather than automatic inclusion.

This step is also where you apply the permission, notice, and opt-out requirements that apply to your contacts and message type. This checklist is an operations aid, not a legal conclusion. When the jurisdiction or audience is unclear, obtain appropriate legal or compliance advice.

5. Reconcile suppression sources

Compare the candidate list with internal do-not-contact records, unsubscribes, complaints, hard bounces, customer preferences, and any provider suppression state. Remove or hold matches before the campaign is assembled. Then check again after enrichment and personalization, because those steps can reintroduce an address from another source.

The outbound suppression rules guide explains how to make this reconciliation durable across a CRM, sending platform, and exports.

6. Approve the final audience

Record the final file or query version, rule version, review date, reviewer, and intended campaign. Store counts only as operational evidence from your own run; do not compare them with an invented industry benchmark. If the audience changes after approval, repeat the relevant checks rather than treating the approval as permanent.

A compact release worksheet

Where RepMail fits

RepMail’s public materials describe contact checks in the campaign workflow, and the existing RepMail list guide describes checking a workspace suppression list at send time alongside bounce and complaint telemetry from AWS SES. Use those controls as part of the release process, not as a replacement for source ownership and qualification. The separate pre-send deliverability checklist is the final campaign gate; this page focuses on the audience itself.

Sources

• Google email sender guidelines
• Yahoo sender best practices
• Microsoft: Outlook requirements for high-volume senders
• Twilio: How to clean an email list
• RepMail: CSV formatting for email lists