Creative operations4 min read
V5 sent, v3 approved, v1 live: why nobody can find the final version
The final version is not the newest file. It is the one with a recorded decision: approver, date and a locked file in a place the whole team can open.
In short: The final version goes missing because the approval decision lives apart from the file. There is one way out: versions stacked in a single place, the approved one flagged, protected from editing, with approver, date and time on the record.
Wednesday, nine in the morning. The client writes to say the asset that went live is not the one they approved. Someone opens the folder and finds seven files that look alike. v5 was the last one sent, v3 was the one approved in the meeting, and v1 is the one published, because that was the file sitting on the machine of the person at the end of the line.
Nobody got it wrong on purpose. And the whole operation still stops, on an ordinary Wednesday, to answer a question that should not exist: which file counts?
Why the approved version disappears
In a typical operation, the approved version lives in three places at once. In the thread where someone wrote “approved”. In the agency’s shared folder, next to the other six versions. And on the machine of whoever published, who downloaded the right attachment in the wrong week.
Three addresses, none reliable. The thread records the decision but does not point to the file. The folder holds the files but does not record the decision. And the machine of whoever publishes answers to nobody. Keeping an asset and its history in one place is the old premise of digital asset management, and applying that premise to versions is where most operations still stop.
Renaming does not solve it. Every team has seen a “final-v2-THIS-IS-IT.psd” and laughed, and the joke aged better than the routine: a file name carries hope, not a decision. Current industry estimate: 30% to 50% of creative work gets redone, and part of that rework is people reproducing what was already finished somewhere nobody found.
AI made an old problem worse
The study Maturidade da IA no Marketing, run by ActiveCampaign with Anamid and published by Varejo S.A on August 6, 2026, surveyed 215 companies and brings a figure that helps explain the moment: 90% of Brazilian brands say they use AI day to day, with application concentrated in content production.
Producing got cheap. Every asset is now born with more variations, more formats and more intermediate versions than the team can name. The bottleneck changed address. It left creation and moved to governance. We wrote about how artificial intelligence affects creative operations in marketing agencies back in 2023, and the point holds harder now: producing ten times more versions without changing how the approved one gets flagged only multiplies the size of the pile the final version hides in.
Peter Carloni argues that this is the real maturity test of a creative operation. Not the speed at which it produces, but the time anyone takes to find the version that counts.
What defines a final version
Four definitions are enough:
- Versions stacked in a single place.
- The approved one visibly flagged.
- Approver on the record, with date and time.
- File frozen and protected from editing.
Only the fourth needs justifying: without freezing, Friday’s “quick tweak” undoes in practice what was approved on Tuesday, and the record becomes fiction.
With that in place, the question “which file counts?” dies. Whoever arrives later does not ask the group. They open it and see.
Frequently asked questions
Does renaming the file as “final” solve it?
No. A file name carries no decision: anyone renames it, nobody audits it. The flag has to sit in the system where the versions live, tied to who approved and when.
Who should flag the approved version?
The approver of that stage, in the act of approving. If flagging is a separate task, done later by somebody else, it becomes one more step someone forgets.
And when the client approves in a chat?
The chat counts as a signal, not as a record. The practice that works: move the decision to the place where the asset lives on the same day, with the exact version linked. A decision with no file pointed at is half a decision.
Where this gets solved
The whole argument in this article points to one condition: demand, production, approval and assets need to live in the same place, otherwise the decision will always sit far from the file. That is the problem Wikimee solves for creative operations. To see how it works in practice, the path is to look at the platform and book a conversation.
