Learn

Video Delivery Checklist

A video delivery checklist is a systematic document that ensures every deliverable meets the required technical specifications before it is sent to the client, broadcaster, or platform. Using a consistent checklist prevents embarrassing errors, costly rejections, and time-consuming redeliveries that damage your professional reputation.

Pre-Delivery Technical Verification

Before any deliverable leaves your facility, verify the fundamental technical parameters. Confirm resolution matches the specification (1920x1080, 3840x2160, etc.), frame rate is correct (23.976, 25, 29.97, etc.), and the codec and profile match requirements. A single wrong parameter can cause a platform to reject the entire file.

Check the file wrapper (container format) and ensure it matches specifications. MP4, MOV, MXF, and other containers have different capabilities and compatibility profiles. Verify that the correct video and audio streams are present and that there are no extraneous streams that should have been removed during export.

Run the file through MediaInfo or a similar analysis tool to verify all metadata. This includes color space tags, aspect ratio flags, timecode, and any platform-specific metadata fields. Metadata errors are among the most common delivery rejections and are entirely preventable with a quick automated check.

Audio Delivery Checks

Verify audio channel configuration matches the specification. If 5.1 surround is required, confirm all six channels are present and correctly mapped (L, R, C, LFE, Ls, Rs). If stereo is required, confirm the file contains exactly two channels and that they are true stereo (not dual mono or a duplicated mono track).

Check loudness compliance against the target specification. Measure integrated loudness, loudness range, and true peak values. For broadcast, these must comply with EBU R128 or ATSC A/85. For streaming platforms, check the platform-specific target to ensure your content will not be aggressively normalized during processing.

Listen to the beginning and end of the file. Confirm there is no pre-roll audio before the content starts and that the audio does not cut off abruptly at the end. Check audio sync by watching a section with visible speech and confirming the audio aligns with lip movement. Even a few frames of drift is noticeable and should be corrected.

Visual Quality Control

Watch the entire deliverable from beginning to end. There is no substitute for a full playback review. Look for compression artifacts, banding in gradients, blocking in dark areas, and any visual anomalies introduced during encoding. Pay special attention to sections with fast motion, fine detail, and gradual gradients, as these are where compression issues are most visible.

Check the first and last frames of the content. Confirm the first frame is the correct start of the program (not a blank frame or test pattern) and that the last frame is correct. Verify that any required slates, countdown leaders, or bumpers are present and formatted correctly according to the delivery specification.

If the deliverable includes graphics, titles, or subtitles, verify they are correct, properly positioned, and readable. Check for typos, ensure text is within the title-safe area, and confirm that subtitle timing is accurate. These elements are often finalized late in the process and are prone to last-minute errors.

File Naming and Documentation

Follow the specified file naming convention exactly. Many delivery systems use automated file processing that depends on precise naming. A file named "Final_v2_FIXED.mp4" instead of "CLIENT_SHOW_S01E01_TX.mp4" may not be processable. If no naming convention is specified, use a clear, descriptive name that includes the project, version, and date.

Include all required documentation with the delivery. This may include a technical specification sheet, a QC report, music cue sheets, closed caption files, poster art, and metadata documents. Missing documentation can delay delivery acceptance even when the media file itself is perfect.

Record the delivery in your project management system. Note what was delivered, when, to whom, and by what method. If using a platform like RecReview, the delivery event can be tracked automatically with version history. This creates an audit trail that is invaluable when questions arise weeks or months later about which version was delivered.

External Resources

See it in action

Start your free trial and experience it yourself.

Start 15-Day Free Trial →

No credit card required

Frequently Asked Questions

What are the most common reasons for delivery rejection?
The most common reasons are audio loudness violations, incorrect metadata tagging (especially color space), wrong file naming, missing or incorrect closed captions, and technical parameter mismatches like wrong frame rate or resolution. A thorough delivery checklist catches all of these before submission.
Should I use an automated QC tool or manual review?
Both. Automated QC tools efficiently check technical parameters like bitrate, resolution, loudness, and file structure. Manual review catches visual quality issues, content errors, and subjective problems that automated tools cannot detect. The combination provides the most thorough QC coverage.
How do I handle delivery to multiple platforms with different specs?
Create a separate delivery checklist template for each platform or destination. Export each version according to its specific requirements and QC each one independently. Do not assume that a file passing QC for one platform will pass for another, as specifications differ significantly.
Keep Learning

Related Articles

Try it free for 15 days

No credit card required. Full access to all features.

Start Free Trial →