01
Two layers, never one record
Every song in the catalogue is two things, and they are stored separately. The Work is what was written — words and music. The Recording is one performance of it, captured and mixed. One Work can carry dozens of Recordings; a Recording belongs to exactly one Work.
The split matters because rights attach to different layers. Publishing income arrives against the Work. Master, neighbouring-right and video-out income arrives against the Recording. Registering a performance against the composition — or the reverse — is how a catalogue ends up with income that cannot be paid to anyone.
Work
- · The composition — words and music
- · Holds ISWC and APRA GW#
- · Writers, shares, publisher
- · Sync rights attach here
- · One record, however many titles
Recording
- · One performance, captured and mixed
- · Holds the ISRC
- · Performers, studio, capture
- · Master and video-out rights attach here
- · Many per Work — each its own code
02
Five identifiers, and what each one marks
| Code | Attaches to | What it means |
|---|---|---|
| ISWC International Standard Musical Work Code | The Work — the composition as written | Never sits on a recording. One per composition, for its life. |
| GW# APRA AMCOS work registration number | The Work | The Work’s second key. Royalty statement lines are quoted against it, so an unmatched GW# means unmatched income. |
| ISRC International Standard Recording Code | The Recording — one specific performance, mix and capture | Reserved at the recording’s creation, so every avenue is open immediately. A version inside a recording’s stack never gets one of its own. |
| UPC Universal Product Code | One format edition of a release | Changes per format — digital, streaming, vinyl, CD. The ISRCs inside it do not. |
| IPI Interested Party Information number | A writer or publisher — a party, not a song | Follows the person or company across every work they appear on. |
// A release stores none of these of its own. Its ISRCs are read from its manifest, which points at Recordings.
03
Re-recording, arrangement, cover
When a song is recorded again, the question is never “does it sound different”. It is: did the person who made this add something protectable?
| What happened | Call it | APRA / composition | ISRC |
|---|---|---|---|
| Same song, different session, band or project — arrangement unchanged | Re-recording | Nothing new. Same Work, same GW#. | New one — it is its own master. |
| Same song, but the arrangement adds protectable material — new melody, harmony, structure or lyrics, or a credited arranger’s contribution | Arrangement | A new work with its own GW# and ISWC. The arranger joins the writers. The original registration stays live and separate. | New one. |
| An RFI-controlled song performed by a different RFI act | Cover recording | Nothing new. RFI already controls the composition — new master only. | New one. |
| A third-party song performed by an RFI act | Cover of a cover-type Work | Nothing to register — the owner already has it. A mechanical licence is needed before the master can be distributed. | New one. |
The test
Protectable new material, not audible difference. A metal version or a string-quartet reading that keeps the same melody, harmony and lyrics is a re-recording — one Work, two masters. A re-harmonised, restructured rewrite is a new registration.
The trap
“Cover” describes two unrelated things. Applied to a composition it means RFI does not own the song, so a mechanical licence applies. Applied to a performance it only means somebody else performed it. A Jason Freddi song covered by another RFI artist is a cover recording of an original, RFI-controlled Work — if the Work is retyped as a cover, the writer loses their own share and the release gets blocked behind a licence that was never needed.
04
A version, or a new recording
A recording’s stack holds iterations of one performance. The moment the performance itself changes, it is a different recording and needs its own code.
// Two studio masters of the same song, from two different sessions, are both correct and both stay — they are two recordings, not a duplicate to be merged.
05
Three words that kept meaning the same thing
“Collaborator” used to mean an artist type, a project role and a rights relationship at once — so a question like “who is credited here” had three answers and no way to tell them apart. Each of the three now has exactly one job.
Artist.type
Whose label is this act on. rfi — signed, RFI controls the masters. external — a third party: a guest, a licensor, the act being covered. discovery — a prospect. A question about the relationship to the label, never about contribution.
ProjectRole
What someone did on one project. Co-writer, session performer, producer, engineer — the specific values that decide which agreement is generated — or a bare collaborator when it fits none of them. Per project, so the same person carries different roles on different records.
Collaboration
The rights relationship on a track: which rights the contributor holds, whether they route through RFI or an external publisher, and which agreement governs them. A contract-layer record — what the deal is, not what the person is or what they did.
Who is this person
Every one of those roles points at a registry record, not at a name. One person, one record — and a duplicate registry record is merged away with its code kept, archived rather than deleted.
Where a cover starts
A covered composition names its original writers and its publisher as references — writers to registry people, the publisher to a registry organisation. That organisation is the party a mechanical licence is obtained from, so the clearance step reads a record instead of re-finding a string.
06
Glossary
- Accession
- Taking a recording, work or asset into RFI holdings. Intake happens at the moment of transfer, and the internal registry code is assigned then.
- Arrangement
- A version of a song that adds protectable material — new melody, harmony, structure, lyrics, or a credited arranger’s contribution. A derivative Work, and separately registrable.
- Catalogue tier
- Live = current RFI holdings. Legacy = the inherited CD Baby catalogue, read-only. Tier is per record: a live recording can sit under a legacy Work.
- Cover
- Two different things depending on the layer. On a composition, a cover-type Work is one RFI does not own, so a mechanical licence applies. On a performance, a cover is simply another act performing it.
- Designated master
- The one version in a recording’s stack approved for distribution. Not a separate recording, and not a separate ISRC.
- Edition
- One delivery format of a release — digital download, streaming, vinyl, CD. Each has its own UPC and its own release date, and all share the same manifest, so all share the same ISRCs.
- Master
- The finished, distributable recording. Also used loosely for the file itself, which is why RFI names a designated master version instead.
- Mechanical licence
- The clearance to manufacture and distribute recordings of someone else’s composition. Distribution is blocked until it is obtained.
- Recording
- One specific performance, captured and mixed. The sole holder of an ISRC. Audio master, music video, remix, instrumental, radio edit.
- Re-recording
- A new master of a song that already exists — different players, room or era, arrangement unchanged. No new composition.
- Release group
- The logical release a set of editions belongs to: a single, its remix package and its vinyl pressing are one group, three editions.
- Sync licence
- Permission to place a work and a recording in timed relation with picture. Sync rights attach to the Work; master-use and video-out rights attach to the Recording.
- Version
- An iteration inside one recording’s stack — demo, rough mix, mix, master, remaster, alternate take. Never carries its own ISRC; it shares the parent recording’s code.
- Work
- The composition — what was written. One Work may carry many alternate titles but is only ever one record. The sole holder of an ISWC and an APRA GW#.
- External artist
- An act that is not signed to RFI — a guest, a licensor, the act whose song is being covered. It is a value of Artist.type, held on the artist record, with the Organisation its rights route through named beside it.
- Project role
- What a person did on one project: co-writer, session performer, producer, engineer, or a plain collaborator when it fits none of those. Roles are per project and never describe who someone is — the same person can hold a different role on the next record.
- Collaboration
- The rights relationship between an RFI act and a contributing party on a track: what rights they hold, where those rights route, and which agreement governs them. Not a role, and not a type of artist.
- Registry merge
- Folding a duplicate identity into a survivor. Every credit, role and clearance is re-pointed; the duplicate is archived rather than deleted, because a registry code is permanent and may already sit on a registration.
- Submitter identity
- A song submission arrives with a name and an email only. When the team takes it up, the submitter is linked to a registry Person — and promoted into a discovery Artist if they are being pursued.
Reference maintained with the catalogue · For corrections or enquiries: licensing@rfirecords.com.au