How a small label keeps its catalogue straight

Placeholder. This article was written to prove the publishing pipeline end to end — the page, the index, the structured data and the sitemap entry are all real. Replace this file with the first piece you actually want to publish, or delete it.

An independent label is mostly an administrative object. The music is the part everyone sees; the catalogue is the part that decides whether anyone gets paid for it. Most of the work sits between those two facts.

A release is not one thing

A single release is at least three separate assets, each registered somewhere different and each capable of going missing on its own.

• The master — the recording itself, delivered to a distributor and from there to the streaming services.
• The composition — the underlying song, which belongs to whoever wrote it and is collected by a performing rights organisation.
• The metadata — the identifiers that let the first two find each other. An ISRC on the recording, an ISWC on the work, a UPC on the package.

Skip the third and the first two never reconcile. The money is generated, but nothing connects it to the person owed it.

Where the gap opens

The delay between a release and its royalties is not usually a dispute. It is a registration that was never made, or was made twice, or was made against a slightly different spelling of a name.

Catching that is unglamorous and entirely mechanical. It is also the single highest-leverage thing a small catalogue can do, because the alternative is discovering the problem years later, when the statements arrive and the numbers are smaller than they should be.

What this looks like in practice

Keep one record per work. Make it the record — not a spreadsheet that shadows a different spreadsheet. Register early rather than at the point the first statement is due. And write down the decisions, because the reason a split was agreed at 60/40 is obvious for about a month and opaque forever after.

None of this is difficult. It is only easy to postpone.