Most delays in music work do not come from writing speed. They come from unclear expectations. No timeline. Vague references. Missing gameplay context. Late implementation decisions. A better brief solves a lot of this before the first cue is written.

1. Start with the project format and current stage

Start with the basics. Is this a game, series, trailer, or brand video? What stage is it in: prototype, vertical slice, production, or post? Then say what material exists right now: gameplay capture, animatic, rough cut, script, or concept art.

This tells the composer how the music can be planned and reviewed.

2. Define the role of music in the project

“We need music” is not enough. The composer needs to know what the music is doing in the project. Is it leading the emotion? Sitting in the background? Signaling game states? Building identity for a series or brand?

  • Where should music be foreground vs background?
  • What scenes or states must the score support?
  • What should the audience/player feel at key moments?

3. Share useful references (and explain why)

References help most when you explain why you picked them. “Like this soundtrack” is vague. “This has the right warmth and pacing” is much better.

Send 2 to 4 references and one short note for each. This keeps the direction clear and saves time later.

4. For games, describe the gameplay loop and music states

If it is a game, describe what the player does and when the music should change. A short state map is often enough:

  • Menu / setup
  • Exploration / planning
  • Tension / encounter
  • Combat / action
  • Win / fail / results

Even a rough version helps estimate cue count, structure, and whether adaptive music planning is needed.

5. State timeline and review rhythm clearly

Include internal review time, not just the final deadline. If three people need to approve the music, that changes the schedule. It also helps to say who gives notes and how often.

6. Include budget range early

A budget range is not just about price. It affects scope: cue count, production detail, revision time, and whether implementation support is included. Without it, proposals are often off target.

7. Specify technical requirements and deliverables

If you need loops, stems, alternate layers, implementation notes, or a specific file setup for the engine, say it in the brief. Technical delivery is part of the work too.

  • Stereo only, or stems as well?
  • Loop-ready exports required?
  • Adaptive implementation support needed?
  • File naming convention or engine pipeline constraints?

8. What a strong first message can look like

Indie strategy game in prototype. PC target. Looking for original soundtrack (30-40 minutes total) with cozy but characterful tone. Need exploration, seasonal progression, and tension cues. Vertical slice gameplay capture available. Target first milestone in 5 weeks. Budget range provided. We may need stems for implementation.

That message is short, but it gives enough to start a real conversation and a realistic proposal.

Common mistakes that slow projects down

  • Sending only style references and no gameplay/video context
  • No decision-maker defined for feedback
  • Changing scope after benchmark cues without updating timeline/budget
  • Leaving implementation requirements until final delivery

Next steps

If you are getting ready to commission music, start with the hiring FAQ, then send your brief through the contact page. If the project is interactive and you are not sure about music states yet, read the adaptive music and implementation service page first.