How do I set up a video ad approval workflow?
Use six gates: source intake, concept, script, rough creative, brand and compliance review, and final export. Give each gate a named approver, decision criteria, a version, a deadline and a change record, and approve risky claims before expensive production. Name one accountable final approver and one owner to consolidate conflicting feedback. Record launch and spending authority separately.
A reliable video ad approval workflow has six gates: source intake, concept, script, rough creative, brand/compliance review, and final export. Each gate needs a named approver, decision criteria, version, deadline, and record of what changed. Approve risky claims before expensive production.
Six approval stages
- Intake: Product facts, rights, audience, offer, restrictions.
- Concept: Insight, angle, format, proof, hypothesis.
- Script: Spoken words, visual beats, captions, CTA.
- Rough creative: Structure, product fidelity, pacing, UI.
- Brand/compliance: Claims, disclosures, identity, licenses, standards.
- Final export: Specs, audio, captions, files, destination, tracking.
Who approves what
Marketing owns campaign intent. Product verifies functionality and UI. Brand reviews identity and tone. Legal or compliance reviews claims where necessary. The media buyer confirms placement and tracking. The client or accountable leader gives final commercial approval.
One person can hold multiple roles, but the responsibilities should remain explicit.
What belongs in the brief
Audience, insight, objective, angle, approved promise, evidence, offer, format, placement, duration, CTA, assets, prohibited content, disclosure, due date, and success criteria.
Give actionable feedback
Use: timecode + observed issue + reason + requested outcome.
“At 00:08, the interface text is unreadable on mobile; zoom to the results panel and hold for one second” is better than “make it pop.”
Version naming
Include client/product, campaign, angle, format, hook, ratio, duration, language, version, and status. Never let “final-final-2” become the approval record.
Final delivery checklist
Provide masters, cutdowns, captions/transcripts, thumbnails, licenses, naming sheet, destination mapping, approval record, and source archive according to the retention policy.
Make each approval a recorded decision
A review link is a place to comment, not proof that a file is cleared for use. Record the exact version, the reviewer, the decision and any conditions. A useful set of statuses is needs review, changes requested, approved for production, approved for delivery and approved for launch. Define the meaning of each status before the first batch.
For example, approval of a script authorizes the production team to make that script. It does not automatically approve an altered voiceover, a different product claim or a later promotional offer. Keep the approved script available beside the rough cut so the reviewer can identify material changes without relying on memory.
Use a small approval register:
| Gate | Item the reviewer sees | Decision being requested | What stops progression |
|---|---|---|---|
| Concept | Angle, intended buyer and proposed proof | Is this the right argument to produce? | Missing product evidence or unclear audience |
| Script | Spoken lines, visuals and disclosure plan | Is the meaning accurate and approved? | Unsupported statement or misleading scene |
| Rough cut | Watermarked preview with stable timecodes | Does the execution match the approved idea? | Unreadable demo or incorrect product behavior |
| Delivery | Exact exports and asset manifest | Are these files complete and usable? | Wrong version, missing captions or rights record |
| Launch | Creative, destination and campaign instructions | May this package run under the agreed scope? | Unapproved offer, budget or destination |
Keep creative release and spending authorization explicit even when the same person owns both. An editor should not have to infer permission to launch from a comment saying the video looks good.
Resolve conflicting feedback without endless rounds
Consider a hypothetical software ad. The brand reviewer asks for a wider interface shot because it looks cleaner. The product reviewer asks for a closer crop because the important control is unreadable. Both comments are understandable, but sending them separately to the editor creates an unresolved design decision.
The approval owner should consolidate the outcome: keep the wider shot for context, then cut to a close-up during the product action. If duration prevents both, decide which purpose matters more for the brief. Send one instruction with the reason, rather than asking the editor to choose which stakeholder to disappoint.
Organize the review into factual errors, required corrections and preferences. Resolve factual errors first. Discuss preferences against the original objective and constraints. A subjective request can still be valuable, but it should not silently overrule an approved product requirement.
Set a feedback deadline and identify a backup approver in advance. When a deadline is missed, record the schedule consequence and request a decision. Do not treat silence as permission unless a clearly agreed process actually authorizes that action. The aim is an unambiguous release record, not a faster-looking spreadsheet.
Decide what needs another approval
Classify a revision by what it changes. Fixing a misspelled word may need a quick accuracy check. Replacing the headline can change the claim and require another script review. Changing the destination can change the context in which the offer is understood, even when the video file stays identical.
For a recurring program, agree a revision matrix at kickoff. Routine technical corrections can return to the relevant reviewer. Changes to product meaning, customer identity, offer, rights or scope should return to the accountable owner. If an apparently minor edit affects a disclosure or removes a limitation, handle it as a material change.
When a client requests a new direction after approval, show the choice clearly: finish the existing approved direction, replace it with the new direction, or schedule both. Record the effect on deliverables and dates before production continues. This is more useful than arguing over whether a comment counts as one round or two.
Review the whole impression of an AI-generated scene
Put product reference images and the approved script beside the generated preview. Check which details changed during generation: controls, packaging, scale, texture, labels and the physical interaction. A scene can look polished while showing a feature the product does not have.
Review the sequence as well as individual frames. A before-and-after transition might suggest a result that no spoken line claims. A presenter might appear to describe personal use when the approved concept was a brand explanation. Flag the intended interpretation during script review, then verify the actual interpretation in the final edit.
Use a specific correction request. For example, replace the generated close-up with approved product footage because the lid mechanism is wrong. If repeated generation cannot preserve the necessary detail, change the production method or simplify the scene. Approval should depend on accuracy, not on how many attempts have already been made.
Build a release manifest that survives handoff
The release manifest should identify the approved filename, creative ID, version, format, destination, offer, approval date and owner. Add a link to the rights and evidence records where appropriate. If another team receives the package tomorrow, it should be able to determine what may run without reading an entire chat history.
Review the actual exported file, not only the editing timeline. Check the beginning and ending, audio, captions, image boundaries and the product shown beside the CTA. Confirm that cutdowns preserve necessary context. A shorter version can become misleading if the editor removes the sentence that explained a limitation.
Archive replaced versions so they cannot be mistaken for current deliveries. Keep a record of what changed, rather than deleting the history needed to investigate a later question. Agree access and retention rules with the client instead of assuming every stakeholder needs the complete source archive.
Prepare a correction path before a problem appears
Name the person who can stop use of a released asset and the person who can approve its replacement. If a factual issue is discovered, identify every version that contains it, notify the campaign owner and record which files require replacement. Where the campaign team determines that use should stop, confirm that action explicitly.
After correcting the file, repeat the affected review gates and update the manifest. Do not reuse the old approved filename for a materially changed asset. Close the incident with a brief explanation of the source error and the prevention step, such as a product-reference check or a clearer boundary on script improvisation.
Move approved briefs into production
Knowlify offers end-to-end Meta ads, combining creative production and campaign management under an agreed approval process. Creative-only support is also available for teams that manage their own campaigns. Define client approval, launch authority and reporting responsibilities on your planning call, with media spend separate from service fees. See how creative as a service fits a recurring review process.
Related video marketing guides
Continue with animated ads versus UGC, scaling video ad creative, or our video ad campaign briefs.
Check the claim before production
The FTC says advertisers need evidence for their claims. Use its advertising guidance when reviewing the brief.
FAQ
Who should give final approval?
Name one accountable decision maker in the brief. Product, brand, legal and media reviewers can supply their checks, but final delivery should have one unambiguous approval record.
What makes revision feedback useful?
State the version, timecode, observed issue and requested outcome. Explain the product or campaign reason so the editor can solve the problem without guessing.
When should claim review happen?
Review claims at the brief and script stages, then check the final edit for new visual implications. Late review can reveal a problem after the footage and captions have already been produced.
Does approving the video authorize the agency to launch it?
Define that explicitly in the engagement. Creative approval confirms a version is acceptable; launch can also depend on the destination, offer, budget and campaign instructions. Record who can authorize spending and who can release the final package. This matters whether production and Meta campaign management sit with one partner or different teams.
What happens when the product changes after an ad is approved?
Identify every version affected by the change and ask the campaign owner to review its current use. Update the script, footage, captions and destination as needed, then repeat the affected approval gates. Give the corrected asset a distinct version and update the release manifest so the old file cannot be mistaken for the current delivery.