Co-authors: how to prove contributions and shares?
When collaborating, the best evidence combines dated files, version history, exchanges, and a clear agreement on contributions.
First registration free · no bank card required
music co-authors’ rights: key takeaways
When collaborating, the best evidence combines dated files, version history, exchanges, and a clear agreement on contributions. First priority: Keep demos, sessions, exports, lyrics, notes, and messages related to key stages. Next: Link each contribution to a person, a date, and a version, rather than relying on the group’s memory.
Music co-authors’ rights here refers to a concrete process: identifying the correct rights holders, defining the intended use or evidence required, formalising decisions and keeping the elements that will help understand the agreement later. This method avoids vague promises and reduces misunderstandings between artists, producers, labels, publishers, and users.
TuneLockr helps creators organise their files, evidence, and permissions. The tool does not replace a collecting society or personalised legal advice. The information below is educational and should be tailored to the project, territory, and any existing contracts.
Music co-authors’ rights: the four key decisions
Creation history
Keep demos, sessions, exports, lyrics, notes, and messages related to key stages.
Attribution
Link each contribution to a person, a date, and a version, rather than relying on the group’s memory.
Agreement on shares
Discuss percentages while the session is still fresh and formalise them.
Development of the track
A new arrangement, added lyrics, or a part replacement may change the analysis; document these changes.
Implementing music co-authors’ rights, step by step
1. Map out the people and assets
Start by naming the work, the recording, the exact version, and the relevant files. Add the authors, composers, performers, producers, publishers, or relevant representatives. This mapping prevents a decision made about the master from being mistakenly applied to the composition, or vice versa.
2. Describe the requirement using verifiable parameters
Replace general wording with observable parameters: uses, media, territory, duration, exclusivity, volumes, permitted modifications, recipients, and termination conditions. When the project changes, create a new version of the agreement or the record instead of quietly altering the history.
3. Check existing documents
Review contracts, mandates, licences, split sheets, statements, invoices, and relevant exchanges. Prior authorisation, management mandates, or exclusivity may affect your room for manoeuvre. Where important stakes are involved, a professional analysis ensures a reliable interpretation.
4. Keep an accessible record
Archive the final version, attachments, date, identity of the people who validated, and the corresponding files. Use a consistent naming convention and save everything in a location separate from the place of creation.
- Named and dated versions
- Archived intermediate exports
- Identified contributors
- Split validated
- Evidence backed up somewhere other than the primary device
Integrate music co-authors’ rights into the release cycle
Before finalisation
Bring together the relevant people while creative and business decisions are still easy to explain. For "creation history", assign a person in charge and set a validation date. This early step takes less time than searching for documents a few months after release.
Upon delivery
Create a reference folder containing the approved export, metadata, agreements, contact details, and a summary of decisions taken. Do not overwrite old versions: archive them with a clear status. This will allow you to show which file was delivered, when, and under what conditions.
During use
Monitor any divergence between the intended scope and the actual use. A campaign might extend, a video may be re-edited, a partner may change, or a new platform might arise. The aim is not to block all change but to identify when a new approval or extension becomes necessary.
At closure or renewal
Note the definitive end, the files returned or deleted, the amounts paid, and any possible extensions. A brief review creates a reliable record and improves future agreements. For a catalogue, apply the same framework to each title in order to make decisions comparable.
How to assess the quality of the mechanism?
For co-author music rights, a well-organised file is understandable by someone who was not involved in the discussions, traceable thanks to consistent files and dates, proportionate to the value of the use and reversible when the authorisation comes to an end. These criteria are more useful than a stack of unrelated documents.
Test your organisation with a simple scenario: if the project manager is absent, can someone else identify the correct version, know who makes decisions, find the proof and understand what is permitted? If the answer is no, add an index or an overview sheet rather than multiplying the number of folders.
International project: additional checks
International exploitation requires checking territories, languages, intermediaries, and the applicable law. Terms and formalities are not identical everywhere. Therefore, avoid presenting a French model as universal. For significant operations, have the scope confirmed by a professional familiar with the relevant countries and consult the resources of the [organisation].World Intellectual Property Organization.
Example of a properly defined decision
A workable decision answers five questions: who authorises or declares, which file is involved, for what use, for how long and with what compensation or proof. If any of these answers is missing, add it before sharing.
Common mistakes to avoid
- Using a template without adapting it to the actual project.
- Treating the work and the master as a single asset.
- Forgetting a co-author, a producer or a previous licence.
- Granting exclusivity without a defined duration or precise territory.
- Only keep isolated screenshots, without source files or context.
- Present a detection or identifier as absolute proof.
Sources and guidance
To explore further, consult the official resources of INPI. Texts and practices evolve: check the applicable version at the time of your project.
Frequently asked Questions
Is a session file enough?
It can be helpful but is best supported by exports, exchanges, dates, and agreements between participants.
What should you do in case of disagreement?
Avoid making any hasty unilateral statements, gather supporting documents, and seek agreement or appropriate advice.
Can you add a co-author later?
Yes, if the contribution justifies it and if the parties update the relevant documents and declarations.
Practical decision matrix
This matrix turns the topic into checks directly applicable to your project.
| Point to address | Expected decision | Record to keep |
|---|---|---|
| Creation history | Keep demos, sessions, exports, lyrics, notes, and messages related to key stages. | Keep the decision, its date, and the files concerned. |
| Attribution | Link each contribution to a person, a date, and a version, rather than relying on the group’s memory. | Keep the decision, its date, and the files concerned. |
| Agreement on shares | Discuss percentages while the session is still fresh and formalise them. | Keep the decision, its date, and the files concerned. |
| Development of the track | A new arrangement, added lyrics, or a part replacement may change the analysis; document these changes. | Keep the decision, its date, and the files concerned. |
Verified references
- CopyrightFrance · INPI
- Copyright — intellectual propertyInternational · WIPO
- Copyright basicsUnited States · U.S. Copyright Office
- How copyright protects your workUnited Kingdom · UK IPO
Links checked on 20 September 2026. The applicable rules depend on the territory and situation.
Verification and history
- Addition of the essential answer, the practical matrix, international sources and the contextual links.