Conflicting Mix Notes: Who Actually Approves the Music?

Why Conflicting Client Mix Feedback Stalls Projects

Conflicting client mix feedback usually doesn't come from bad faith. It comes from more listeners joining the conversation without anyone deciding whose ears count. The artist wants a warmer vocal, the drummer wants more kick, a friend says it sounds muddy, and the engineer is left with instructions that cancel each other out. Each round moves the mix sideways instead of forward.

One community anecdote, available to us only as a short search excerpt from an audio engineering forum, describes an engineer on revision eight who received a second engineer's critique that contradicted what the client had previously asked for [R1]. We don't know the outcome or full details, and one post says nothing about how common this is. It does show the problem: eight rounds in, a new voice can reopen decisions everyone thought were settled.

This guide treats that situation as a workflow problem, not a personal conflict. None of it is legal advice or an industry standard. It's a practical process you can adapt and write into your own agreements.

Second Opinions Are Legitimate; Unmanaged Approval Is Costly

A client asking another engineer to listen isn't, in itself, a sign of distrust. It's their music and their budget, and they may lack the vocabulary or confidence to judge a mix alone. Outside ears can catch a real translation problem you missed. The engineer in the forum anecdote asked whether this was normal [R1], and wanting a second opinion is a reasonable impulse. That said, sharing isn't automatically unrestricted. If the project is covered by a confidentiality clause, a label agreement, or a pre-release access arrangement, who may hear unreleased audio may be limited. Rather than assuming either way, ask the client or the rights holder what sharing is authorized, and check your own agreement too.

What makes outside advice costly is when it arrives as instructions with no owner. If a consultant's notes overrule the client's earlier direction, someone has to decide which wins, and that decision belongs to the client or their designated approver, not to you and not to the consultant. You don't hold final artistic authority over someone else's record. Your job is to make the decision easy and visible, and to be clear about what extra rounds cost.

Identify Who Approves Work and Requests Paid Changes

Before the next revision, ask directly: who signs off on this mix, and who can authorize changes outside the agreed scope? On a solo project that's usually the artist. With a band, label, or producer involved, it may be one designated person or a small group that must agree before notes reach you. Get the answer in writing, even as an email reply.

This matters most when an outside critique conflicts with earlier client instructions, as in the anecdote [R1]. If you know the approver, you don't have to choose sides. You forward the conflict and ask which direction they want. If extra rounds are billable under your agreement, the approver also confirms they accept that cost before you start.

• Name one approver, or a group that must agree before sending notes
• Confirm who can authorize billable extra revisions
• Ask that friends and consultants route feedback through the approver
• Confirm who is allowed to receive unreleased mixes
• Check your agreement for revision limits before raising cost

Translate Opinions Into Audible Goals

Friends and other engineers often send prescriptions: cut 300 Hz on the guitars, use a faster attack on the bus compressor, swap the reverb. Two listeners can prescribe opposite settings for the same perceived issue, or settings for problems that only exist on their playback system. Settings without context are hard to evaluate and easy to argue about.

Ask instead for the goal in listening terms. What should the chorus feel like? Is the vocal hard to understand, or just not exciting? Where does it fall apart: car, earbuds, a club system? A goal like the lyrics get lost in verse two can be solved several ways, and you can choose one that doesn't break something else. It also reveals whether two notes truly conflict or describe the same issue in different words.

Build One Consolidated Revision List

Scattered texts, voice memos, and forwarded emails are where version chaos starts. Keep a single shared revision list, such as a shared document or spreadsheet, where every note includes the version name, a timestamp in the song, who said it, and what they want to hear. When the approver passes along a friend's note, it goes on the same list, not a separate thread.

With notes side by side, contradictions become obvious and the approver can resolve them before you touch the session. Mark each item accepted, declined, or needs decision. A revision-eight scenario like the anecdote [R1] is easier to handle when you can point to the earlier line item showing what the client asked for and when.

Separate Delivery Defects From Artistic Preference

Not every note is taste. Clicks, digital clipping, a missing instrument, a wrong edit, the wrong sample rate or file format, or a mix that misses the delivery specs your client provided are defects. Those generally deserve prompt fixing, and it's fair for anyone, including an outside engineer, to point them out. Verify the claim on the file in question before assuming it's real.

Preference covers vocal level, brightness, reverb size, how hard the low end hits. These are valid notes, but they're choices, and conflicting preferences need the approver's decision. Labeling each item as defect or preference keeps a taste disagreement from being treated as a quality failure, and keeps the client from feeling that fixing your errors is a billable revision.

Compare Options With Matched Levels and Clear Names

When the approver must choose between directions, give them a fair comparison. Louder versions tend to win quick comparisons, so a change can seem better just because it's hotter. Level-match the excerpts by ear or with a loudness meter, and use the same section of the song for each option.

Name files so nobody can confuse them: song title, version number, date, and a plain description such as vocal up or wide chorus. Avoid names like final, final2, or real final. Clear names also let you confirm that a critique was made on the current mix rather than an older bounce.

• Use the same 20 to 40 second excerpt for each option
• Match loudness before sending
• Include version number and date in every filename
• Ask the approver to reply with the exact filename they choose

Hypothetical Worked Example

This is an invented scenario for illustration. A singer-songwriter is on round six of a mix. Her guitarist texts that the vocal is too loud; a producer friend she chose to share the mix with emails that the vocal needs more presence and less reverb. The engineer replies to the singer, confirming she's the sole approver, and adds both notes to the shared list with timestamps.

The engineer asks each listener what they're hearing. The guitarist says the acoustic guitar disappears in the bridge; the producer says the lyrics blur in verse two. These don't really conflict. The engineer sends two level-matched excerpts, v6a with a guitar lift in the bridge and v6b with that plus a clearer verse vocal. The singer picks v6b by filename, notes one exception she accepts, and the engineer records both in the sign-off email.

Red Flags, Verification, Sign-Off, and Escalation

Watch for notes with no traceable source, such as an engineer friend says it's wrong with no details, credentials you can't confirm, critiques of a file that isn't the current version, or sudden demands to restart from scratch framed as an expert verdict. You don't need to accuse anyone. Ask which file was reviewed, on what playback system, and what specifically should change, then check the claim against the actual bounce.

At sign-off, record the approved filename, date, approver, and any exceptions the client accepted. That record doesn't automatically bind anyone or settle disputes; it reduces confusion. If rounds continue past what you agreed, pause and discuss scope and cost before more work. If the disagreement becomes a payment, ownership, or confidentiality dispute, review your written agreement and consider advice from an attorney or mediator familiar with your state.