A community organization photographs a local event. A volunteer edits the images, a colleague uploads them, and a partner republishes one with a new caption. By the time a reader asks where the photograph came from, nobody is sure which copy was approved.
This hypothetical handoff is ordinary enough to be easy to overlook. For public-interest information, a lost original or changed caption can make a correction much harder. Small teams need a process that survives a change of person, tool, and file.
C2PA helps with provenance; the handoff still needs people
C2PA can bind signed provenance records to an asset. Those records may describe creation, editing, and source materials. They provide evidence about the asset's history within the scope of what was recorded. They do not certify the truth of a caption, grant publication rights, or guarantee that all previous activity is known. See the official C2PA explainer.
The practical aim is to preserve both the useful technical evidence and the human context needed to interpret it.
Conceptual illustration with fictional scenes, not a real verification result. The recorded fields depend on the file and software.
- Preserve the original: Keep the received file separate from the publication copy.
- Carry the context: Pass on the source, caption, permissions and contact privately.
- Check the delivered copy: Record the credential result for what the reader receives.
- Plan corrections: Name an owner who can update the caption and notify recipients.
Keep four things distinguishable
| Item | Why keep it separate? | Suggested handling |
|---|---|---|
| Received original | Later transforms may change the file and its readable provenance | Preserve it with appropriate access controls |
| Working and publication copies | The approved edit and the delivered file may differ | Give each version an identifier and record its role |
| Caption and source notes | Text outside the image is not automatically covered by image verification | Track the caption, source URL, and unresolved claims |
| Private coordination record | Contact details and sensitive context need not be public | Keep access restricted and assign a responsible person |
This is a proposed operating checklist, not a standard mandated by C2PA. A file hash can help distinguish two exact byte sequences, but it does not prove a photograph's truth, authorship, or permission status.
At intake: ask what you actually received
Record who supplied the file to the team, where it was obtained, and which facts are confirmed or unknown. Do not fill in a missing capture time from memory. Keep the received caption beside the file, and mark any later caption revisions separately.
Clarify the intended publication and any restrictions with the relevant people. A record that can be verified cryptographically is not evidence that a person depicted agreed to every possible reuse.
During editing: preserve the chain you can explain
Work on a copy. Note the tool, version, and operations that matter for understanding the image. Where your supported workflow produces a new manifest for an edited asset, retain the relationship to its ingredients as intended by that workflow.
Do not add a new record to an old photograph and describe that as recovery of its complete past. A new record can describe the operation now performed; it cannot create trustworthy knowledge of earlier events that were never recorded. The implementation guidance is a starting point for planning supported edit and distribution workflows.
Avoid placing sensitive contact details into a record just because the software offers a field. C2PA's harms analysis explains why privacy and later rediscovery of earlier information need consideration before publication.
At delivery: check what a reader receives
An upload completing successfully is not evidence that the final delivered file has the same readable provenance as the original. A content management system, thumbnail service, or content delivery network may transform the image.
Have the reviewer obtain the actual delivered copy and note:
- which URL and file were checked;
- the verifier and version, including relevant trust configuration;
- which recorded details were readable and which checks completed;
- any errors or unknowns, without relabeling them as proof of false content;
- whether the surrounding caption still matches the approved explanation.
This article reports no measured preservation rate and no completed tool comparison. Run and record these checks in your own environment before making a claim about your pipeline.
Make correction ownership part of the package
Before handing a file to a partner, decide who receives a correction request and who contacts downstream publishers. Keep a short version note that can be shared without exposing private sources. Replacing one copy on your own website does not recall copies held elsewhere.
A useful handoff ends with a statement such as: “This is the approved publication copy. The date in the caption remains unconfirmed. Contact the designated editor before reusing it as evidence of a current event.” It gives the next person something concrete to act on.
PKI Channel's implementation playbook in Japanese and image-sharing verification guide in Japanese provide further checklists for planning this work. The goal is not to attach a badge to every picture. It is to make the evidence, limits, and responsibility travel with the image.
AI was used for research assistance, writing and illustration.
