Sending revision notes is part of the mixing process: clear feedback helps a mixer understand what to change while preserving what already works. Use a consistent format that ties each request to a place in the song, describes the desired result, and records which version you reviewed.
Start with the right listening setup
Before writing notes, make sure you are reviewing the same mix version and listening in conditions that let you judge it fairly. A note about a vocal feeling too loud is only useful if you know which file you heard and whether the level difference persists across playback systems.
Confirm the version
Ask the mixer or project lead for a clear version label, such as SongTitle_Mix_v03_2026-11-11.wav.
Save the file with that name and record it at the top of your notes.
If the filename is ambiguous, confirm which version is current before commenting.
Do not combine feedback on two different mixes in one document.
Keep earlier versions in a separate archive rather than overwriting them. This makes it easier to compare revisions and recover an earlier direction if a change does not work. If the project uses a shared folder, avoid renaming or moving files that another person may be using; agree on a naming convention first.
Listen once before editing the mix
Make one uninterrupted pass without stopping to write detailed instructions. Note broad impressions such as whether the vocal is intelligible, whether the chorus lifts, and whether the ending feels complete. Then listen again and capture specific moments.
Use the main listening setup you trust, such as your regular studio monitors or headphones, at a comfortable level. Check a few sections on another familiar system if translation is a concern, but treat those checks as comparisons rather than separate mixing targets. Consumer speakers and headphones can color bass, treble, and stereo width, so a problem that appears on only one unfamiliar device may not call for a mix change.
Turn reactions into actionable requests
A useful note connects a location, an observation, and a desired result. Avoid asking for a specific plugin setting unless you are directing the mix yourself and know why that setting is needed. The mixer can choose the method that fits the session.
Use this simple pattern:
Location: 1:12, second verse
Observation: The lead vocal is hard to understand when the guitars enter.
Request: Bring the vocal forward slightly in this line, while keeping the guitar tone and level elsewhere.
The observation explains the listening problem; the request describes the outcome. “Make it warmer” or “fix the vocal” leaves too much interpretation. Add a comparison or a musical reference when it helps: “Keep the vocal as present as in the first verse, but soften the consonants in the second line.” References are useful only when everyone knows the same recording or section.
Use precise locations
Include a timestamp in the reviewed mix.
For a request that spans a phrase or section, give a range: 1:12–1:19.
If the song has clearly labeled sections, include both, such as second chorus, 2:08.
A timestamp alone can be unreliable if the arrangement or edit changes, so section names and a short lyric fragment can provide backup.
When the change is global, say so explicitly: “Across the full song, reduce the brightness of the doubled backing vocals slightly.” If the problem occurs only in one spot, state that too. This avoids a local fix being applied to every section, or a global change being mistaken for a one-time automation adjustment.
Describe the outcome, not just the symptom
Translate subjective impressions into something another person can listen for. “The bass feels muddy” might mean the kick and bass mask each other in the chorus, the low notes blur together, or the bass lacks definition on small speakers. State which effect you mean and where it occurs.
| Instead of | Try a more useful note |
|---|---|
| “More energy” | “The chorus feels smaller than the verse; can the drums and backing vocals lift slightly in the chorus?” |
| “The vocal is weird” | “At 0:48, the lead sounds thinner than in the previous line; please check the transition.” |
| “Less reverb” | “At 2:14, the last word trails over the next lyric; shorten or reduce that vocal tail.” |
| “Make the bass bigger” | “In the second chorus, give the bass more definition without adding weight to the kick.” |
Use tentative language when you are uncertain about the cause: “Could you check whether the backing vocal is masking the lead around 1:30?” This communicates what you hear without prescribing a technical fix that may not solve it.
Prioritize notes and manage conflicting feedback
A long list of equal-weight requests can obscure the changes that matter most. Group notes by importance and topic so the mixer can work through them efficiently. A practical order is:
- Must fix: an obvious edit, click, wrong lyric, missing part, or mix issue that blocks approval.
- High priority: a clear balance, intelligibility, or arrangement-support issue affecting the song.
- Optional: a taste change that could improve the mix but is not essential.
Separate mix feedback from production or arrangement requests. “Raise the harmony” is a mix request; “add a harmony to the final chorus” changes the production. If a request requires new recording, editing, or a changed arrangement, flag it so the team can agree on the work and timing before the next mix.
Resolve disagreements before sending
If several people are reviewing, ask them to submit notes to one coordinator or agree on one consolidated list. Two reviewers may give opposing instructions—for example, one asks for a brighter vocal while another asks for less high end. Keep both opinions visible during discussion, but do not send contradictory requests as if they were settled.
The lead artist, producer, or other agreed decision-maker should resolve conflicts. When the group cannot decide, identify the issue as a question and request a comparison between two restrained alternatives. Avoid asking for many versions at once; that can create unnecessary work and make the choice harder.
Build a repeatable note-taking workflow
A simple document or spreadsheet is usually enough. Choose a format everyone can open and keep one authoritative copy for each revision round. A shared document works well for comments and discussion; a spreadsheet is useful when there are many notes to track.
Suggested fields include:
- Mix version and review date
- Reviewer or coordinator, if the team needs to track ownership
- Timestamp or song section
- Observation and requested outcome
- Priority: must fix, high, or optional
- Status: open, addressed, or needs clarification
- Follow-up note after hearing the next version
Listen through in order and enter notes as they arise. After the pass, combine duplicates, clarify wording, and sort notes by song order. Keep one row or bullet per distinct request; splitting “raise the vocal and reduce the guitar” into separate notes can help the mixer address and report each change independently.
Do not treat status labels as proof that a request is complete. When the new mix arrives, listen to the relevant locations and mark each item based on what you hear. If a change was attempted but the problem remains, describe the remaining issue rather than repeating the original note verbatim.
Choose a delivery method that preserves context
Send the notes in the format agreed with the mixer. A clean email or shared document is usually sufficient for a modest list. A spreadsheet can help with a large project, while time-coded comments in a collaboration tool can make locations quick to access. Confirm that recipients can open the document and that comment permissions are appropriate; do not assume a link is public or accessible to everyone.
If you annotate audio, use a method that makes comments easy to connect to the mix. A short screen recording or voice memo can help explain a complicated musical transition, but pair it with a written summary of the key requests. Audio messages are harder to scan, search, and track, and speech can be ambiguous when the listener is not looking at the same timeline.
For each revision round, send one consolidated set of notes with the reviewed mix filename or version number. If you need to add a late correction after sending, label it as an addition and identify the version again. Avoid sending a sequence of unmarked messages that leaves the mixer unsure which instruction is current.
Include playback or equipment details only when relevant
If a note concerns a specific monitoring setup, mention it briefly: for example, “The low end seems heavy on my closed-back headphones; I also heard the same balance issue on my monitors.” Include the model only if it helps reproduce the observation. Do not imply that a particular speaker or headphone is a universal reference.
For equipment-specific questions—such as routing, level controls, or safe handling—follow the manufacturer’s instructions for the device. Compatibility matters when sharing project files: the recipient may need the same audio format, sample rate, session software, or plug-ins to open a session. For mix feedback alone, a clearly labeled stereo file is often easier to review than a full session, but confirm the expected delivery format with the mixer.
Review the next version without reopening every decision
When a revision arrives, compare it with the previous mix at a similar playback level. Louder versions can seem better even when the actual change is not. Listen to each requested location and check whether the intended result was achieved and whether it created a new problem elsewhere.
Keep the follow-up focused. If the vocal is clearer but now too prominent across the whole song, say that and identify whether the issue is global or limited to a section. If the request was addressed, mark it complete. If you changed your mind after hearing the result, state the new preference clearly and recognize that it is a new direction.
Some decisions cannot be settled from one listening environment. Low-frequency balance, stereo width, and subtle effects can translate differently across rooms and devices. If playback systems disagree, describe the difference and ask the mixer to check translation; avoid prescribing an extreme correction based on one speaker. Similarly, a mix cannot fully repair a performance, source recording, or arrangement issue. If the problem appears to come from the recording itself, ask whether editing, another take, or a production change is feasible before treating it as a simple balance adjustment.
A useful revision note should be easy to find, easy to understand, and possible to verify in the next mix. Keep the version label, timestamp, observation, request, and priority together, then maintain a short status for each item. This gives the mixer room to solve the problem while keeping the project’s decisions clear.