Capture & Delivery

What Belongs in a Final Video Delivery Folder?

Build a delivery folder whose manifest tells a recipient which video to publish, which one to archive and how to validate both.

Put the approved upload path and revision at the top of the manifest. Ask the recipient to find that file with your editing timeline closed. Include the other assets they need to use it, such as the matching captions and an audio language list.

Decide which deliverables the agreement calls for. An upload copy, a review copy and a master have different jobs even when all three contain the same cut. Include an editable project in its own package when it is part of the handoff, together with its dependencies. Here the folder covers finished media and the notes needed to identify it.

Name files from the job each one does

Sample path Purpose Check to record
review/demo-v04-review.mp4 Approval and comments Contains the approved edit, marked review only if applicable
publish/demo-v04-sdr.mp4 The client's agreed upload Plays with the final grade, full narration and intended duration
publish/demo-v04-en.srt English captions for that exact cut Early and late cues align with the publish file
master/demo-v04-master.mov High-quality master for later encodes Opens in the archive reader with the agreed picture and audio
delivery.txt File index and validation notes Exact paths, duration, audio languages and revision

Add any alternate master, clean audio stem or accessibility file only if the client needs it. Give each a row explaining which version and purpose it serves. The W3C caption guidance describes captions as timed speech and sound information. Keeping the caption file alongside its matching video reduces the chance that somebody uploads an older language track by mistake. For a platform delivery, record the standard or encoding preset you used, such as the applicable settings from YouTube's upload guidance.

Test the folder as a recipient

Copy the package to a fresh folder or storage destination. Give the checker the copied index and package. If you work alone, close the editor and find the assets using that index alone. Open the publish-ready version and spot-check the title, last scene, audio and captions. Locate the archive master using the index and open it separately. If you cannot identify the correct file from its description and path, fix the manifest before delivery.

For a large transfer, add a file checksum after the exports are final. The BagIt packaging specification provides a formal example of pairing relative paths with checksums to verify payload files. You can use a short SHA-256 list in a simple delivery. Ask the recipient to compare the checksums they compute locally with that list. When you replace an export, move the previous revision out of the active folder. Update both the manifest and checksum so they describe the exact file marked for publication.

Put the expected first job at the top

Imagine the recipient has ten minutes before a scheduled upload. Give them one file to choose, the accompanying caption language, and the cue that proves it is the new revision. A completed delivery might list the SDR upload first, followed by the separate high-quality master that supports later encodes. Identify any review copy as such. If the review and final export have similar filenames, use the manifest to call out which one is safe to publish.

Give the recipient a simple recovery instruction. If the uploaded platform reports a caption issue, the record can name the SRT file and the expected language. If they need to generate a new version, the record can tell them which master to open and any audio tracks available. A reader should be able to find the necessary file from the note without asking which directory your editor exported into. Add only the source files and working material the delivery actually promises.

Include the major facts about the file in its row. A video can mention picture dimensions, delivery frame rate, audio language, colour signal and exact revision. Captions can list a matching video identifier, language and type. Put the rendered and editable versions in different locations if both are part of the agreement. Keep dependencies for editable work with its project and point to the packaging check. A final video folder should avoid mixing earlier drafts into the path used for publishing.

Run the handoff from a fresh download

Copy the package to a directory that cannot use the old project's local media paths. If your archive will be unzipped on another operating system, test an ordinary extraction there or verify the filenames meet that environment's constraints. Open the manifest with the editing application closed. Follow its path to the upload, play the latest change you expect, and load the matched captions. Check a short early and late cue using the caption playback procedure. The timecode for each gives the next person a useful test point.

When a large archive reaches the recipient, compare the number of expected files and the checksum for the key payload files if you provided one. A correct checksum shows that the bytes match the file you hashed. It does not certify that the chosen file has the right cut or all the audio. Make separate entries for transfer validation and media acceptance. If the hash differs, transfer the affected file again and leave the previous file identified as incomplete until it is replaced.

Finding during the handoff Evidence to return
A file named for the latest revision shows the old ending Exact path, playback time and the expected revision marker
The caption language is present but appears late Video and caption names and the first mismatched cue
The archive master cannot be opened File path, player, and whether the transferred checksum matches
An alternate audio file is absent Requested purpose and the manifest entry identifying it

Replace one revision without leaving two candidates

After a correction, stage the new video and any revised captions. Update those rows and any hashes after the new files are final. Keep the download name or version clear in the delivery note. Move the superseded assets out of the active publish area according to the agreed archive plan. A recipient who still has the old package should see which version is authorised now, and what change to look for.

Open the new copy from that same delivery path and rerun the minimum acceptance check. If the only planned change is a credit, verify that the end card is changed, the narration still matches the cut and the captions remain in time. Keep the manifest with the accepted folder so another person can repeat the proof months later without reconstructing the original editing project.

Sources