Resource

Cold email infrastructure checklist: verify, document and hand over

Use this checklist before launching or inheriting an outbound setup. Record evidence for the actual sending path, assign an owner to unresolved issues and pause when checks fail. Authentication is necessary preparation, not permission to contact someone or a guarantee of inbox placement.

Editorial update:

Use the template ↓Discuss your outbound plan →

Copy this infrastructure handover record

Original worksheet. Replace the bracketed fields after running the checks; this is not a completed audit or a claim about a real campaign.

  1. Setup and access record

    Project: [name] Accountable owner: [name or role] Sending provider and accounts: [inventory reference] Domain and DNS administrator: [role] Recovery access verified: [date and verifier] Approved sending purpose and recipient policy: [reference] Open access issues: [issue, owner, due date]

  2. Test and acceptance record

    Test date and sending account: [details] Controlled receiving address: [internal reference] Received-header evidence: [restricted location] Authentication and alignment findings: [observed results] Reply delivery test: [result and owner] Suppression test: [result and evidence] Unresolved checks: [pass/fail/not checked, owner, next action] Launch decision: [hold or approved scope, reviewer, date]

  3. Monitoring and handover record

    Review cadence and reviewer: [details] Provider logs and reporting locations: [links] Signals to review: [delivery errors, complaints, replies, opt-outs] Stop conditions: [specific agreed conditions] Person authorized to pause: [role] Escalation route: [internal contact] Change history and next review: [location and date]

Audit workflow
5 stages
Each acceptance check
Evidence + owner
Handover record
Copyable

Evidence to collect before accepting the setup

Scroll the table sideways to compare all columns.

Evidence to collect before accepting the setup
CheckEvidence to retainHold the launch when
Ownership and recoveryAccount inventory, named administrator and recovery-access checkThe responsible team cannot administer or recover an account
Actual sending routeTest date, sending account and received headers with private details removedThe observed route differs from the approved configuration
Reply and opt-out handlingControlled test showing a reply reaches its owner and a suppression is appliedReplies are unowned or opted-out contacts can re-enter a sequence
Monitoring and escalationNamed reviewer, review cadence, relevant provider logs and stop conditionsNobody can explain who pauses sending or investigates failures

Start with the recipient and provider rules

Google's sender guidelines cover personal Gmail accounts. They distinguish all-sender requirements from bulk-sender requirements: SPF or DKIM for all senders; SPF, DKIM and DMARC for bulk senders. Direct messages need From-domain alignment with SPF or DKIM to pass DMARC. Applicable bulk marketing and subscribed mail also needs one-click unsubscribe and a visible body link. Consult the linked guidelines for the full scope; do not apply one provider's thresholds universally.

Verify a message, not just a DNS screenshot

A published record does not show which route a particular message took. Keep a received test message from an address you control, its full headers, the sending account and the test date. Compare authentication results with the intended configuration. Never paste credentials or private recipient details into a public audit document.

Treat gaps as a handover decision

For each check, record pass, fail or not checked. Assign failed and unchecked items to someone who can resolve them. A handover is ready when the next operator can reproduce the checks and knows when to stop. The evidence table below is a suggested operating method, not a provider certification.

Action checklist

1. Ownership and sending purpose

  • List every domain, mailbox, sending tool and administrator

    An inventory makes renewals, recovery and later changes traceable.

  • Confirm provider policy and recipient eligibility

    Address verification does not establish that the recipient wants the message. Resolve policy and permission questions before scheduling.

  • Choose an identifiable sender and document the domain decision

    A separate domain does not make unwanted mail acceptable or isolate every reputation risk. Record the business reason and approval.

2. Authentication and message checks

  • Validate the configuration against the current provider documentation

    Use the records for the actual sending service. Do not copy another company's DNS configuration.

  • Review received-message authentication and alignment

    Record SPF, DKIM and DMARC results from the controlled test. Resolve discrepancies before scheduling further sends.

  • Confirm who owns transport and DNS issues

    Hosted and self-managed sending require different administrative access. Route findings to the team that can change the relevant setting.

3. Recipients, replies and suppression

  • Document list origin, eligibility review and deduplication

    A traceable source supports an investigation; a clean-looking file alone is not an acceptance test.

  • Hold uncertain addresses for review

    An uncertain verification result is not evidence that an address can receive mail. Do not automatically send a slower sequence to every catch-all address.

  • Test replies and opt-outs with controlled contacts

    Confirm both the inbox owner and the suppression behavior across tools. Keep test contacts separate from production recipients.

4. Controlled release

  • Approve a limited starting scope

    Document the audience, message, sending path and review point so changes can be investigated independently.

  • Avoid universal mailbox caps or warm-up deadlines

    A fixed number does not establish readiness. Follow the provider's restrictions and assess observed delivery behavior before expanding.

  • Record an explicit hold decision when checks fail

    Replacing accounts to continue through unresolved restrictions is not a corrective action. Investigate the underlying issue.

5. Monitoring and handover

  • Review signals by relevant sending path and recipient segment

    An overall average can hide a localized fault; retain enough context to reproduce it without exposing private data.

  • Retest after a provider or configuration change

    Compare new evidence with the previous accepted record and update the owner and date.

  • Give the next operator a usable evidence index

    They need access, open issues, stop conditions and an escalation route—not only a list of completed tasks.

Who this helps

  • RevOps teams inheriting an undocumented setup
  • Founders preparing an initial approved campaign
  • Agencies handing infrastructure to a client operator

Work through the process

  1. 01

    Inventory

    List the accounts, responsible people and applicable requirements.

  2. 02

    Test

    Use controlled receiving accounts to gather message and workflow evidence.

  3. 03

    Resolve

    Assign gaps and repeat failed checks before approval.

  4. 04

    Hand over

    Record the approved scope, monitoring owner and stop conditions.

Questions and answers

Does passing authentication guarantee inbox placement?
No. Authentication results are one part of the evidence. Recipient response, provider rules and sending behavior still matter; no checklist can promise a particular folder placement.
Is a paid warm-up tool required?
This checklist does not require one. A tool subscription or elapsed warm-up period is not an acceptance criterion. Check provider policy and actual test results.
Should I replace a mailbox when errors increase?
First hold the affected sends and investigate the provider response, configuration and recipient segment. Document the cause and corrective action before resuming.
Is this the same as buying infrastructure setup?
No. This is an ungated self-audit and handover worksheet. The linked setup service explains a managed engagement; ownership, deliverables and commercial terms must be confirmed in its proposal.

Sources and editorial notes

Provider requirements were reviewed on 12 September 2026. The evidence matrix and handover records are original editorial worksheets, not audited customer results. Provider requirements can change; consult the linked guidance. No inbox-placement, volume or timing guarantee is made.

Keep reading