A clear composer collaboration agreement can prevent confusion long before a cue, soundtrack, or concert reaches an audience. Use this reusable checklist to align on credits, ownership, publishing, deadlines, revisions, payment, recording rights, performance use, and dispute handling before work begins.
Overview
Collaborations often start informally: a filmmaker sends a brief, a game developer shares a build, or two composers exchange ideas in a composer community. That ease can be valuable, but a friendly working relationship is not a substitute for written expectations. A short agreement gives everyone the same reference point when the scope changes, a deadline moves, or a successful piece gains new uses.
A composer collaboration agreement does not need to be unnecessarily complicated. It should explain who is doing what, who owns or controls the resulting music, how contributors are credited, and what happens if the project pauses or expands. The exact language depends on the project, location, participants, and applicable law, so treat this checklist as a planning tool rather than legal advice. For higher-value or rights-sensitive work, have an appropriate legal professional review the agreement.
Before drafting, gather the project basics:
- Working title, client or commissioning party, and the names of all collaborators.
- Format and purpose, such as a short film, game, live performance, album, trailer, or installation.
- Expected deliverables, file formats, approximate duration, and delivery dates.
- Known distribution channels and intended uses.
- Decision-maker or approval process.
If you are developing your network first, resources on finding collaboration opportunities for composers online and locally can help you identify projects worth discussing. Once a project becomes specific, move the important terms from messages into a shared written document.
Checklist by scenario
The same core questions apply across projects, but the emphasis changes by scenario. Use the table below as a first-pass discussion guide.
| Scenario | Prioritize | Questions to answer |
|---|---|---|
| Film or television scoring | Credits, ownership, revisions, delivery, and screen use | Who is the lead composer? Are contributors credited as co-composers, additional music, orchestrators, or another role? Who approves cues, and how many revision rounds are included? |
| Game scoring | Interactive implementation, updates, and ongoing use | Will music be edited or layered in the game? Who handles stems, loop points, and technical specifications? Does the agreement cover patches, expansions, downloadable content, and future updates? |
| Live performance | Arrangements, recording rights, performance permissions, and royalties | Who owns the underlying composition and arrangement? May the organizer record, stream, archive, or release the performance? How will each contributor be credited in programs and online listings? |
| Joint original release | Composition splits, master ownership, publishing, and promotion | Who controls the master recording? Are writing shares agreed for each work? Who may license, distribute, edit, or remove the release? |
| Remote or community collaboration | File management, communication, and approval authority | Which version is authoritative? Where are sessions stored? Who can approve changes, and what happens if a contributor becomes unavailable? |
1. Define roles and deliverables
List each contributor’s responsibilities in concrete terms. “Help with the score” is difficult to measure; “compose three themes, prepare orchestral mock-ups, and deliver separated stems” is clearer. Identify whether someone is composing, orchestrating, arranging, producing, editing, performing, mixing, or preparing notation. State who supplies source materials and who is responsible for technical delivery.
2. Agree on credits and ownership
Decide how every contributor will be credited and where the credit will appear: screen, liner notes, game credits, concert programs, metadata, promotional material, or platform descriptions. Also distinguish the composition from a recording of that composition. A contributor may have an agreed role in one without owning or controlling the other.
Do not leave ownership to implication. State whether rights are assigned, licensed, jointly owned, or retained by individual contributors. If shares are used, record the agreed percentages and identify which work each percentage applies to. Cover unused themes, rejected cues, stems, sketches, and derivative arrangements where relevant.
3. Set payment and expenses
Write down the fee, currency, payment schedule, invoice requirements, and any conditions attached to payment. Separate composition fees from recording, arranging, session, mixing, travel, equipment, or rush costs. If the project is unpaid or partly deferred, say so plainly and describe what each person receives instead, such as a credit, revenue share, or portfolio permission. Avoid relying on a verbal promise that future success will resolve an unclear arrangement.
4. Specify deadlines and revisions
Use a delivery schedule with milestones: brief approval, first sketch, review, final mix, stems, notation, and archival handoff. Define who can request revisions and how many rounds are included. Explain what counts as a revision versus a new creative direction. Add a process for deadline changes, late feedback, missing assets, or a project pause.
5. Cover recording and performance use
For live music, specify whether the organizer may record, broadcast, stream, publish, edit, or reuse the performance. Identify whether permissions apply to audio, video, photographs, rehearsal footage, and promotional excerpts. For soundtrack work, clarify whether the music can appear in trailers, promotional clips, festivals, portfolios, or future editions. These permissions should be explicit rather than assumed.
6. Add a dispute and exit process
Choose a practical route for resolving disagreements: a good-faith meeting, written notice, a review period, mediation, or another agreed process. Explain what happens if one person withdraws, misses repeated deadlines, or cannot complete the work. Address payment for completed work, delivery of project files, treatment of unfinished material, and whether the remaining collaborators may replace or revise a contribution.
What to double-check
Before signing or beginning substantial work, read the agreement once as a contributor and once as the project owner. Check the following points:
- Names and authority: Every party is correctly identified, and the person signing can make the relevant commitments.
- Scope: Deliverables, formats, duration, territories, media, and deadlines match the current brief.
- Rights language: Ownership, licenses, publishing, master rights, performance rights, and reuse are not being treated as interchangeable terms.
- Third-party material: Samples, presets, library sounds, commissioned performances, or pre-existing themes have appropriate permissions and are identified where necessary.
- Approvals: The agreement names the decision-maker and establishes how feedback is delivered and recorded.
- Credit placement: Credits are specific enough to use in metadata, programs, end titles, and promotional copy.
- File access: Sessions, stems, notation, source audio, and backups have a clear owner and handoff process.
- Confidentiality and publicity: The parties know what can be shared publicly and when portfolio or behind-the-scenes use is allowed.
- Changes: New media, additional cues, extra performances, or major revisions require a written change to scope and compensation.
For a broader explanation of clauses commonly found in commissioned music work, see Composer Contracts Explained. It is also useful to keep a version history so everyone can see which terms were accepted.
Common mistakes
Starting with only a handshake. Trust is helpful, but written terms protect the relationship by reducing memory-based disagreements.
Using “collaborator” without defining the role. This can hide major differences between a co-composer, arranger, producer, performer, and editor. Name the contribution and connect it to credit and rights.
Agreeing on percentages without defining the asset. A composition split, master split, publishing share, and performance payment may concern different rights. Identify exactly what each percentage covers.
Promising unlimited revisions. Open-ended feedback can consume time and create uncertainty. Include review rounds, response windows, and a process for material changes.
Ignoring successful future uses. A cue written for a short film may later be used in a trailer, live presentation, album, or online promotion. Decide whether those uses are included, separately licensed, or subject to a new agreement.
Failing to document approvals. Keep final briefs, cue lists, split sheets, invoices, and approval messages together. A simple project folder can be as important as the contract itself.
Copying language without checking the project. A template may not fit a game, concert, film, or international collaboration. Adapt the document and seek professional review when the financial or rights implications justify it.
When to revisit
Revisit the agreement before each new collaboration, not only when a dispute appears. A practical review schedule includes the start of seasonal planning cycles, the move from development to production, a change in client or distributor, and any expansion from a single release to multiple formats.
Update the document when workflows or tools change as well. A new collaboration platform, remote file process, notation workflow, interactive audio system, or distribution route may introduce responsibilities that the original brief did not address. Review permissions whenever a project adds a live recording, stream, soundtrack release, trailer, festival screening, game update, or promotional campaign.
Use this final action list before work begins:
- Write the project scope in one page or less.
- List every contributor’s role, deliverable, credit, and approval responsibility.
- Agree on ownership, publishing, recording, performance, and reuse terms.
- Set payment, expenses, deadlines, revision limits, and file handoff requirements.
- Document how changes, withdrawal, and disputes will be handled.
- Share the final version, collect approval from all parties, and store it with the project files.
Clear agreements support better creative work because collaborators can focus on the music instead of reconstructing expectations later. Keep this checklist available alongside your briefs, cue sheets, and delivery templates, and revisit it whenever the people, tools, or intended uses of a project change.
