Guides
Working with AI, documented properly.
Sourced, practical guides for creative teams that deliver AI-assisted work to clients. Every external claim links to the original requirement so you can check it yourself.
Compliance and delivery
The requirements, and the records that answer them.
Guide
01 / 04
How to document AI-generated work for client delivery
What broadcasters, platforms, agencies, and rights offices already require when AI is part of delivered work, and the per-shot checklist that answers all of them.
Read the guide
Guide
02 / 04
EU AI Act Article 50 for creative teams
What the transparency obligations for AI-generated and AI-manipulated content actually say, the real timeline and penalty ceiling, and what a team should record to be ready.
Read the guide
Guide
03 / 04
AI provenance: what you can prove and what you cannot
An honest map of provenance claims: what a record can demonstrate about inclusion, integrity, and time, and which causal claims no system can support.
Read the guide
Guide
04 / 04
Prompt and model documentation: a practical checklist for studios
The fields worth capturing for every generation: prompts, models, versions, settings, references, and edits, and how to keep the habit alive in production.
Read the guide
Definitions, comparisons, and templates
Direct answers you can put into production.
Guide
01 / 04
What is an AI production log?
An AI production log is the per-asset record of prompts, models, settings, references, edits, rights decisions, and approvals behind AI-assisted work. Here is the minimum useful structure and the limits of what that record can prove.
Read the guide
Guide
02 / 04
C2PA vs. AI workflow documentation
C2PA and AI workflow documentation solve different parts of the provenance problem. C2PA protects signed assertions attached to media; workflow records preserve prompts, sources, decisions, rights, versions, and approvals around the file.
Read the guide
Guide
03 / 04
AI shot log template for image and video production
A practical AI shot log template for prompts, models, references, versions, human edits, disclosure, and approval. Download the CSV and adapt the field guide to your production workflow.
Read the guide
Guide
04 / 04
How to record client approval for AI-generated work
A client approval record for AI-generated work should identify the exact version, disclosed AI use, review scope, requested changes, approver, and time. This guide turns sign-off into evidence instead of an ambiguous email.
Read the guide
By tool
Documentation guides for the tools you generate with.
Guide
01 / 10
How to document Sora work for client delivery
Sora embeds C2PA metadata in every asset and marks downloads with a visible moving watermark, but the prompts, iterations, and cameo consents behind a clip stay in the app. This guide covers what OpenAI's provenance signals prove and what you still have to record before client delivery.
Read the guide
Guide
02 / 10
How to document Google Veo work for client delivery
Every Flow output made with Veo carries an invisible SynthID watermark, and Gemini can verify it, but the check names Google AI as the origin and nothing else. This guide covers what to record so a Veo delivery can answer the questions SynthID cannot.
Read the guide
Guide
03 / 10
How to document Luma Dream Machine work for client delivery
Dream Machine keeps your work organized in Boards and an Ideas stream, but the watermark and the commercial license of a clip depend on the plan that generated it, and the exported file names neither. This guide covers the records that close that gap before client delivery.
Read the guide
Guide
04 / 10
How to document Ideogram work for client delivery
Ideogram shows the seed and even the Magic Prompt rewrite for every image in its Details Panel, but none of it travels with the downloaded file, and images are public by default. This guide covers what to copy out of the panel and when to generate privately.
Read the guide
Guide
05 / 10
How to document Midjourney work for client delivery
Midjourney keeps a searchable archive of everything you generate, but the record stays inside your account and images are publicly discoverable by default. This guide covers what midjourney.com actually stores, what never travels with a delivered file, and the per-job checklist that closes the gap.
Read the guide
Guide
06 / 10
How to document Runway work for client delivery
Runway keeps your generations in sessions and an asset browser, with a Fixed seed option for related takes, but the video you deliver carries no prompt, seed, or settings. This guide covers what Runway stores in the account and what a producer has to record per shot.
Read the guide
Guide
07 / 10
How to document ComfyUI work for client delivery
ComfyUI automatically embeds the workflow graph in the metadata of every image it saves, which makes it unusually self-documenting. This guide covers what that embedded workflow proves, where it silently disappears, and what a client record still needs on top.
Read the guide
Guide
08 / 10
How to document self-hosted Stable Diffusion work for client delivery
A self-hosted Stable Diffusion setup writes its generation parameters into every image by default, at least in the AUTOMATIC1111 web UI most teams run. This guide covers what that buys you, what silently breaks it, and what a client record still needs.
Read the guide
Guide
09 / 10
How to document FLUX work for client delivery
The FLUX API from Black Forest Labs delivers each image through a signed URL that stays valid for ten minutes, and the docs describe no archive to return to later. This guide covers what the API gives you at request time and the logging your pipeline must do in that window.
Read the guide
Guide
10 / 10
How to document Adobe Firefly work for client delivery
Firefly attaches a Content Credential naming the model and version to what it generates, and its API returns the seed for every image. This guide covers what that provenance layer proves, how it can be stripped, and what a client delivery record still adds.
Read the guide
By role
Production records from your side of the work.
Guide
01 / 05
AI production records for AI producers
AI producers own the delivery questions nobody else can answer: which model, which prompt, which version, approved by whom. This guide sets out the records that let a producer answer from evidence instead of memory.
Read the guide
Guide
02 / 05
AI production records for creative directors
Creative directors approve what ships, so questions about AI in the work come to them, in client meetings and in review rooms. This guide covers the records that let them answer precisely instead of vaguely.
Read the guide
Guide
03 / 05
AI production records for post-production teams
In post, AI arrives as a hundred small fixes inside shots rather than one big generation, which is exactly what makes it hard to declare on a delivery form later. This guide covers records that map to shots, versions, and conforms.
Read the guide
Guide
04 / 05
AI production records for freelance AI artists
Freelance AI artists warrant their own process in every contract they sign, with no legal department behind them. This guide covers the records that back those warranties, survive tool subscriptions, and win repeat work.
Read the guide
Guide
05 / 05
AI production records for agencies
Agencies carry contractual responsibility for AI use across every team, freelancer, and production partner on an account. This guide covers records that hold at agency scale, where the person who generated and the person who answers are never the same.
Read the guide
About this library