A post-production compliance workflow should analyse the correct version, create timecoded evidence, route findings to authorised reviewers, convert approved decisions into non-destructive edit instructions, perform technical and editorial QC, and deliver only the conformed, approved package.
Compliance, quality control and remediation are often treated as separate departments. In practice, they share the same asset identity, timeline and destination profile. A dialogue issue may require a mute or alternate line; visible PII may require a tracked blur; a rating decision may require an EPG advisory; and a loudness failure may require a new mix or normalised deliverable.
The safest workflow keeps the finding, decision, change and final QC connected.
Eight stages from master to delivery
- Ingest: register the master, checksum, duration, frame rate, audio layout, languages, text assets and source metadata.
- Proxy and analysis: create an appropriate review proxy while high-resolution masters can remain on customer-controlled storage.
- Evidence extraction: detect and timecode dialogue, OCR, brands, PII, technical faults and configured content categories.
- Human review: confirm the evidence, its context, severity and destination relevance.
- Remediation planning: approve edit, mute, replacement, blur, caption, subtitle, graphics, metadata or scheduling actions.
- Conform: apply approved work in the NLE, DAW, finishing, localisation or packaging environment.
- Final QC: re-check the conformed picture, audio, captions, subtitles, metadata and package.
- Delivery: release the approved version with reports, markers, provenance and policy version.
Post-production compliance control matrix
| Area | Checks | Typical remediation |
|---|---|---|
| Picture | Gamut, HDR/SDR, flashes, freeze, black frames, logos, PII and prohibited imagery. | Grade, blur, mask, replace, trim or alternate shot. |
| Audio | Dialogue, profanity, loudness, true peak, phase, silence, channel layout and crosstalk. | Mute, replace, remix, route, gain-stage or normalise. |
| Text | Captions, subtitles, forced narrative, timing, reading speed, spelling and restricted terms. | Retiming, translation correction, replacement or additional version. |
| Metadata | Title, episode, rating, advisory, territory, language, rights and identifiers. | Correct fields, retain provenance and republish package. |
| Commercial | Brand safety, brand suitability, product placement and advertising conflicts. | Approve, disclose, restrict adjacency, replace or escalate. |
| Delivery | Codec, container, resolution, frame rate, naming, checksum and package completeness. | Re-encode, rewrap, rename, rebuild or reject. |
Broadcast QC and OTT QC need different profiles
Many checks overlap, but the target values and delivery expectations do not always match. A linear broadcaster may require a specific programme loudness, channel layout, active-picture format and continuity metadata. An OTT service may use different loudness treatment, adaptive streaming packages, maturity metadata, artwork and accessibility requirements.
Standards belong in versioned delivery profiles
EBU R 128 provides a broadcaster-oriented loudness framework and has dedicated supplements for streaming and cinematic content. ITU-R BT.2100 defines image parameter values for HDR television production and international programme exchange. Neither removes the need to follow the destination’s current specification.
Explore the EBU loudness publications →Outputs that return work to post-production
| Output | Consumer | Purpose |
|---|---|---|
| Timeline markers | Editor or compliance reviewer | Open the exact timecode and evidence. |
| AAF / audio automation | Pro Tools or audio team | Carry structured, non-destructive mix work. |
| Review JSON | MAM, orchestration or platform | Exchange findings, status and provenance. |
| Evidence report | Compliance, legal or customer | Explain what was found and decided. |
| Edit decision list | Post-production coordinator | Track approved changes by version. |
| Delivery manifest | Operations or recipient | Confirm package identity and completeness. |
PII, privacy and brand safety in the finishing room
Phone numbers, addresses, documents, licence plates, computer screens and identifiable people may require privacy or editorial review. Logos and products may trigger advertiser, sponsor, product-placement or destination-policy decisions. Detection should generate evidence; it should not automatically blur every face or logo.
Why final QC must check the conformed version
An approved change can introduce a new fault: a blur may slip, a replacement line may peak, a subtitle may become mistimed or a re-encode may change colour. Final QC must operate on the exact package scheduled for delivery—not on the earlier review proxy.
Use the current broadcaster, platform, distributor or airline specification for each package. Keep automated findings reviewable and final technical and editorial decisions human-authorised.
Frequently asked questions
What is post-production compliance?
It is the controlled conversion of policy and technical findings into approved edits, corrected assets and verified delivery packages.
How do broadcast QC and OTT QC differ?
They share core checks, but loudness, package, metadata, accessibility and platform requirements can differ by destination.
Should AI automatically edit a programme?
No. It can propose evidence and remediation, while authorised teams approve changes and verify the conformed asset.
Sources and scope
- Audio production and deliveryEBU Loudness publications, including R 128 and streaming guidance.
- HDR productionITU-R BT.2100, image parameter values for HDR television production and programme exchange.
- MethodDestination specifications control actual acceptance. This guide is a workflow model, not a substitute for those specifications.
Make compliance native to post-production.
Return evidence as markers, reports, AAF and structured review data while masters stay on customer-controlled storage.
Explore the platform