A release can become difficult to manage when the final master is mixed with old demos, the artwork has several conflicting versions, and important permissions exist only in a chat thread. Build one organised source folder before uploading, then keep a separate backup you have tested.

Give each release a stable home

Create a folder named for the artist and release, with clearly labelled subfolders for final audio, artwork, metadata, permissions, and promotional assets. Keep work-in-progress sessions separate from the files approved for delivery.

A simple example is Artist/Release/Final-Audio, Artist/Release/Artwork, and Artist/Release/Rights. You do not need this exact structure; you need a structure that you and authorised collaborators understand.

Distinguish approved masters from working versions

Avoid filenames such as final-final-newest.wav. Use a clear version label and record which file was approved for distribution. Keep the actual approved lossless export rather than assuming a downloaded stream can replace it.

Retain the format and technical details of your source master. Do not convert a lossy file to a lossless container and describe it as an original lossless master: changing the extension or container does not recover missing audio detail.

Save a metadata sheet alongside the music

Record the artist and release names, track order, titles, versions, main and featured artists, contributor credits, explicit-content flags, and release date. Add existing ISRCs and UPCs when available, identifying which code belongs to each recording and release.

Keep verified codes rather than inventing replacements from memory. If a release has already been distributed, matching original materials and identifiers may matter during a catalog transfer. Store matching and preservation of listening history are not guaranteed.

Keep rights evidence usable

Save relevant agreements, sample permissions, beat licences, artwork permissions, and collaborator approvals in an access-controlled location. Link the documents to the correct song or asset. Do not assume that a payment receipt alone establishes every right required to distribute or advertise the work.

If a licence has restrictions on distribution, promotion, monetisation, territory, or duration, record those restrictions where you will see them before submitting. Seek qualified advice if the permission is unclear.

Test the backup instead of assuming it works

Keep another copy in a separate location or service, not just a second folder on the same device. Open a few backed-up files, check the metadata sheet, and verify that important documents are readable.

Protect access with strong unique passwords and available multi-factor authentication. Share only what a collaborator needs, and review access when the project ends. Do not put private identity or financial documents into a public press folder.

What should I keep after the release is live?

Retain the approved master, delivered artwork, final metadata, permissions, release codes, and a record of the delivered release. Keep an untouched copy before making corrections.

Use separate exports for social clips and publicity. The short-form content plan can help you organise those assets, while the press-kit checklist explains what is safe and useful to share publicly.