Spanish Point has appointed former Kobalt executive Simon Dennett as chief product officer. For an independent label, the useful question raised by a product role is close to home: who decides the rules that staff follow when a recording changes, and who checks that the release workflow applies them?
Product work starts with a decision
A dashboard can present fields, buttons and approval steps. It cannot decide by itself whether a cleaned-up master is the same recording as the one already in a catalogue. Someone must define that rule before a product team can turn it into a useful prompt or control. The same applies inside a label, even when the label uses a distributor’s system rather than building its own.
A label can offer mastering inside its release dashboard while still needing a separate decision about who may deliver the recording and receive its royalties. Those are different questions. The mastering step concerns the audio being prepared. Delivery authority concerns who may send it onward. The royalty decision concerns who should receive the resulting income. Putting the steps on one screen does not give one employee authority to settle all three.
That is the work an internal release operations owner needs to do: write down the decision each step requires, identify the person who can make it, and make sure the answer reaches the next person in the workflow. A product executive’s appointment makes the function visible at company level. For a label, the immediate application is a clear rule that staff can use on the next release.
A version rule has a financial consequence
The international standard recording code (ISRC) provides a concrete test. An unchanged master and a simple technical cleanup retain the existing ISRC; an expurgated version, a remix and a new interpretation require a new one. The release date does not reset the recording’s identity. That means a label needs to classify the audio change before it fills in the code field.
If the person preparing a release treats every new upload as a new recording, a technical cleanup can acquire an unnecessary new identifier. If that person treats every file with the same title as the same recording, a distinct version can inherit an identifier it should not use. In either case, the operational mistake begins before delivery. The remedy is to give one role responsibility for the version decision and require the person entering the data to use that decision.
A short version policy can cover the cases that recur:
- Unchanged audio or simple technical cleanup: check the existing recording record and retain its ISRC. The code follows the recording rather than the release date.
- Expurgated version, remix or new interpretation: create the distinct recording record and assign a new ISRC. These changes require a new code.
- Any file ready for delivery: confirm who has authority to send it and who should receive its royalties. Rights work passes between licensing, repertoire and release operations.
This is a staffing decision as much as a metadata decision. The label needs a named person who can classify the change, another clear approval point for delivery and a route for resolving disagreement before the recording moves.
Company charts change the handoffs
Warner Music Group bought Zebralution Music from Bookwire and kept the distributor’s co-managing directors in place. Nebula17 expanded its US team while signing a global distribution deal with The Orchard. An acquisition and a team expansion change which companies and employees participate in release work. They do not, on their own, tell a label which individual will answer a version question or approve a royalty recipient.
The practical response is to ask for the decision path at the point where a label’s staff meet the distributor’s staff. Who resolves a disputed recording identifier? Who can correct a delivery instruction? Who confirms the royalty recipient when the release record and the rights record disagree? Identifying a recording, authorising delivery and naming the royalty recipient are separate handoffs. Each needs an owner who can give an answer that the next team will use.
That path should be checked when an account changes hands or a new team joins the work. A familiar company name or a retained senior executive does not tell the release coordinator where to send a specific correction. The coordinator needs the responsible role and the point at which its approval enters the release process.
Give the role a measurable job
An independent label can test its workflow with one recording that has both an earlier master and a changed version. Ask the release operations owner to identify which file keeps the existing ISRC, which needs a new one, who approves delivery and who confirms the royalty recipient. If the answers depend on separate people, record the order in which each decision must arrive.
Then use the same sequence for the next release. The useful output is a completed recording decision that the delivery team can act on, not merely a filled dashboard field. Spotify’s spam filter rollout has also put playlist discovery under scrutiny, with independent teams needing to connect changes in reach to listening and rights income. That measurement depends on staff being able to follow the recording and its rights through the workflow. The first job is to assign the decisions that make that trail reliable.
