AI-assisted production does not remove ordinary rights and consent questions. Teams still need authority to use sources, a lawful and respectful basis for depicting people, and clear records of human contribution and material alteration. This guide identifies review questions, not legal advice.
Trace every source and reference
Record where source photographs, illustrations, typefaces, logos and reference images came from, who owns them and which uses are permitted. A file found online is not automatically available for training, editing or campaign use.
Check licence scope, territory, duration, modification rights, attribution and restrictions on sensitive or commercial contexts. Escalate uncertainty before uploading material to a service whose terms have not been approved.
Treat consent as contextual
A release for one photograph does not necessarily authorise synthetic alteration, a new sensitive context or imitation of a person’s likeness or voice. Check the agreement, intended use, audience and applicable publicity, privacy and consumer rules.
Avoid implying that a real person performed an action, endorsed a product or appeared in a place without support. Obtain specific review for children, health contexts, political messaging, intimate material and other high-impact uses.
Disclose and preserve what matters
Agree with the client how material generation or alteration will be described. Preserve source attribution, licences, consent records, prompts or settings where relevant, human edits and final approvals. IPTC metadata can carry rights and descriptive fields when the workflow retains them.IPTC Photo Metadata Standard ↗
C2PA provides a technical standard for content provenance and authenticity assertions. It can support transparency but does not decide ownership, consent or truth on its own.C2PA technical specification ↗
Add rights questions to creative intake
Ask who supplied every source, who created it, which licence or agreement applies, where the asset will run and whether alteration is permitted. For people, ask whether the proposed synthetic change and context were contemplated. Capture uncertainty before material is uploaded to a tool.
Do not treat a client-supplied file as automatically cleared. The client may expect the studio to flag a scope mismatch, embedded third-party element or sensitive use. The project owner should assign responsibility for confirmation in writing rather than letting both parties assume the other checked.
Review the new depiction, not only the old release
A model release for a neutral portrait may not answer whether the person can be placed in a health, political or testimonial context. A product licence may not allow removal of attribution or creation of lookalike variants. Compare the delivered agreement with the new communication, audience and territory.
Ask whether a reasonable viewer could infer endorsement, participation or factual presence. If so, verify that the inference is supported and permitted. Disclaimers are not a universal cure for a misleading depiction, and the correct response may be new consent, a different concept or specialist advice.
Align the delivery record with the contract
State which assets are delivered, what the studio actually created, which third-party terms remain, what usage scope was agreed and which records accompany the files. Avoid promising exclusive ownership when the legal and technical facts do not support it.
Retain signed agreements, source licences, consent evidence and alteration notes under the project retention policy with access limited to people who need them. The public asset may carry concise credit or provenance, while sensitive evidence remains in the controlled production record.
A practical decision table
| Question | Record | Escalate when |
|---|---|---|
| May we use the source? | Licence and provenance | Scope or origin is unclear |
| May we depict the person this way? | Consent and intended context | Use is new or sensitive |
| What did humans create? | Brief, edits and selections | Ownership is material to delivery |
Release checklist
- List every source
- Confirm licence scope
- Review service terms
- Document human contribution
- Check likeness permissions
- Assess sensitive contexts
- Agree disclosure language
- Preserve rights metadata
- Record final approval
- Seek local legal advice when needed
Common questions
Is every AI-assisted output free to use?
No. Source rights, service terms, likeness rights, trademarks, contracts and local law can still apply.
Do content credentials prove copyright ownership?
No. They can record provenance assertions, but ownership and permission require separate analysis.