Blazalek.com

Email deliverability checklists for decisions and handoffs

Document email changes with these five checklists: the sender register, an ESP migration, DMARC readiness, a support case and a DNS change, each with blank tables to copy and a synthetic example of a completed record.

By

You have collected the evidence for a decision, and someone else has to review it. These five checklists, written for mail administrators, integration teams and the people who approve changes, provide blank Markdown tables you can copy into your working notes and a synthetic example that shows how a completed one reads. Pick the decision you need to document.

If you are still mapping out who sends mail for your organization, start with the sender register. If you already know the specific rollout or incident, head directly to the matching checklist.

Record who approved each sender and what comes next

The sender register keeps two questions separate: why the company uses a service, and whether it is authenticated. It tracks each sending account, who approved it, who runs it, authentication evidence, open questions, and review dates. If an owner or a piece of evidence is missing, the worksheet shows which dependent decision is still pending. Gather your active sending tools and internal owners before filling it out.

Record your senders using the Email sender register template: who approved each service.

Record an ESP migration and know when to stop

When your team is moving one sending stream to a new provider, this checklist records the preflight checks, the cutover, the rollback and the verification. Suppressions and outstanding sends get their own tracking, with evidence, decision-makers and recovery actions. Its example holds replay when the outcome of an earlier send is unknown; a rollback review does not authorize replay. Have old and new paths, owners, and baseline metrics ready.

Track your cutover with the ESP migration checklist: what to record and when to stop.

Collect the evidence before a DMARC policy change

This checklist connects each sending path and its cadence to evidence, gaps and a decision at scope level. It distinguishes HOLD, REPAIR and readiness for a named change, including the conditions for recovery. Readiness here permits preparation under your local change control; it does not direct a DNS edit. Start with the approved sender inventory and the current and proposed policy scope.

Record your evidence with the DMARC readiness checklist: evidence before a policy change.

Support escalation: get your evidence ready first

This worksheet brings together the receiving platform, the symptom, references to the evidence and the precise question for support staff. It covers controlled originals, a shareable copy, and the eligibility and evidence requirements of the route you’ve selected. Any unresolved requirement leaves submission on hold, and the checklist neither submits the case nor establishes that the problem is fixed. You’ll need access to the records and a technical contact for any logs that are missing.

Assemble your escalation package with the Email support escalation checklist: evidence to finish first.

Document an email DNS change: publication is not activation

Publishing a DNS record is only the halfway mark. This checklist keeps four records apart: the starting state, the authoritative zone update, what public resolvers return, and the live delivery check. Its worked example holds activation even though publication succeeded. It records the restrictions on recovery and closes a change only against agreed evidence and the owner’s approval. Start with the current and proposed records, permission for the change and the service’s own procedure.

Log each verification step with the Email DNS change checklist: publication is not activation.

For troubleshooting guides, lab exercises, or setup instructions outside these checklists, return to the knowledge base.

Email deliverability consultant

Get a second opinion on your email setup

Tell me what your customers are seeing or what you’re planning to change. In 30 minutes, we’ll work out what your team can check first and whether a deliverability audit would help.

I led deliverability at GetResponse, designed a dedicated newsletter system for Easy.Tools and helped Youmoney migrate its automated emails in stages. Read the case studies

Book free call

Email deliverability audit

See what I check and read a sample report with recommendations for your team.