Creative · Launch preparation

Creative handoff checklist: what an ad needs before launch

By Mirow · October 5, 2026 · 7 min read

A paid social creative handoff needs the approved message and supporting evidence, the exact files and copy to use, a destination that matches the offer, a named launch approver, and a measurement plan. The media buyer should be able to build the intended ad without guessing which version is current or what the business has agreed to say.

Treat the handoff as a decision record attached to the assets. The checklist below is Mirow's recommended operating method for a brand and its creative or media partner. It separates a finished export from an ad that is ready to launch.

Define what the creative is meant to test

Put one sentence at the top of the handoff: who the ad addresses, which buying reason it presents, and what you want the viewer to do. For example, a hypothetical lunch-container brand might compare the convenience of packing a meal with the convenience of storing the empty containers. Those are two different reasons to buy.

For this workflow, a concept is the central buying reason. A hook variant changes how that concept opens. A format adaptation makes the same execution work in another shape or placement. Agree on these definitions before counting deliverables; a resized file should not quietly become another creative idea in the production report.

Include the question the media plan can actually answer. If the aim is to compare concepts, decide how hook choices, audiences, offers and delivery will be handled. If the aim is simply to put more usable creative into ordinary delivery, label it that way. Uploading several ads does not by itself create a controlled experiment.

This is also the point to assign responsibility. The creative lead supplies the message and assets; the brand's approver confirms product claims and commercial terms; the media buyer checks the build and proposed delivery. Give website or measurement dependencies to their actual owners. Our agency versus in-house guide explains how to divide those responsibilities before hiring another operator.

Use an acceptance checklist with visible evidence

Keep a single handoff document with links to the current assets. Each row should have a named owner, a status and the evidence needed to close it. “Approved in chat” is not enough if nobody can identify which file, copy or offer that approval covered.

Scroll horizontally to see all columns.

These are acceptance questions, not a requirement to create five new documents. A small launch can use one page and an asset folder. The useful part is the link between the approved decision and the files that will run.

For objective claims in U.S. advertising, the FTC's substantiation policy calls for a reasonable basis before the claim is disseminated, including reasonable implied claims. In the handoff, connect the actual wording and demonstration to the supporting evidence. A study about a different product or a general product description is not automatically support for this execution.

For footage, music, photographs and creator content, record the intended paid use and any channel, territory or time restrictions. Ask the responsible owner to resolve missing permission. A file arriving in a shared drive does not tell the buyer what use was agreed.

Count the exports, then show which ones can launch

Consider a hypothetical launch with two concepts, two hooks per concept and two format adaptations per hook. The team chooses 9:16 and 4:5 for this plan; those choices are not a claim that either export fits every placement.

The production count is 2 concepts × 2 hooks × 2 formats = 8 exports. There are four concept-and-hook combinations. None of those counts establishes that eight ads were built, that eight ads delivered, or that eight independent tests happened.

Suppose six exports pass review. The remaining two use a storage claim whose evidence has not been supplied to the approver.

Scroll horizontally to see all columns.

Both C02-H02 formats stay on hold. The missing support is a handoff blocker; this example does not establish that the claim is false. The owner can supply suitable evidence or revise the message and route the changed files for approval.

A partial launch now leaves two hook variants for the packing concept and one for the storage concept. That changes the planned comparison. The decision owner should choose whether to wait, redesign the comparison, or launch the six accepted exports as an explicitly reduced delivery plan. Do not silently present the reduced plan as the original test.

Use filenames that preserve the mapping, such as c02-h01-9x16-v03.mp4. Record the selected revision in the handoff, and keep superseded exports out of the folder the buyer uses for launch. When the ad is built, add its platform ad ID to the record. The file name alone will not tell a later reviewer which ad delivered.

Review the ad as it will appear to the customer

Preview each selected placement using the exact export, copy and destination. Check the opening frame, readable text, captions, product detail, CTA and any interface covering the image. Listen to the sound and review it muted. A technically valid upload can still hide the price, crop the demonstration or lose its meaning without audio.

Treat changes in the ad-building tool as part of the approved execution. If cropping, overlays or other creative settings change what the viewer sees, record those settings and review the resulting preview. An approval of the original video should not leave everyone guessing about the version assembled in the account.

Then open the exact destination on a phone. Confirm the correct product and variant, the stated offer, availability and the next action. Follow redirects and check that any campaign parameters survive as intended. A review link to a product page is insufficient when the ad uses a different URL. The ad-to-page promise diagnostic provides a fuller check when the message and buying experience do not line up.

Keep the preview or screenshot alongside the approval record. State who accepted it, when, and which file, copy and destination were covered. For a material change to the claim, offer, destination or execution, return the changed parts to the relevant approver.

Separate traffic labels from purchase measurement

UTM parameters label where traffic came from; they are not a purchase-event test. Google's campaign URL guidance explains how source, medium and campaign parameters identify referred traffic, and how utm_content can distinguish creatives. Choose a consistent naming scheme and connect it to the creative IDs in the handoff.

For a sales campaign, ask the measurement owner for separate evidence that the intended purchase event is received by the platform used for optimization, with the expected value and currency. Record the environment and date of the check, and resolve duplicate-event issues where relevant. Preserve the site's consent behavior during testing.

If GA4 is part of the reporting setup, Google's purchase-event guide shows how to send the event and verify it in DebugView. That confirms the test event and inspected parameters reached GA4. It does not, by itself, validate the Meta event used by the ad account.

Record an unresolved measurement issue as a dependency with an owner and a launch decision. It should not be hidden by a checked box saying “UTMs added.” The creative team can finish its deliverable while the launch remains blocked elsewhere.

Close the handoff with a decision

The final record should say ready, held, or reduced scope approved for the exact launch package. Name the person who may authorize spending, the limit they approved and the next review date. Creative approval alone is not authorization to change the media budget.

After launch, add the ad IDs, first-delivery dates and any deviations from the approved plan. Keep “exported,” “approved,” “built” and “delivered” as separate states so the next weekly paid media report can describe what actually happened.

For the next handoff, choose one upcoming concept and walk through the acceptance table with the person who will build the ad. Every unanswered question becomes either a correction before launch or a named dependency with a decision date. That is the work the handoff needs to finish.