Prepare AI music metadata from a record of what you actually made and who contributed. Treat an ISRC as the identifier for a specific recording, not evidence that you own every right in it. Before uploading, make the final audio, credits, version label, and rights documentation agree.
This AI-assisted worksheet is published by the Galvanized Souls Editorial Desk. It gives an administrative workflow; it does not determine copyright eligibility for an individual song.
Keep identifiers and ownership evidence separate
An ISRC identifies a sound recording or music video recording. It does not identify the underlying composition; IFPI distinguishes it from ISWC for musical works and release-level product identifiers. IFPI's official FAQ explains those differences.
Ownership can change without changing the ISRC. The code does not encode a legal verdict or clearance status. IFPI's ownership guidance explicitly separates recording identity from current rights ownership.
That distinction matters when someone asks, “Is this cleared?” Sending a recording code answers which recording you mean. It does not answer who controls the lyrics, whether a sample was licensed, or which commercial uses the generator permits. Send the appropriate evidence for those separate questions.
Make one master metadata sheet
Use a spreadsheet or a plain document you can export. Avoid letting the distributor form become the only copy of your information. A useful starting structure is:
| Field | What to record |
|---|---|
| Internal track ID | Your stable reference, such as GS-TRACK-001 |
| Public title and version | The exact title listeners should see |
| Artist identity | Display name and existing profile links |
| Contributors | Actual names, agreed roles, and approvals |
| Audio | Final filename, duration, and version date |
| ISRC | Assigned code, assigner, and assignment date |
| Release | Release title, date, artwork, and destination |
| Rights evidence | Location of agreements, receipts, and licenses |
| AI involvement | Tool, relevant dates, and contribution notes |
The internal example is a filing label, not an invented ISRC. Leave an unassigned official identifier blank until the appropriate service or authorized assigner supplies it.
Credit contributions without inventing authorship
Write down who supplied lyrics, sang, played, edited, produced, or mixed the track. Confirm roles with collaborators before delivery. Do not give an uninvolved person a credit to make the release appear more established, and do not use another artist's identity as a discovery tactic.
AI generation and human contribution may coexist in one track. Keep notes specific enough to distinguish them: “wrote verse lyrics,” “recorded guitar,” and “rearranged the final section” explain more than “made with AI.” If a destination requests an AI disclosure, answer the actual question it asks.
For U.S. registration, the Copyright Office's guidance calls for disclosure of more than minimal AI-generated material and identification of the human contribution claimed. Do not turn a metadata credit into a claim that the complete output is protected. Other jurisdictions may use different rules.
Decide whether a changed file is a new recording
Keep a log of changes between versions. A format conversion, a new edit, and a new performance are different events. IFPI says an unchanged recording retains its code, while edits or remixes can require a new one; remastering generally keeps the code unless significant new creative input justifies a different assignment. Consult the FAQ and linked handbook for the specific case.
As an editorial workflow, preserve the original master and name later exports clearly. “Track-final-final-2.wav” creates avoidable confusion. “Track-radio-edit-approved.wav” tells a distributor or collaborator which version you intend, provided it matches the sheet.
Do not reuse an assigned code for a different track to save time. Before changing distributor, gather the existing codes and correct public metadata so you can ask the new service how to preserve recording continuity.
Check the delivered listing against the sheet
When the release appears, compare its title, artist profile, artwork, explicit designation, and playable audio with your record. Listen far enough to identify the correct version; a familiar introduction may not reveal that the wrong ending was uploaded.
Log corrections with the date, destination, requested change, and response. Keep the original record so later collaborators can see what happened. If a platform's form cannot express a contributor role or AI detail clearly, ask that platform how it expects the information before inventing a workaround.
Use the release checklist for the complete delivery process. The rights and policies hub covers permission questions, while the distribution hub connects the practical steps. Good metadata makes your catalogue easier to manage; it works alongside rights evidence rather than replacing it.