The Version That Went Live Without Approval
A creative is approved on Monday. On Wednesday, the designer uploads a new version with a small copy change. On Friday, the new version goes live — without anyone reviewing it. The approval was for Monday's version, not Wednesday's.
This is the version control problem in creative operations. It's not that approvals don't happen — it's that they're not tied to a specific version. When a new version replaces an approved one, the approval should be invalidated. Without version locking, it isn't.
What Version Locking Does
Version locking freezes the approved version of a creative. Once locked, the file can't be replaced without initiating a governed amendment. The lock is a server-enforced control — not a convention, not a checkbox, not a best practice. It's a hard stop.
When a creative is version-locked:
- The approved file is the only file that can be published or shared
- Any replacement triggers an amendment workflow with its own approval cycle
- The lock timestamp and the approved version ID are recorded immutably
- The approval snapshot references the locked version, so the context can't drift
Why Versioning Without Locking Isn't Enough
Many creative operations systems have versioning — each upload creates a new version, and you can see the history. But versioning without locking is just a history. It doesn't prevent the wrong version from going live.
The problem is that versioning is passive. It records what happened, but it doesn't enforce what should happen. A designer can upload a new version, and the system will dutifully record it as version 4 — but it won't stop version 4 from going live without approval.
Version locking is active. It says: this version is approved, and no other version can take its place until a new approval is granted. That's the difference between a history and a control.
The Amendment Workflow
When a locked creative needs to be changed, the amendment workflow is initiated. This isn't just uploading a new file — it's a governed process:
- The amendment reason is documented — why does the creative need to change?
- A new version is uploaded — the replacement file
- The new version goes through review — the same approval process as the original
- A new approval snapshot is created — capturing the context of the re-approval
- The new version is locked — replacing the prior lock
The prior snapshot isn't deleted — it's preserved as the historical record. The amendment creates a new snapshot that references the prior one, so the full approval lineage is traceable.
The Cost of Not Locking
The cost of not locking versions is felt in two ways:
Compliance risk. An unapproved version goes live, and the organization can't prove what was actually approved. The approval record says version 3, but the live creative is version 4. The gap is a compliance exposure.
Reputational risk. A stakeholder sees a creative they didn't approve, and the organization can't explain what happened. The trust damage extends beyond the single creative — it affects the entire approval process.
Version locking eliminates both risks. When the approved version is locked, only that version can go live. When a change is needed, it goes through a governed amendment. The approval is always tied to the exact version that was reviewed.
Governance Without Friction
The argument against version locking is the same as against any governance control: it adds friction. In practice, it adds clarity. Designers know when a creative is locked and when it's not. Reviewers know which version they're approving. Publishers know which version is approved. The lock isn't friction — it's certainty.