The Snapshot You Wish You Had
Picture this: six months after a campaign launched, a legal dispute arises. The claim is that a talent's usage rights didn't cover the placement. You need to prove that at the time of approval, the rights were active.
But the rights record has since been updated. The talent contract has been amended. The reviewer who approved the creative has left the company. The version of the creative that was approved has been replaced by a newer one.
Without an approval snapshot, you're reconstructing history from fragments. With one, you have a frozen record of the exact governance context at the moment of approval.
What an Approval Snapshot Captures
An approval snapshot is an immutable record created at the exact moment a creative is approved. It captures the full governance state — not just the decision, but everything that informed it:
- The creative version — the exact file that was approved, not just "the creative"
- The reviewers — every reviewer assigned, their review type, their decision power, and their decision
- Compliance checks — whether brand compliance, legal clearance, and deliverable validation passed
- Usage rights — a summary of all active usage rights, including expiration dates and territorial coverage
- Linked claims — each product claim and its clearance status at approval time
- Legal clearance — whether legal clearance was confirmed, by whom, and when
- Advisory warnings — any warnings that were flagged but didn't block approval
- Gate result — the approval gate verdict, including any blocking conditions
Why Immutability Matters
The snapshot is immutable. It can't be edited after the fact. This is what makes it evidence rather than assertion.
Without immutability, an approval record is just a claim. Someone can say "the rights were active when we approved it" — but without a frozen record, they can't prove it. The rights record might have been updated, the reviewer might have changed their mind, the compliance check might have been re-run with different results.
With immutability, the snapshot is a point-in-time fact. It says: at this moment, on this date, these were the conditions under which the creative was approved. That's not a claim — it's a record.
Amendments and Prior Snapshots
When an approved creative is amended, a new snapshot is created. The new snapshot references the prior one, so the amendment history is preserved. You can trace the full approval lineage: the original approval, the amendment, the re-approval, and the conditions at each step.
This is important because amendments are where governance often breaks down. A creative is approved, then someone changes a line of copy or swaps an image. Without a new snapshot, the original approval covers a creative that no longer exists. With one, the amendment is a new governed event with its own context.
The Cost of Not Having Snapshots
The cost of not having approval snapshots isn't felt until something goes wrong. When everything is fine, nobody asks for the approval record. When something goes wrong — a legal dispute, a compliance audit, a client challenge — the approval record is the first thing everyone needs.
Without a snapshot, you're reconstructing the approval context from memory, email, and whatever records still exist. With one, you have a single, authoritative record that shows exactly what was approved and under what conditions.
The question isn't whether you'll ever need an approval snapshot. The question is whether you'll have one when you do.