Watch and listen to the export
Play the exported file from start to finish on a phone. Look for errors in hands, faces, shadows, transitions and subtitles. Listen for wrong pronunciation, clipped words and sudden jumps in volume. Check that every line of text can be read in the time it is on screen.
Use the preview for the planned ad placement to check cropping and anything that could cover the message. Confirm technical requirements for the current placement instead of assuming them from an earlier campaign.
Turn a defect into a precise task
Record the filename, version, timecode and the change needed. "The logo blurs at 00:06" is easier to fix than "the product looks wrong". Separate a defect that must be fixed before delivery from a suggestion that could become a new variant.
Check the fix in the new export. Store the approval with that exact version, and pass on only approved files. See the approval workflow guide if feedback often spreads across several channels.
Make rejection a clear decision
A practical check can end in three different decisions: the file can be delivered, a specific defect must be fixed, or the concept needs a different production method. Do not average these into one score. A beautiful image of the wrong product cannot be approved because the rest of the review is good.
Our free challenge Would You Approve This Ad? lets you practise these calls on six fictional ads, each with its approved product facts. It takes about two minutes.
Picture a clip where a hand unscrews the lid of a cream jar. If the label changes during the movement, the product depiction has to be fixed. If the on-screen text promises an effect that is not documented, the claim has to be removed or changed to something the company can stand behind. If the subtitle is correct but on screen too briefly, it is a readability fix. Each defect has its own owner and its own way of being checked.
Agree which reference files the check uses. If the brand team and the producer compare against different pack versions, both can believe they are right. Keep the current reference next to the task, and mark older material as retired in the internal overview.
Review the delivery as the recipient
Open the folder with the files that will actually be handed over. Can you find the approved version without reading the whole message history? Do the filename, language and variant description match? Is there a clip with an audio fix still sitting next to the old export without a clear label?
Pass on only the agreed delivery, and give whoever runs the ads a short overview of the variants. If the material is an illustration or a demonstration concept, do not describe it as a documented customer result. The handoff has to keep the caveats that made the material correct at approval.
Check the AI label too. The label for each platform and market should be agreed before delivery, and each file should come with a usage note that lists what in it is AI-generated. AI Vidia sets out how it agrees labels with clients on its page on AI labels and disclosure. For the legal side, read who has to label an AI ad under the EU AI Act.
For the next batch, the team can use earlier defects to improve the brief. A repeated error in product size may call for better measurement references. Repeated fixes to how the product name is pronounced may call for an approved audio reference. That learning belongs in the production inputs, so the check does not have to catch the same problem every week.