How to Build a Track Title-and-Version Style Guide Before Release

A title-and-version style guide keeps one song from arriving under six slightly different names. It defines the approved main title, the exact language for each real recording version, the artist spelling and order, and the person who can authorize a change. Build it before distribution, radio outreach, mastering delivery, and live playback packages begin.

The guide is not a place to manufacture extra versions for search visibility. Every label should identify a genuine audible or production difference. If two files are identical, fix the duplicate instead of giving it a new subtitle.

Lock the main title first

Write the main title exactly as the artist wants it displayed: capitalization, punctuation, spacing, abbreviations, and any intentional stylization. Compare it with the approved artwork, composition records, master metadata, release announcement, and distribution entry. Record who approved that form and when.

Keep artist names and roles in their own fields. Spotify's current metadata guidance tells suppliers to list contributing artists separately, keep artist-name formatting consistent, and avoid putting artist names into track or release titles. A featured artist belongs in the appropriate artist credit, not inside a homemade title string.

Separate title from version information

Create two columns: main title and version title. DDEX guidance explains that reference metadata treats the title and version title separately so each delivery channel can format them appropriately. Its ERN guidance places version information such as a remix or instrumental in a subtitle field when the supplying system supports that structure.

Use a version label only when it helps distinguish the actual recording: Radio Edit, Instrumental, Live at a named event, Extended Mix, or another approved description. Do not use “album version” and “single version” when the audio does not differ. DDEX also advises that featured artists and deal terms do not belong in the version subtitle.

Treat clean and explicit status as metadata

Do not type “explicit” into the main title simply to make the status visible. Spotify says explicit tracks should be marked through the explicit-content metadata rather than by adding an E or the word to the title. DDEX similarly separates audience-advice metadata from the version title.

A clean edit may still be a genuinely different recording that your team needs to distinguish in its internal files. Record both facts: the approved version label used in delivery and the content-advisory field required by the distributor. Never assume a filename alone will set platform metadata correctly.

Create a version ledger

Give every deliverable one row with: internal version ID, main title, version title, explicit-status field, duration, mix or master date, ISRC when assigned, intended use, filename, and approval state. Add a checksum or file size if the team regularly exchanges masters and needs another identity check.

Keep “working,” “review,” and “approved” states separate. A file called final-final should not outrank a signed approval record. When a new master replaces an earlier one, preserve the retired row and mark why it changed instead of deleting the history.

Set a filename pattern that supports the metadata

Internal filenames can carry practical detail that public titles should not. Choose one pattern such as artist, main title, version, master date, and revision. Avoid slashes, mystery abbreviations, and names that become identical when a cloud service removes punctuation.

Test the pattern with the longest title and every planned export. The full mix, clean edit, instrumental, performance backing track, and mastered release file should remain distinguishable when they sit in one folder or appear on a phone screen.

Connect live versions to the show plan

A performance file needs the same approved song identity plus a precise live-use label. If the DJ intro is shorter, the lead vocal is reduced, or the ending has been changed, document that difference. The IHHR rap-show changeover plan shows how to connect playback filenames, cues, and stage responsibilities without confusing a show file with the release master.

Run a channel-by-channel preflight

1. Compare the distributor entry with the approved title ledger.
2. Check artist order and roles at both track and release level.
3. Confirm version labels describe real differences.
4. Verify explicit-content fields separately from titles.
5. Open every delivered audio file and confirm duration and content.
6. Check artwork, one-sheet, radio email, and public links for the same approved spelling.

For an approved clean edit or release campaign, the sponsored IHHR Radio Promotion page explains available package scope without promising rankings, streams, royalties, sales, or listener totals. Submit only the version you intend the station to review, and keep the release master, clean edit, and performance files clearly separated.

A strong style guide is deliberately boring: one source of truth, one owner, and no guessing. Archive it with the final masters and distribution receipt so future remixes, reissues, edits, and live versions inherit the correct identity instead of repeating an old typo.

References: DDEX, Differentiating versions using SubTitle; DDEX, Titles and subtitles in ERN-4; Spotify for Artists, Music metadata guidelines. Checked November 11, 2026.