BuyingGuide · Editorial guide

Video Project Handoff Checklist: Files, Captions, Rights and Revisions

Draft prepared November 19, 2026 · 1,933 words · approximately 9 minute read
Editorial staging · This article is not published and is intentionally excluded from search indexing.

A video can look finished in an editing timeline and still be impossible for a client to use. The export may be the wrong shape for its destination, the music license may cover only one channel, or a contractor may disappear without leaving behind the source files. A professional handoff is not merely a downloadable MP4. It is a small, organized package that lets the recipient publish the work, request reasonable revisions and find the correct version six months later.

This guide is for freelance editors, production teams and creators working with clients. It focuses on what to deliver and what to clarify before the last invoice, not on one editing app or cloud-storage company. The same principles apply to a one-minute product demo, a recorded webinar or a batch of vertical clips.

Agree on the deliverables before editing starts

The most expensive handoff argument is about something nobody specified. A client asks for “the final video,” but an editor assumes that means one widescreen file. The marketing team later expects square crops, editable graphics and a version without music. None of those expectations is inherently unreasonable; they are simply different deliverables.

Write a delivery list at the beginning of the project. Include final aspect ratios, approximate durations, output resolution, captions, thumbnails, editable files if applicable and the number of revision rounds. Specify whether the client will receive raw footage, assembled project files or only finished exports. These three items are not interchangeable.

A useful scope sentence is: “Delivery includes one approved 16:9 master, two 9:16 cutdowns, separate English captions, a thumbnail and one organized archive of client-owned supplied footage.” Adapt the sentence to the actual job. If project files, font licenses or stock footage cannot legally be transferred, explain that at the outset.

Create an understandable folder structure

A handoff folder should make sense without a phone call. Avoid the classic collection of final.mp4, final2.mp4, final_REAL.mp4 and final_use_this.mp4. A client needs one obvious approved master, with alternatives grouped by purpose rather than chronology.

A practical structure is:

Campaign-Name/
  01-Final-Exports/
    Campaign-Name_16x9_Approved_v03.mp4
    Campaign-Name_9x16_Approved_v03.mp4
  02-Captions/
    Campaign-Name_English.srt
    Campaign-Name_English.vtt
  03-Thumbnails/
    Campaign-Name_Thumbnail.jpg
  04-Source-Assets/
  05-Project-Files/
  06-Rights-and-Notes/
    README.txt
    Asset-Licenses.pdf

Not every job needs every folder. What matters is consistency. Put finished files first, label unfinished versions clearly, and avoid making the client guess which one to upload. If the delivery is large, add a short text index listing each file and its intended platform.

Use filenames that remain useful outside your cloud folder. A date-only name or a short code can be convenient inside a studio but confusing once copied into a client’s downloads directory. Include the project, shape, status and version. Avoid special characters that may be rejected by older systems.

Export for the actual destination

An attractive preview inside an editing application is not proof that the final export is correct. Review the delivered file in a separate player. Confirm orientation, dimensions, audio channels, subtitles where embedded, color appearance and beginning and ending frames. Make sure the final five seconds do not contain a stray timeline marker, black frame or unfinished credit.

For social platforms, verify current upload specifications directly with the platform instead of relying on a year-old universal preset. Social services re-encode uploads, and their preferred aspect ratios, duration limits and caption behavior can change. Keep a high-quality approved master alongside platform-specific exports when the scope permits it.

Also distinguish captions from on-screen design text. Burned-in captions are part of the picture and cannot easily be corrected by a publishing team. Separate caption files offer editing flexibility and often help with accessibility, but the receiving platform must support the chosen format. When both are requested, label them so a client does not accidentally publish a version with duplicated subtitles.

Test captions as content, not a checkbox

Automatic captions save time, but they can mishandle names, technical terms, accents and brand vocabulary. A human review should compare the transcript to the actual speech, correct speaker changes where supported, and check that captions do not conceal important on-screen information. An SRT file is usually plain text with timed caption blocks; a VTT file is a different format and should not simply be renamed.

If a clip includes essential information only in images—such as a chart, a price, or a demonstration—the video may also need narration, a written description or another accessible equivalent. Captions alone do not communicate information that nobody says aloud. Discuss accessibility expectations with the client before exporting all the variants, especially when the video will be used for education, hiring or public services.

Make a distinction between a transcript and captions. A transcript can be useful for a blog post, search indexing or translation; captions need time alignment and readable segments. Delivering a text document labeled “captions” when no timing data exists creates extra work downstream.

Document rights before anyone posts

A finished video can contain assets with different ownership or usage rights: recorded interviews, music, stock clips, logos, graphics, fonts, location footage and third-party screenshots. The client needs to know what is cleared for what purpose. A paid music license may be limited by platform, territory, project type or account. A subscription asset does not automatically give the recipient a transferable license.

Provide an asset sheet with source, asset description, rights holder or vendor, licensed use, licensee and restrictions. If the client supplied an asset, record that fact rather than silently promising that it is cleared. If a creator used an AI-generated element, note the tool and any relevant commercial terms without making unsupported claims about exclusivity or copyright protection.

For interviews and testimonials, note whether the production relied on a signed release and who holds it. This does not require embedding confidential forms in every delivery folder. It means a named person knows where the authorization is maintained. Retain only the personal information necessary for the legitimate project and deliver it through an appropriate private channel.

Decide whether editable files are part of the agreement

Source files sound simple until the recipient opens a project that refers to missing media, licensed plug-ins and a font installed only on the editor’s computer. If editable delivery is promised, test whether the handoff works on a clean machine or a separately configured workspace. Collect and relink media, identify software versions, outline required plug-ins and replace temporary or offline references.

An editable timeline also does not necessarily mean a client can legally reuse every third-party asset in a new campaign. Separate the question “Can we open the project?” from “Can we repurpose everything inside it?” A clear README can explain both. If the client receives only final exports, make that equally explicit.

Ask how long the editor will retain backups. A retention period and restoration fee should be established rather than assumed. The client should not depend on one freelancer’s laptop as its sole asset archive. For a larger team, nominate the person responsible for final storage and permissions after project close.

Handle revisions without version chaos

Approval deserves a recorded milestone. Put the approved version number, date, approver and delivery method in one shared message or document. Specify whether post-approval changes are new work. This keeps reasonable client corrections from being confused with an unlimited creative rewrite.

When feedback arrives, consolidate it into a single change list with timestamps, exact text replacements and the reason for a change. “Make it pop” is not a reproducible instruction. “At 00:18 replace the lower-third title with ‘Operations Director’ and extend it one second” is reproducible. For subjective changes, provide two concrete options and ask for a choice.

If multiple teams give contradictory notes, the agreed final approver should resolve them. Never rely on a chain of screenshots and voice messages as the sole approval record. Keep a brief decision log inside the project, especially when legal, brand or factual corrections were made.

Secure the transfer and verify it arrived intact

A delivery link is a temporary transport method, not an archive strategy. Before sharing it, check the permissions: is it limited to the named recipient, does it allow editing, and when will it expire? A client may need long-lived access to approved files but not to raw interview footage or unredacted production notes.

For large handoffs, compare file sizes after upload and download, and test at least one export on the recipient’s side. If checksum verification is practical, keep a SHA-256 list in the archive. Hashes can establish that two copies are byte-for-byte identical; they do not prove that the content is accurate or safe to publish.

Never email sensitive interview data or private customer records simply because the video is large. Use the client’s approved transfer service. If files contain personal data, discuss retention and who may access them instead of assuming every stakeholder should have the full raw footage.

A realistic ten-minute final review

Before sending the last link, play the start, middle and end of every approved export. Listen through headphones for dropped audio, mixed-language tracks or peaks that distort. Scan the thumbnail at small size. Open the captions in an ordinary text editor and spot-check three timestamps. Confirm that filenames, folder contents and links match the agreed deliverables.

Next, check your licensing sheet and any release status. Read the final title card word by word. Make sure no one is listed as endorsing a claim they did not approve. Confirm the receiving email address and access permissions. Finally, send a compact handoff note identifying what is approved, what is editable, what remains with the editor and the deadline for reporting technical delivery problems.

A good delivery message can fit in a paragraph: “The approved exports are in 01-Final-Exports; captions and thumbnail are separate. The README identifies versions, licensed third-party assets and project-file dependencies. Please download and test the master before the link expires.”

Frequently asked questions

Should a freelance editor deliver raw footage automatically?

Not unless the agreement provides for it. Raw footage might be client-owned, contractor-created, or captured under separate conditions. Confirm ownership, access, transfer cost and privacy implications before promising it. If the footage contains private conversations or unused interviews, additional restraint may be appropriate.

Is one MP4 enough for YouTube, Instagram and TikTok?

Sometimes a single asset can be repurposed, but it is rarely the ideal final deliverable for every destination. Cropping changes composition, text placement and what remains visible. Define separate aspect ratios and review each version rather than treating one automatic crop as universally correct.

What should stay with the client after a contractor leaves?

At minimum, the deliverables the client paid to receive, a record of approval, the relevant rights documentation and an understandable way to access the files. Where editable delivery was agreed, include the dependent assets and instructions that make those project files usable.

How do we stop losing the final version?

Use a clear approved filename, a single master folder, an approval date and a designated archive owner. Do not rely on whatever appeared most recently in a chat thread. Periodically test restoration of a stored project so backup confidence is based on evidence.

The bottom line

A professional video handoff reduces operational risk for both sides. Define deliverables early, separate masters from source files, test captions and exports, document licensing, record approval and close the project with a usable archive. That is what turns a good edit into work a client can confidently publish and reuse. For related equipment and workflow decisions, see VidGrow’s storage and backup guide and creator gear upgrade guide.