AI Music for Client Videos: A Licence Pack You Can Hand Over
Handing a client an audio file is not the same as handing them permission to use it. The real deliverable for client video work is a licence pack: five written answers covering what the client may do with the track, a four-axis scope grid naming the media, territory, term, and exclusivity you are granting, a copy of the generator terms that were in force on the day you made the track, and a plain statement of what you cannot grant them. Build that pack once per track and every handover becomes a form you fill in rather than a promise you make from memory. Nothing here needs a paid plan, a lawyer, or a purchase of any kind to run.

The gap between a file and a permission
Most music deliverables for a client video are sent as a file and a line of friendly text. The file lands in the client's inbox, the track gets cut into the edit, and the job closes. What nobody wrote down is the only part that matters later: whether the client is allowed to use that track in the piece you made, in a second piece they made, on a paid advertisement, on a page they own forever, in a country you never considered, and whether they may pass the track to a third party such as their own agency or a broadcaster.
That silence is not a paperwork habit. It is a genuine gap in the handover, and the cost of leaving it open is usually paid later rather than now. It surfaces when a client asks to run the same track on a different cut, or when their legal team asks for a warranty they cannot get from you, or when a platform flags the audio during distribution. At that point the useful information has usually left your head and never entered the file.
There is a second reason the pack matters, and it is more specific to AI music. A track produced by a generator is governed by two separate layers of permission: the terms of the tool that produced it, and your own agreement with the client. The tool terms decide the outer boundary of what any output can be used for. Your client agreement decides how much of that boundary you actually pass across. When those two layers are never written down side by side, the most common outcome is that you grant more than the tool allows, and the failure lands on the client at the worst possible time.
So the deliverable is a pack, and the pack is small. This page gives you the five questions that decide its contents, the four-axis grid those answers fit into, a ten-item checklist, a copy-paste rights summary you can paste into an email or a contract attachment, a term-hunting table for reading the tool's own terms before you commit, and a rule set for reusing one track across more than one client.
The five questions a handover must answer
This is our own framework, and it is deliberately five questions long. Each one is written so that the answer is a fact about the deal rather than an opinion about the music. If any question cannot be answered in a single sentence, the pack is not finished and the conversation is not over.
| Question | An answer a client can act on | An answer that causes trouble later |
|---|---|---|
| 1. What exactly is being licensed | One named track, by file name and length, with the version they received | "The music" — which includes the other eight takes still in your folder |
| 2. What may the client do with it | A named list of uses: this video, this campaign, these platforms | "Use it as they see fit" |
| 3. For how long and where | A term in months or years, and a territory in named regions | Silence on both, which reads as perpetual and worldwide |
| 4. Who else may use it | A named position on their agency, their broadcaster, their client | No position stated, so the client assumes they may pass it on |
| 5. What is not included | An explicit list: standalone release, reselling the track, other clients, a claim to ownership | Nothing — so every prohibition has to be inferred from silence |
Two design choices are worth naming. First, the fifth question is the one people skip, and it is the one that does the most work. Every licence that only lists permissions is read by a nervous reader as unlimited, because the absence of a prohibition is the absence of a limit. Writing "not licensed for standalone commercial release, not transferable to another client" in plain words removes the ambiguity that a bare permission list leaves behind.
Second, question one is about identity, not quality. A track is identified by its file name, its length, and its version. This sounds pedantic until a client comes back three weeks later saying "the one with the long intro" — at which point the only way to resolve the reference is a written record, and if the record does not exist the two of you are guessing about two different files.

The four-axis scope grid
Every permission you grant sits on four axes. This is our own grid, and it exists because most handover arguments are really disagreements on one axis that nobody named out loud. A client who wants to run a paid advertisement against the track is not arguing about your friendship; they are asking for the media axis to widen, and the right answer is to say so plainly.
| Axis | The narrow end | The wide end | How to state it |
|---|---|---|---|
| Media | One named piece of content, one named platform | All advertising, all platforms, all future content | List the platforms and the content by name |
| Territory | One country, or the country where the client operates | Worldwide, in all media | Name regions; "where the client operates" is a common middle |
| Term | Until the campaign ends, or a fixed number of months | In perpetuity, with archive use | Give a number of months and a review date |
| Exclusivity | Non-exclusive: the same track may serve other clients | Exclusive within a category, or exclusive outright | Say whether anyone else may receive the same track |
The grid is written into the pack as a short block, and the block is what you quote when a client asks for something new. Here is the shape of it, with the four axes in a fixed order so that two packs for two tracks can be compared by reading them side by side:
TRACK: [file name].wav | length: [mm:ss] | version: [date] MEDIA: [content title] on [platforms, named one per line] TERRITORY: [regions, named] TERM: [N] months from [date], renewable by written agreement EXCLUSIVITY: [non-exclusive / exclusive within [category] / exclusive] PASS-THROUGH: [their agency / their broadcaster / their client: allowed or not] NOT INCLUDED: standalone release, reselling the track, use in other work DELIVERY FORMAT: [file names and formats sent with the audio] REFERENCE TRACK: [the file name of the previous version, if this replaces one]
Fill every line, even the ones where the answer is "none", because an empty line in a licence document is an invitation to argue. A pack with six filled lines and four empty ones is the same as no pack at all, and a pack with all ten lines filled is a document that can be read once by a client, a legal reviewer, or a platform rights team without anyone needing to call you to interpret it.
Three buckets: what you received, what you added, what they need
Before you can grant anything, you have to know what you are granting from. This is our own three-bucket split, and it is useful because most people treat "the output" as a single undifferentiated thing.
| Bucket | What it contains | Who owns it | What you can hand over |
|---|---|---|---|
| 1. The generated output | The audio the tool produced from your prompt | Determined by the tool's own terms for your plan | Whatever those terms allow, no more |
| 2. What you added | Your arrangement, edits, mixes, stems, and any recording you layered in | Yours, subject to whatever you signed when recording it | Yes, for the uses you name, because you hold the rights |
| 3. What the client needs | The right to use the combined work in a specific place | Nobody holds this until you write it down | This is the thing you are actually creating |
Bucket 1 is where the sharp edge is. Tool terms differ between free and paid tiers, and they can differ between a personal plan and a commercial one. The practical consequence is that the same prompt on the same tool can produce an output you may use commercially and an output you may only use personally, and the interface may not make that difference obvious at the moment you click generate. Reading the terms for the plan you are actually on is a ten-minute task that removes the largest unknown in the pack.
Bucket 2 is where clients get confused and where you can be generous. If you recorded your own guitar loop and laid it under a generated track, that layer is yours and you can licence it freely — but the generated track under it is still governed by bucket 1, and your permission does not extend over it. This is the point at which "we own the session" and "we own the rights" come apart, and it is worth naming the split out loud in the pack so that nobody later assumes the whole stack came from the same source.
Bucket 3 is the one people forget entirely, and it is the only one that is genuinely new when you hand it over. Before the pack, the client's use of the track rests on nothing more solid than a friendly message. After the pack, it rests on a written grant with a scope, a term, and a limit. That difference is the entire value of doing this work.
The handover packet: ten items and one template
The pack is a folder with a fixed structure. This is our own checklist, and the ordering matters because items four through seven are the ones that people assemble last and need first.
- 1. The audio file in the format the client asked for, named as the pack names it.
- 2. The rights summary — the template below, filled in and dated.
- 3. A copy of the tool terms in force on the generation date, saved as a file with the date in the name, not a link that may change.
- 4. The scope grid — the ten lines, with nothing left blank.
- 5. Your own contribution statement, one line naming what you added on top of the generated output.
- 6. The prompt and the settings used, kept as evidence of how the track was made.
- 7. The list of what is not licensed, written in plain language rather than legal shorthand.
- 8. The attribution position, if the client wants to credit anything, stated as a fact rather than a favour.
- 9. A named contact and a review date for the licence itself, not just for the project.
- 10. A change log for this track: which version superseded which, and when.
Item three is the one people treat as bureaucracy and it is the one that pays. Tool terms change, links move, and a summary page written for a different tier says something different from the terms you accepted. A saved copy, dated, is the only version of the terms that reliably describes the grant in your hands.
Here is the rights summary, written to be pasted into an email body or attached as a text file. It is deliberately short enough that a client reads it in one go, and complete enough that it can stand alone as the record of what was agreed:
LICENCE SUMMARY - TRACK [file name] Prepared by: [your name / studio] Date: [date] | Client: [client name] | Project: [project name] WHAT IS LICENSED The track named above, as delivered on [date], in the file formats listed. Use granted: [one line per content piece and platform] Territory: [regions] Term: [N] months from the delivery date Exclusivity: [position] Pass-through: [who else may use it, if anyone] WHAT IS NOT LICENSED - standalone commercial release of the track on its own - resale, rental, or licensing of the raw track to anyone else - use in any other project or client work - any claim to authorship or ownership of the track HOW THE TRACK WAS MADE [tool] generated output, produced on [date] under the plan named in the attached terms, with [your added elements] added by [your name]. Terms in force on the generation date are attached and dated. CONTACT AND REVIEW [name, email] | this licence is reviewed on [date] and does not renew automatically.
The last two lines of the template do more work than they look like they do. A named contact means the client does not have to guess who to ask, and a review date means a licence that was meant to cover one campaign does not quietly sit in a drawer granting rights to something nobody approved. "Does not renew automatically" is four words that remove an entire category of dispute.

The term hunt: what to look for before you promise anything
Tool terms are long, and the part that matters is buried. This is our own hunting table: the words worth searching for, what each one usually decides, and what to do about it before you write a grant. The list is a set of search terms, not a summary of anyone's contract — your plan's terms are the ones that bind you, and they change.
| Word to search for | What it usually decides | What to do before promising |
|---|---|---|
| commercial | Whether a plan allows revenue from the output | Confirm your plan tier, then write the tier into the pack |
| ownership | Who holds the rights in the output | Note the exact wording; many plans grant a licence rather than ownership |
| exclusive | Whether output is unique to you | Check whether exclusivity is limited to the paid plan |
| redistribute | Whether you may pass the raw file on | Assume a raw file needs separate permission, not an implied one |
| attribution | Whether credit is required | Decide your own credit position before the client asks |
| train | Whether output may be used to improve models | Read this one yourself; it rarely affects the client but affects you |
| termination | What happens if the plan ends | Check whether a lapse affects output you already delivered |
| refund | What you get back if a claim is made | Do not promise the client a remedy you have not read |
Two habits make this quick. The first is to search rather than read: a terms page that matters is usually under a few thousand words, and the words in the table above surface the paragraphs that decide your grant. The second is to save the result with the date in the filename, so that when a client asks in six months what the terms were at delivery, you send a file rather than an interpretation.
One caution about the table itself. It tells you where to look, not what you will find. Terms differ by provider, by tier, by country, and by date, and this page deliberately does not quote any specific clause from any specific service. If a term would change what you are willing to grant, read it in full and, if it is unclear, ask before you deliver.
Reusing one track across clients
Reuse is where the money is and where the trouble concentrates, because the same file is now attached to two different relationships. This is our own rule set for the four reuse cases you will actually meet.
| Reuse case | What to check first | Safe default |
|---|---|---|
| Same track, same client, new piece | Whether the term and the media list in the pack cover it | Add a line to the pack rather than sending the file alone |
| Same track, different client | Whether you granted exclusivity anywhere, and whether the tool terms restrict resale of the raw file | Non-exclusive wording, and say plainly that the same track may serve other clients |
| Same track, new version of the piece | Whether the new cut changes the mix, the length, or the structure | Keep the original reference line in the pack and name the new file |
| Same track, client asks for a cutdown | Whether the edit changes the character of the music | Treat a trim as the same track; treat a new melody as a new track |
The distinction in the last row is the practical one. Trimming a thirty-second cue to twenty seconds leaves the same work. Rebuilding the music around a new melody in the same genre is a new work, and it needs its own track identity in the pack. Clients rarely see this line, which is why you should put it in writing before they ask, and not after.
There is a second reuse question that belongs here: what happens when the same track serves two clients in the same category, and one of them later complains that their competitor is using the same music. If your pack says non-exclusive, that complaint has an answer. If your pack says nothing, the answer becomes a matter of who talks more persuasively. Write the exclusivity position down once, at the first delivery, and the question stops being a crisis later.
A thirty-minute pre-delivery routine
Here is the whole method as a sequence, in the order that avoids rework. It is our own sequence, and every step is deliberately cheap.
- Read the tool terms for your actual plan and save a dated copy (10 minutes). One search per word in the hunting table. Save the file as terms-[date].txt next to the project.
- Fill the three buckets (3 minutes). Name the generated output, name everything you added, and leave the third bucket empty because that is what the client agreement creates.
- Fill the scope grid (4 minutes). All ten lines, with "none" written where the answer is none.
- Write the rights summary and attach the terms (6 minutes). Paste the template, fill it, and date it.
- Check the two internal links (2 minutes). Does the licence grant reach the tool terms, and does the term list match the scope grid? Most contradictions live between those two.
- Send it with the audio, not after (3 minutes). The pack and the file should arrive in the same message. A pack that arrives after the client has already cut the track is a negotiation instead of a handover.
- Log the delivery in one line (2 minutes). Date, track file name, client, project, term, media. One line per delivery, in the same file you keep your prompts in.
Total time is about half an hour per track, and it drops sharply for the second and later tracks because the terms copy and the scope grid are reused. The value of the routine is not the half hour. It is that in two years, when a client calls about a track they used in a campaign that ended, you can answer in one sentence because you wrote the sentence down on the day.
Where this stops being a paperwork problem
Two honest limits belong here, because licence frameworks get oversold. First, this method handles the handover you control, not the world the track lands in. It cannot make a track eligible for a platform, and it cannot make a claim disappear. It tells your client what they may do and what they may not, which protects the relationship; it does not change the tool terms, and it does not replace advice from a qualified reviewer when the stakes are high enough to justify one.
Second, a licence summary is a record of understanding, not a contract. For a small project between you and a client you know, a plain summary sent in an email is usually the right level of formality, and it is far better than the usual alternative of nothing. For a large campaign, an exclusivity request, a broadcast placement, a term of years, or a client with their own legal team, the summary becomes an attachment to a real agreement, and the right move is to have the agreement drafted properly rather than to treat the summary as if it were the agreement.
A third limit is worth naming because it is uncomfortable. Some tool terms make certain commercial uses impossible regardless of what you write, and no amount of careful wording changes that. This is the reason the term hunt comes first in the routine: read the outer boundary before you start describing the inner one.
Where this fits beside the rest of the workflow
A licence pack assumes you know what you are licensing. If the track itself is still uncertain, the licence reading page covers the clause that decides what a royalty-free label does and does not mean, and the upload checklist covers the steps after a release. If the audio has structural problems, the ending repair kit handles the last eight seconds and the longer-than-three-minutes page covers length and structure. For a track that must sound like the last one you delivered, the five-slot style fingerprint keeps a client's series consistent. If the real question is what the platform will do with the upload, the upload volume page and the watermark and fingerprint page cover the surrounding ground. When the track does not fit the brief at all, the four-axis split is the right place to start.
Common questions
Do I need a licence if the client paid for the work?
Payment for a service is not the same thing as a grant of rights. In many cases the two are implied by the working relationship, which is why small projects often work fine without any document. The pack matters at the point where the client does something you did not plan — a paid advertisement, a second country, a longer term — because that is where the implied grant stops being obvious and the question has to be answered in writing.
What if the client asks for a track I have already licensed exclusively?
You cannot grant what you gave away, so the answer is no on that track, and the useful thing is to offer the alternative in the same message: a non-exclusive version of the same brief, a variation on the same fingerprint, or a new track from the same style slot set. The style fingerprint is what makes the second option cheap, because you are not starting from nothing.
Do I have to hand over the raw audio file, or is a finished mix enough?
That is a pass-through decision, and it is yours to make. A finished mix limits what the client can do with the track and keeps your arrangement intact. A raw or stem version gives them flexibility and creates a redistribution question that the tool terms may not even allow. Many clients accept a mix for a piece of content, and the pack is where you state that limit rather than discover it later.
How much of this do I really need for a small job?
The scope grid and the one-paragraph rights summary. Those two things cost fifteen minutes and cover the five questions, the four axes, and the exclusions in a single artefact. The dated terms copy and the change log matter more as the number of clients grows, because that is when your own memory stops being reliable.
Is a licence pack enough if the track gets flagged somewhere?
No, and it would be misleading to say otherwise. A pack documents what you granted and what the tool terms said at the time. It does not make a track eligible for distribution, and it does not resolve a rights claim. What it does is give everyone a clear starting point: the terms, the date, the scope, and the person who granted it.
What if the client wants the track for a purpose I did not license?
Answer in writing and in the same order every time: what is licensed today, what the new use would require, and what you are willing to add. Widening the media axis for a named paid placement is often reasonable. Widening it silently is how a scope you never agreed to becomes a scope you are stuck defending.
Does the client need to know the track was made with AI?
That is partly your policy and partly a question of the platform and the client's own rules, and it is better decided before delivery than during a review. Whichever position you take, record it in the pack, because "we did not say and it came out later" is worse than either answer. Some clients need to know for their own disclosure, and telling them early is the cheaper option.
How long should the licence last?
Long enough to cover the use you granted and no longer. A campaign licence that matches the campaign is easier to defend than a perpetual one, and the review date on the summary turns an open-ended grant into a decision you make deliberately. If the client wants a longer term, treat that as a new question with a new answer rather than a detail to be vague about.
What if I have already sent the track without any pack?
Send the pack now, with a short note explaining that it is a record of what was agreed rather than a new condition. The scope grid is usually accurate to what you both assumed, and writing it down converts an assumption into a record without making the client feel they have been caught out. It is a much better position than continuing to rely on what was said in a message three weeks ago.
Can I reuse the same licence pack for a second track?
Yes, as a template, but not as a document. Every track needs its own identity line, its own date, its own terms copy if the generation date differs, and its own reference to the version being delivered. What you reuse is the structure, which is the point of having a structure at all.
Bottom line: the deliverable for client video work is a pack, not a file. Five questions decide what goes in it, four axes decide what you can actually grant, and a dated copy of the tool terms decides the outer limit of the whole thing. Fill the scope grid, paste the rights summary, save the terms with the date on them, and send it with the audio — then the only question left in a handover is whether the music is good, which is the question you wanted to be having.