INTERSCOPE / REQUIRED BEFORE A LIVE LAUNCH

These are required release checks, not completed certifications.
The files are demonstration HTML and planning materials, not a deployed campaign.

[ ] Confirm publication owner, sender identity, editorial cadence and content scope.
[ ] Review the final content, primary sources and any commercial disclosures.
[ ] Configure and verify the sending domain and authentication with the selected ESP.
[ ] Implement title-specific signup and permission records; retain source and notice version.
[ ] Confirm any audience transfer is permitted; do not infer consent from topic preferences.
[ ] Implement actual preference and unsubscribe URLs, list-unsubscribe headers and suppression.
[ ] Map the data dictionary to provider-specific fields and identity requirements.
[ ] Test entry, duplicate entry, delays, missing name, missing topic and resubscription.
[ ] Test opt-out during a wait, complaint and hard-bounce handling before every next send.
[ ] Replace demonstration labels and footer controls only after the actual functions are connected.
[ ] Replace relative preview URLs and image paths with absolute live URLs and check every destination.
[ ] Test HTML and plain text in Gmail, Apple Mail and supported Outlook versions.
[ ] Check small screens, dark mode, blocked images, keyboard navigation and reading order.
[ ] Send only to authorized internal test addresses for QA before audience rollout.
[ ] Inspect delivery and unsubscribe events, including event retries and suppression latency.
[ ] Review the provider's current terms and content requirements before launch.
[ ] Approve the final audience, content version, schedule and rollback/stop procedure.

No subscriber data or credentials are included.