Credits and Metadata Sheet
Keep everyone who worked on a release in one place, with roles, ISRCs, ISWCs and writer shares. Export a PDF or... By Music Manager Resource.
Credits and Metadata Sheet is part of the Studio section of Music Manager Resource.
Related
Why credits matter
Credits are how people get found, hired and paid. A producer, engineer or session player without a credit has less proof of their work, and missing or misspelled details can get in the way of royalties. Yet this information is often scattered between emails and group chats, and it gets harder to find the longer you leave it. This sheet keeps it in one place from the day the session ends.
What to collect
For the release, you need the title, the main artist exactly as it will appear, the label, the UPC and the release date. For each track, note the title, the ISRC and the ISWC if there is one. An ISRC identifies a specific recording, while an ISWC identifies the song, so one song can have several recordings. Then list each person, their role, what they played and any identifying number, such as an IPI for a songwriter.
Writer shares
Songwriter shares should be agreed in writing and add up to 100 percent. Enter them here and the sheet warns you if they do not. Those shares only apply to the song. Fees and royalties for producing, mixing or playing on a recording are separate, so do not mix them up with a writing share.
How to use this sheet
Add your release, tracks and people. Export a PDF to share with the team, or download a spreadsheet you can open in Excel or Google Sheets. Different distributors, labels and collecting societies ask for details in their own way, so check what each one needs. Save your work to your account, and export a copy when you finish.
When to fill it in
The best time is on the day of the session, while people are in the room. Ask for full names and how each person wants to be credited, because a stage name and a legal name may be needed in different places. Check spellings with the person themselves. Getting this right before release is far easier than trying to fix it across several services afterwards.