MINIMVisit Website →
← Back to blog

Avoid Redelivery: Post Production Deliverables for Pros (IMF, IMSC1)

September 27, 2026
Avoid Redelivery: Post Production Deliverables for Pros (IMF, IMSC1)

Post-production deliverables are the final media assets, ancillary files, and manifests a production must supply to a platform, broadcaster, or agency partner. The single non-negotiable rule is to meet the receiver's spec and validate every file with quality control before upload. Standards like IMF (SMPTE ST 2067), MXF/MOV, and IMSC1 govern how those files are packaged, named, and read downstream.

TL;DR:

  • Meeting the receiver's specifications and validating all files with quality control are critical before upload, especially for package completeness and labeling.
  • Packaging standards like IMF are preferred for streaming platforms, with IMF allowing easy version updates, while MXF, MOV, and DCP suit broadcast, editorial, and theatrical needs respectively.
  • Embedded metadata and signed manifests prevent relink failures, ensuring proper file identification, checksum verification, and consistent naming conventions across the delivery chain.
  • Routine technical QC, including sync checks, channel mapping, and metadata embedding, reduces rejection risk and should be scheduled for full review before final submission.
  • Securing deliverables through encryption, access control, and early approval collection prevents leaks, legal issues, and delays in the distribution process.
MINIM
weareminim.com
Deliver Every Campaign With Confidence
MINIM integrates with your creative team to deliver cinematic campaigns from concept through final delivery, without expanding internal headcount.
Visit MINIM

Table of Contents

Checklist: exact deliverables you should prepare and what each must include

Every delivery package breaks down into a handful of asset categories, and each one has its own failure points. Missing a textless version or the wrong channel layout is what triggers a redelivery request, not a creative note.

  • Picture masters: supply a mezzanine master alongside any HDR and SDR derivations, and clearly label texted versus textless versions since platforms often require both for localization.
  • Audio: deliver the final mix plus M&E (music and effects) stems, with channel layout documented explicitly; note when a title includes immersive or object-based audio so the receiver knows to expect IAB metadata.
  • Proxy and editorial files: keep low-resolution proxies tied to relink instructions so any vendor picking up the project later can reconnect to full-resolution media without guesswork.
  • Captions and subtitles: decide between sidecar files and burned-in text early, since most streaming platforms now prefer IMSC1 sidecar delivery over open captions baked into picture.
  • VFX and documentation: include organized VFX shot directories, camera reports, and any license or clearance paperwork tied to stock footage, fonts, or music.

Skipping any one of these categories rarely kills a delivery outright, but it almost always adds a review cycle you didn't budget for.

Formats and packaging standards: when to create IMF or MXF, MOV, and DCP

IMF, the Interoperable Master Format, is a packaging standard defined by SMPTE ST 2067 that separates picture, audio, and metadata into discrete track files referenced by a Composition Playlist. It's built for version efficiency: a studio can swap in a new language mix or a regional edit without re-rendering the entire picture, which is why most major streaming platforms request it for finished titles.

A proper IMF package, or IMP, includes a CPL (Composition Playlist) describing how track files assemble into a final program, an AssetMap listing every file in the package, a PackingList confirming file integrity, and the TrackFiles themselves, typically JPEG 2000 image essence with linear PCM audio.

Diagram of four IMF package components

Outside of IMF workflows, MXF OP1a remains common for broadcast masters, MOV wrapped around ProRes is standard for editorial and agency review copies, and DCP (Digital Cinema Package) applies specifically to theatrical exhibition. Match the container to the receiver's stated spec rather than defaulting to whatever your edit system exports fastest.

Filenames alone are a weak link in any delivery chain. A vendor renames a file during transfer, a folder gets flattened during upload, and suddenly your carefully organized package is unreadable. Embedded metadata and signed manifests solve this in a way that naming conventions alone cannot.

  • Embed technical metadata directly into files (codec, frame rate, color space, timecode) rather than encoding it only in the filename.
  • Use ISO 8601 date formatting (YYYY-MM-DD) in any folder or file name that includes a date, which keeps sorting predictable across operating systems.
  • Follow MovieLabs and ETC naming guidance for VFX image sequences so automated ingestion tools can parse shot and version numbers without manual correction.
  • Generate a manifest (an AssetMap or PackingList in IMF terms) that lists every file, its checksum, and its role in the package.

Pro Tip: Never rely on a spreadsheet as your only manifest. A signed PackingList travels with the files and survives a folder copy; a spreadsheet does not.

Technical QC and verification: a compact pre-delivery QC routine

Most rejected deliveries fail for the same handful of reasons: a sync drift nobody caught, a channel mapped incorrectly, or metadata that didn't embed the way the export tool claimed it would. A short, repeatable QC pass catches nearly all of it before the file leaves your building.

  1. Run a 5-point sync spot check across the head, tail, and three points in the middle of the program.
  2. Verify channel layout matches the spec (5.1, stereo, or immersive) rather than assuming the export defaulted correctly.
  3. Validate codec and container against the receiver's published spec, not against what played back fine on your workstation.
  4. Confirm HDR metadata, including Dolby Vision metadata where applicable, actually embedded rather than just displaying correctly in your local player.
  5. Schedule a full watch-down when the title is high-visibility or when a previous delivery to that partner was rejected.

Netflix's own QC guidance recommends a technical spot check paired with a full watch-down for branded IMP deliveries, since metadata and package integrity issues are easy to miss on a casual playback. Most rejections trace back to audio layout mismatches or metadata that never embedded, both catchable in a routine that takes less than an hour per title.

Captions, subtitles, and accessibility: practical rules to meet delivery requirements

Caption requirements vary more by receiver than almost any other deliverable, so check the spec before assuming your existing workflow covers it.

  • Prepare IMSC1 sidecar files as the default, since most streaming platforms now expect this format over legacy alternatives.
  • For broadcast delivery, follow ATSC guidance on fragment timing, which recommends short caption fragments, typically limited to one to three seconds, to support decoder joinability.
  • Decide upfront whether captions need to be burned in or delivered as selectable sidecar tracks, since mixing the two approaches across a season causes inconsistent viewer experience.
  • QC every caption file for rendering accuracy and alignment against picture, not just for spelling and timing.

The path from set to final delivery is really a chain of handoffs, and each one is a place data can go missing if nobody owns the checklist.

  1. Offload camera media and immediately run checksum verification (MD5) before anything gets erased.
  2. Apply a 3-2-1 backup rule: three copies of the data, on two different media types, with one copy stored offsite.
  3. Generate editorial proxies, commonly 1080p H.264 or ProRes Proxy, so editors work efficiently without touching full-resolution media.
  4. Ingest into your project structure with consistent naming and embedded metadata.
  5. Relink to full-resolution media at finishing, verify against the original checksums, then package for delivery.

Pro Tip: Build in buffer time for at least one redelivery cycle. Even clean QC passes occasionally surface a platform-specific issue that only shows up on their ingest system.

Someone on the team needs to own final sign-off on the delivery checklist, whether that's a post-production supervisor or a delivery coordinator, so nothing ships without a named person confirming every box is checked.

Finished picture and audio are only part of what a receiver expects. Most delivery specs also require a documentation package proving the content is legally clear to distribute, and missing paperwork can hold up a delivery as long as a technical QC failure.

A music cue sheet lists every piece of music in the program, including composer, publisher, and usage duration, and is typically required whenever a title includes licensed or original score. Talent releases confirm that everyone appearing on camera, including background performers, has signed off on their likeness being used in the way the finished piece uses it. Location releases serve the same function for filming locations, particularly private property or recognizable public spaces.

Stock footage, photography, and font licenses need to be documented with proof of purchase or license terms, since a receiver may ask for this if a claim arises after the title is live. E&O (errors and omissions) insurance often depends on this documentation being complete, and many broadcasters and platforms won't accept delivery without proof of coverage.

Keep this paperwork organized in the same structured way you organize technical assets. A missing talent release found during final QC is one of the more painful reasons a delivery gets held, because it's a legal problem rather than a technical one, and it often can't be fixed quickly.

Archiving and long-term storage deliverables and standards

Delivery to a platform or broadcaster isn't the end of the asset's life. Most contracts also require an archival deliverable, a complete package of masters, project files, and documentation stored in a way that can be retrieved years later if a remaster, reversion, or legal question comes up.

Archival packages typically include the full-resolution master, all stems and M&E audio, VFX project files and shot directories, and the same manifest and metadata documentation used for the original delivery. Storing this on LTO tape remains common for long-term physical archiving, while cloud cold storage has become a practical complement for faster retrieval.

Whatever the medium, the 3-2-1 backup principle still applies to archives: multiple copies, on more than one type of media, with at least one copy stored in a different physical location than the original production facility. An archive that lives on a single drive in the same building as your working storage isn't really an archive.

Illustration of three-two-one archive principle

Label archival packages with the same naming and metadata discipline used for delivery, since an archive that requires guesswork to open five years later has failed at its one job.

Delivery timelines and scheduling considerations

Delivery deadlines rarely account for the QC and redelivery cycles that almost every project ends up needing, which is why building schedule buffer around the final delivery date matters as much as hitting the creative deadline.

Platform partners often allow multi-week windows for QC validation before a title is confirmed final, and that window exists because technical review takes real time, not because platforms are being cautious for no reason. Plan your internal finishing schedule so the delivery date isn't the day you export the final file. It should be the day you expect the receiver's QC process to begin.

Build in time for at least one round of corrections after initial submission, since even clean deliveries sometimes surface a platform-specific issue that only appears on their image delivery formats ingest system. Coordinate this timeline with everyone who needs to sign off, including legal for rights documentation and music supervisors for cue sheets, since those approvals often lag behind the picture and audio finishing schedule.

Security and encryption standards for deliverables

High-value content moving between a production and a platform or broadcaster needs handling that matches its value, and most delivery specs now include explicit security requirements alongside the technical ones.

Encrypt files in transit and at rest, particularly for pre-release content where a leak carries real commercial risk. Many platforms require delivery through secure, access-controlled transfer systems rather than general-purpose file sharing, and some specify encryption standards for the transfer itself. Track file transfer confirmations and never rely on an unmonitored upload as your only proof of delivery.

Limit access to raw and master files internally to the people who actually need them, and remove access once a project wraps. This matters as much for a small agency project as it does for a major studio title, since the reputational cost of a leak doesn't scale down with budget.

How a strategic production partner organizes deliverables to avoid re-delivery

We approach every delivery mezzanine-first: build the highest-quality master, then derive everything else, packages, proxies, captions, from that single source of truth. A technical watch-down happens before anything ships, and a manifest gets generated alongside the files rather than after.

Clients speed this up by supplying approvals, cleared assets, and rights paperwork early. Where we add value is in the packaging discipline and QC routine that keeps a delivery from bouncing back.

— Steven Reina

MINIM services for deliverables and how to get started

Building a delivery package that survives QC on the first pass takes the same discipline as the creative work that precedes it. MINIM works alongside agency creative teams from concept through full-service production, including screenwriting, art direction, photography, film, and visual effects, so the deliverables stage isn't an afterthought bolted onto the end of a project.

MINIM

If your team needs a production partner who treats packaging and QC with the same rigor as the creative brief, get in touch with MINIM to talk through your next delivery.

Authoritative specs and platform pages to consult before delivery

Check SMPTE ST 2067, your platform's own delivery specs, and ATSC caption guidance against your production's actual Delivery Requirements List before packaging anything.

Sources

FAQ

What does post-production include?

Post-production covers everything after filming wraps: editing, color grading, audio mixing, visual effects, captioning, and the final packaging and QC that produces deliverables ready for a platform or broadcaster. It also includes documentation like music cue sheets and talent releases that must accompany the finished media.

What are some examples of post-production work?

Common examples include picture editing, color correction, sound design and mixing, visual effects compositing, and caption or subtitle creation. It also includes technical work like mastering to a mezzanine file and packaging that master into formats such as IMF for delivery.

What are the three phases of postproduction?

Postproduction is generally organized into editorial (assembling and refining the cut), finishing (color grading, visual effects, and audio mixing), and delivery (mastering, packaging, and QC before the final files ship). Each phase feeds the next, and skipping QC at the delivery phase is where most rejections originate.

What are the 5 pre-production documents?

Pre-production documentation typically includes a script or shot list, a production schedule, a budget, location and talent releases prepared in advance, and a shot breakdown or storyboard. These documents set up the clearances and paperwork that later become part of the legal and rights deliverables at final delivery.