How to Write a Mix Brief That Gets Results

A mix brief that gets results tells the engineer what the song should feel like, which references matter, what the priority problems are, what not to change, how the files are organized, and what delivery or revision expectations matter. It should be clear enough to guide the first mix without becoming a long essay that makes the engineer guess what is most important.

A good mix brief does not need fancy language. It needs useful direction. "Make it sound professional" is not enough because professional can mean loud, clean, dark, bright, dry, wide, intimate, aggressive, soft, polished, or raw. The engineer needs to know what professional means for this song.

This guide shows how to write a practical mix brief for online mixing, remote mixing, or any situation where the engineer is not sitting in the room with you. It covers references, priorities, file notes, creative boundaries, revision clarity, and the difference between helpful direction and micromanaging the mix.

The Short Answer: Give Direction, Not a Novel

The best mix brief is usually one page or less. It gives the engineer the song context, the desired sound, the most important references, the biggest problems to fix, and the details that prevent mistakes. Long notes can be useful when they are organized, but long emotional paragraphs with no priorities can slow the mix down.

Brief section	What to include	Why it helps
Song goal	One or two sentences about the intended feel.	Gives the engineer a target before processing starts.
References	One to three songs with specific reasons.	Prevents vague comparisons and loudness confusion.
Priorities	The top problems or moments that matter most.	Shows where the engineer should spend attention first.
Do-not-change notes	Effects, rough ideas, edits, or balances you want preserved.	Protects intentional creative choices.
File notes	Dry/wet files, alternates, missing stems, BPM, key, rough mix.	Reduces setup mistakes.
Delivery needs	Deadline, clean version, instrumental, TV track, stems, or master needs.	Makes the final delivery match the release plan.

If you have not prepared the files yet, handle what to send your mixing engineer before writing the final brief. The notes are only useful if the files match them.

Start With the Song Goal

Open the brief with the emotional target. This is the north star. The engineer should know whether the record is supposed to feel aggressive, clean, dark, intimate, club-ready, warm, wide, raw, or polished. Keep it short and concrete.

Good examples:

"The vocal should feel close and emotional, not too wet."
"The hook should hit harder than the verse, with wide doubles and a cleaner lead."
"Keep the beat dark and heavy, but make the vocal easier to understand."
"I want the song polished but not overcompressed."
"The rough mix has the right vibe, but the low end and vocal clarity need help."

Weak examples:

"Make it radio quality."
"Do your magic."
"Make it sound like every big artist."
"Fix everything."
"Just make it loud."

The first group gives direction. The second group creates guessing.

Choose References With a Reason

References are only helpful when the engineer knows what to listen for. If you send three songs with no explanation, the engineer may copy the wrong thing. Maybe you wanted the vocal level from one song, the low end from another, and the reverb from a third. Say that.

Use references like this:

"Use this song for vocal brightness, not loudness."
"I like how dry and close the lead is in the verse."
"The hook width is the main thing I like here."
"This reference has the kind of low-end weight I want, but my vocal should stay cleaner."
"Do not copy the effects exactly; this is only for overall polish."

Reference tracks should be close enough to your song to be useful. A sparse acoustic ballad is not a useful vocal reference for a dense trap beat unless you are only pointing to intimacy. The guide on choosing the right reference track before mixing can help if your references keep confusing the direction.

List the Top Three Priorities

A mix can have many details, but the brief should rank what matters. The engineer needs to know which problems will decide whether the first mix feels successful. If everything is equally important, nothing is prioritized.

Common priority examples:

Lead vocal clarity.
Low-end control between kick and 808.
Hook energy.
Ad-lib placement.
Less harshness on the vocal.
More natural vocal effects.
Cleaner transition into the second verse.

Write them in plain order:

Make the lead vocal easier to understand without making it too bright.
Keep the 808 heavy but stop it from covering the kick.
Make the hook wider than the verse without burying the main vocal.

That is much more useful than a paragraph that says the vocal, beat, drums, effects, master, and whole song all need to be perfect.

Explain What Should Stay the Same

Artists often focus only on what needs fixing, but a good brief also says what should be preserved. Maybe the rough vocal delay is important. Maybe a distorted ad-lib is intentional. Maybe the beat is already approved and should not be heavily changed. Maybe the vocal should stay raw and not become glossy.

Tell the engineer what not to change:

"Keep the delay throw on the last word of each hook."
"The distorted bridge vocal is intentional."
"Do not make the vocal too wet; I want it close."
"The beat drop at 1:18 should stay dramatic."
"The rough mix has the right vocal attitude, just not the quality."

This protects the ideas that already work. A mixer should improve the record, not accidentally remove the parts that made you excited about it.

Include Dry and Wet File Notes

If you send both dry vocals and wet references, explain what each one is. The engineer should know whether the wet vocal is a creative target, a rough idea, or a file you expect to be used in the final mix. This is especially important if the rough effects include tuning, distortion, pitch effects, or delays that are part of the song identity.

Useful file notes include:

"LeadVocal_Dry is the main vocal to mix."
"LeadVocal_WetReference shows the effect vibe only."
"The tuned hook reference is closer to what I want than the dry hook."
"Adlibs_Optional can be muted if they crowd the lead."
"HarmonyStack_Wet has a printed effect that should stay close to this sound."

If your vocals were recorded at home, use how to prepare home-recorded vocals for online mixing to make sure the file handoff and brief match each other.

Tell the Engineer About Known Problems

Do not hide problems and hope the engineer will not notice. A good engineer will notice. It is more useful to explain the problem clearly. If the beat is only a two-track, say so. If the lead vocal has a little room noise, mention it. If a harmony stack is optional because the tuning is not perfect, label it.

Good problem notes:

"The beat is a stereo file, so I know drum control is limited."
"The verse vocal has some room noise, but this is the best take emotionally."
"The second hook double is loose; use it only if it helps."
"There is a clipped word at 0:42. If it cannot be fixed, lower it or use the alternate."
"I only have the wet effect vocal for the bridge."

This kind of honesty saves time. It tells the engineer what is intentional, what is a limitation, and where judgment is needed.

Keep Revision Direction Separate From First-Mix Direction

The first brief should guide the first mix. Revisions come later after you hear the result. Do not try to pre-write every possible revision. Instead, explain the initial target, then use revisions to respond to the mix that comes back.

Still, you should understand the revision policy before the job starts. Some services include a certain number of revisions. Some charge for extra work, arrangement changes, or new files after mixing begins. If you are ordering online, read the terms before assuming unlimited changes.

The guide on how to read a revision policy before ordering a mix explains what to look for. Your brief should reduce revisions by giving clear direction early, but it should not replace a clear approval process.

Match the Brief to the Type of Service

A mix brief should match what the engineer is actually doing. If you booked mixing, ask for mix decisions: vocal level, tone, effects, low-end balance, automation, and clarity. If you booked mastering, do not ask for individual vocal changes from a stereo file. If you booked editing, focus on timing, tuning, cleanup, and comping.

This prevents mismatched expectations. A mixer working from separate tracks can adjust the lead vocal against the beat. A mastering engineer working from one stereo file cannot cleanly turn down one ad-lib or remove one vocal delay. A brief should ask for work that the files allow.

If you are working remotely, how to work with a remote mixing engineer gives the broader communication process beyond the brief itself.

Use Plain Language Instead of Plugin Instructions

Unless you have a specific technical reason, describe the result you want rather than the plugin move you think should create it. "Make the vocal less sharp on S sounds" is usually better than "put a de-esser at 6.5 kHz with this threshold." The engineer may solve the problem with clip gain, automation, EQ, de-essing, saturation changes, or a different chain order.

Good result-based notes:

"The vocal should feel closer."
"The low end should hit but not swallow the vocal."
"The hook should feel wider than the verse."
"The delay should be noticeable only at phrase endings."
"The vocal should be smoother without losing energy."

Technical notes are helpful when they explain a real file issue. For example, "The beat is already limited" or "The bridge vocal has printed distortion" is useful. But micromanaging every plugin can prevent the engineer from solving the problem in the best way.

Use a Simple Mix Brief Template

You can use this structure for most songs:

Section	Example
Song goal	Close emotional vocal, clean low end, hook should feel wider than verse.
References	Reference 1 for vocal level, Reference 2 for low-end weight.
Top priorities	Vocal clarity, 808 control, hook width.
Preserve	Keep the delay throw on the last hook word and the distorted bridge effect.
File notes	Dry lead is main. Wet lead is reference. Beat is two-track only.
Delivery	Need full mix, instrumental if possible, and clean version.

This is enough for many projects. If the song has unusual routing, missing stems, alternate hooks, or special effects, add those details under file notes. Keep the top priorities easy to see.

What a Finished Brief Can Look Like

Here is a simple example:

Song goal: I want the track to feel dark, close, and polished without making the vocal too wet. The hook should lift more than the verse, but the main vocal should stay clear.

References: Use Reference A for vocal level and closeness. Use Reference B for low-end weight. Do not copy the exact reverb from either reference.

Top priorities: First, make the lead vocal easier to understand. Second, keep the 808 heavy but controlled. Third, make the hook wider with doubles without burying the lead.

Preserve: The delay throw after the last word of the hook is important. The rough mix has the right mood, but the vocal is too muddy and the low end is too loose.

File notes: LeadVocal_Dry is the main take. LeadVocal_WetReference shows the effect vibe only. Adlibs_Optional can be muted if they crowd the lead. The beat is a stereo file.

Delivery: Please send the full mix and an instrumental if possible.

That brief is short, but it gives the engineer direction, priorities, limitations, and creative boundaries.

Common Mix Brief Mistakes

Most bad mix briefs fail because they are either too vague or too controlling. A vague brief gives no target. A controlling brief gives too many plugin instructions and not enough creative direction. The strongest brief leaves room for engineering judgment while clearly explaining what the artist values.

Mistake	Why it causes problems	Better approach
No references	The engineer has to guess the tonal target.	Send one to three references with reasons.
Too many references	The direction becomes contradictory.	Pick the few that match this song.
No priorities	The engineer does not know what matters most.	List the top three mix goals.
Only plugin instructions	The engineer may be blocked from better solutions.	Describe the sound you want.
Hiding file problems	Limitations appear later and slow the job.	Explain missing stems, clipping, or rough source issues early.

If you are still choosing who to hire, red flags when hiring a mixing engineer online can help you avoid services that do not communicate clearly before the job starts. A good brief works best with a mixer who actually reads and uses it.

When to Book Help Instead of Rewriting the Brief Again

If the files are organized and the brief is clear, the next step is not always more planning. At some point, the song needs a mix. Rewriting the brief over and over can become a way to avoid committing to a direction. If you know the goal, have references, and can name the top problems, you are ready to send the project.

BCHILL MIX mixing services are a natural fit when you have the separate tracks, a rough mix, and a clear direction but need the final balance, tone, space, and polish handled professionally. The brief helps make that first pass more accurate.

Review the Brief Like an Engineer Would

Before sending the brief, read it from the engineer's point of view. Can they tell what the main vocal is supposed to feel like? Can they tell which reference matters most? Can they tell which files are dry, wet, optional, or final? Can they tell what would make the first mix a win?

This review is useful because artists often write notes from memory. The engineer only has the files and the brief. If the note says "use the good hook vocal," but three hook files are labeled final, the brief is not clear. If the note says "make it like the reference," but there are four references with no explanation, the direction is not clear. If the note says "fix the vocals," but does not say whether the issue is level, harshness, tuning, timing, or effects, the engineer has to guess.

Use this final check:

Can the engineer find the main lead vocal in under one minute?
Can the engineer explain the song goal in one sentence?
Are the references tied to specific mix qualities?
Are the top three priorities obvious?
Are creative effects labeled as intentional?
Are known limitations explained without over-apologizing?
Are delivery needs listed clearly?

If the answer is yes, the brief is ready. If not, simplify it. A shorter clear brief is stronger than a long unclear one.

How to Give Feedback After the First Mix

The first brief sets direction. Feedback after the first mix should respond to what you actually hear. Keep the same clarity. Instead of "it still does not sound right," explain the specific change: "raise the lead vocal slightly in the hook," "make the delay less obvious in verse one," or "the 808 is covering the kick on small speakers."

Good feedback usually has three parts:

What part of the song you mean.
What you hear now.
What you want changed.

For example: "At 1:06 in the second hook, the ad-lib is pulling attention away from the lead. Please lower it or push it wider." That gives the engineer a clear action. "The hook feels weird" gives emotion but not enough direction.

Do not restart the entire brief during revisions unless the first direction was wrong. If the mix followed your notes but you changed your mind about the style, say that clearly. Revision clarity keeps the working relationship healthy and keeps the song moving toward approval.

FAQ

How long should a mix brief be?

A mix brief should usually be one page or less. It can be longer for complex sessions, but the most important parts should be easy to find: song goal, references, priorities, file notes, and delivery needs.

How many reference tracks should I send?

Send one to three strong references. Explain what each reference is for, such as vocal level, low-end weight, hook width, dryness, or overall polish. Too many references can make the direction unclear.

Should I tell the engineer exact plugin settings?

Usually no. Describe the sound you want rather than the plugin move. Exact settings can help only when there is a specific technical reason. Most of the time, the engineer can choose the best tool for the result.

Should I mention problems in the files?

Yes. Mention clipping, room noise, missing stems, loose doubles, optional ad-libs, two-track beats, or printed effects. Clear problem notes help the engineer make better decisions faster.

Can a mix brief reduce revisions?

Yes, a clear brief can reduce avoidable revisions because the first mix starts closer to the target. It does not remove the need for feedback, but it makes the first pass more informed.

What is the most important part of a mix brief?

The most important part is the priority list. The engineer needs to know what matters most: vocal clarity, low-end control, hook energy, effects style, or preserving a specific rough-mix idea.

Final Takeaway

A strong mix brief is simple, specific, and useful. Tell the engineer what the song should feel like, which references matter and why, what the top priorities are, what should stay the same, what file limitations exist, and what delivery you need. The brief should guide the mix without trying to mix the song for the engineer.