The fastest way to lose money on AI client work is not a bad generation. It’s a friendly project with no written agreement that hits revision nine, a rights question nobody settled, and a client who reasonably believes they bought something you reasonably believe you never sold. Both of you are being honest. There’s just no paper, so the honesty collides.
AI video needs its own clauses because the work breaks analogies clients bring from normal video production. There’s no shoot day, no raw camera footage in the usual sense, revisions are partly lottery, and the tools’ terms sit underneath your terms. Here’s the contract structure I use — the thinking behind each clause, in plain language you can adapt. This is general information from a creator’s workflow, not legal advice; for high-value work, have a lawyer in your jurisdiction review your template once and bill it to professionalism.
Why AI Work Needs Its Own Clauses
A traditional video contract assumes re-shooting is expensive and editing is cheap-ish, that footage is owned outright, and that the deliverable is the deliverable. AI work inverts half of that. Generating another option can be fast, but generating the same option again can be impossible. There’s no camera negative — only prompts, references, and project files. And your right to deliver the work commercially rides on the terms of Seedance, Veo, or whatever produced the frames, which your client has never read and shouldn’t have to.
So the contract’s job is translation. It converts your real process — storyboard approval, generation rounds, edit revisions, tool terms underneath everything — into promises a client can sign without needing to understand the pipeline. Clients don’t actually want to own your prompts or audit your tools. They want to know four things: what they’ll receive, what happens when they want it different, what they may do with it forever, and who handles the AI paperwork with platforms and audiences. Write those four answers clearly and most client anxiety evaporates. Because most client anxiety was never about art. It was about surprise.
Defining Deliverables: Resolution, Ratios, Revisions
Vagueness here is where margin goes to die. “A promo video” is not a deliverable. A deliverable list reads like a packing slip:
- The master file: duration target, resolution, frame rate, codec or delivery format, and where it will be delivered.
- The ratio set: which aspect ratios are included — horizontal master only, or vertical and square cutdowns cut and re-framed properly, not auto-cropped afterthoughts. Ratio work is real work; list it or charge for discovering it later.
- Captions and text versions: burned-in, sidecar, or none. On short-form work this matters daily.
- Revision definition: what counts as one revision round. My working definition: one round is one consolidated set of client notes answered with one new export. A client trickling fourteen messages across a week is having one conversation, but the contract should say rounds are counted per consolidated delivery, or the trickle becomes infinite by accident.
Put numbers in. Two edit revision rounds on the approved storyboard’s video, for example, with extra rounds priced. And anchor revisions to the storyboard: clients approve boards first, then generation follows the approved boards, then revisions adjust execution — timing, grade, text, music — rather than re-litigating the concept in the edit. That single linkage, storyboard approval as the concept lock, prevents the classic disaster where feedback at the video stage is secretly a request for a different video. Our storyboard-first workflow article shows the boards side; the contract is where you make clients glad the boards exist.
The AI Disclosure Clause: Who Tells Whom
Somebody has to decide how the AI involvement gets disclosed: to the platform at upload, to the audience in the post, and sometimes to regulators or a client’s own customers depending on the use. The contract should name who decides and who executes, because the person uploading is usually the client while the person who knows is you.
My clause does three things. It states the work is created with AI tools (no surprises later, ever). It states the client, as publisher, is responsible for platform disclosures and labels at posting, with me supplying any information they need about how the work was made. And it protects the work from the opposite problem: if a client’s industry, campaign, or brand guidelines require specific disclosure language or prohibit certain synthetic uses, the client surfaces that before storyboard approval, not at delivery. A brand with a legal department will respect you for raising this early; a brand without one needs you to raise it anyway.
Agreeing this upfront also removes the late-night message every AI freelancer eventually gets: “Legal just saw it, can we say it wasn’t AI?” With the clause, the answer was written before the question existed. If disclosure obligations are new territory for the client, walking them through how platforms expect synthetic ads to be labeled tends to settle the conversation better than arguing clause language.
Rights, Ownership And Source Files
This is the section clients care about most and freelancers write worst — usually by promising “full ownership” of things no AI freelancer can cleanly promise. Untangle three layers and write each one honestly.
Layer one: the delivered video. On full payment, the client receives the rights to use the final delivered files as broadly as your underlying tool terms allow you to grant — typically wide commercial use of the finished piece. Say that, in those honest terms, rather than swearing you own every atom outright. General principles and tool terms decide what can be granted; our AI video copyright guide digs into that layer.
Layer two: usage scope. Where may the client run it — organic social only, or paid media, broadcast, out-of-home, for how long, in which territories? AI work for a local business’s Instagram and AI work anchoring a paid campaign are different products with different exposure. Your price should know the difference even when your goodwill does not.
Layer three: source materials. Prompts, reference sheets, project files, unused generations. Default professional practice: these are your working tools and stay yours unless the client pays for a handover package — because handing over a project file hands over your process, your reusable systems, and sometimes references you have no right to pass on (a licensed voice, a hired performer’s likeness). If a client needs source files for their in-house team, price it as the asset transfer it is and clean the files of anything third-party before they move.
Payment gates the transfer. Rights on final payment, stated warmly and plainly, is standard — and clients accept it when it’s written before work starts rather than discovered during an invoice dispute.
Retake Limits: Generations Are Not Free
Clients raised on stock footage think in “pick another take.” Clients raised on shoots think in “we got what we got.” AI sits between: another take costs a generation, and generations cost credits, time, and — the part nobody budgets — selection and continuity work reviewing them. Unlimited retakes is the clause that quietly eats a fixed fee.
So define the generation budget the way a shoot defines a day. For each approved shot, a stated number of generation attempts is included; the best result, judged against the approved board, goes to the edit. If the client wants to explore beyond the board — new angle, new action, new character beat — that is a direction change, quoted before it burns credits, not after. Also define the failure case honestly: occasionally a shot won’t generate acceptably after reasonable attempts. The contract should offer the ladder in advance — adjust the board, substitute the shot, or credit that portion — so a stubborn generation becomes a production decision instead of a breach-of-promise argument at midnight.
I include one more sentence that has saved more relationships than any other: client feedback that reopens an approved storyboard restarts that shot’s generation budget as a change order. Said early, clients nod. Said mid-project without paper, it sounds invented. The revision mechanics pair naturally with our client revision workflow guide; contract language and day-to-day process should tell the same story.
A Plain-English Clause Checklist
Before your next AI engagement, confirm your agreement answers all of these in writing — email confirmation counts for small jobs if it’s explicit and saved:
- Deliverables listed as files: count, duration, resolution, ratios, captions.
- Storyboard approval step named as the concept lock.
- Revision rounds defined and counted; extra rounds priced.
- Generation attempts per shot included; direction changes treated as change orders.
- AI use stated openly; disclosure responsibilities assigned to the publisher, with you supplying production information.
- Client to surface brand, legal, or platform constraints before boards are approved.
- Usage scope for delivered files: media, term, territory; rights transfer on final payment.
- Source files excluded by default; handover available as a priced, cleaned package.
- Third-party elements (music, voices, fonts, likenesses) listed with their clearance holder named.
- Timeline with client feedback windows, so approvals do not drift silently.
Three Situations That Test Every Clause Above
The scope-creep special. A client booked one vertical video, then asked for horizontal, then captions, then a second ending “while you’re in there.” Without a deliverables list, each ask feels small and rude to refuse; with one, the conversation is arithmetic — these two are inside the agreement, those two are a small addition I’ll price today. The clause didn’t create friction. It gave goodwill a price tag so it could be spent deliberately.
The model changed mid-project. Generation tools update, retire versions, and shift output quality between your storyboard approval and your delivery deadline. My contracts carry a plain sentence: if a tool change materially alters the approved look, we revisit the affected shots together and agree the adjustment before I burn the budget. Clients accept this instantly when it’s written early, because it protects their approval too — the boards they signed off on remain the reference point, not whatever the model felt like this week.
The client wants to reuse the character everywhere. A delivered ad’s character turns out to be a hit, and the client wants her in next quarter’s campaign, then a mascot program. Delightful — and a new rights conversation: my source files, possibly a performer’s likeness consent scoped to one campaign, and generation work priced for a series. Contracts that named source-file ownership and consent scope at the first job make this expansion a celebration with an invoice attached, instead of an argument about what the first fee supposedly included.
None of this requires a twelve-page document. Most of my working agreements would fit on two pages a client actually reads, and that readability is the point: a contract the client understood is the one that protects you both. Write yours before the next friendly project, while friendly is still the mood, and let the paper carry the awkwardness so the work never has to.