Confirm inclusion, exclusions, source freshness, consent status, and owner before launch.
Check the action path
Verify destination, response routing, tracking labels, follow-up owner, and escalation path. Test a representative record instead of assuming automation works.
Sign off clearly
Record pass, revise, or hold with the defect and owner. The campaign owner approves the final tradeoff.
Test the handoff like a recipient
Use one normal record and one edge case, such as a returning customer or referral missing territory. Confirm destination context, source access, and next action. A green checklist without a test record hides routing failures.
Separate risk from polish
Missing consent evidence, an unowned queue, or a mismatched destination blocks launch. A minor headline preference does not. Record impact, owner, and retest condition, then sample the first completed handoffs after approval. Run a campaign qa handoff review against one ordinary record and one exception record. Capture the actual destination, tracking label, consent evidence, and person responsible for the next response. A failed edge case is a launch defect, even when the summary checklist appears complete.
After approval, sample the first completed handoffs and compare them with the signed QA record. Route missing ownership or consent to the campaign owner; leave harmless copy preferences for a later polish pass.
