Small Recording Studio File Naming: A Proposed Handoff for Alternate Mixes and Approval

A client says the one with the louder vocal is approved. The studio has four files with similar names. Which one did they mean? This article proposes a file naming and approval handoff for alternate mixes. It is an optional example convention, which a studio can adapt, not a rule for every studio.

Principle: the name carries the decision

A file name should tell a stranger what song, which mix, which version and what its status is, without opening the file. Keep it short, readable and free of spaces and special characters if the studio wants the name to survive being sent around.

A proposed pattern

Project-Song-MixType-vNN-Status-YYYYMMDD

For example: HarborLights-Tidewater-Main-v03-ForReview-20261014

Fields:

Project and song: stable short names agreed at the start.
MixType: for instance Main, Instrumental, VocalUp, VocalDown, Radio. The studio defines its own list and keeps it short.
vNN: a two digit version number that only increases within that mix type.
Status: Draft, ForReview, Approved or Superseded.
Date: the date the file was exported.

Status should not be edited in the name after sending. Instead, an approval creates a new file name, described below.

Handoff steps

Export each alternate mix with its own name. Never overwrite an earlier version.
Send the client a short list: file names, one line on each difference, such as vocal raised relative to the main mix.
Ask the client to reply naming the exact file they approve, copying the file name from the list.
On approval, create the approved copy with Status set to Approved and the same version number, and keep the reviewed file unchanged.
Rename earlier versions of the same mix type to Superseded only if the studio wants to; otherwise keep a simple log.
Record the approval in a log with date, file name and who approved it.

Decision branches

Client names a file exactly: copy it to the approved name and log.
Client describes a file loosely, such as the louder one: do not guess. Reply with the two or three candidate names and ask which.
Client wants a change plus approval, such as approved if the guitar is lowered: treat as not approved. Make v04, send it again, and wait for a clear reply.
Client approves two mix types: approve each separately, with its own log line.

Stop conditions

Stop if two exported files share a name. Stop if the client's approval message names a file that is not in your log. Stop if the date or version in the name does not match your export record; resolve before sending anything further.

Example

Proposed example: the studio sends Main-v03 and VocalUp-v01. The client replies, we approve Main v03, VocalUp needs more work. The studio creates HarborLights-Tidewater-Main-v03-Approved-20261016, keeps the reviewed file as it was, and logs the approval. VocalUp stays at ForReview until the client replies again. Later the client says the louder vocal one is fine, which is ambiguous only if more than one candidate exists; here the studio replies naming VocalUp-v01 and waits for a direct confirmation.

Why the studio should avoid editing status in place

Changing a status inside an old file name makes it hard to tell what the client actually saw. A new copy with a new name keeps the reviewed file as evidence of what was sent.

Practical acceptance test

Create five dummy exports: two versions of Main, one VocalUp, one Instrumental and one with a deliberate duplicate name. Ask a colleague to run the handoff using only this article.

Pass if:

The duplicate name is caught before sending.
A simulated vague approval triggers a clarification message, not an approval copy.
The log lists one approval with the exact file name.
A third person can find the approved file from the log within a minute.

If any step fails, adjust the pattern or the list of mix types and repeat.

Conclusion

Clear names and a clear approval message remove most arguments about which mix was agreed. Treat the pattern as a starting point, adapt the fields, and keep the rule that approval always names an exact file.