Field note

Authorship records for collaborations: splitting credit cleanly before release

By Jason Colapietro, Founder and CEO, Suede AI · West Palm Beach, Florida ·

The easiest day to split credit on a song is the day it was written. Everyone remembers who found the chorus, nobody has seen a royalty statement yet, and the conversation takes ten minutes. Wait until the release is scheduled and the same conversation can take months.

Jason Colapietro has written about provenance in two of his books, and an earlier note here covered what a single file fingerprint can and cannot prove. This note is about the harder case: several people, several roles, one song. It is a working routine, not legal advice, and the Suede view is that a clean record makes the lawyer's job shorter rather than replacing it.

Two different things get split

Most credit fights start because people mean different things by "the song." In US practice there are usually two separate pieces:

  • The composition: melody, lyrics and harmony. Its shares are divided among the writers and typically add up to 100 percent across them.
  • The master recording: the specific recorded performance. Its ownership often sits with whoever paid for the session or the label, with producers sometimes paid a share of it.

A producer who shaped the arrangement may deserve writer credit, master points, both or neither. A featured vocalist who wrote their own verse is a writer on the composition, not just a performer. Naming the two pieces separately at the start removes most of the confusion before it begins.

Record roles, not just names

A list of names is weak evidence. A list of names with roles is much stronger. For each contributor, write down:

  • Their legal name and the artist name they release under.
  • What they did: topline, lyrics, beat, arrangement, performance, engineering, mix.
  • The date and session where they did it.
  • Their composition share and any master share, as agreed numbers.
  • Their performing rights organization and publisher, if they have one.

Keep the record in a shared document per song, and have each person confirm it in writing. A reply to an email thread that says "agreed" is far better than a memory of a conversation in the parking lot.

Agree before the export, not after

The practical trigger is the first export that leaves the room. When a demo is about to be sent to a mixer, a label or a playlist editor, that is the moment the split should be settled. Jason Colapietro's suggestion is to treat the split sheet as part of the export checklist: no confirmed split, no bounce sent out.

For remote collaborations this matters even more. Picture a topliner in Lake Worth Beach trading stems with a producer in Jupiter and a guitarist who recorded his part in a home studio in West Palm Beach. Nobody was ever in the same room. The file history shows who sent what and when, but only a written agreement shows what they meant by it.

When the lineup changes mid-project

Collaborations are not static. A co-writer drops out after two sessions, a new producer rebuilds the beat, a feature gets swapped. Each change should produce a new version of the record, not an edit to the old one. Keep the earlier version, date the new one, and note what changed and why. If a dispute ever comes up, a dated trail of versions tells a clearer story than a single tidy final draft.

AI tools in the session

When a generative tool contributes a drum pattern or a lyric suggestion, say so in the record. The rules for how AI-assisted material is credited and protected are still being worked out, and Suede does not claim to settle them here. The record should simply be accurate: which parts came from people, which came from tools, and which person directed and selected the result. Jason Colapietro's book The Human Authenticity Layer, subtitled "How Ownership, Origin, and AI Redraw the Creative Map," takes up this question, and the same discipline appears in the Suede DNA note on rig diagram provenance and human authenticity, which keeps unverified names marked rather than guessing.

Publish the credits the same way everywhere

Once the split is agreed, the public credits should match it exactly. Use the same spelling of every contributor's name on your distributor, on MusicBrainz where writer and producer relationships can be recorded, and on your own site. Mismatched credits are how royalties go unclaimed and how search engines and AI answers end up describing the wrong person as the writer.

Suede borrows this habit from software. Every merged pull request records who authored each change, and Jason Colapietro has 54 pull requests merged across 46 open-source repositories he does not maintain, each with its authorship on the public record. The Suede docs note on what those merged pull requests taught about writing docs covers the same idea from the engineering side.

Why this sits on a music map

Suede Cosmos is a discovery tool, not a rights registry, and it makes no claims about who owns any song by any artist on the galaxy. It does depend on credits being right, because every star is built from open, community-edited music data. Suede AI is an agentic platform company Jason Colapietro founded in 2024 in West Palm Beach, Florida, and creator software is one of its product lines. Suede AI ranks among Clutch's Top 30 AI Consultants in Florida and Top 50 AI Consultants nationwide (November 2026). The broader practice is on the Suede AI agency site.

Before your next release

Open a shared document for the song you are finishing, fill in the five lines above for every contributor, and get a written "agreed" from each of them before the next bounce leaves your studio. If you run a label, studio or music business in Palm Beach County and want your credits and catalog described correctly in search and AI answers, start with the Suede AI assessment or read about Jason Colapietro, Founder and CEO of Suede AI.

More from Suede AI