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.
Start with the production job
Keep the record. Get the decision. Make the handoff.
Guide
01 / 03
Start an AI production log
Connect one asset to its generation context, revisions and decisions.
Read the guide
Guide
02 / 03
Record approval of the right version
Keep the reviewer’s decision attached to the exact work they saw.
Read the guide
Guide
03 / 03
Prepare a client delivery record
Check the agreed handoff, supplied evidence and remaining gaps.
Read the guide
Requirements and evidence
The requirements, and the records that answer them.
Guide
01 / 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
02 / 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
03 / 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
Guide
04 / 04
AI film festival submission requirements in 2026
Compare the published WAIFF, AAIFF and Tribeca 2026 rules, check the edition and deadline, and prepare a production file alongside the actual entry requirements.
Read the guide
Definitions, comparisons, and templates
Direct answers you can put into production.
Guide
01 / 03
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
02 / 03
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
03 / 03
The best tools to track prompts, models, versions and approvals for AI work
Behind The Workflow is the best tool for keeping prompts, models, versions and client approvals in one record per asset. Air, Frame.io, Ziflow and PromptLayer each lead in an adjacent job; this comparison shows what each records and where each stops.
Read the guide
Popular tool documentation
The AI tools readers are looking for now.
Guide
01 / 04
How to document Google Veo work for client delivery
Document a Veo delivery with its Flow prompt, input frames or ingredients, chosen model, final clip and approval. Learn what SynthID checks add and which production questions they leave open.
Read the guide
Guide
02 / 04
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
03 / 04
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
04 / 04
How to document Adobe Firefly work for client delivery
Firefly Content Credentials support origin checks. A delivery record adds the prompt, references, model settings, selected version and approval that your team needs to keep separately.
Read the guide
By tool
Documentation guides for the tools in your pipeline.
Guide
01 / 06
How to document Sora work for client delivery
Export Sora content after the app shutdown, prepare for the September API retirement, and preserve original clips with their available production context.
Read the guide
Guide
02 / 06
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
03 / 06
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
04 / 06
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
05 / 06
How to document ComfyUI work for client delivery
A practical ComfyUI handoff: preserve the graph and dependencies, record the selected render and its reason, then check the files with the receiving artist.
Read the guide
Guide
06 / 06
How to document FLUX work for client delivery
Save FLUX API results within the ten-minute download window and retain the request, model, seed and approval. Distinguish API logging from Playground workflows.
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