What to Include in a Music Production Brief for a Collaborator

Make it clear what you need and what can change

Your brief should explain what you want to achieve with the song, what task you're assigning, which decisions are approved, and what files you expect to receive, along with dates and a way to review progress. Include a clearly identified demo and references with notes. If you work in wuse, use that agreement to organize the project's versions, files, and comments.

I'd recommend starting with a sentence the other musician can turn into actual work: “I need a guitar arrangement for the second verse and the choruses; keep the vocal melody and suggest a rhythm.” Then fill in the details. That makes it clear from the start where you need their judgment.

The brief is your starting agreement. You don't need to figure out the whole production before sharing it, but you do need to separate what's decided from what's still open. If you're still looking for the song's sound, ask for an initial idea and define what you'll evaluate before assigning the rest.

Complete and download the editable music brief template while defining the project.

Why a vague request leads to doing the work twice

Imagine this request: “Make the chorus explode.” Your collaborator might add instruments, change the drums, or suggest different harmony. Maybe all you wanted was a stronger entrance after the verse. Those are different possibilities, and that sentence doesn't rule any of them out.

Work has to be redone when you judge a decision against a condition you never shared. For example, rejecting an arrangement because it changes a bass part you considered approved, even though the demo didn't identify it as final. My advice is to write down the constraints before hearing the first idea.

It also helps to separate the goal for this stage from the goal for the release. If you're approving songwriting and arrangement today, say so. Define what you need to hear to take the next step and which issues you'll review later.

Before moving forward, answer one question: what would that person need to deliver for you to say, “Yes, this meets the brief”? That answer becomes your review criteria.

Explain the artistic direction with examples you can hear

Describe the emotion, the energy, and where each main element should sit. You could write “an intimate vocal, restrained backing, and a more open final chorus.” Include the intended use whenever it changes the task: a version for live performance may call for different decisions than a production intended for release.

References and demos help communicate an intention, but they need context. Choose a few short sections and explain what interests you about each one. The songs don't all have to be in the same genre if you're pointing to specific elements.

Example: “Reference A, 0:42–1:03: I'm interested in how the guitar comes in between the phrases. Reference B, 1:15–1:35: I want to explore that contrast in energy when the chorus hits.” Also clarify what doesn't apply: “The vocals in those references aren't the direction for this song.”

Identify the demo by name and version. Then explain its purpose: it might guide the arrangement while still containing temporary sounds. To avoid confusion, write down what needs to stay, what you want to replace, and where you're open to ideas.

Once you have selected references and a demo, you can prepare the session with a brief and files. The link brings notes and materials together before opening the booking to work.

• Goal: what emotion and what change you're looking for at this stage.
• References: the section, the element you're interested in, and how it relates to the task.
• Demo: the exact name and the decisions that are already approved.
• Creative freedom: what the collaborator can suggest and what they need to check with you about.

Define the task and get the materials ready

“Help me with the production” leaves too much open to interpretation. Specify whether you need songwriting, arrangement, performance, sound selection, editing, or mixing. If you're assigning several tasks, write down which comes first and who approves each stage.

Include the musical details you already know: tempo, time signature, key, and structure. If any are still undecided, mark them that way and assign someone to confirm them. To locate a part, you can write “second verse, 1:08–1:36 in Demo_v03.” The timestamps need to match the file you're sharing.

Prepare a list of materials: the demo, backing track, lyrics, chords, and available recordings, depending on what that person needs. Explain which one to use as the starting point and which are just for reference. If you attach alternate takes, say whether you expect the collaborator to choose or whether you've already made the selection.

Also define the practical scope: the agreed budget, included services, payments, and how you'll handle extras. Record the planned credits and any outstanding agreements about contributions. If there's third-party material, identify who will clarify its use. Don't leave those conversations buried in a note about the arrangement.

Agree on the files before anyone starts

Write a deliverables list that makes it easy to check whether anything is missing. Instead of asking for “the stems,” specify what you want to receive separately, which groupings are acceptable, and what processing each file should include. To prepare for that conversation, read the guide to stems or multitracks: what to send for a song mix.

Leave fields to agree on the format, sample rate, bit depth, mono or stereo, start, end, and effects tails. Don't copy settings out of habit: ask whoever will receive the material to confirm what they need. Also clarify how many takes or alternatives the job includes.

If you'll be exchanging an editable project, note the production software—the DAW—along with its version, edition, and required plugins. In Ableton Live, the .als file contains references to resources; sending that file alone isn't the same as sending all the materials. Collect All and Save gathers audio and Max for Live devices, but not third-party plugins. To transfer the project, collect the resources and compress the entire folder.

When the other team doesn't have the same plugins, agree on which tracks need to be rendered to audio to preserve their sound and which need to stay editable. The guide to collaborating when each producer uses a different DAW helps you work through that part of the agreement.

Set dates, assign responsibilities, and agree on how to review

Separate the first proposal from the final delivery. Write down specific dates and a time zone when you're working from different places. Add how much time each person will have to respond: there's no point scheduling a delivery for Friday if the approval it needs won't arrive until the following Monday.

Name the person who gathers the comments and the person who gives approval. Several musicians can be involved, but it helps to send feedback you've all agreed on. If two people ask for incompatible changes, resolve that difference before turning it into another task for the collaborator.

Ask for every comment to identify the version, timestamp, and goal. Example: “On Demo_v04, at 1:12, try a shorter guitar response to leave room for the next vocal phrase.” That note points to an action you can evaluate.

Agree on how many rounds the work includes and what you'll do if the scope changes. Changing the artistic direction after approving it calls for a conversation about dates and budget. To prepare your notes, continue with how to give mix feedback and avoid endless revisions.

To separate agreed changes from new proposals, see how to collect comments in a review round.

A template you can copy for your next job

Copy these four blocks and fill in the blanks. You can keep them short; what matters is that they let you start and review the work. If a decision hasn't been made yet, write “pending,” who will resolve it, and by when.

Job: song [title]; contact [name]; collaborator and task [role and specific work]; expected result [what needs to be ready]; intended use [release, live performance, or other]. Scope: [included services], budget [agreed or pending], extras [how they're approved], and credits [agreed or pending].

Direction: we're looking for [emotion and energy]. Working demo [exact name]. Keep [approved decisions]. Change [problems or temporary elements]. You're welcome to suggest [creative freedom]. References [name, section, and desired element]. Musical details [known tempo, time signature, key, and structure].

Materials and delivery: you'll receive [files and the purpose of each]. We need back [exact list of tracks, groups, alternatives, or project]. Audio settings [to be confirmed with the recipient]. Included processing [details]. Tools and compatibility [DAW, version, edition, and dependencies where applicable].

Schedule and review: first proposal [date and time]; feedback [date]; final delivery [date]. Gathers the notes [person]; approves [person]; makes the changes [person]. Agreed channel [place]. Included rounds [number]. If the scope changes [procedure].

A compact example of a complete task description: “I need guitars for the second verse and both choruses of Demo_v03. Keep the chords and melody; you can suggest the rhythm and sound. First, we'll review an idea for the second chorus. Once it's approved, you'll develop the other sections. The delivery will include the performances separately and a reference bounce with the backing track; we'll confirm the audio settings before recording.” Fill in dates, terms, and names before sending it.

Mistakes to check for before sharing

Read the brief while opening the files. Check that the demo name matches, that the sections you've pointed to exist, and that you aren't asking someone to work from an older version. If you've updated the structure, check the timestamps in your notes too.

Another mistake is asking for creative freedom and then treating every difference as a required correction. Define the room for exploration: “You can change the drum pattern; keep the structure.” If you want to hear an alternative, say whether it's included and when you'll make a decision.

Finally, ask the collaborator to confirm the task, the first delivery, and any outstanding questions in their own words. A short response can reveal a different interpretation before work begins.

• The demo and materials match the names in the brief.
• Approved decisions and ideas still open for discussion are clearly separated.
• The deliverables and their settings have been confirmed with whoever will receive them.
• The dates, revisions, and person responsible for approval are defined.

How to bring this agreement into wuse

wuse works as a space to organize your music project, its audio versions, stems and files, collaborators, and comments. Use the same names as the brief when adding materials, and indicate which version goes with each review. When you share a delivery, identify which part of the job you're marking as complete.

The tool supports the agreement you define together. It doesn't automatically convert sessions between DAWs; compatibility and the necessary files need to be sorted out before the exchange. If you also use split sheets and signatures, treat agreements about shares as a separate conversation, with legal advice when needed.

Your next step can be concrete: copy the template, fill it out for one song, and check the four points above. Then organize the project in wuse and share the brief with your collaborator. Start when you're both clear on the first task and how you'll approve it.

To choose your tools after writing the brief, review what Split includes and what Pro adds. Calendars, projects and versions are part of the Pro workflow.

Frequently asked questions

How long should a music production brief be?

Long enough to understand the task, find the materials, and evaluate the delivery. I'd start with one short page and expand only the parts that need it. If an explanation doesn't affect any of the collaborator's decisions, you can cut it.

Can I prepare the brief if I don't know what sound I want yet?

Yes. Define the first stage as exploration and ask for an idea with a limited scope, such as one chorus. Explain what feelings you're looking for, which elements you want to keep, and when you'll choose a direction. Agree on the scope of that exploration before asking for several alternatives.

Does the demo need to be finished before I send it?

It doesn't have to represent the final result. Identify its version and explain what it communicates well and what's still temporary. You can approve the structure while leaving the sounds open. Your collaborator needs to know which decisions they should respect.

How many references should I include?

I'd recommend starting with two or three references with notes, and adding another only if it clarifies a different need. Point to the section and the element you're interested in. That number is a practical choice for this workflow, not a requirement of the job.

What if I don't know the key or tempo?

Mark that detail as pending and ask who can confirm it before any work that depends on it. Share the demo you have and avoid presenting an estimate as final. The brief can include open questions, as long as it's clear how they'll be resolved.

How do I handle comments from several team members?

Choose one person to gather them and resolve contradictions before sending them. The feedback should say which version everyone listened to and which changes they agreed on. It also helps to distinguish suggestions to explore from decisions needed for approval.

What if I want to change the task after the first proposal?

Explain what changed and review together how it affects the work, dates, and budget. Update the brief so the new direction is visible. Avoid adding a new task to a list of corrections without first confirming who will do it and under what terms.