The artwork arrives with Content Credentials. Its signature validates, so the launch team moves it into the ready-to-publish folder. One detail is missing: the product owner approved the previous version, before the latest copy edit.
This hypothetical handover is not an ONCE client incident. It illustrates a useful acceptance question for overseas brands commissioning content from China: does the signature attached to this file correspond to an actual decision to release this version for this use?
A draft can be signed
Adobe’s “Content Credentials for organizations,” last updated October 6, 2026, describes automatic credentials in GenStudio for Performance Marketing. Modified assets exported from a draft are re-signed and linked to the original. The documentation separately describes re-signing approved experiences when they are saved to Content.
That establishes the documented workflow in this product, not a capability shared by every editing tool or a first-launch date. The procurement implication is specific: a signing event can occur during drafting. The presence of a signature alone cannot establish completion of business review.
The C2PA 2.2 explainer describes provenance and history, and explains that provenance alone cannot establish whether content is accurate or factual. ONCE’s further inference concerns internal release decisions: a general credential indicator should not substitute for an approval record. A particular implementation may carry explicit approval assertions; reviewers must examine what those assertions mean and whether they satisfy the brand’s process.
Give verification and release different statuses
Provenance verification asks which file was checked, which tool was used, what assertions were available and what result was returned. Release approval asks who authorized this version, for which markets and channels, and whether conditions remain outstanding.
A technically valid draft can still be awaiting product review. Conversely, an approved film may lose detectable credentials during distribution. Handle the latter against the project’s provenance and disclosure requirements; missing credentials alone do not establish that the content is false.
The operational question here is not how to preserve every source record. It is whether the publishing team has sufficient authority to use the exact file now in its hands.
ONCE’s signature-to-release check
Keep a short record for each candidate release. This is ONCE’s proposed management method, not a required C2PA schema or a claim that ONCE has deployed a particular integration. A simple shared table can support it.
Identify the actual object
Record the asset ID, exact version and file location. Where exact file matching matters, ask the technical team to record a checksum. “Final launch image” is an inadequate identifier when files can be overwritten. Both the verification result and the approval decision must point to the object being published.
Record two different kinds of result
For provenance, retain the checking tool, time, available signer or tool assertions and actual validation status. Do not turn “not detected” or “unable to verify” into an invented pass or fail.
For release, retain the approver, approved version, permitted use and outstanding conditions. Permission for an English product page does not automatically cover every language or advertising channel. If the approval belongs to an earlier version, identify the subsequent change and its disposition before marking the file ready.
Assign the final matching task
Production explains how the export corresponds to the reviewed version. The brand confirms the intended use. The publisher checks that the uploaded object is the right one. One person may perform several roles, but none of the tasks should disappear. Software access does not itself confer brand approval authority.
Decide what a change requires
Imagine an approved image for a desktop device. To make a portrait variation, the team shortens its feature statement. The resulting file may receive fresh credentials, yet the new wording still needs to be assessed for a change in the product promise. A continuous provenance chain makes the change traceable; it does not settle the copy decision.
A technical transcode may instead fall within an already approved transformation rule, with no change to content or use. An assigned person can confirm that it meets the rule, rather than sending the entire project through another full review. The rule must exist before the exception is invoked.
Changes to a model, numerical claim, accessory, language, use scenario or distribution purpose should go to the relevant decision owner. Do not require a complete restart for every alteration, and do not describe every alteration as technical. The actual change determines whose approval is needed.
Buy clarity about two completion points
Delivery completion means the files, provenance records and version references are present. Release completion means the brand has approved this version for its intended use and the published object matches. A supplier may support both tasks or only the first. State the division in the scope of work.
Also assign responsibility for post-approval content additions, changes in intended use after export and alterations made at the publishing end. These can create new review or replacement work. Agree the treatment rather than hiding every possible task inside a generic number of revision rounds. No universal time saving or cost percentage is assumed here.
Adobe’s documentation additionally requires administrator certificate configuration for an organization’s own brand signature. For an outsourced team, the practical step is to let the brand’s system owner manage configuration and authorization while production follows the agreed submission process. This article does not provide certificate deployment or key-management instructions.
Test whether a signed draft can slip into release
Using authorized test material, prepare a version that has credentials but has not received business approval. In a test environment or internal handover, check whether a badge, successful export or library entry causes it to be treated as ready to publish. Correct ambiguous statuses or handover rules before using the process for live material.
Then reverse the check. For a candidate launch file, can the publisher find the approver and permitted use tied to that object? A validation screenshot alone is insufficient. A message approving the previous cut requires an explanation of what happened afterward.
For ongoing content work, the useful asset is the relationship between files, changes and decisions. It makes reuse easier to evaluate without claiming that provenance replaces factual review, licensing or business judgment.
When briefing ONCE’s production and AI content team, describe who exports, who approves and who uploads. Make those actions refer to one identifiable version before deciding which steps to automate.
Sources and limitations
Adobe Experience League, “Content Credentials for organizations,” updated October 6, 2026; C2PA, “C2PA and Content Credentials Explainer,” version 2.2. Both checked October 29, 2026. Version 2.2 is not presented as the latest specification. The review method and hypothetical example are ONCE’s analysis, not client results or a finding of platform failure. The original AI cover is a conceptual commercial scene.
