Build a campaign launch QA command center before anything goes live

Start in Airtable and create one campaign launch record before any asset review begins. Add fields for launch date, campaign owner, target audience, offer, channels, landing page URLs, form URLs, UTM naming, HubSpot campaign, CRM handoff, approval owners, success metrics, risk level, and launch status. Mirror the same major milestones in Asana with tasks for asset completion, web QA, tracking QA, approval review, and first-48-hour monitoring. The output should be a single source of truth that tells anyone what is launching, who owns each gate, and what still blocks launch. QA check: every channel in the brief should have at least one owner, one asset row, one tracking row, and one approval field.

Add each landing page, email draft, ad, social post, form, thank-you page, calendar link, downloadable asset, creative file, sales note, and enablement document into the Airtable asset table. Include fields for channel, source URL, draft URL, owner, reviewer, approval status, dependency, due date, and final live URL. For Webflow pages, include both staging and production URLs so reviewers can separate draft review from live QA. For HubSpot assets, include the campaign association, form name, workflow name, list name, and conversion event that should fire after submission. QA check: no asset should be marked launch-ready unless it has a source URL, owner, reviewer, final destination, and tracking requirement.