Lifecycle Decisioning & Human+AI
Pre-Send QA Checklist: 25 Checks That Prevent "Oops" Emails (Plus Three Apology Templates)
By Artem KukharenkoPublished Updated 8 min read
Updated 1 November 2026. Download the checklist as CSV or PDF below; no email required.
The 25 checks
Group 1: Audience (the group that causes the expensive mistakes)
Scroll for more → On small screens, choose cards for wide tables.
| # | Check | How to verify | Fail means |
|---|---|---|---|
| 1 | The right segment is selected, and it is the segment the brief names | Open the segment; read its conditions, not its name | Wrong audience |
| 2 | Recipient count is within the normal range for this program (for example, within 25% of the last five sends) | Compare to the sends log | A broken segment condition, or a full-list send by accident |
| 3 | Suppressions applied: unsubscribed, complained, bounced, in a sunset flow, and suppression lists from other systems | Segment exclusions visible; reconciliation current | Complaints and bounces |
| 4 | Unengaged tier excluded for campaigns (received 5+ emails, no click in the inactivity window) | Exclusion present | Engagement and placement drop |
| 5 | No profile mailed in the last 90+ days without an approved reactivation plan | Filter the segment by last send | A cold-list blast |
| 6 | Frequency cap respected across brands and programs for everyone in the segment | Cross-program check | Fatigue, unsubscribes |
| 7 | Seed and test addresses included; internal "do not mail" list excluded | List check | No visibility of the real send; internal complaints |
Group 2: Headers and authentication
Scroll for more → On small screens, choose cards for wide tables.
| # | Check | How to verify | Fail means |
|---|---|---|---|
| 8 | From name and From domain are the usual ones for this program | Preview headers | Recognition loss; alignment failure |
| 9 | Reply-To is a monitored mailbox | Send a test, reply to it | Lost replies; Microsoft recommends a valid, monitored P2 address |
| 10 | One-click unsubscribe headers present (List-Unsubscribe, List-Unsubscribe-Post) |
Send a test to Gmail; look for the Unsubscribe link next to the sender | Non-compliance for bulk senders |
| 11 | SPF, DKIM and DMARC pass and align on the test | Gmail "Show original" | Rate limits or rejections |
| 12 | Tracking and link domains are branded and resolve | Click two links in the test | Shortener or unknown-domain filtering |
Group 3: Content
Scroll for more → On small screens, choose cards for wide tables.
| # | Check | How to verify | Fail means |
|---|---|---|---|
| 13 | Subject line and preheader have no placeholders, test text or wrong brand | Read them in the inbox preview | The classic "oops" |
| 14 | Personalization fields have fallbacks ("there" if no first name) | Send to a test profile with blank fields | "Hi FNAME" |
| 15 | Every link goes where its text says, with the right UTM | Click every link | Broken promise; wrong attribution |
| 16 | Offer, price, dates and codes match the brief | Read against the brief | Costly correction |
| 17 | Visible unsubscribe link and physical address in the footer | Footer check | CAN-SPAM and provider requirements |
| 18 | Images have alt text; plain-text version exists and reads correctly | Toggle images off; view plain text | Blank email in some clients |
| 19 | Renders on mobile; no horizontal scroll; buttons tappable | Device preview | Lost clicks |
Group 4: Timing
Scroll for more → On small screens, choose cards for wide tables.
| # | Check | How to verify | Fail means |
|---|---|---|---|
| 20 | Send time and time zone are what the brief says | Scheduler | 3 a.m. sends |
| 21 | No other send to the same audience within the cap window | Calendar check | Fatigue |
| 22 | Nothing in the news, the product or the account (outage, incident) makes this send wrong today | Ask | Tone-deaf send |
Group 5: Compliance
Scroll for more → On small screens, choose cards for wide tables.
| # | Check | How to verify | Fail means |
|---|---|---|---|
| 23 | Everyone in the segment has consent for this message type and brand; no transactional template carries promotional content without unsubscribe | Consent field; template type | Violations; complaints |
| 24 | Regulated content reviewed (health, finance, claims, sweepstakes); for healthcare, nothing patient-specific in a marketing stream | Reviewer sign-off | Legal exposure |
Group 6: Measurement
Scroll for more → On small screens, choose cards for wide tables.
| # | Check | How to verify | Fail means |
|---|---|---|---|
| 25 | Campaign named by convention, goal and primary metric recorded, holdout or cohort frozen if this is a test | Campaign record | Unmeasurable send |
Checks 1–7, 10–12 and 21 are deterministic, which is why they can be automated. Campaign Error Shield validates the audience, the status of every profile and the headers before launch, and blocks sends that fail. See the application →
Your 25-check pre-send review
Results stay in this browser when local storage is available. No account or upload is required.
0 of 25 reviewed · 0 failed
What to automate, what to keep human
Scroll for more → On small screens, choose cards for wide tables.
| Automate (deterministic) | Keep human (judgment) |
|---|---|
| Segment size vs norm; suppression reconciliation across systems; unengaged-tier exclusion; 90-day cold check; frequency caps; header presence; authentication pass on a test; placeholder and test-text detection; link resolution | Right audience for the message; truth of the claim; timing against the news; tone; regulated content |
The automated half is the same set of gates the decision waterfall runs for every profile (validation, consent, status, frequency); a pre-send checklist is that waterfall applied to a whole campaign at once.
When it fails anyway: correction rules
- Decide fast whether a correction is needed. A wrong link, wrong price or wrong audience: yes. A typo: no. Inbox Collective's guidance and Fulcrumtech's correction how-tos agree on the principle: correct what misleads, ignore what merely embarrasses.
- Send only to the affected recipients. Everyone else gets nothing.
- Say it in the subject line. "Correction:" or "Oops, the right link" beats a clever subject.
- Keep it short, plain and signed by a person. One sentence on what happened, the fix, optionally a make-good, done.
- Log it. Cause, segment, count, what changed in the checklist.
- Do not resend the whole campaign. Two full sends in an hour is a frequency and complaint problem on top of the original mistake.
Three apology templates (original copy)
Template 1: wrong link or placeholder
Subject: Oops, the right link this time Preheader: Our last email pointed to the wrong place. Sorry. Hi [first name], the email we sent earlier today had a broken link. Here is the right one: [Link text]. Nothing else has changed. Sorry for the extra email. [Name], [Brand] [Unsubscribe] · [Address]
Template 2: wrong segment
Subject: That email wasn't meant for you. Sorry. Preheader: No action needed. Hi [first name], earlier today you received an email about [topic] that was intended for a different group of customers. Please ignore it; nothing changes for your account or subscription. If you'd rather not get emails from us at all, the link below works in one click. [Name], [Brand] [Unsubscribe] · [Address]
Template 3: wrong offer or price
Subject: Correction: the [offer] details Preheader: We got a number wrong. Here is the right one. Hi [first name], our earlier email listed [wrong detail]. The correct [detail] is [right detail], valid until [date]. If you already [acted] based on the wrong information, reply to this email and a person will sort it out. [Name], [Brand] [Unsubscribe] · [Address]
FAQ
What should an email pre-send checklist include? Audience (segment, size, suppressions, unengaged exclusion, cold-profile check, frequency), headers (From, Reply-To, one-click unsubscribe, authentication, link domains), content (placeholders, fallbacks, links, offer accuracy, footer, alt text, mobile), timing, compliance and measurement. Twenty-five checks above.
How long does a pre-send check take? About ten minutes for a routine campaign when the deterministic checks are automated; twenty when done by hand.
Should I send an apology email for a typo? No. Correct what misleads (links, prices, dates, audience), not what embarrasses. A second email for a typo is an unnecessary send.
Who should receive a correction email? Only the recipients of the original mistake, and only if the mistake affects them. Never the whole list.
How do I stop wrong-segment sends? Compare the recipient count to the program's norm before every send, read segment conditions rather than names, reconcile suppressions across systems, and block sends automatically when a profile fails status checks.
Is a wrong-segment send a deliverability problem? Yes. Recipients who should have been suppressed or who did not expect the mail complain, and complaints are what mailbox providers measure. One bad send can push a day over Gmail's 0.3% limit.
Want the deterministic checks enforced automatically before every launch? Campaign Error Shield validates audience, status and headers and blocks sends that fail. See the application →
Sources
- Benchmark Email, Email pre-send checklist (2026): links, preview text, segment, mobile, subject. https://www.benchmarkemail.com/blog/email-pre-send-checklist/
- Inbox Collective, How to send an apology email: sender name, subject, preheader placeholders, audience confirmation, correction principles. https://inboxcollective.com/how-to-send-an-apology-email/
- Fulcrumtech, Oops! Email Mistake–Correction How-tos: correct quickly, target only affected recipients, flag in subject line. https://fulcrumtech.net/resources/oops-email-mistake-correction-how-tos/
- Really Good Emails, Oops-proofing your emails like a pro; Smart Insights, Email marketing broadcast checklist. (Practitioner checklists.)
- Google, Email sender guidelines: one-click unsubscribe, spam-rate thresholds. https://support.google.com/a/answer/81126
- Microsoft, Outlook's New Requirements for High-Volume Senders (April 2025): valid Reply-To, functional unsubscribe.
- FTC, CAN-SPAM Act: A Compliance Guide for Business: physical address, accurate headers.
- EngageMKTG, Campaign Error Shield, Applications (decision waterfall), Email Marketing Audit Template (internal).
Cite this page
Pre-Send QA Checklist: 25 Checks That Prevent "Oops" Emails (Plus Three Apology Templates). Artem Kukharenko. EngageMKTG. 2026-11-02. https://engagemktg.com/knowledge/pre-send-email-checklist
Related articles
- Agentic Marketing: Definition, What's Real in 2027, and a Governance Checklist for Email Teams
- Email Sender Requirements 2027: Gmail, Yahoo and Microsoft Rules Side by Side (Updated Monthly)
- Email Unsubscribe, Spam Complaint and Bounce Rate Benchmarks: Healthy, Warning, Critical
- Why Are My Emails Going to Spam All of a Sudden? A 15-Minute Diagnostic for Gmail, Outlook and Yahoo