Creative operations guide
What Does “Done” Mean for an Ecommerce Ad Creative?
An editor’s finished export is not necessarily a launchable ad. D2C teams need a shared definition of done that separates creative execution from platform compliance, commercial checks, and final launch approval.
Direct answer
What should “done” mean before an ad enters the launch queue?
An ecommerce ad is done only when it is launch-ready: the exact approved version has every deliverable required by the media plan, passes factual and brand review, includes an intact source package, meets current placement specifications, uses cleared assets, points to a verified destination, and has recorded approval from named owners. “The edit is finished” should mean only edit-complete. Use four enforceable states—concept-complete, edit-complete, platform-ready, and launch-ready—and admit only launch-ready work to the launch queue.
01
Why does one generic “complete” status fail?
“Complete” fails when it describes the editor’s activity rather than the asset’s accepted condition.
A creative can look polished while remaining unusable. It may be missing a square crop, contain an expired offer, point to the wrong product page, lack commercial music rights, or have essential text hidden by a platform interface. None of those defects necessarily prevents an editor from calling the visual edit finished.
Requirements also vary by campaign and placement. Google describes responsive ads as combinations of assets and currently recommends horizontal, square, and vertical images for relevant formats. TikTok’s in-feed specifications distinguish vertical, horizontal, and square video, while safe areas can depend on dimensions, caption length, and additional format elements (Google Ads Help; TikTok Ads Manager).
Therefore, “all ratios delivered” should mean every ratio assigned in the current media plan—not an assumed package used for every campaign. A 9:16 video can be edit-complete while failing platform-ready acceptance because the campaign also calls for 1:1 or 16:9 deliverables.
Statuses should name what has been accepted. Avoid labels such as “final,” “almost done,” or “ready” unless the team has written criteria for them.
02
What are the four acceptance states?
The four states separate approval of the idea, execution of the edit, compliance with placement requirements, and readiness for trafficking.
Use this acceptance table as the minimum operating standard. Add campaign-specific rows when a category, market, platform, or promotion creates additional requirements.
| State | Acceptance criteria | Primary owner | Required evidence | |---|---|---|---| | Concept-complete | Audience, product, hook, claim, offer, CTA, format, placements, and required variants are defined; factual and brand concerns are resolved | Creative lead or strategist | Approved brief, script or storyboard, claim references | | Edit-complete | The approved idea is executed; picture, audio, captions, branding, product details, and end card are checked; editable materials are collected | Editor | Review export, project file, source media, linked assets, transcript, manifest | | Platform-ready | Every media-plan variant meets the assigned placement’s current ratio, dimensions, duration, file, size, safe-area, text, caption, and audio requirements | Editor produces; media buyer verifies | Deliverable manifest, upload check, placement previews | | Launch-ready | Destinations, offers, dates, tracking, rights, disclosures, approvals, naming, and campaign mapping are verified | Named launch owner | Checked URLs, preview evidence, rights records, approval log, trafficking sheet |
Only the fourth state authorizes entry to the launch queue. Teams can adapt these states in a roadmap, but moving an item must indicate acceptance—not merely that work has started.
03
How should concept-complete acceptance work?
Concept-complete means the intended message is specific, supportable, and approved before production effort is spent on it.
The brief should name the target customer, product or SKU, core angle, hook, objective claims, offer qualifications, CTA, intended campaign, placements, required variants, creator or testimonial status, reviewer, and final approver.
Claims need support before publication. The FTC states that advertisers must possess proof for objective claims and that a money-back guarantee does not substitute for substantiation (FTC advertising FAQs). Endorsements also require attention to truthful experience, claim support, and disclosure of material connections (FTC endorsement guidance).
Reject the concept if its central claim is unsupported, the offer remains undefined, the CTA conflicts with the intended destination, required variants are unknown, or nobody has authority to approve it. Do not ask the editor to resolve strategic or evidentiary ambiguity through visual choices.
- Record the intended audience, product, angle, hook, offer, CTA, placements, and variants.
- Attach substantiation or an authorized reference for every objective claim.
- Identify creator relationships, testimonials, and likely disclosure requirements.
- Name the person who can approve or reject the concept.
- Approve the brief, script, or storyboard before treating the concept as complete.
04
What must the editor provide for edit-complete acceptance?
Edit-complete requires both an approved viewing version and a recoverable master package.
A flattened export is insufficient when the team may need another crop, corrected claim, new end card, expired-offer replacement, or future iteration. The handoff should include the current editable project, original or approved source footage, linked graphics, product images, fonts or documented replacements, music, voice-over, sound effects, script, caption transcript, clean master, final review export, and a manifest explaining versions and dependencies.
Review the execution against the approved concept. Confirm that the product, packaging, color, and SKU are correct; spoken and written claims agree; prices, dates, percentages, and qualifiers match the brief; captions match dialogue; audio is intact; logos and text are legible; and the export contains no watermarks, placeholders, offline media, black frames, or unintended platform interface elements.
Feedback should point to the exact version and location. Frame.io, for example, supports comments attached to frames or time ranges, illustrating how timecoded review reduces ambiguity (Frame.io commenting guide). The specific review tool matters less than preserving one authoritative decision trail.
Reject edit-complete acceptance when source dependencies are missing, factual errors remain, open review notes are unresolved, the final export differs from the approved script, or nobody can identify which file was approved.
05
How do you decide whether an ad is platform-ready?
Build the deliverable manifest from the actual media plan, then verify every assigned placement against current platform requirements.
For each placement, record the platform, placement name, aspect ratio, pixel dimensions, duration, file type, size limit, safe-area template, on-video subtitles, ad caption or primary text, headline, description, thumbnail, CTA, destination, language, and market. The media buyer should verify current specifications because platforms can impose format-specific requirements.
Treat two kinds of captions separately: on-video subtitles, which communicate spoken content inside the asset, and the ad caption or primary text, which is entered during trafficking. If the ad’s essential meaning disappears when muted, require accurate on-video subtitles or equivalent text treatment even if a platform does not technically mandate them. TikTok’s creative guidance recommends captions or text overlays for context and keeping important elements within interface-safe areas (TikTok creative best practices).
Preview meaningful variants with their real caption length, page identity, CTA, thumbnail, overlays, and destination. TikTok notes that safe zones can vary with elements such as caption length and additional formats, and that previews may differ slightly from live presentation (TikTok in-feed specifications).
Reject platform-ready acceptance if a required placement is absent, an upload fails, dimensions or duration are invalid, subtitles are inaccurate, or essential claims, products, logos, disclosures, or CTAs are cropped or obscured.
06
What must be checked before launch-ready approval?
Launch-ready approval verifies the commercial reality around the asset: destination, offer, tracking, rights, disclosures, campaign mapping, and authorization.
Open the final URL rather than reviewing it as text. Confirm that the page resolves on mobile, tracking parameters do not break it, the advertised product is visible and available, the currency and geography match targeting, promo codes work, and price, discount, bundle, gift, shipping terms, start dates, and expiration dates agree with the ad.
Google requires ad destinations to be functional, navigable, useful, and relevant, and identifies issues such as inaccurate display URLs, unfinished sites, and destinations that fail in common browsers (Google advertising policies). TikTok’s ad-format policy requires consistency among the product, brand, offer, caption, CTA, and landing page (TikTok ad format policy).
Confirm documented commercial rights for footage, photography, creator likeness, testimonials, music, effects, fonts, templates, third-party logos, and media clips. Records should cover applicable platforms, territories, terms, and paid-media use. “The editor found it online” is not rights evidence.
Required disclosures must appear where audiences can notice and understand them—not solely in an internal brief. FTC guidance says qualifying disclosures should be clear, close to the relevant claim, and not hidden by small type, brief timing, or distracting presentation (FTC advertising FAQs).
Finally, verify the campaign and ad-set mapping, naming, identity, CTA, destination, and exact asset version in the platform preview. The launch owner should be able to reproduce the approval decision without asking the editor for missing context.
07
Who owns each acceptance decision?
Assign one accountable owner to every decision, even when several people contribute information or review comments.
A practical ownership model is: creative lead for strategic fit; designated claims or compliance owner for substantiation; editor for execution and source-package completeness; producer or rights owner for licenses; brand approver for brand acceptance; editor for producing assigned ratios; media buyer for current platform specifications; ecommerce or merchandising owner for product and offer accuracy; media buyer or growth operator for tracking and campaign mapping; and one named launch owner for admission to the queue.
A reviewer is not automatically an approver. Reviewers can identify defects; approvers have explicit authority to accept, reject, or authorize a documented exception. Keep the decision, date, exact version, and evidence together. Avoid “shared ownership,” which often means nobody is responsible for the final check.
ATIYO can organize the roadmap, brief, brand context, assets, iterations, approvals, and reusable learnings around this process. It does not connect to ad accounts, buy media, calculate ROAS, or independently know performance. Media performance remains in the ad platform. ATIYO preserves the creative context and learnings around what was made, why it was made, how it was approved, and what should inform the next iteration.
08
When should the team accept, reject, or conditionally accept?
Accept only with complete evidence, reject every hard blocker, and reserve conditional acceptance for documented non-blocking exceptions.
Accept when every required checklist row has passed or has been marked not applicable by an authorized owner. Evidence must be accessible, attached to the exact launch version, and sufficient for another operator to reproduce the decision.
Reject for a missing placement, wrong product or offer, unsupported claim, broken destination, absent commercial rights, missing mandatory disclosure, unresolved approver rejection, unusable source package, failed upload requirement, or preview that obstructs essential information. These are launch blockers, not small cleanup tasks.
Conditionally accept only when an issue cannot affect legality, rights, factual accuracy, destination integrity, technical delivery, or required approval. Record the exception, why launch remains safe, affected placements, owner, due date, and person authorizing it. Never use conditional acceptance to protect a deadline from a genuine blocker.
The final standard is simple: a creative is done when the launch owner can identify the approved version, locate every planned deliverable, open the working destination, verify the offer and claims, find the source package and rights evidence, inspect placement previews, and reproduce the approval trail without requesting missing context.
- Complete every required gate and attach its evidence.
- Confirm that the approved version and trafficking version are identical.
- Resolve hard blockers rather than converting them into exceptions.
- Record any permitted exception with an owner, due date, scope, and authorization.
- Move the creative into the launch queue only after the named launch owner accepts it.
Frequently asked questions
Questions about this workflow
Is an editor responsible for making an ad launch-ready?
The editor should own execution quality, source-package completeness, and production of assigned variants. The media buyer should verify current platform requirements, while ecommerce, rights, claims, brand, and launch owners approve their respective areas. One person should not silently inherit every commercial and technical decision.
Should every ad always have 9:16, 1:1, and 16:9 versions?
No. Required variants should come from the actual media plan and assigned placements. A standard bundle may be operationally convenient, but “done” means all planned deliverables exist—not that every possible ratio was produced.
Can a creative enter the launch queue with a minor issue?
Only through documented conditional acceptance, and only if the issue cannot affect claims, rights, disclosures, destinations, offers, technical delivery, or required approvals. The exception needs an owner, due date, affected scope, reason, and authorized decision-maker.
Does ATIYO verify ad-platform performance or ROAS?
No. ATIYO does not connect to ad accounts, buy media, calculate ROAS, or know performance unless a user records it. Media performance remains in the ad platform; ATIYO preserves creative context, assets, decisions, iterations, and learnings.
Primary and official sources
Sources used in this guide
External product facts were checked against the organizations’ own documentation. Features can change; confirm current details before making a purchase or campaign decision.
- Google Ads specs: ad formats, sizes, and best practices Consulted for responsive-ad asset formats and image-ratio guidance.
- TikTok Auction In-Feed Ads Consulted for in-feed ratios, technical requirements, safe areas, and preview caveats.
- FTC Advertising FAQs Consulted for claim substantiation and disclosure guidance.
- FTC Advertisement Endorsements Consulted for endorsement truthfulness, substantiation, and material-connection principles.
- TikTok Creative Best Practices Consulted for captions, text overlays, and safe-area practices.
- TikTok Ad Format and Functionality Policy Consulted for creative quality and consistency among ad elements and destinations.
- Google Advertising Policies Consulted for destination functionality and relevance requirements.
- Frame.io Commenting Guide Consulted for frame-specific and time-range review-comment functionality.
Move the plan out of scattered sheets
Run the roadmap, briefs, assets, and learnings in ATIYO.
ATIYO keeps the brand context and production decisions connected. It does not buy media, connect to ad accounts, or invent performance results.