Give Each Release Version a Job Before Delivery

A new release version can change the recording identifier, the campaign plan and the rights price. Decide which of those changes applies before delivery.
ISRC for Remasters: Keep the Code, Give Clean Edits a New One ISRC for Remasters: Keep the Code, Give Clean Edits a New One

An unchanged master keeps its International Standard Recording Code (ISRC), while a clean edit needs a new one. That distinction belongs at the start of a release plan: the team needs to know which recording it is delivering before it assigns campaign work to each version.

Decide what the audio change created

Start with the recording, rather than the date on the delivery schedule. The International Federation of the Phonographic Industry (IFPI) says an unchanged master and ordinary technical cleanup retain the existing ISRC; clean edits, remixes and new performances require new codes. A remastering task therefore needs an audio decision before it becomes a metadata task. Ask what changed in the recording, record that decision, and give the delivery team the corresponding code.

This matters when several versions share a campaign. A clean edit can serve a different use from the original, but its new ISRC identifies it as a separate recording. Ordinary cleanup keeps the existing recording identity. If a label treats every updated file as a new recording, it changes the identifier where IFPI’s rule calls for continuity. If it sends a clean edit under the original code, it loses the distinction the rule requires. Both errors begin before a store displays the release.

Make the version decision a handoff with a named owner. A release dashboard can make a task easy to complete without deciding whether the underlying rights and recording data are correct. The useful field is the approved answer: unchanged master, technical cleanup, clean edit, remix or new performance, followed by the ISRC that answer requires. The person approving it should understand the audio change, rather than simply marking delivery complete.

Assign a purpose to each campaign asset

Once the recordings are identified, decide what each asset is meant to achieve. A clean edit may have a delivery purpose. A video or a social post may give listeners another route to the recording. A store programme may give a release placement. Those are separate jobs, so write down the intended audience action for each one before spending time on it.

Apple Music’s Up Next programme can provide a release with a placement, but the placement alone cannot show its effect on listening. Treat placement as an event to measure, rather than the result itself. Record when support begins, then inspect the listening measures available to the team for the relevant recording. That gives the label a basis for deciding whether similar placement deserves effort on the next release.

A video can open another campaign window after the initial release. Separate video and music rankings do not establish that attention on one caused movement on the other. The practical response is to set the window and its measure in advance. If the aim is renewed listening, examine listening during that window. If the aim is discovery, use a discovery measure. The release plan should say which result would justify repeating the activity.

The same discipline applies to social use. A recording’s reach in a social post neither prices the music use nor shows whether the campaign worked. Agree on the rights terms for the use and choose an audience measure before the post goes live. Keep those two records separate: one governs permission and payment for the recording, while the other evaluates the campaign.

Measure what happens after attention

A first burst of attention is only one part of a release window. Older tracks account for much of Korea’s top-400 digital usage, and search and saves can show how listeners find and keep a song. That makes retention a useful planning question for a new recording too. Can listeners find the intended version later, and do they save it when they do? Put those questions beside any placement or social target.

Use a short decision sheet for each version:

Carry the decision through the rights records

The campaign sheet should also identify who follows the recording into the rights workflow. Master registration, work registration and statement review are separate jobs. A correct ISRC settles the recording identity decision; it does not complete every claim attached to the music. Give each job an owner and connect the delivered version to the records those owners review.

That sequence gives an independent label a workable rule for this week’s delivery: classify the audio first, approve its ISRC, assign each asset one campaign purpose, and name the measure before placement or posting begins. Then carry the approved version into registration and statement review. The team can evaluate the campaign against listener behaviour while keeping the recording and its rights records aligned.

Previous Post
Malaysia Master Royalties: PPM Needs a Mandate and Recording Registration

A Buy Button and a Royalty Claim Require Different Checks

Next Post
Philippine Song Royalties: FILSCAP’s Three Claim Deadlines

Philippine Song Royalties: FILSCAP's Three Claim Deadlines