Start with a delivery contract, not an export preset
A professional AI video delivery should name the approved message, selected edit, destinations, ratios, duration limits, caption state, audio state, file format, naming pattern, and approval owner. The export preset is only one part of that contract.
Record current destination requirements at handoff time. Platform specifications can change, and a technically valid master may still be unsuitable for a particular placement, ad account, player, or publishing workflow.
- Approved master: the edit, message, product version, identity, and disclosure state that cannot drift.
- Destination variants: each platform, placement, ratio, duration, safe zone, and file-size boundary.
- Audio and captions: mix state, loudness review, licensed sources, burned-in text, subtitle file, or clean version.
- Package boundary: final exports, editable files, source frames, generations, fonts, voice assets, and usage notes included or excluded.
Inspect the encoded file from beginning to end
Timeline playback does not prove that the delivered file is correct. Open every exported variant independently and watch it at normal speed with sound on and off. Confirm the first frame, final frame, duration, orientation, resolution, frame rate, color, audio channels, captions, and file name.
AI-specific checks remain necessary after encoding. Compression can make flicker, unstable text, lip-sync drift, edge crawl, skin texture, or small product inaccuracies more visible. Compare the export with the approved master rather than trusting that a successful render preserved every accepted detail.
Separate correction, re-export, and new scope
A failed codec, incorrect crop, missing caption, muted channel, or naming error usually calls for a corrected export. A changed concept, new language, new platform, new duration, new product version, or newly requested editable package can require a scope decision instead.
Document the failed check, responsible owner, next action, and replacement version. Do not overwrite the approved master or silently substitute an earlier generation to make a delivery deadline.
Acceptance does not authorize publication
Technical acceptance confirms that the agreed files open, play, match the approved creative, and meet the recorded delivery specification. It does not automatically approve product claims, synthetic identity use, music or voice rights, paid-media placement, or publication.
Keep those permissions visible in the handoff record. When a requirement is unresolved, mark the affected variant as held rather than presenting the complete package as publish-ready.
Final-file review
Video Export Acceptance Matrix
Complete one row for every delivered variant. Use the client-approved specification and current destination requirements; do not assume one preset is valid for every placement.
| Deliverable | Record before export | Inspect in the final file | Accept when | Reject or hold when |
|---|---|---|---|---|
| Approved master | Version, duration, dimensions, frame rate, codec, color state, and audio layout. | Opening and closing frames, identity, product facts, claims, disclosures, motion, and final CTA. | The encoded file matches the approved edit and opens cleanly on the agreed review device. | A factual element drifts, the render differs from approval, or playback reveals a structural defect. |
| Vertical placement | Destination, 9:16 dimensions, duration, safe zones, maximum file size, and caption mode. | Face and product crop, on-screen copy, interface overlap, CTA visibility, and sound-off readability. | Every required element remains readable without adding bars, stretching, or unsafe cropping. | A platform overlay hides copy, the crop removes evidence, or a required caption is missing. |
| Square or feed placement | Destination, 1:1 or 4:5 dimensions, duration, safe zones, thumbnail, and file limit. | Reframed composition, title hierarchy, product scale, subtitles, and end-card balance. | The variant was intentionally reframed and preserves the approved message and product presentation. | It is a blind center crop, contains clipped text, or changes the visual implication of the master. |
| Caption package | Burned-in, sidecar, clean master, language, spelling source, timing, and speaker labels. | Word accuracy, line breaks, contrast, timing, safe zones, product names, and required disclosures. | Captions match approved copy and remain readable in every delivered placement. | Generated words are unverified, timing obscures meaning, or required notices are cropped or absent. |
| Audio package | Mix version, channel layout, sample rate, music and voice sources, clean or music-free variants. | Dialogue clarity, sync, clipping, silence, channel balance, room tone, ending, and rights notes. | The intended mix plays correctly and every included voice, music, and effect has an approved use state. | Lip sync drifts, a channel is missing, levels distort, or source permission is unresolved. |
| Delivery manifest | File name, version, purpose, destination, ratio, status, included sources, and approval owner. | Files against the manifest, superseded versions, download integrity, and stated exclusions. | A recipient can identify what to publish, what to archive, and what still requires approval. | Final status is ambiguous, old variants remain mixed with masters, or the package implies missing rights. |
This matrix supports production review. It does not replace current platform requirements, rights clearance, claims review, client approval, or publication authorization.
Continue building
Learn the complete production workflow.
The Academy connects prompt structure to references, first frames, motion, editing, distribution, and monetization.
Explore the Academy