The IP warranty carve-out for AI deliverables
You cannot assign copyright that never existed, so a blanket originality warranty may already be broken. Carve-out language that stays honest and still sells.
There is a sentence in almost every creative services agreement that reads something like: "All Deliverables shall be original works of authorship, and Agency hereby assigns to Client all right, title and interest in and to the Deliverables, including all copyright therein." It has been boilerplate for decades. Nobody negotiates it. It is frequently the shortest paragraph in the contract.
If any meaningful part of your deliverable came out of a generative model, that sentence may contain two promises you cannot keep. The first is that the work is original in the copyright sense. The second, and the harder one, is that there is a copyright there to assign at all. You cannot assign rights that do not exist, and signing a document that says you can does not create them.
This is a walkthrough of the fix. It is not legal advice, and the drafting here is a starting point for a conversation with counsel rather than a substitute for one.
The gap between contractual ownership and copyright
The confusion usually starts with platform terms, because they sound like they settle the question. Terms of service from the major model providers do assign ownership of outputs to the user, and that assignment is real and useful. But it is a contractual allocation between you and the provider. It says the provider will not claim the output. It cannot manufacture a copyright that statute declines to grant in the first place.
The distinction matters commercially, not just academically. Contractual ownership means the provider will not sue you and will not license your output to someone else. Copyright means you can stop a stranger who copies it. If a competitor lifts your client's hero frame and runs it in their own campaign, the question is not what the provider's terms said. It is whether the frame is protectable at all.
The US Copyright Office position on that is consistent and reasonably well settled in practice: protection attaches to human contribution. Three routes are recognised in the guidance practitioners work from. Substantial human modification of generated material. Human-authored elements combined with generated ones. And the creative selection, arrangement and coordination of AI-generated material into a larger work. Raw output, prompted and delivered untouched, sits outside all three.
Note what this does not say. It does not say AI-assisted work is unprotectable. It says the protection tracks the human layer, and the human layer has to actually be there. A thirty-second edit assembled from forty generated clips, sequenced, timed, colour-matched, scored and captioned by a person is a very different object from a single unedited render, and the contract should stop treating them as the same object.
Jurisdiction adds a second axis. That analysis is a US framing, and ownership treatment varies between jurisdictions. A warranty defensible for a US-only campaign may not be for a client shipping across regions, and the carve-out should say so rather than pretend to a single global answer.
Carve-out language that stays honest
The replacement has three moving parts: a definition, a narrowed warranty, and an honest statement about what is unresolved.
Define the category first. Vagueness here undoes everything downstream. Something in the shape of: "AI-Generated Portions" means any element of a Deliverable produced in whole or substantial part by a generative model, prior to human modification, selection or arrangement. Use the defined term consistently. If you only use it once, in the carve-out, a reader can reasonably argue about scope later.
Narrow the warranty rather than deleting it. Deleting the originality warranty entirely reads as evasive and will not pass procurement. The version that does pass keeps the warranty for the human layer and carves out the rest:
Agency warrants that the Deliverables do not, to Agency's knowledge, infringe the intellectual property rights of any third party, and that all human-authored elements of the Deliverables are original to Agency. Agency does not warrant that AI-Generated Portions are protectable by copyright, and the parties acknowledge that copyright protection for AI-generated material is determined by the extent of human authorship and varies by jurisdiction. Agency assigns to Client all right, title and interest that Agency holds or may hold in the Deliverables, including any copyright subsisting in the selection, arrangement, modification and human-authored elements thereof.
Three things that language does. It preserves the non-infringement warranty, which is the one the client genuinely needs and the one that is actually about risk. It stops promising a legal outcome nobody controls. And it still assigns everything you have, which is the part clients care about once they understand the difference.
Say the unresolved part out loud. A single sentence acknowledging that the position varies by jurisdiction and may change is worth more than it looks. It converts a future surprise into a disclosed known, which is the whole function of a warranty schedule.
Give the client what they actually wanted
Almost no client wants copyright for its own sake. Push on the question and what emerges is a short list of commercial outcomes, and every one of them can be delivered by contract without relying on copyright at all.
| What the client wants | How to deliver it without a copyright warranty |
|---|---|
| Use the asset freely, anywhere, forever | Full assignment of whatever rights exist, plus an unrestricted licence as a fallback |
| Nobody else gets the same asset | Contractual exclusivity: you will not deliver these Deliverables or substantially similar work to another party |
| Not get sued over it | Non-infringement warranty plus a scoped indemnity |
| Keep working with the asset later | Delivery of project files, prompts, seeds and source layers |
| Stop a copycat | Trademark, passing off, contractual routes; be honest that copyright may not be available |
That fallback licence is the underrated line. Write it as: to the extent any element of the Deliverables is not subject to assignable rights, Agency grants Client a perpetual, worldwide, royalty-free, irrevocable, sublicensable licence to use it for any purpose. Belt and braces, costs you nothing, and answers the "so what do I actually have?" question in one sentence.
Exclusivity deserves emphasis, because it is what clients reach for once they understand copyright may not be available. It is a promise you make rather than a right the law grants, and it works fine as long as it is written down. Check that it agrees with the rest of your licensing terms rather than contradicting them, and with the underlying usage rights grant.
The production record that decides the answer
Here is the operational consequence most studios miss. Whether there is a copyright in the deliverable is a question of fact about human contribution, and facts need evidence. Two years after delivery, when it matters, "we edited it quite a lot" is not evidence.
What is evidence: a timeline. An EDL-based editor keeps the edit as a re-renderable decision list rather than a flattened file, which means the selection, sequencing, timing and arrangement of every clip is recorded as structured data rather than baked into a single output. That is almost exactly the shape of the creative selection and arrangement route the Copyright Office guidance describes. Keeping the project rather than only the export costs nothing and makes the human layer legible after the fact.
Worth keeping alongside it, per deliverable:
- The brief and any human-authored script, storyboard or copy.
- Which models produced which elements, and roughly how many attempts were discarded.
- The edit project itself, not just the flattened export.
- Licence terms for third-party inputs and for any open-weight model used. Fonts are a recurring trap, since OFL terms permit less than most people assume, and what open weights let you ship varies sharply.
That record does double duty. It supports the human-authorship argument if protection is ever contested, and it supports the non-infringement warranty, which is the promise you are still making and the one most likely to be tested. Broader background on how copyright, safety and platform policy interact for generated work is worth reading before you draft, and so is the general licensing picture for business content, because the warranty sits on top of both.
FAQ
If the output might not be protectable, why does the client still pay for it?
Because they are buying a working asset on a schedule, not a copyright certificate. The commercial value sits in the brief, the judgement, the iteration and the finish, and none of that changes. In practice most clients react to the carve-out with a shrug once the fallback licence and the exclusivity promise are in front of them. The ones who react badly are usually those whose own downstream contract promised something they now cannot.
Does heavy editing guarantee copyright protection?
No, and promising that is the same mistake in the opposite direction. Substantial human modification is one of the recognised routes to protection, but "substantial" is assessed after the fact and there is no threshold you can point at in advance. Document the work, make the human layer real, and let the warranty stay silent on the outcome.
Should the carve-out apply to every deliverable?
Apply the definition to every deliverable and let it come out empty where no generative model was involved. Trying to maintain two contract templates, one AI and one not, fails the first time a designer uses a generative fill on a background at 6pm on a deadline. One template with a definition that scopes itself is more robust than two templates that depend on someone remembering.
What if the client insists on the original warranty unchanged?
Ask what they need it to do, then offer the specific outcome instead. If the answer is "our legal team requires an originality warranty," the carve-out plus a non-infringement warranty plus the fallback licence usually satisfies the underlying requirement once someone reads it. If they insist on the literal sentence, price the risk or decline. Signing a warranty you know to be inaccurate is worse than losing the project, and it undermines every other clause in the agreement.