High-Stakes Email Launch Readiness Audit
Verify email deliverability, rendering, tracking, and compliance before executing high-volume marketing sends.
Use this template when preparing a major promotional or product launch email campaign across diverse email clients. It systematically checks authentication, rendering safeguards, tracking parameters, and fallback mechanisms.
Role: Senior Email Deliverability Engineer & Technical QA Specialist
Context
- Organization & Brand: {{brand_name}}
- Campaign Concept & Objective: {{campaign_type}}
- Dedicated Sending Domain: {{sending_domain}}
- Target Audience Volume: {{target_segment_size}}
- Primary Call to Action & Goal: {{primary_conversion_goal}}
- Email Service Provider Architecture: {{esp_platform}}
Task
Generate an exhaustive pre-launch email QA checklist evaluating technical authentication, inbox placement risks, cross-client rendering fidelity, and data tracking accuracy for {{brand_name}}'s upcoming release.
Method
- Validate DKIM, SPF, and DMARC alignment for {{sending_domain}} to ensure zero policy rejections.
- Audit the sender reputation thresholds and suppression lists against {{target_segment_size}} to prevent hard bounce spikes.
- Scrutinize subject line and preheader combinations for spam-trigger keywords, rendering truncations, and personalization token fallbacks.
- Inspect responsive HTML layout, image-to-text ratio, dark mode styling overrides, and accessibility alt-text.
- Verify all UTM parameters, redirect chains, conversion tags, and deep-links against {{primary_conversion_goal}}.
- Confirm legal compliance disclosures, one-click unsubscribe headers, and physical footer address requirements.
- Structure findings into operational checklist items with severity ratings, verification steps, and owner assignments in {{esp_platform}}.
Constraints
- MUST categorize every check under Technical Deliverability, Rendering & UX, Tracking & Analytics, or Legal Compliance.
- MUST specify an explicit pass/fail verification method for every single item.
- Do not provide generic recommendations without actionable validation tests.
- MUST NOT omit fallback string validation for personalized dynamic tags.
Output format
Provide a structured markdown document containing:
- Executive Pre-Flight Summary (max 100 words)
- Deliverability & DNS Audit Checklist (4-6 items with status, impact, and test procedure)
- Creative, Rendering & Accessibility Checklist (5-7 items)
- Tracking, Links & Conversion Checklist (4-5 items)
- Sign-Off & Go/No-Go Gate Criteria (3 specific gating conditions)
Self-review
- Confirm all 6 variables are seamlessly embedded and contextualized.
- Verify every checklist item includes an explicit verification protocol.
- Check that total character count falls between 1400 and 2600 characters.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.