Watch every file. Know what you are signing off on.
Delivery QC puts playback, technical details, scopes, audio analysis, and an explicit clear-or-flag decision around the actual local files a reviewer must approve.
Delivery QC preview that scans a local export and confirms its delivery details.
Built for
The people responsible for this part of the work.
For editors, assistant editors, post producers, post supervisors, finishing producers, and other trusted members of the post team who are technically prepared to approve final files.
The current workflow
The last review is repetitive, informal, and too important to rush.
A campaign may finish with hundreds of closely related files after grade, mix, conform, versioning, and export. A reviewer still has to watch every one, notice the one-frame or one-version mistake, and remember what has actually been approved.
Why purpose-built
Technical analysis supports the reviewer. It does not replace them.
A program can surface frame rate, duration, loudness, channel relationships, and other evidence. Only someone who knows the project can recognize the wrong take, an outdated title, a missed revision, or a creative error. Delivery QC keeps both kinds of attention in one focused workspace.
What it helps you do
A focused system for the actual task.
01
Review the actual delivery locally
Select an individual file or an entire nested folder. Playback and media analysis happen in the browser, so large masters do not wait on an upload and the selected media stays on the reviewer's computer.
02
Read the technical evidence
See human-readable file details, frame-accurate playback controls, video scopes, mattes, channel information, and ITU-R BS.1770 integrated loudness around the picture.
03
Make every signoff explicit
Clear or flag each file. Add an issue note and screenshot without leaving the review, then export a PDF record of cleared, flagged, and automatically flagged items.
04
Check the delivery as a whole
Connect a folder to a Deliverable Tracker project to reconcile what is present with what was expected, automatically where the generated folder tree was used or manually where names changed.
After your first session
Leave with something useful.
Select a delivery folder, review each file with its technical context, and leave with an explicit record of what passed, what needs attention, and—when connected to Tracker—what may be missing.
Delivery QC does not automate final signoff. An informed person still needs to watch every file from start to finish.
Technical signals cannot determine whether a take, title, legal line, grade decision, or client revision is creatively correct.
It is not a remote creative-review, annotation, or client-approval platform.
The current public product runs in the browser. A downloadable offline application is an idea under exploration, not a generally available feature.
Questions, answered
The practical details before you begin.
Does Delivery QC upload my video files?
No. The selected media is played and analyzed locally in your browser. That keeps sensitive masters on your computer and avoids waiting for large delivery files to upload.
Is this automated QC?
No. The tool automates useful measurements and warnings, but the central act is still an informed human watching every edit and explicitly clearing or flagging it.
Who should perform the review?
Usually an editor, assistant editor, post producer, post supervisor, finishing producer, or another trusted and technically proficient member of the post team who understands the project.
Do I need a Deliverable Tracker project?
No. You can review any supported local delivery folder on its own. Connecting Tracker adds a completeness pass by comparing the files present with the deliverables the team previously defined.