The starting point
The quickest way to avoid conflicting names and versions is one master release record that everyone copies from. Separate artistic information, recording identity and the delivery file.
A practice case
The file says final_7; the submission says v6
Practice case: you mixed three versions. The folder contains Night_final.wav, Night_final_2.wav and Night_final_7.wav. The distributor form was filled out two days earlier and the shared link still points to a different mix. This is not an audio problem: there are several competing sources of truth.
First choose the approved render. Record its exact filename, date, duration and a brief change note. Then review the public title, version information and credits in a separate record. A working filename does not have to become the commercial track title.
A record you can use, not just archive
Include the main title, version name where applicable, artists in the intended order, contributors and roles, language, explicit-content indication if relevant, intended date, identifiers already assigned and the approved file. Do not invent identifiers to fill a box. For each uncertain field, record a question and who will resolve it. A blank with a clear pending action is better than an assumption copied everywhere.
A recording and a release are different records
An audio recording and the release containing it are different information levels. An album has a sequence, artwork and release date; each recording has its file and credits. Identifier and file-replacement rules depend on the situation and distributor. This checklist preserves confirmed information and decisions; it does not automatically assign a new code to every mix export.
The final check must include listening
Open the approved file from the delivery folder. Check its beginning, ending, left and right channels, unexpected silence and duration. Read the submission fields against the master record rather than from memory. If another person can review it, ask them to compare those fields and that file; they do not need to reopen the mix discussion. The goal is for delivery to match what was agreed.
Choose a test from what you hear
| You notice | Try this |
|---|---|
| Title and filename disagree | Check whether it is a working name or public version before renaming. |
| Two renders are marked approved | Designate one and record the difference; do not reflexively delete the other. |
| A credit or identifier is missing | Flag it and verify the source before submission. |
Bring it into your session
One pass, with a clear objective
0 / 4
Checks stay on this page and are not sent anywhere.
When to stop
Someone who was not in the session can identify the delivery file, the publication details and any remaining questions.
Quick diagnosis and decision protocol
Check first
- Lock artist spelling and featured-artist format.
- Lock track title and version labels.
- Confirm writer, producer and identifier fields against the rights record.
Then decide
- Export a final metadata snapshot with the master.
- Use controlled values for explicit, version and language fields.
- Correct the source record before correcting downstream copies.
Measurement boundary
Consistency reduces operational errors; distributor-specific requirements still need current verification.
Watch out for this: Editing one storefront manually without fixing the canonical record guarantees the mismatch can return.
Technical references
Documentation for the methods and product behaviour discussed. Practice cases are illustrative examples, not client case studies.
References reviewed:Try it with your own audio
Choose the free tool that fits your task. You do not need to buy a plugin to use the guide.
Open the free tools →