AI Video Client Handoff: Rights, Files and Approvals

A client handoff is where trust either holds or breaks. You deliver a video. The client asks who can use it, where, and for how long. If you answer slowly, the project ends on doubt. This guide gives you a simple handoff manifest. It separates ownership, license terms, speaker permission, script sign-off, channel scope, versions, source assets, client access, and an exit plan.

The method below is an editorial checklist, not a ready-made contract. It helps you ask the right questions and record clear answers. Whether a signed manifest has legal effect depends on its wording and the law in your region. For legal or security decisions, get qualified advice.

Why a Handoff Manifest Matters

AI video tools make delivery fast. That speed can hide loose ends. A client may assume they can use every generated frame anywhere, forever. You may assume they only bought a license for one campaign. Speaker consent may be verbal. Script changes may live in chat messages. When a question comes later, memory is not proof.

A handoff manifest is one short document. It lists what was delivered, what the client may do with it, and what you both agreed. You create it before final delivery. The client signs it or confirms it in writing. Then you send the files.

This is not a copyright registration. It does not create rights by itself. It records what the parties intended. That record is useful when questions come later.

The Nine Fields of the Manifest

Keep the manifest to one or two pages. Use plain language. Each field answers one question.

1. Ownership and Rights

State who holds which rights in the final video. Common arrangements: the client owns the final edited video, or you keep ownership and grant a license. These are different things, so record them separately.

Also separate three categories that often get tangled:

• Transferable rights: What the client can use without coming back to you.
• License terms: What you grant for a set period, channel, or purpose.
• Third-party asset restrictions: Stock footage, music, fonts, or AI tool outputs that come with their own limits.

If you use AI tools, check their terms. Some tools grant broad rights to paying users. Others keep rights in outputs or restrict commercial use. Do not assume generated files are automatically copyrightable in every country, and do not assume your tool passes on everything the client needs.

Write one sentence for each category. Example fields: "Rights available to grant: confirm from the asset records. Agreed client use: a 12-month campaign license. Stock music: web and social use only, not broadcast." These are fictional fields to resolve, not ready-to-sign terms.

2. License Scope

If you keep ownership or grant limited rights, define the license. List allowed uses: website, social media, paid ads, broadcast, internal training. List excluded uses: resale, third-party licensing, editing into new works without approval.

Be specific about channels. "Social media" is vague. Say "organic posts on Client's own Instagram, LinkedIn, and YouTube accounts for 12 months." A channel scope prevents a client from running a local ad on national television without a new agreement.

3. Speaker Permission

People appearing in the video must agree to that use. This is separate from data protection consent. The UK Information Commissioner's Office (ICO) explains that consent for data processing is not the same as other legal or ethical permissions you may need (UK ICO guidance on when consent is appropriate). The ICO also notes that a power imbalance can make data protection consent inappropriate, including in employment relationships. That guidance is about data protection, not likeness rights. For likeness, the editorial point is simpler: record who appears, what they agreed to, and where that agreement lives.

A written release is usually the clearest evidence. Whether email is enough depends on the project, the jurisdiction, and what you need to prove later. Do not assume a small job is fine with email, and do not assume every job needs a signed form. Note any limits: "Speaker agreed to use on Client's website and YouTube only. No paid advertising."

If the speaker is the client's employee, a release form is still wise. It shows the person agreed to the specific use, not just to being filmed.

4. Script Sign-Off

AI tools can generate scripts quickly. That speed invites last-minute changes. Record which script version was approved, when, and by whom. Attach the final script or link to it.

The approved script must match the final exported words. If the client changed the script after voice recording, note that. A mismatch between script and spoken words can matter for claims or compliance. If words change after sign-off, get the new version re-approved. The manifest should say: "Final script v3 approved by Client on 14 March. Voiceover matches v3 exactly."

5. Versions Delivered

List every file you send. Include format, resolution, duration, and purpose. Example: "Final cut, MP4, 1920x1080, 90 seconds, for website. Square cut, MP4, 1080x1080, 60 seconds, for Instagram feed. Vertical cut, MP4, 1080x1920, 30 seconds, for Stories and Reels."

This prevents confusion about which file is the master. It also helps if the client asks for changes later. You both know what "the video" means.

6. Source Assets

AI video projects involve prompts, generated clips, stock footage, music, and project files. Decide what the client receives. Some agencies deliver only final renders. Others include source assets for an extra fee.

List what you will provide and what you will keep. Example: "Client receives final MP4 files only. Agency retains project files, prompts, and raw generated clips for 12 months." If the client wants to edit later, they need source assets. Make that a separate line item.

If you include third-party assets such as stock music or footage, check whether your license lets you pass them on. Some licenses are non-transferable. If the client needs those assets, confirm transferability in writing or point them to the original license.

7. Client Access

State how the client can access files. A shared drive link is common. Say how long the link stays active. Example: "Files available via secure link for 30 days. Client should download and back up all files within that window."

Do not promise indefinite hosting unless you offer it. Storage costs money. A clear access window sets expectations.

Also provide downloadable accessible support files where relevant: captions, transcripts, or audio descriptions. If you generated captions with AI, check them before delivery. Say what format they are in and where the client can find them.

8. Retention and Deletion

You may keep project files for future edits. You may also hold personal data, such as speaker names or contact details. The UK ICO's storage limitation principle says personal data should not be held longer than needed for the purpose (UK ICO guide to the storage limitation principle).

Write a simple retention line. Example: "Agency keeps project files and speaker release forms for 24 months after delivery, then reviews for deletion. Legal duties may require keeping some records longer." Do not promise immediate deletion of all backups. Backups are often automated and hard to purge instantly.

9. Exit Plan

Say what happens when the relationship ends. Can the client request deletion of raw footage? Can they take the project file to another agency? What fee applies?

Example: "On written request, Agency will provide a copy of the project file and all source assets within 14 days for a flat fee of £150. Agency will then delete client-specific files, except where legal duties require retention."

This field prevents a messy breakup. Both sides know the rules before tension starts.

Fictional Worked Example

The following scenario is fictional and for illustration only.

Team A is a small video agency. They use AI tools to create a product explainer for Client B, a fictional bakery chain.

Team A sends Client B a handoff manifest before final delivery. Here is the filled version:

Project: 90-second product explainer for Client B's new ordering app.

Ownership and rights: Client B owns the final edited video. Team A grants Client B a license to use it as set out below. Team A keeps ownership of the project file and reusable motion templates.

License scope: Client B may use the final video on its own website, YouTube channel, and Instagram account for 18 months. Use in paid advertising requires a separate written agreement. Client B may not resell or sublicense the video.

Third-party asset restrictions: The background music is licensed for web and social use only. It is not cleared for broadcast or paid advertising. The voiceover artist's performance is licensed for the same web and social uses.

Speaker permission: One voiceover artist and one on-screen presenter appear. Both signed release forms. Forms cover use on Client B's website and social channels only. Forms are stored in Team A's client folder.

Script sign-off: Script v2 approved by Client B's marketing manager on 5 June. Voiceover matches v2 exactly. No wording changes were made after recording.

Versions delivered: Final cut MP4 1920x1080, 90 seconds. Square cut MP4 1080x1080, 60 seconds. Vertical cut MP4 1080x1920, 30 seconds.

Source assets: Client B receives final MP4 files only. Team A retains project files, prompts, and raw generated clips. Stock music license terms are attached for Client B's records.

Client access: Files available via secure download link for 30 days. Client B should download and back up all files within that window. Captions and transcript are included as SRT and TXT files.

Retention: Team A keeps project files and release forms for 24 months after delivery, then reviews for deletion. Some records may be kept longer to meet legal duties.

Exit plan: On written request, Team A will provide the project file and source assets within 14 days for a flat fee of £150. Team A will then delete client-specific files, except where legal duties require retention.

Client B signs the manifest. Team A sends the files. Three months later, Client B asks to run the video as a paid ad. Team A points to the license scope and the music restriction. They agree on a new fee and a cleared music track. The question is resolved without a dispute.

Handoff Checklist

Use this table before every delivery. Tick each row.

Field	Question to Answer	Done
Ownership and rights	Who owns the final video, and what license is granted?	☐
License scope	Which channels and time period are allowed?	☐
Third-party restrictions	Which assets have their own license limits?	☐
Speaker permission	Who appears, and what did they agree to?	☐
Script sign-off	Which script version was approved, and does it match the final audio?	☐
Versions delivered	Which files, formats, and resolutions are included?	☐
Source assets	What does the client receive beyond final renders?	☐
Client access	How and for how long can the client download files?	☐
Retention	How long will you keep files, and when will you review?	☐
Exit plan	What happens if the client wants files or deletion later?	☐

Decisions and Edge Cases

Decision: Who owns AI-generated output? This depends on your tool's terms and your jurisdiction. Do not assume the client owns everything just because they paid. Check your AI tool's license. Record what your tool allows in the manifest.

Edge case: The client wants raw footage. Raw footage is not the same as source assets. Raw footage may include unused takes, unedited audio, or internal notes. Decide in advance whether you sell or share it. Many agencies do not. State this in the manifest.

Edge case: A speaker withdraws permission. If a speaker says they no longer agree to the use, pause the disputed use while you check the scope of the original agreement, the contract, and the legal rights involved. There is no universal rule that withdrawal always stops ongoing use. The manifest helps you see which uses were covered and what the speaker originally agreed to.

Edge case: The client edits the video and reposts it. Your manifest covers the version you delivered. If the client edits it, the new version may not match your records. Provenance tools can help here. The C2PA specification records tamper-evident provenance associated with a file (C2PA explainer). But valid provenance does not prove depicted claims are true. Provenance can also be incomplete. Missing credentials alone do not prove a file is fake. Do not promise that provenance survives editing or reposting.

Edge case: The client asks for deletion. You can delete client-specific files. But you may need to keep some records for legal duties, such as tax or contract evidence. Say this in the manifest. Do not promise to delete every backup immediately.

Three Short FAQs

Q: Is a handoff manifest a legal contract? A: It can have legal effect if it is worded as an agreement and meets the requirements in your jurisdiction. But this article is an editorial checklist, not a ready-made contract. For high-value projects, have a lawyer review your terms. The manifest works best alongside a proper contract.

Q: Do I need a signed release form for AI-generated voices? A: If the voice is based on a real person, get written permission for the specific use. If the voice is fully synthetic and not based on a named person, the question changes. Check your tool's terms and local rules.

Q: How long should I keep client files? A: There is no single right answer. Choose a period that fits your business need, such as 12 or 24 months. Review it regularly. The UK ICO says retention must be justified and reviewed (UK ICO storage limitation guidance). Legal duties can justify keeping some records longer.

Next Step

Create a one-page handoff manifest template today. Use the nine fields above. Fill it in for your next AI video project before you send the final files. Ask the client to confirm it in writing. Use the record to resolve open questions before delivery.

For more on running an AI video service, see our guides on AI video for agencies, how to start an AI video service, and whether AI video is legal.