Producer's Notes to Prevent Communication Loss

Published Aug 9, 2026 · Updated Aug 11, 2026

A good mix can still go wrong when the communication around it is unclear.

This happens more often than people realize. A producer hears something that feels slightly wrong, sends a message such as "make the vocal bigger," and the engineer has to guess what "bigger" means. The engineer makes a change, sends a revision, and the producer hears something different from what they originally imagined.

The problem is not always the mix. Sometimes the information being exchanged is too vague.

Describe What You Hear, Not What You Think Should Fix It

One of the most useful habits when giving notes is to describe the audible problem before suggesting the solution.

Instead of:

"Add more top end to the vocal."

Try:

"The vocal feels slightly buried when the chorus starts."

The second note gives the engineer useful information without prescribing an unnecessary technical solution.

The engineer can then determine whether the problem is level, masking, compression, arrangement density, tone, or something else.

You are communicating the destination rather than dictating the route.

Use Specific Musical References

Good notes become much easier to interpret when they identify where the problem happens.

Instead of:

"The bass is too loud."

Try:

"The bass feels too prominent during the second verse, especially when the kick enters."

Now the engineer knows what section to examine and what relationship you are hearing.

Useful references include:

• Verse, chorus, bridge or outro
• A specific lyric or musical event
• A timestamp
• A particular instrument relationship
• A comparison to another section of the song

A note such as "1:42, vocal gets buried behind the guitars" is far more actionable than "vocal needs more presence."

Separate Problems From Preferences

Not every note describes a technical problem.

Sometimes you simply prefer one creative direction.

"The vocal is unclear" describes a problem.

"I want the vocal to feel more intimate" describes an artistic preference.

Both are valid. The important thing is making the distinction clear.

This gives the engineer better context when deciding how aggressively to make a change.

Explain What Changed From the Previous Version

If something was correct in the previous version and feels wrong now, say so.

For example:

"The vocal level felt right in V2, but after the instrumental changes it now feels slightly buried."

This prevents the engineer from treating the note as an isolated request.

Mixes are interconnected. Changing one element can change how another element is perceived. A useful revision note therefore includes the context surrounding the problem whenever possible.

Don't Send Five Different Interpretations of the Same Problem

Long notes can sometimes create more confusion instead of less.

If the actual problem is that the chorus feels crowded, sending separate requests for more vocal level, less guitars, more kick, less bass, more width and more reverb may accidentally prescribe several unrelated solutions to one underlying problem.

Start with the thing you actually hear:

"The chorus feels crowded and the vocal loses focus."

Then let the engineer investigate the relationships causing it.

Give Notes in Priority Order

Not every issue deserves equal attention.

If there are ten notes, identify the two or three that matter most.

A simple system works well:

• Must fix: Problems that affect the record significantly.
• Would prefer: Changes that improve the result but are not critical.
• Optional: Ideas worth trying if they fit the mix.

This gives the engineer a sense of hierarchy instead of making every request appear equally important.

Don't Assume You Know the Technical Cause

It is perfectly fine to say:

"Something around the low mids feels congested here."

You do not need to identify the exact frequency, compressor setting or processing chain responsible for it.

The engineer's job is to translate what you hear into technical decisions.

Likewise, an engineer should be willing to ask questions rather than pretending to understand an ambiguous note.

Good Communication Protects the Music

The goal of producer notes is not to control every technical decision.

The goal is to make sure the person mixing understands what you are hearing, what matters to you, and what you want the record to communicate.

Clear notes reduce guesswork. Less guesswork means fewer unnecessary changes, faster revisions and more time spent improving the actual record.