How to Give Mix Revision Notes Your Engineer Can Use

Horia Stan is a music producer and sound engineer at The One Records in Bucharest, Romania, who mixes and masters songs for artists worldwide, mostly remotely and in writing. Good revision notes are specific, prioritized and sent once. Name the moment, the element and the direction you want, and attach a reference when a word like "warmer" could mean five things.

Vague notes cost you rounds. Clear notes usually get you to the right mix in one pass.

Quick answer

• Send one batch of notes, not a stream of messages. Listen to the whole mix first, then write.
• Every note needs three parts: where (timestamp), what (element), and what you want (direction or reference).
• Rank your notes. Mark the two or three that matter most so they do not get lost under small tweaks.
• Agree on the number of included revisions before the mix starts. On my projects it is two standard rounds.

Why most revision notes fail

The first mix is a set of decisions. A revision is you asking for different decisions. That only works if the engineer can tell which decisions you disagree with.

The notes I would call useless look like this:

• "Make it more modern."
• "The vocal feels off."
• "Can it be bigger?"

Each of these is a feeling, not an instruction. "Bigger" could mean louder, wider, lower in the low end, or more reverb. An engineer will guess, and a wrong guess burns a revision round.

Other mixing engineers say the same thing. Production Expert and NoteTracks both recommend specific, timestamped, batched notes. This is a common view among mixers, not a rule. Still, it matches how remote work behaves in practice.

Before you write a single note

Listen on more than one system

Do not judge a mix after one pass on one pair of earbuds. Play it on:

• Headphones you know well
• Your phone speaker
• A car or a living-room speaker, if you can

If a problem only shows up on one system, say which system. "Vocal is hard to hear in the car" is useful. "Vocal is too quiet" might be a speaker issue.

Match levels with your reference

A louder track almost always sounds better. If you compare the mix to a reference song, match the volume first. Otherwise you will ask for changes that are just loudness.

If you need a refresher on references, read the reference track method. It covers how to use a reference without losing your own sound.

Wait a day

A mix you hear for the first time at 11 pm after a long session is not the mix you will hear tomorrow. Write your notes, sleep, reread, then send. Half the notes usually disappear.

The note format that works

Use one line per note. Keep the same structure every time.

You do not need to tell the engineer which plugin to use. Describe the result, not the tool. "Cut 3 kHz by 2 dB" is a guess about the cause. "The vocal sounds harsh when she goes up in the chorus" lets the engineer find the cause.

Use words that carry meaning

Some words are common and still unclear. Here is how I would translate them.

Attach a reference for subjective notes

If a note contains a word like warm, bright, big or tight, add a reference. One line is enough:

"Chorus drums: closer to the drum punch in this reference at 0:45. Not the tone, just the impact."

Name what you like about it. A reference with no explanation invites the engineer to copy the whole sound, which is rarely what you meant.

Prioritize or lose the important notes

Ten notes with equal weight are a worse brief than three ranked ones. I suggest this split:

1. Must fix: problems that stop you from releasing the song. A buried hook, harsh vocal, a clipped section.
2. Should fix: things that would improve the song but would not stop a release.
3. Taste: small preferences. These are the first to drop if you are running out of rounds.

Put the must-fix list at the top of the message. If everything is marked high priority, nothing is.

What counts as a fair revision

This is where artists and engineers most often disagree, so here is how I handle it on my own projects.

• Two standard revision rounds are included on every project.
• Extra rounds are available when the work genuinely requires them.
• Revisions are not counted when the feedback is fair. For example, if I missed something that was in your brief, that is on me, not on your round count.

What usually does count as a new round:

• Changing the creative direction after the mix is approved in principle
• Swapping in a new vocal take or new arrangement after mixing has started
• Reversing an earlier note, for example asking for the vocal louder in round one, then quieter in round two

What usually does not count:

• A mistake in the mix, such as a missed edit, a pop or a wrong level
• A note that clearly follows from the original brief
• A technical delivery fix, such as wrong file format

Ask about this before paying. I covered other questions to ask in how to choose a mixing engineer. Revision policy is one of the most important ones.

Common mistakes

Sending notes in pieces

Five messages over two days lead to conflicting requests and missed notes. Collect everything, then send one message. This is also the standard advice for online clients in the sources linked above.

Too many voices

If a band, a manager and a friend all have opinions, merge them first. Contradicting notes force the engineer to guess who wins. Send one consolidated list from one person.

Asking for everything at once

If the mix has a problem in the foundation, such as the low end or the vocal level, fix that before asking about reverb tails. Order your notes from big to small.

Changing the song during mixing

Mixing is not the place to rewrite the arrangement. If you want a new part or a new vocal take, it is a production change. Do it before the mix, or accept that it may reset the process. If your stems are not final, read how to prepare stems for a mixing engineer first.

Judging a mix against the mastered reference

A finished, mastered song will sound louder and more polished than an unmastered mix. If your reference is mastered and your mix is not, part of the gap is mastering. Mixing vs mastering explains where that line sits.

A copy-paste template

Paste this into an email or a message and fill it in.

Telling the engineer what you like is not politeness. It protects the parts of the mix that already work.

Where a mixing engineer helps with this

If you are not sure how to describe what you hear, that is normal. When I work on a mix remotely, everything runs in writing and files. You send the stems and references, I send a mix, you send notes, I revise. There is no need to be on a call, and the notes become a record of the decisions.

If you want to see how that flow works end to end, online mixing and mastering for international artists walks through it. For timing, see how long it takes to mix and master a song.

When to do it yourself and when to hand it over

Writing revision notes yourself is fine when:

• You are working with a mixer you already trust
• The changes are small, like a level or an effect amount
• You have a clear reference and know what you want from it

It is worth handing the whole process to someone experienced when:

• You keep rejecting mixes and cannot say why
• You want a polished, tightly edited modern pop vocal and not just a balanced mix
• You want a clear revision policy agreed up front

If that sounds like your song, see mixing and mastering for how I work. If you are ready, send the song, references and your notes through the request form. For a full production, see music production in Romania. Starting price for a song is 500 euros, with two standard revision rounds included. Confirm scope and price before booking.

Frequently Asked Questions

How do I give feedback on a mix without sounding rude?

Describe what you hear, not what the engineer did wrong. Say "the vocal gets lost in the second chorus" instead of "you made the vocal too quiet." Start with what you like, then list the changes. Engineers want specific notes because they make the next version better.

How many revisions should a mixing engineer include?

There is no industry standard. Quotes vary, and many engineers include about two rounds, with extra rounds costing more. Ask for the number and the definition of a round in writing before work starts. On my projects, two standard rounds are included and fair feedback is not counted against them.

What should I include in mix revision notes?

Include a timestamp, the element, what you hear and what you want. Add a reference for any subjective word. Rank notes by priority and say what you want left unchanged. Send everything in a single batch rather than several messages.

Should I use reference tracks when asking for changes?

Yes, when the note is about tone, space or impact. Attach the link with a timestamp and explain what to match, for example "the drum punch, not the brightness." A reference with no explanation can push the engineer to copy the whole sound.

Why does my mix sound worse than my reference?

Common reasons are loudness differences, mastering and the playback system. A mastered reference is louder and more polished than an unmastered mix. Match the volume and check the same section on the same speakers. If the gap remains, write the specific difference as a note.

Can I ask for a revision after the mix is approved?

You can ask, but it is usually treated as a new job or an extra round because the work was accepted. Check the engineer's terms. Listen on several systems and wait a day before approving so you catch issues earlier.

Do I need a call to give mix feedback?

No. Written notes with timestamps and references work well and leave a clear record. Remote and async mixing is common, and it forces you to be precise, which usually improves the result.