Email campaign handoff checklist

Before source review

Freeze the campaign version you intend to hand off. List the destination hosts and exact UTM values the campaign should use; these are campaign expectations, not universal email rules.

1. Collect the final HTML files without renaming or reformatting them.
2. Record the approved landing-page hosts, including whether subdomains are allowed.
3. Record only the UTM keys and exact values that should be consistent across this campaign.

During EmailReady review

Run all files together so cross-template tracking differences are visible. Correct only destinations or alt values you have reviewed. Keep template expressions, signed destinations, conditional branches, and unsupported source for manual platform review.

1. Resolve every action-level source defect.
2. Record each intentional review finding or leave it explicitly open.
3. Undo and recheck any correction that does not match the approved source change.
4. Save the local project before leaving the device or opening Checkout.

What to include in the handoff

The EmailReady QA package contains exact originals, reviewed HTML, readable HTML and JSON reports, and a hash manifest. The local project file is separate: it can reopen the source and replay verified corrections, but it is not proof of purchase. Purchase recovery restores active access only and cannot restore either file.

1. Attach or archive the QA package with the campaign ticket.
2. Keep the local project file only where customer source is permitted.
3. Call out every open or manual-review finding in the handoff note.

Final checks outside EmailReady

Send representative personalization through the real sending platform. Open destinations from delivered test messages, inspect the target inbox clients, confirm unsubscribe and platform-added tracking, and complete your accessibility, legal, and deliverability review. EmailReady does not perform those checks.