tools

Cold Email Checklist: The Pre-Send Routine That Protects Every Campaign

Dev Anand

AI Tool Reviews & Automation Safety2026-10-246 min read

Part of: Cold Email
A checklist panel glows beside a sealed envelope on a launch pad.

Key Takeaways

  • Check authentication before anything else: SPF, DKIM, and DMARC published, aligned, and passing on the exact domain you are sending from.
  • Verify the list close to the send date, remove hard bounces permanently, and never send to a list that has sat unverified.
  • Match volume to the domain's history. A warmed domain asked to spike will behave like a new domain, because to the filters it looks like one.
  • Read the copy as a stranger would: one clear ask, no borrowed familiarity, and personalisation that is actually true of the recipient.
  • Decide who answers replies, and how fast, before the first email leaves. Reply handling is part of the campaign, not an afterthought.

By Dev Anand, AI Tooling & Automation Safety. Last updated: 2026-10-24

What should you check on authentication and sending setup?

Start with identity. Confirm that SPF authorises the servers you actually send from, that DKIM signing is on and passing, and that DMARC is published with alignment between the visible From domain and the authenticated domains. Send a test message to an account you control and inspect the authentication results rather than assuming a DNS record you published months ago is still correct. Records get edited, sending tools get swapped, and a record that was right for the old setup can be silently wrong for the new one.

Confirm you are sending from the domain you meant to send from. Most teams protect their primary domain by running cold outreach from secondary domains, and the checklist item is simply to verify the campaign is attached to the right one, with its own completed authentication and warmup. Then check the mechanics: a working unsubscribe or opt-out path, a plain reply route that reaches a human inbox, correct sending hours for the recipients' time zones, and daily volume set to a level the domain's history supports. Our explainer on cold email deliverability in 2026 covers why each of these setup items affects placement, not just delivery.

What should you check on the list before it sends?

Treat the list as a deliverability asset, not a spreadsheet. Every address should have a source you can explain: where it came from, when, and why this person fits the campaign's targeting. Addresses with no provenance are where spam traps and invalid mailboxes hide.

Verify addresses as close to the send date as the tooling allows, and act on the results: remove hard bounces and invalid addresses permanently, treat risky or catch-all results with caution rather than optimism, and re-verify any list that has been sitting unused, because people change jobs and mailboxes close. Check the targeting itself with a small manual sample. Read a handful of profiles by hand and ask whether the message makes sense for each person. If the sample contains people the offer clearly does not fit, the filter that built the list is too loose, and sending anyway trades a short term volume number for replies that say, accurately, that you did not check.

Finally, suppress properly. Anyone who has opted out, replied negatively, or been contacted in a recent campaign should be excluded by the system, not by someone's memory.

Want to put this into practice?

Reachium automates LinkedIn outreach, content publishing, and inbox management in one platform.

See Reachium →

What should you check in the copy itself?

Read the email as its recipient, a busy stranger with no context and no obligation. The subject line should be honest about what is inside. The opening line should show the message is about the recipient's situation, and any personalisation should be verifiably true: a wrong detail is worse than no detail, because it proves the personalisation was automated and unchecked.

Keep the body to one idea and one ask. A cold email that introduces the company, lists three capabilities, and asks for a call, a reply, and a referral has no clear next step, and unclear asks get deferred, which in an inbox means deleted. Cut anything that exists to make the sender feel thorough rather than to help the reader decide. Check the plain text rendering, the links, and the tracking settings, and proof the merge fields by sending a test to yourself with real sample data, because a broken placeholder in the first line is the fastest way to announce that a machine wrote to thousands of people at once.

Compare the approach against the alternative channel honestly as well. Some prospects are better reached elsewhere, and our breakdown of cold email versus LinkedIn outreach sets out when each channel earns the first touch.

What should be ready before the replies arrive?

Decide ownership in advance. Name who reads replies, what counts as a positive reply worth same day handling, how objections and not-now replies are logged, and how out-of-office and bounce responses are processed back into list hygiene. Set the follow-up rules at the same time: how many touches, at what spacing, and the point at which silence ends the sequence and retires the contact for a while.

Also decide what you will measure before the numbers arrive. Placement and bounce signals tell you about setup and list health; reply quality tells you about targeting and copy; meetings tell you about the offer. Agreeing the order of those questions in advance stops the common failure where a deliverability problem gets answered with a copy rewrite, or a targeting problem gets answered with more volume.

FAQ

How often should this checklist be run? Before every new campaign, and again whenever anything in the setup changes: a new domain, a new sending tool, a new list source, or a long gap since the last send. Items that were correct last quarter are assumptions this quarter until they are rechecked.

What is the single most skipped item? List verification close to the send date. Teams verify when a list is built, then send weeks later to addresses that have since gone stale, and read the resulting bounces as a deliverability mystery rather than a checklist item they skipped.

Should the checklist differ for a brand new domain? The items are the same; the volume answer changes. A new domain needs a completed warmup and conservative early volume, so the sending setup section takes longer to pass. The checklist does not shrink because the domain is new; if anything it matters more.

Can a checklist fix a domain with a damaged reputation? No. A checklist prevents avoidable damage and catches setup errors. A domain whose reputation is already damaged needs diagnosis and a gradual rebuild, and sending harder against the problem makes it worse. The checklist is how you avoid needing that rebuild twice.

Want to put this into practice?

Reachium automates LinkedIn outreach, content publishing, and inbox management in one platform.

See Reachium →

Sources

  • Internal posts cited by slug: /cold-email-deliverability-checklist (the deliverability focused routine), /cold-email-deliverability-2026 (authentication, warmup, and hygiene in depth), /cold-email-vs-linkedin (channel choice). Live posts, checked 2026-10-24.
  • No bounce rate, placement, or reply rate figures are cited in this post. Those numbers depend on the sender's own domain, list, and audience, and a checklist post should not borrow another program's figures as if they were the reader's targets.

Linked sources:

Want to automate what you just learned?

Reachium turns these strategies into automated LinkedIn campaigns that book meetings on autopilot.

See Reachium→

MORE FROM GTMSTACK