Scope the work, not only the minutes
A soundtrack estimate based only on minutes can hide the most demanding work. A short adaptive cue with several compatible layers, transitions and failure cases may require more production effort than a longer linear piece. Describe the expected musical assets and their behaviour: number of states, supported transitions, alternate versions, live recording needs and implementation responsibilities. Include time for feedback and testing in the game.
Distinguish creative composition, arrangement, recording, editing, mixing, mastering, integration and quality assurance. One person may do all of them, but that does not make them one task. State who supplies gameplay captures and builds, who owns the integration project and who can approve changes. If the engine is changing during production, agree how the audio work will be kept compatible.
Make milestones represent real decisions
A useful sequence is brief approval, representative prototype, expanded cue set, implementation review and final delivery. Each milestone should name the material to review, the review period and the person who consolidates feedback. Tie payment dates and acceptance conditions to the written agreement rather than assuming everyone shares the same interpretation of “finished”. Avoid making a contributor wait indefinitely for a release date outside their control.
Define a revision round as one consolidated set of comments on an identified version. Explain the difference between correcting an agreed requirement and changing the creative direction after approval. Neither party benefits from treating a changed scene, a new platform or an added vocal performance as a small invisible adjustment. A change request should describe the new work and its effect on schedule and fee before production continues.
Separate the music rights
The composition and the sound recording are distinct rights interests. A composer may create both, but additional performers, producers, publishers or sample licensors can complicate the chain of permission. Ask what rights are controlled by the contributor and which permissions must come from elsewhere. A payment invoice is not a substitute for a clear written licence or assignment.
| Term | Working meaning | Question to resolve |
|---|---|---|
| Composition | The underlying musical work. | Who owns it, and what uses are licensed? |
| Master recording | A particular recorded performance or production. | Who controls the recording delivered to the game? |
| Licence | Permission for specified uses under agreed conditions. | Which platforms, territories, term and promotional uses are included? |
| Assignment | A transfer of specified ownership rights, subject to applicable law. | Exactly which rights transfer, and when? |
| Exclusivity | A restriction on licensing or using the work elsewhere. | How broad is the restriction, and how long does it last? |
| Soundtrack release | Distribution of music separately from the game. | Who can release it, approve edits and receive revenue? |
The UK Intellectual Property Office's copyright guidance, PRS for Music's role information and the Musicians' Union are useful starting points for understanding the wider landscape. Their relevance depends on jurisdiction and circumstances. Get qualified advice for the actual agreement, particularly where ownership transfers, collecting-society arrangements or multiple contributors are involved.
Discuss the uses outside the executable
Marketing trailers, store videos, developer diaries, downloadable soundtracks, ports, downloadable content and sequels may involve different permissions. List intended uses instead of relying on an undefined phrase such as “all game-related purposes”. Discuss whether a composer can share excerpts in a portfolio and when unreleased material must remain confidential. Agree how the composer's credit should appear in the game and in soundtrack metadata.
Streaming deserves its own conversation. Consider whether players can upload gameplay containing the music and how automated content-identification claims will be handled. Do not promise that a recording is “claim-free” without understanding the distribution arrangements. If a problem occurs, the team should know whom to contact and what evidence of permission is available. Library music and sample-based material also need licence checks for the actual use.
Deliver a package another person can understand
A final delivery should not require the recipient to guess which file is approved. Use consistent cue identifiers, state names and version numbers. Keep a delivery manifest that connects the creative name to the runtime asset. If source sessions are included, specify the workstation version, plugins and whether consolidated audio is needed for future access. Owning a session file does not automatically include licences for its third-party instruments.
- Approved masters and clearly labelled runtime exports.
- Tempo, meter, loop points, entry rules and transition notes.
- A file manifest with versions and replacement instructions.
- Agreed stems, alternates, source sessions and dependency notes.
- Credit wording and contributor or performer information.
- A record of relevant permissions and agreed permitted uses.
- Known issues, final acceptance notes and a support contact.
Finish with a joint review of the package and the implemented result. Keep a copy of the accepted version and the agreement together. Good documentation is not bureaucracy added after the music; it is the last creative handoff, making sure the score can continue to work when the people who built it move on to their next project.
Prepare a question for the desk →