How to Give Feedback on a Master
Most revision requests I receive fall into one of two categories. The first is specific and actionable. The second is the kind that sends both of us in circles for a round or two before we find our way to the same place.
This is not a criticism. Giving feedback on a master is a skill, and nobody teaches it. Here is what actually helps.
Start With a Reference Point
Before you say anything about the master, ask yourself what you are comparing it to. Your own expectation of how the record should sound is valid, but it is also invisible to me. A reference track is not invisible.
If the low end feels wrong, tell me what low end you are going for and point me to a record that has it. If the master feels too compressed, show me something that breathes the way you want this to breathe. Reference tracks are not admissions that your record is not original. They are communication tools. They give us shared vocabulary and a shared target.
A good reference track is in a similar genre, has a similar arrangement density, and was released in the last five to ten years if streaming translation is a concern. Older references can be useful for feel and character but may not reflect modern loudness and platform normalization realities.
Describe What You Hear, Not What You Want Done
The most useful feedback describes a perception, not an instruction. There is a meaningful difference between these two things:
"Can you boost the high end?" is an instruction.
"The top end feels a little closed or dark compared to the reference" is a perception.
The first tells me what to do. The second tells me what you are hearing, which may lead to a completely different solution than boosting the high end. Sometimes what sounds dark is actually a low-mid buildup. Sometimes what sounds compressed is actually a mix issue that mastering cannot resolve. When you describe what you hear, I can tell you whether what you are hearing is something mastering can address, and how.
Use your ears, not your meters. If something feels wrong, trust that. You do not need to know the technical reason.
Be Specific About Where
Vague feedback applies to the whole record. Specific feedback applies to a moment.
"The low end is too heavy" tells me something. "The low end is too heavy in the verses, especially in the first thirty seconds before the drums come in" tells me much more. I can go back to that exact moment and evaluate what is happening. Is it the kick? The bass? A low-mid resonance in the room ambience? Is it only happening on certain playback systems?
Timestamps help. If something jumps out at 2:14, write down 2:14. It costs you nothing and saves both of us time.
Tell Me What System You Are Listening On
This is one of the most underused pieces of feedback in the revision process, and one of the most useful.
A master that sounds bass-heavy on consumer earbuds may be perfectly balanced on a flat reference monitor. A master that sounds bright on laptop speakers may be exactly right on a calibrated system. Context does not change whether something is correct, but it helps me evaluate whether what you are hearing is a mastering issue or a playback issue.
Tell me if you are listening on AirPods, car speakers, studio monitors, a Bluetooth speaker, or your phone. Tell me if you checked it in multiple places. The more I know about where you heard the problem, the more accurately I can evaluate whether the problem is in the master.
Distinguish Between What You Want Changed and What You Are Unsure About
These are different conversations and they deserve to be treated differently.
If something is clearly wrong to you, say so directly. "The snare feels buried in the chorus" is a clear note. I will address it.
If something feels off but you cannot articulate why, say that instead. "Something about the midrange feels uncomfortable to me but I cannot put my finger on it" is useful information. It tells me where to focus my listening rather than sending me in a direction that may not be the right one.
The revision process works best when it is a conversation, not a list of adjustments. If you are uncertain, say you are uncertain. We can figure it out together.
What Mastering Can and Cannot Address
This is worth understanding before you write your notes, because it changes what you ask for.
Mastering works on the stereo mix as a whole. Every adjustment I make affects the entire signal simultaneously. If the kick drum is too loud relative to the snare, I cannot surgically address that relationship the way a mix engineer can, anything I do in that frequency range affects everything else sitting there at the same time. Multiband processing and careful dynamic control can get closer than a broadband move, but there are limits to how far that goes before the rest of the record starts paying for it. If the imbalance is significant, the mix is the right place to fix it.
What mastering can address: overall tonal balance, low end weight and extension, high frequency air and presence, stereo width and imaging, loudness and dynamic control, inter-track consistency across an album, and translation across playback systems.
What mastering cannot address: individual element balance, timing issues, tuning problems, distortion baked into the recording, phase issues between individual tracks, and anything that requires access to the individual tracks.
If a revision request touches something in the second category, the right answer is to go back to the mix. That is not a failure. It is just the correct sequence. A strong mix is what makes a great master possible. Preparing your mix well before it reaches mastering is the single most effective thing you can do for your final result.
On Revision Rounds
Most projects are approved on the first pass. That is not because clients are settling, it is because the communication at the front end was strong enough that the master lands where it should before revisions are needed.
When revisions do happen, they are most efficient when the feedback is consolidated. One round of specific, considered notes is more productive than three rounds of incremental reactions. Listen to the full master before writing anything down. Live with it for a day if the timeline allows. Then write your notes.
The goal is not to get to zero revisions. The goal is to get to a master that is exactly what the record needs.
Ready to get started? Submit your project here.
