Your team has several versions of an AI-generated ad ready to launch. Who needs to approve each one, and which changes need another review?
Start by assigning decisions to the people who can make them. A production owner can check a crop; a new product claim needs its responsible owner’s review.
The workflow below shows what to approve before generating a batch and how to route later changes. Every finished ad still gets a human release check, so faster production can lead to approved ads your team can test.
The short version: Approve the claim, offer, brand boundaries, and reviewer roles before generating a batch. Minor crop or formatting fixes can follow a lighter review; a new product promise needs the responsible owner’s approval. Tie each approval to the exact ad file, and require a final human check before launch. Track how long that process takes.
What should you approve before generating a batch?
Approve the audience, offer, supported claims, and creative concept before producing variants. Then define which elements may change and which must remain fixed. Attach a representative master so reviewers share the same reference.
These decisions define what the team may produce. Each model output still needs review.
A campaign brief might allow alternate opening shots while protecting the product demonstration and offer terms. Another might permit aspect-ratio changes only. Those are different assignments, even when both request 12 assets.
Our guide to briefing an AI creative agency covers the strategic inputs. Turn those inputs into an approval record that a producer can consult without reconstructing a kickoff meeting.
Record the following before work starts:
- The approved master file and its version.
- The claim wording and the evidence supporting it.
- Allowed changes, plus examples of changes outside that boundary.
- Required reviewers and the person responsible for final release.
- The intended placements, destination page, and review deadline.
If the team cannot agree on the promise, keep production small. Reviewing one rough concept takes less effort than resolving the same disagreement across a finished batch.
Which changes need a fresh approval?
Reopen the decisions an edit could affect, including the evidence behind a new claim. A new voice or spokesperson changes how the message is understood. Even a crop can remove context.
Keep a final human check on every export, while routing changed decisions to the people qualified to judge them.
Classify the proposed edit before production. The table is a starting point for your team agreement, not a universal permission system. Your existing review requirements still determine who must sign off.
| Change | Review owner | Check before release |
|---|---|---|
| Crop or resize | Production owner | Legibility and preserved context |
| Hook or scene order | Creative lead | Meaning and promise |
| Price or product claim | Product or offer owner | Evidence and current terms |
| Voice or spokesperson | Brand lead and relevant specialist | Permissions and implied endorsement |
| Language or market | Local reviewer and relevant specialist | Meaning and market requirements |
Changes can cross rows. A shorter video may remove the sentence qualifying a benefit. Route that edit as a meaning change, even if the production request calls it a simple cutdown.
Set an escalation rule for ambiguous cases. The producer flags the affected decision and asks its owner to classify the change. Do not make an editor guess what silence means.
How should reviewers share the work?
Assign each reviewer a question they own and identify who can resolve conflicting feedback. Run independent checks together, but keep dependent decisions in order. Product accuracy should be settled before approving copy that relies on it.
A deadline should trigger a reminder or escalation. It should never silently turn an unanswered request into permission to publish.
According to Adobe’s Workfront documentation, review stages can run sequentially or in parallel. Teams can configure deadlines, dependencies, and a decision maker for each stage.
You can use the same structure with a shared document. The software does not decide which person owns brand consistency, whether a claim is supported, or whose feedback takes precedence.
Give each role a bounded job:
- Creative lead: Does the ad communicate the approved argument in the intended voice?
- Product owner: Does the demonstration accurately represent what the product can do?
- Relevant specialist: Have they resolved the permissions, claims, or market questions they are responsible for?
- Campaign owner: Is this approved version ready for its placement and destination?
One person can hold several roles in a small team. Keep the questions separate anyway. Consolidate conflicting notes before sending revisions back, with a clear instruction and an owner for each requested change.
What would this look like for 12 ad variants?
For a hypothetical 12-variant SaaS batch, divide work by the decisions each version changes. Route 6 crops through production checks, 4 hook edits through creative review, and 2 new claims through the product owner.
Every finished export still receives release checks. This split reduces repeated decisions without treating an approved master as blanket permission.
Suppose the master demonstrates exporting a report. The 6 crops preserve the footage and wording. Their reviewer checks that the interface remains readable and the placement does not hide important information.
The 4 hooks introduce different opening questions. The creative lead checks whether those questions imply capabilities beyond the demonstration. If one does, it moves to the claim-review route instead.
The remaining 2 versions promise a specific time saving. The product owner must confirm suitable evidence and conditions before approving them. If that evidence is missing, rewrite or hold those versions.
The original 10 may proceed only if they meet their own requirements and can run independently. The 2 unresolved variants stay out of the release folder. They do not inherit approval from neighboring files.
The handoff contains a short file list: asset ID, version, changes, reviewer decisions, and release status. This is an illustrative routing example, not a benchmark for how many ads your account should test.
How do you prevent an approved ad from changing before launch?
Tie approval to an exact export and retain that file with the decision record. Any later edit creates a new version that needs the relevant checks. Before upload, confirm the asset, copy, destination, and placement belong together.
Also inspect enabled platform enhancements. Where automated transformations are available, decide which are acceptable before the campaign launches.
According to Adobe’s GenStudio review documentation, reviewers and approvers have different roles. It also explains that draft records and Workfront proofs differ in what they retain. Check what your own system retains after publication.
Keep the approval record outside temporary review links when necessary. Save the approved export, the source project, the final copy, and the decisions. A folder called “final” alone cannot explain which version someone reviewed.
Our guide to AI creative editing explains protected elements and editable handoffs. Approval adds another requirement: the released asset must match the version accepted at the end of that process.
Use a brief release check:
- Compare the upload against the approved file and copy.
- Preview the selected placements, including mobile presentation.
- Confirm the landing page carries the same offer and conditions.
- Record who released the asset and where it runs.
How do you know whether the workflow is improving?
Measure waiting time, review effort, and corrections after release alongside the number of approved assets that reach a test. Compare similar batches so a simpler assignment does not make the new process look faster.
Keep advertising outcomes separate. A faster approval cycle helps only when the team preserves quality and puts useful creative into market.
Start with one campaign and record a baseline before changing the process. Agree on a review date after the next comparable batch. Use the results to adjust routing and responsibilities.
| Measure | Record | Decision it informs |
|---|---|---|
| Waiting time | Ready for review to decision | Reviewer capacity or routing |
| Review effort | Human minutes per batch | Repeated or unclear decisions |
| Release corrections | Errors found after approval | Missing checks |
| Test readiness | Approved assets used in planned tests | Whether production serves learning |
If the queue shrinks but more incorrect claims reach market, the new process has failed. A larger approved library with no testing budget is unused inventory. Use the creative testing framework to connect releases with a defined learning plan.
If approvals are holding up your next test, bring a recent brief and its review history to a free strategy call. We can help you identify where decisions are waiting and think through who should own them.
Our AI performance creative team can also discuss how production and review would fit together in an engagement. Start with the batch you need to release next. Book a Free Strategy Call.
Seeing patterns like this in your own growth data?
We help growth-stage companies diagnose exactly what's working and what's not.
Book a Free Strategy Call
