A track that is going anywhere will have ten, twenty, thirty versions before it is done. The question is not how to avoid that — you should not — but how to keep thirty versions from turning into a folder nobody dares to open. This is a working method: what deserves a version, what to write on it, how to choose the one that counts, and how to compare two of them without exporting anything.
Most labels already run on a project management tool — a Trello board, a Notion workspace, a shared drive with a folder per artist. And most of them still answer the same question by email several times a week: which mix did we approve? The board tracks tasks; the drive holds files; neither of them understands that a track has versions, that an approval applies to one of them, or that the mixer should not see the rest of the roster. This article is about that gap, and what a tool built around the music itself adds to the tools you keep.
Open the folder of any song that took more than a week and you will find it: mix_v3.wav, mix_v3_FINAL.wav, mix_v3_FINAL_louder.wav, MASTER_use_this_one.wav. Software developers solved exactly this problem decades ago and called the solution version control. Music production has the same problem with worse file names — and a few twists of its own.
Most unreleased music does not leak because someone broke in. It leaks because a WeTransfer link got forwarded, a Dropbox folder held the whole album when only one mix was needed, or a "temporary" link from eight months ago still works. Secure file sharing, for a musician, is not antivirus and firewalls. It is four plain questions you should be able to answer for every file you send: who can open it, for how long, what they can do with it, and how you would know.