Signed Agreements, Ownership Records and Exports
By John Cleary and David Slitzky Last updated
Who this is for
You have signed agreements and want to know where they live, what keysig builds from them, and how to get the data out.
Where signed PDFs live
Every signed agreement keeps its PDF, the one the service produced with the signatures and signing record. Open the agreement and choose Download signed PDF. The Signed section on your dashboard and on Agreements lists them. Other with a keysig account see the same agreement under Shared with you and can download the same PDF. The e-signature service also emailed the completed PDF to everyone when the last signature landed. Downloading a signed agreement never costs a credit.
Ownership records
Some agreements state who owns what share of a song or a recording. From those, keysig derives a record for each track, each , and each side of the :
- Composition (the song): and songwriter agreements.
- Master (the recording): producer agreements (), agreements (the ) and agreements (the player, with no percentage, because the deal is a flat fee).
- A adds a record only when it grants a share of the composition.
- Management agreements, , , agreements, video releases, live performance agreements and invoices produce no records.
Records come from the agreement's answers, not from anything you type separately, and the agreement is always the source of truth. A record from a draft or a pending agreement is marked as coming from a draft, not signed yet. A record from an agreement signed through keysig is settled; one recorded as signed on paper stays provisional, because keysig collected no signatures for it. If the agreement's text was edited by hand, or does not state a record's name and share where the template puts them, that record is marked unverified, so you know to check it against the signed copy. Records need the agreement to be linked to a track; an unlinked agreement has nowhere to put them.
Master vs. composition explains the difference between the two sides.
Exporting
- Per track. Each track's page has an ownership panel with Export : a .zip holding a CSV of that track's records and a plain-language data dictionary.
- Everything. On Account, Export ownership data gives you one .zip with a CSV of every record across your tracks, one row per track, party and side, with a plain-language data dictionary and a column saying whether each row comes from a signed, pending or draft agreement. It is free, and it is built to hand to a royalty or system.
- Your whole account. Export my data, on the same page, downloads your agreements, profile, tracks and who worked on them, projects and collaborators as one JSON file.
What happens next: the file downloads to your device straight away. Nothing is emailed, nothing changes in your account, and no credit is used.
Tracks: the catalog view
Tracks opens on every recording you have added, newest first; Sort puts them A to Z instead, and keysig remembers which on that device. The list shows twenty-five at a time, with Show more for the next twenty-five. Projects group them, one per release. New project starts one; a track moves onto a project when you drag it there, or choose Select, check the tracks and pick the project from Put them on, and Undo puts a move back. All tracks, like each project, opens to list its first ten tracks, and "more" opens the rest right there, with Show fewer to fold them back; choosing a project or No project narrows the table, and All tracks shows everything again. Hide projects puts the project list away until Show projects brings it back, and keysig remembers which you chose on that device. Projects, at the foot of that list, turns the table into your projects: each with how many tracks it holds, how many are released and who worked on them, opening right there to its first twenty-five tracks, several at once; Show in the track list goes back to the tracks narrowed to that project, Tracks switches back, and keysig remembers which you chose on that device. Beside each track, Collaborators lists who worked on it, the people you added and the people its agreements name, each with a small square for whether their agreement is signed, out for signature, drafted or not started. Each track in the list opens in place, as many at once as you like: first who worked on it, each with the agreement their role calls for, where Not started starts it with them already on it and Draft, Pending or Signed opens it, with Add a collaborator, then its title, artist and whether it is released, which Save changes keeps. More on the track page, or the track's title, opens its own page for everything else. Deleting a project keeps its tracks: they move to No project.
Add or import tracks has three ways in. Add a track takes one track at a time: its title, the artist, whether it is released, and a project, or none; choosing New project there moves what you typed to Add a project. Add a project takes the project's name, the artist and whether it is released, then the titles of its tracks, one to a row; a name you already have adds the tracks to that project. The and the rest go on each track's own page. Look up releases finds your on Deezer by your artist name, and skips a track whose ISRC is already in keysig. The catalog audit does the search for a whole catalog at once and asks, track by track, who worked on it. When you finish, it brings you back here showing just the tracks it audited, until Show all tracks, and the people it found credited on each, in the roles you kept, are already its collaborators. Tracks Look up releases and the audit bring in are marked released and, when there is a release name, filed under a project of that name, made for them if you do not have one.
Each track also has its own page. Collaborators lists who worked on it: the people you add, each with what they did (co-writer, producer, featured artist, session musician, owns a , in the video, or something else), and the people its agreements already name, in the role they sign as. Beside each role is the agreement it calls for and how far it got: Signed, Pending, Draft or Not started. Start opens that agreement with them already on it and you on the other side, and co-writers go on one split sheet together, up to seven besides you; Open goes to a draft or a pending one. A role an audit recorded with nobody on it shows as Not known yet until you add them, or until its × takes it off because nobody held it after all, and Just me says nobody else worked on it. When Credits.fm has credits for the recording, from a catalog audit or from Check Credits.fm on a track with an ISRC, the people credited who are not on the track yet are listed under it: Add starts the collaborator form from them for you to confirm, and Not on this one stops offering them on that track. A credit is not an agreement, and independent releases are often missing some. Someone you add is saved to your collaborators, whose page lists the tracks they are on; removing them from your collaborators takes them off those tracks.
Under the track's title, one line says who the artist is, where the release stands and which project it is on. Edit details holds everything else about it: its project, whether it is released and when, its ISRC and , label, and distributor; a released track can also pull its details from Deezer. Other agreements lists the paper no collaborator's row already shows, like a sync license or an NDA, with Other agreement for this track to start one, and the ownership panel sits below.
Collaborators
Collaborators is your address book, each person with how many of your agreements name them and where the agreements their roles call for stand: how many are not started, drafts, pending and signed. No email on file marks anyone keysig cannot send anything to yet. Find a collaborator searches names, emails, companies and , and when you type the number, and Show narrows the list to the people with an agreement not started, the ones waiting on their signature, the ones with no email on file, or the writers missing a PRO or IPI, or the possible duplicates. The list shows twenty-five at a time, with Show more for the rest. Their saved details, including PRO and IPI where you have them, fill into a form with one tap when you name them on a new agreement.
Each collaborator's page says where you stand with them. When an agreement with them would need something that is not on file, the page says so first: an email, without which nothing can be sent to them, and for someone who writes with you, the PRO and IPI split sheets ask for. Add an email, or the button naming the PRO or IPI that is missing, opens their details on that field. If the same person is on file twice, say once from a catalog audit with an IPI and once with an email, the page lists the other entry under Also on file with Merge into this one: the other entry's tracks move here (on a track both are on, its roles join this one's), it fills in what this one lacks, this one's details stand where both have something, and the other entry is removed; agreements do not change. Two entries with different emails, or with different IPIs, are never offered, because keysig treats them as two people. Out for signature lists every request they have not signed yet and whose turn it is: signing runs in order, and each signer is emailed when their turn comes, so Remind appears only on their turn, once the request has been out more than two days, and at most once every 24 hours. Tracks lists each track they worked on, or that an agreement with them is on, with their roles and the agreement each role calls for: Signed, Pending, Draft or Not started, where Start opens it with them already on it and Open goes to a draft or a pending one, and the tracks with something still to do come first. Agreements lists every agreement that names them. New agreement opens the templates with them carried: whichever you pick opens with them on the other party's line and you on your usual side, which you can still change on The Parties where the template has two seats.
If something goes wrong: if a signed agreement's records look wrong, check the agreement's answers first, since the records are derived from them; then see Troubleshooting.
Related guides
About the authors
John Cleary Co-Founder, keysig
A classically trained musician and producer who spent 15 years building A&R, sync, and music strategy for labels and brands like Atlantic Records, Audiomack, and Epidemic Sound.
David Slitzky Co-Founder, keysig
GRAMMY-nominated audio engineer who spent over a decade in the studio with artists like The Roots, Usher, and Travis Scott before spending eight years running music strategy and A&R at Epidemic Sound.
keysig is not a law firm and this is not legal advice. This guide explains how the keysig product works. It does not tell you what your agreement should say. Have agreements reviewed by qualified counsel before signing.