QC Report (Quality Control Report)

Nick HartyBy Nick HartySeptember 14, 2026

Definition

A QC report is the document a post house or distributor's lab produces after reviewing a master file or DCP from first frame to last. It logs every picture, audio, and caption fault with its timecode and a severity grade, then gives an overall pass or fail. Distributors use it to accept or reject delivery.

How a lab runs QC

An operator watches the program in real time on a calibrated monitor with headphones or a calibrated speaker setup, while software checks the file for things eyes miss: video levels outside the legal range, audio loudness against the delivery spec, dropped frames, and metadata that doesn't match the file name. Each fault gets a timecode, a description, and a grade. Labs use their own scales, but most boil down to three levels. A minor note is something the distributor will probably accept, a moderate fault should be fixed, and a severe fault fails the file.

Sample lines from a report

A report for a 96-minute feature master might include:

TC inTypeDescriptionGrade
00:04:12:03VideoDead pixel, upper right, 3 framesMinor
00:31:40:18AudioDialogue drop, 6 frames, center channelSevere
00:52:07:00VideoFlash frame at editModerate
01:10:22:14CaptionSubtitle on screen 2 seconds after line endsModerate
01:36:02:00ProgramTail slate missing, black runs 4 seconds shortMinor

One severe fault is enough to fail the whole file. The flash frame at 00:52:07:00 is typical of a conform problem: a single frame from the adjacent shot slipped in when the online was rebuilt from the EDL.

Fixes and who handles them

Picture faults go back to the online editor or colorist. A dead pixel may need a paint fix from VFX. Audio drops go back to the re-recording mixer, and caption timing goes to the captioning vendor. Each fix creates a new version, so a post-production supervisor logs which report version relates to which file. Sending the lab a file that fixed four items but broke a fifth is common enough that labs often re-check the full program rather than only the flagged timecodes.

Common misunderstandings

Filmmakers sometimes treat QC notes as creative criticism. They aren't. A lab can flag intentional grain, a deliberately clipped highlight, or a crushed night exterior as a fault. When the choice is intentional, the producer writes a waiver or a creative intent note, and most distributors accept that for minor and moderate items if the director of photography and colorist sign off. Get that note written during color grading, before the first QC, so no one argues later.

How QC connects to delivery

QC sits at the end of the deliverables process. Every master file gets its own report: the feature, the textless version, the M&E tracks, and the DCP. Budget for at least one re-QC in the post budget of your film budget.

Frequently asked questions

Who pays for QC?

Usually the producer, since passing QC is part of delivery. Some distributors run their own QC on top and charge back the cost of a re-check if the first submission fails. Read the delivery schedule in your distribution agreement for who pays for re-QC.

What happens if a film fails QC?

The distributor sends the report back, the producer fixes each flagged item, and the file goes back for another pass. Delivery isn't complete until it passes, and payments tied to delivery wait.

Is a QC report the same as a spot check?

No. A spot check samples parts of the file. A full QC is a real-time watch of the whole program, usually combined with automated analysis of levels, gamut, and file structure.

Can I QC my own film?

You can and should do an internal check before sending anything out, but distributors normally want a report from a lab they approve, so a self-check doesn't replace it.

Keep the paperwork in one place

Upload a PDF, Word, or Final Draft script and Storiara pulls out scenes, cast, locations, props, and wardrobe, then builds the schedule, budget, and call sheets from that breakdown.

Start Planning for Free
Nick Harty

Nick Harty

Technical Lead, Storiara

Technical architect and full-stack engineer building the core systems that power Storiara. Creates technology that enhances creative workflows.