Lock Artwork and Masters Before You Announce
Announcing a release date before the master and artwork are final is how the wrong file ships. Lock artwork and masters first, then set the date.
Lock your final master and final artwork before you announce a release date, not after. The moment you announce, the date becomes fixed and everything else has to bend to it, which means any master still "almost done" or artwork still "waiting on one tweak" gets rushed, and rushing is how the wrong file goes live on every platform at once. The professional sequence is backwards from what most artists do: finish the assets, confirm they are truly final, then count backward to set the date. Announce first and you have handed control of your quality bar to a calendar.
Why does announcing first cause bad releases?
Because a deadline you cannot move turns every open item into a fire. Artwork that needs one more revision now ships at v3 instead of v4 because there is no time. A master the engineer wanted another pass on goes out as-is. A last-minute swap happens under pressure and someone uploads the wrong bounce. Every one of these is a self-inflicted wound created by fixing the date before the work was done.
The fix costs nothing: finish first. When the master and artwork are genuinely locked before the date exists, there is no pressure to swap anything at the last minute, because there is nothing left to finish. This is one of the most common mistakes coordinating a music release, and it is entirely avoidable by reordering two steps.
What does "locked" actually mean?
Locked means final, named, and untouchable. For the master:
- The final approved bounce, at full quality, correctly named with its version.
- Signed off by whoever has approval (you, the artist, the label).
- No "we might revisit the vocal level" hanging over it.
For the artwork:
- Final file at the exact spec the distributor requires.
- All text correct: title, artist name, features, spelled right.
- Approved by everyone who gets a say.
The naming matters more than people think. "master_final.wav" and "master_final_v2.wav" sitting in the same folder is how the wrong one ships. Version discipline on your masters is the same problem as tracking song versions and stems. If you cannot point to the one true final file with certainty, it is not locked.
How do you handle the approval chain?
Get every approver to sign off explicitly, before you announce, in one place. A release often needs sign-off from more than one person: the artist, a manager, a label, a featured guest who wants to approve how they are credited. If you announce the date and then chase approvals, you are back to rushing, and an approver who feels rushed either rubber-stamps something they will regret or holds up your date.
Collect approvals as a gate, not a formality. Nobody's asset is locked until the people who matter have said yes. Doing this over scattered emails and texts is how an approval gets lost and the wrong artwork ships, which is the case I made in why Dropbox and email are not a workflow. Approvals need to be visible and recorded, not buried in a thread.
How do you make this your default?
Put "master locked and approved" and "artwork locked and approved" as hard gates on your release checklist, ahead of "announce date" and "submit to distributor." Order enforces itself when the checklist will not let you proceed. I keep a full release checklist for independent artists built exactly this way, so the date is the last thing set, not the first.
Keep the locked files, their version names, and the approval status in one view, so at a glance you know whether you are actually ready to announce or just eager to. When the final assets are provably locked and everyone has signed off, the announcement is safe and the release is calm. Run it through Track Pitch so the master, the artwork, and the approvals live together and the wrong file can never sneak through. Set the date last. Your future self will thank you on release morning.