Content Credentials can carry a signed record of a media asset’s origin and editing history. For an AI film, use that record alongside a plain-language process note and organised source files. Inspect what is actually recorded; do not treat a badge as proof that a scene happened or that every production step is documented. This guide is editorial advice, not a Milan AI Festival submission rule.
Start with what the record actually says
The C2PA 2.4 explainer describes Content Credentials as signed provenance structures associated with digital assets. They can contain statements about creation, modifications, and AI use. The standard distinguishes validation of that record from a judgement that the depicted content is factually true.
For your own project, begin with one specific file. Is it a generated source image, a working clip, a promotional still, or the final film export? Write down which version you inspected and which information you found. A record attached to a source image does not, by itself, explain the editing decisions behind an entire film.
Keep the observation modest and readable. “This source image includes a creation record from the tool used to make it” is more useful than a broad claim that the whole production has been verified. Only describe a result that you have actually checked.
Build a handoff around one scene
Choose a scene with a clear production history. Create a small handoff folder containing the source material you can share, the selected working version, the final excerpt, and a short note linking them. This is an editorial organisation method; it is not a prescribed C2PA implementation.
In the note, explain the scene’s intention, which material was generated or captured, and what changed during selection and editing. Name the collaborators responsible for sound, performance, compositing, or other contributions. If the record covers only some elements, state which ones those are.
For example, an illustrative project might combine a generated background, a filmed performer, and an edited soundscape. The accompanying note would account for those contributions separately. It would not describe a credential on the background as evidence about the performer or the sound. Replace this example with the actual materials in your project.
Check each delivery version, not just the working file
Make a simple delivery log with the filename, intended use, export date, and the result of your provenance check. Use separate entries for the master, the screening copy, and a promotional image when those files exist. Do not assume a finding about one version applies to another.
If you plan to publish a file through a platform, inspect the version a viewer can actually access as well as the version you uploaded. Where the two differ, record the difference without guessing why it happened. Keep your original handoff files so you can revisit the comparison.
This is a useful point to divide responsibilities. The maker can describe the production; the editor can identify the approved export; the publishing team can check what the public receives. A short shared log makes those responsibilities clearer than a generic assurance in an email.
Handle absent credentials without guessing
C2PA’s guidance on media without Content Credentials says their presence or absence alone should not determine trustworthiness. An absent record is not a basis for declaring a file human-made, AI-generated, or misleading.
When a check finds no usable record, report that observation and move to the information you do have: the maker’s explanation, available working versions, credits, and production notes. Distinguish a statement supplied by the maker from something you inspected yourself.
Avoid filling a gap with a confident story. If you do not know whether a tool added credentials or whether a later workflow retained them, write that down as unresolved. For a creative conversation, a precise uncertainty is often a better starting point than an unsupported technical claim.
Write a process note that an audience can understand
Keep the public explanation shorter than your internal log. A useful structure is: what the work aims to communicate; which parts used AI; what people selected, changed, performed, or edited; and what provenance information is available. Put the creative intention first so the explanation has a purpose beyond naming software.
Use our AI film project breakdown guide when you want to show a before-and-after decision in more detail. For a concise presentation, Prompt2Screen’s guide to explaining an AI film process offers a related editorial resource.
Review any material before sharing it publicly. Your internal folder may include unpublished collaborator work, private filenames, or information unrelated to the audience’s question. Select the examples that explain the process and that you are authorised to share.
Keep festival requirements separate from editorial advice
Milan AI Festival is a VIA Group — Visual Innovation Awards event. This article offers a way to organise and discuss creative work; it does not announce a credential requirement, submission category, or judging policy.
Consult the official Milan festival information for confirmed participation details. When preparing work for any event, read that event’s own instructions and ask the organiser about missing technical requirements. A well-organised provenance handoff can support the conversation, while the creative work still needs to communicate on its own.