AI creative-work contracts: Negotiate terms before you adopt the tools
Use a permission ledger to negotiate AI credit, consent and compensation before upload or replica creation, with a stop rule when the terms do not fit.
A studio wants to upload commissioned artwork to a model. An agency wants writers to revise generated copy. A client wants a synthetic version of a performer’s voice. Before buying access or sending files, identify whose permission each action needs and what the agreement actually allows.
Negotiate credit, consent and compensation before authorising a defined use; reject the tool when the required permission is missing.
This is a documentary-based negotiation playbook, not a tested implementation or a prediction that adoption is inevitable.
When to run this playbook
Run this process before procurement, a contributor-contract change, a first upload, a replica session or an expansion into another project. Include the creative workers and rights holders, not just the buyer and vendor.
The history explains why timing matters. Sousa’s 1906 objections to mechanical music included unpaid reproduction. In 1908, White-Smith held that piano rolls were not copies under the existing statute, leaving the remedy to Congress. The Copyright Office’s testimony traces the player-piano dispute to the first compulsory mechanical licence in 1909. Under the 1909 Act, that mechanism followed the owner’s authorisation of an initial mechanical reproduction; it was not unrestricted permission to make the first one.
The historical royalty was two cents per part. Register of Copyrights Marybeth Peters explained: “The two cent rate set in 1909 remained in effect until January 1, 1978, and acted as a ceiling for the rate in privately negotiated licenses.” That is a warning about stale terms, not a rate to copy into an AI contract.
The 1927–1937 transition to sound cost musicians their jobs. Robin D.G. Kelley’s history, as paraphrased with his approval in Local 802’s Allegro, describes around 22,000 theatre-pit musicians in 1926, most unemployed within two years, and a later campaign ending on July 8, 1937. A larger art form does not compensate the particular people who lose work. Negotiating terms does not guarantee protection for everyone.
Step-by-step procedure
1. Define the action before discussing the tool
Write a one-paragraph scope: which project, which assets, which model or service, which people, which outputs and which audience. Separate uploading, generating, editing, training, fine-tuning and publishing. Permission for one action must not silently become permission for all of them.
Ask the vendor for the applicable terms and retention settings in writing. Ask the contributor what rights they can grant. Buying a finished illustration does not, by itself, answer every question about uploading it or using it to train a model.
2. Open a permission ledger
Keep one row per asset and proposed action. Copy this structure into a spreadsheet; split an asset across rows when its uses differ.
| Field | What to record |
|---|---|
| Asset and action | File/version; upload, edit, generate, train or publish |
| Rights holder and approver | Named person or organisation; authority to grant this use |
| Permission evidence | Signed agreement or licence; clause and stored document location |
| Scope and exclusions | Project, service/model, audience, territory, term; prohibited uses |
| Credit and disclosure | Required names, placement and synthetic-content notice |
| Compensation | Creation fee, reuse rate, substitution floor and payment trigger |
| Retention and exit | Storage period, deletion duties, withdrawal process and limitations |
| Decision and review | Approved, pending or rejected; owner, expiry and change triggers |
Use “pending” rather than a guessed yes. A ledger is an index to permission evidence, not a substitute for the agreement. Keep contributor permission, client approval and vendor commitments distinct.
3. Negotiate the three levers separately
Credit: specify who is named, where attribution appears and how synthetic material is disclosed. Decide how supplied AI material affects the human contributor’s credit and fees. Do not let a provenance label imply permission that has never been granted.
Consent: describe the particular use, project and duration. Keep training and fine-tuning separate from ordinary processing. Specify whether reuse needs fresh approval, how consent can be withdrawn and what withdrawal can realistically stop. Do not promise that deletion can undo completed training without evidence.
Compensation: price the initial work and subsequent permitted uses. If the proposed workflow substitutes for a paid engagement, negotiate a floor or reuse payment rather than assuming the original fee covers indefinite substitution. These are proposed bargaining terms, not universal legal entitlements.
4. Turn principles into clauses
The historical 2023 WGA agreement’s Article 72 shows how a broad demand becomes specific boundaries. It excluded AI-generated writing from literary material, required disclosure of supplied generative-AI material and, in specified circumstances, kept it from counting as assigned material for pay or source material for writing credit. Article 72.E also prohibited requiring a writer to use a generative program to produce otherwise-literary material as a condition of employment.
Treat these as historical examples, not a statement of current entitlements or clauses that automatically cover your organisation. For your own agreement, disclose supplied material, protect agreed human credit and pay, and define whether using the tool is optional.
Article 72.F reserved rights relating to AI, including the training question; it did not establish a blanket training-consent prohibition. Put your own requested training restriction explicitly into the negotiation rather than assuming a reservation settles it.
5. Issue a bounded approval or a stop decision
An illustrative approval could read: “Project A only; the listed assets may be processed in the named service for internal drafts until the recorded expiry date. No training, fine-tuning, replica creation or public release is authorised. The project lead checks every output before circulation. Any new asset, use or service, or a substantive change to the terms, requires renewed approval.”
Choose actual names and dates before signing. Check that the vendor can honour those exclusions. If its terms reserve incompatible training or retention rights, an internal note cannot override them.
Stop before upload when authority is missing, a contributor declines, the proposed use exceeds the licence or the vendor cannot accept the restrictions. Stop an approved workflow when any of those conditions changes. Quarantine affected outputs, record the reason and follow the agreed deletion or exit process.
Checkpoints
Before access is enabled, the project owner should be able to locate the signed permission, identify every approved action, explain the payment trigger and name the person who can stop work.
Before release, compare the output and intended distribution with the ledger. Check credit placement, disclosure and reuse fees. Review again at expiry or a scope change; do not rely on a calendar reminder alone.
Variations
For an agency, client approval does not replace contributor permission. For an internal team, employment does not answer every training or likeness question. For a replica, separate permission to create it from permission to use it.
Reject tools without permission. Keep the human workflow, commission a licensed alternative or abandon the proposed use. Negotiation is useful only when refusal remains a real outcome.
Jeffrey Katzenberg’s September 23, 2026 X essay, quoted through Cartoon Brew, says: “The tools-versus-no-tools argument is a trap. First, we must all agree that there should be terms. Then we can have the crucial debate about what fairness requires.” That framing can open a negotiation. It is not evidence that promised gains will reach displaced artists; Cartoon Brew challenges that gap.
Anti-patterns
Do not equate vendor access with permission, treat a broad buyout as informed agreement, promise future compensation without a payment mechanism or use historical adoption as proof that refusal is futile. Do not call a pilot harmless merely because it is small.
Done means
Every proposed action has documented permission or a recorded rejection. Approved work has credit instructions, payment terms, an expiry, an accountable owner and an executable stop condition. Missing permission means no use, not provisional adoption.
What this article does NOT cover
This is not legal advice, a fair-use determination, a review of current union entitlements or a model-quality assessment. It does not settle training rights, forecast employment or claim that every technology wins. The procedure is an inference from documentary evidence, not reported hands-on experience.
Related guides
Use Agent containment for technical boundaries once a use is authorised. Restricting an agent’s access cannot supply missing creative-work permission.
Research basis: shared/abs-research-briefs/aidb/terms-not-technology/terms-not-technology-research-2026-09-27.md (documentary dossier; key primary evidence re-verified 2026-10-11).
Sources
Sources
Submit a take
Have a different read on this? Drop a comment below — your email isn't published, and I read every one. Nothing leaves the site until I approve it.