Client Feedback Etiquette for Audio Pros: Giving and Getting Notes

Good client feedback etiquette in audio comes down to four habits. Notes are specific and tied to a time in the file. They arrive in one consolidated list per round. They describe what the listener hears, not how to fix it. And the number of rounds is agreed before the work starts. This guide covers both sides: how you, the producer or engineer, ask for and respond to notes, and how to coach clients into giving notes you can act on.

Audome

Keep Audio Feedback in One Place

Audome brings audio files, timestamped comments, project management and communication together in one hub for clearer collaboration.

Explore Audome

TL;DR

Send one version at a time, with context, and ask for one consolidated list of timestamped notes.
Ask clients to describe the audible problem and the outcome they want. You choose the technical fix.
Never guess at vague notes like “more energy”. Ask which element and which section, then offer options.
Agree on revision rounds, a response window and extra-round pricing in writing before work begins.
Push back in terms of what the listener will hear, never in terms of who is right.

Why feedback goes wrong in audio
Set expectations before the first file
How to ask for feedback that you can use
How to respond to vague, conflicting or subjective notes
Etiquette when you give feedback to clients
Organize notes, versions and approvals
Wording you can steal
Our perspective: make feedback the easy part
Put it into practice with Audome
FAQ
Sources

Why feedback goes wrong in audio

Audio is hard to talk about. A client hears a mix on earbuds in a car, you hear it on calibrated monitors, and both of you reach for the same vague words: warm, punchy, thin, flat. Add notes scattered across email, text messages and voice memos, and nobody knows which version a comment refers to.

Most etiquette problems are really process problems. The client isn’t being rude, they just have no structure. When you provide that structure, the tone usually takes care of itself. The rest of this article is the structure.

Set expectations before the first file

The best time to handle a difficult round of notes is before the project begins. Three conversations help.

Talk about references and intent

Sound On Sound’s piece on client feedback notes that giving clients a sense of ownership early, for example by discussing reference tracks before starting, tends to lead to a smoother feedback loop. It also points out that involving artists in remote mixing can give them a feeling of ownership of the mix. Ask what they love about their references and what they want the listener to feel. You will refer back to those answers every time a note seems to pull in a strange direction.

Agree on the number of rounds

For podcasts, Pristine Podcasts suggests agreeing on two revision rounds before work begins: the first for structural or factual changes, the second for polish. If the two sides are still mismatched after that, a short alignment call beats another long written exchange. The same logic works for music: round one covers balance and big decisions, round two covers fine detail.

Put the rules in writing

Clariva’s revision-policy guide says an agreement should define the included rounds, what counts as a revision, a client response window, extra-round pricing, and written approval before any out-of-scope work. The AIGA standard design agreement, written for a different creative trade, takes the same stance: revisions or additions beyond the described services are additional services, and client-caused delays in approvals or materials can move the schedule. Borrow the idea, and have a lawyer review your own terms if the stakes are high.

A short paragraph in your proposal is enough:

Your project includes two rounds of revisions. A round is one consolidated list of notes on one version. Please return notes within five business days. Additional rounds or changes to the agreed scope are quoted before we begin.

Put in your own numbers. The point is that nobody is surprised later.

How to ask for feedback that you can use

How you deliver a file shapes the notes you get back.

Send context with the mix. Violet Recording recommends sending the first mix with context and setting a feedback window. Say what you focused on, what you chose to leave alone, and when you need notes.
Label the version. Every file gets a clear name and version number so every note points at something specific. Sound On Sound suggests incremental filenames for project files and bounces, which also lets you roll back if the client prefers an earlier draft.
Ask for one list. Ask everyone on the client side to compile their comments before sending. Three people sending three emails is how contradictions arrive.
Ask for timestamps. Timestamps let producers find and address specific audible concerns quickly, instead of hunting through a file.
Ask for the outcome, not the fix. A good note describes what the client hears and what they want, and leaves the technical solution to the mixer, as MixMasterPro’s guide on managing mix notes puts it.

What a good note looks like

The difference is easy to see side by side.

Weak note	Strong note
“Make it more exciting.”	“At 0:18 the lift covers the spoken line. I want the line clear and the build still obvious.”
“The middle feels slow.”	“Between 12:10 and 13:40 we repeat the point from earlier. Can we cut that section?”
“Vocals are wrong.”	“The vocal gets lost in the second chorus. I want it to stay in front of the guitars.”
“Turn the bass down 3 dB.”	“The low end feels heavy on my laptop speakers in the verse. Can we check it?”

The first two pairings echo examples from Mix & Meaning, which recommends attaching every note to a clearly identified version with a timestamp, a description and a priority, and from Pristine Podcasts, which says constructive podcast feedback replaces a general feeling with a location and an action.

Adjust for who you are talking to

Not every client is an engineer. Nomograph Mastering advises that younger or non-technical artists shouldn’t be asked for “notes”, which can cause anxiety, but rather how the music feels. Then translate that feeling into a technical decision yourself. Audio professionals who ask the right way get more honest answers.

How to respond to vague, conflicting or subjective notes

This is where etiquette is tested. The client says something you can’t act on, or two stakeholders disagree, or the note would hurt the record.

Don’t guess, ask

TrackBloom advises against guessing at notes like “more energy”. Ask which element and which section the client means, then offer concrete alternatives. Their sample wording works well:

“When you say it needs more energy, are you referring to the drums, overall loudness, or dynamics? Can you point me to a specific section?”
“When you say ‘warmer,’ do you mean more low-mids or less harshness in the highs?”

These questions treat the client as the expert on what they want and you as the expert on how to get there.

Keep their words, then interpret

MixMasterPro suggests you preserve the client’s wording, interpret it before making mix decisions, and explain pushback by focusing on outcomes and offering options. In practice, copy the original note into your tracking list and write your interpretation beside it. If you read it wrong, the client can see exactly where the misunderstanding happened.

Push back with outcomes and options

When a request is technically problematic or outside the agreed scope, the same guide says to explain the audible consequence and offer alternatives, rather than refusing outright or agreeing against your best judgment.

Compare two replies to a client who wants the vocal 6 dB louder:

Poor: “That will sound bad.”
Better: “If we raise the vocal that much, the snare will lose its snap in the chorus. Here are two versions: one with the vocal up 2 dB, one with the vocal up and the guitars rebalanced. Which feels closer?”

The second reply doesn’t say no. It lets the client hear the tradeoff.

Conflicting notes from several people

Don’t pick a winner yourself. Send back a short message: “Two notes conflict at 2:40: one asks for the pad louder, the other wants it out. Can you confirm which direction before I make the next version?” One person on the client side should own final approval. Ask who that is at the start.

When the tone turns sour

e-Magic USA recommends acknowledging the client’s concern, asking for the specific audible problem, separating criticism of the work from personal insults, and calmly restating boundaries if behavior becomes abusive. Criticism of a snare sound is feedback. Criticism of you is something else, and you can say so politely and move on.

Etiquette when you give feedback to clients

Sometimes the producer or engineer is the one with the note: a client’s vocal take is out of tune, their script rambles, their reference track is clipped. Respect matters even more here.

SoundBetter’s guidance for working with clients is to check your ego at the door, stay patient and kind, and treat feedback as an objective service to the client’s vision instead of a personal critique.

A few practical habits:

Frame concerns as questions. Audio professionals can focus on what they hear and the desired outcome, rather than calling something wrong. “I’m hearing some harshness around 3 kHz on the vocal in the bridge. Is that the sound you want?” invites a conversation.
Start with what works. Matthew Weiss argues in ProSoundWeb that engineers should first identify what the client likes in a rough mix, because preserving the client’s intention matters more than imposing your own aesthetic.
Be specific and bundle. The same rules you ask of clients apply to you: timestamps, one list, clear outcome.
Offer a choice. “I can fix this in the edit, or we can re-record the line. Which do you prefer?”

Organize notes, versions and approvals

Etiquette collapses when the paper trail does. A simple routine keeps everyone calm.

Receive notes in one place, never scattered across text messages.
Acknowledge each note and confirm your interpretation. Violet Recording suggests acknowledging and confirming every note before making changes.
Make all changes together and send one new version per round, not a stream of tiny fixes.
Record which version was approved, and by whom.

Teams that handle many concurrent projects often borrow tools from other fields. Looking at team collaboration and approval workflows from social media management gives a good picture of how shared review and sign-off stages keep several people aligned. The same ideas apply to audio rounds.

If you want to go deeper on the mechanics, our own guides cover how to track every mix and master, how to run a timestamped feedback process and how to resolve client comments in one edit pass.

Wording you can steal

Situation	Say this
Note is vague	“Can you point me to the section where you hear that? A timestamp is perfect.”
Note could hurt the mix	“I can do that. Here’s what it will do to the vocal. Want to hear it both ways?”
Client sends notes in pieces	“To keep this round clean, could you send everything together by Friday? I’ll deliver one version after.”
Request is out of scope	“That’s beyond the two rounds in our agreement. I can quote it as an extra round, or we can swap it for one of the remaining changes.”
Client approves, then changes mind	“Version 3 was approved on the 14th. I’m happy to start version 4 as an additional revision. Here’s the quote.”
You have a concern about their work	“I’m hearing some clipping in the second verse. Is that intentional, or should we look at it?”

Our perspective: make feedback the easy part

We built Audome because we kept watching good relationships get strained by bad logistics. A client is never rude because they want to be. They email “the chorus feels off”, you reply asking which version, they send a voice memo, and three days disappear.

Our view is that etiquette should be built into the process so nobody has to remember it. Clients should be able to open a link, play your audio at full quality, click the waveform where something bothers them, and type a note. They shouldn’t need an account to do it. Each note should sit at a timestamp on a specific version. You should be able to cap the revisions you included and bill for extras without an awkward conversation, because the rules were visible from the first file.

In our experience, the politest thing you can do for a client is make giving feedback effortless. The second politest is to make your own response visible: which notes you’ve addressed, which you’ve questioned, which are waiting on them.

— Kreg

Put it into practice with Audome

If you want this structure without stitching together email, chat and cloud folders, Audome gives you a single place for it. Clients can leave time-stamped comments on the waveform without logging in, you can share lossless audio up to 96kHz/24-bit, versions are tracked automatically, and you can set revision limits and bill for paid revisions through Stripe.

Plans start with Studio at $12.50 per month or $150 per year, and Pro is $48 per month or $576 per year. See the plans on our pricing page or look at how Audome works.

FAQ

What is good client feedback etiquette for audio producers?

Be specific, be timely and be kind. Ask clients for timestamped notes in one consolidated list per round, describe problems by what you hear rather than who is wrong, and confirm your interpretation before you change anything. Agree on revision rounds in writing beforehand.

How do I handle a client who gives vague notes like “make it pop”?

Don’t guess. Ask which instrument and which section they mean, and whether they want more level, more brightness or more impact. Then send two concrete options so they can react to something they hear. TrackBloom’s examples show how to phrase those questions.

How many revision rounds should I offer?

Two is a common starting point for podcasts, with the first for structural changes and the second for polish, according to Pristine Podcasts. The right number depends on your fee and project size. What matters is that you state it, along with the price of extra rounds, before work begins.

How do I say no to a client’s request without damaging the relationship?

Explain the audible consequence, then offer alternatives. Saying “that will make the snare disappear in the chorus, here are two ways to get the lift you want” keeps the client in control of the decision while you protect the record.

Should clients need an account to leave feedback?

It helps if they don’t. Every login screen is a reason for a note to arrive by text message instead. A link they can open and comment on directly keeps the feedback attached to the right version and the right moment in the audio.