How to give a collaborator notes where they make sense

The track is at 90%, and it's been there for two weeks. The notes come in at 11pm as voice memos and WhatsApp lines, and they don't agree on what language they're in. One message says "make the chorus feel wider". The next one says "dip 250Hz on the rhythm bus". It takes a day to work out that they're both about the same problem.

Everyone involved knows what they're doing, and it's still the fifth round.

This post is about the notes, not the mix: what a note needs so the other person can act on it the first time, how notes get lost between versions, and what helps. Mix notes are where it starts, but the same goes for a note on a lyric, an arrangement or a master.

The last 10%

Tracks rarely stall because nobody knows how to fix them. They stall because the notes about them don't point at anything in particular.

A note like "the vocal needs to sit better" isn't wrong. It just doesn't say where. Is it the whole song or the second chorus? Is it level, or is it the 3k bump that only shows up when the guitars come in? Is it the reverb, the timing, or the line itself? You fix one of those, send it back, and it turns out they meant another one.

That's a round gone, and nobody did bad work in it. The note was read as something it didn't mean, so the fix went somewhere else. It also gets worse as you go, because by round four everyone is tired and the notes get shorter.

Who your collaborator is

"Collaborator" covers a lot of people. It might be the person who wrote the lyrics, a songwriter, a topliner you've never met in person, the producer, the mix engineer, whoever's mastering it, the artist you're writing for, or the other half of your duo. They all hear the track differently, and they all describe what they hear differently.

The lyricist says the line gets lost in the second verse. The mix engineer says the low mids are crowded. The mastering engineer says it's hot going into the limiter. Sometimes those are three problems. Sometimes they're one problem described from three different jobs.

Agreeing on vocabulary doesn't really fix that. You can't ask a topliner to describe a problem in frequencies, and you shouldn't have to translate a mix engineer's notes into how the song feels. What works across jobs is a note that points at something you can both find: a place in the song, a thing in it, and the version you were listening to.

What a good note points at

A note someone can act on the first time usually has three parts. There's a fourth that's optional, and it often saves the most time.

• A place. Which section, or which moment. "The second chorus" beats "the chorus", and "at 2:14, when the guitars come in" beats both. If it's the whole song, say so, because otherwise people assume it's local.
• A thing. What you're hearing, as specifically as your job lets you say it. A measurement if you have one ("the master is around −7 LUFS and the reference is closer to −9"), an element ("the snare reverb"), or a line ("I can't hear 'nothing left to say'"). If you have a suggestion, add it, but keep it apart from the observation. The other person can then disagree with your fix and still agree with the problem.
• A version. Which mix you were listening to. "Mix 4, the one from Tuesday." It sounds obvious until two versions are going around at once and half the notes are about the old one.
• "That's on purpose." Sometimes the most useful note says don't fix this. The vocal is low in the verse because the verse is supposed to feel far away. The kick is quiet in the intro because it hasn't arrived yet. Write it down once and the same argument doesn't come back every round.

Here's the same note twice. Before: "vocal needs to sit better". After: "Mix 4, second chorus from about 2:14: the vocal gets buried when the guitars come in. Feels like the 2–4k area, not level. The verse vocal is fine." The second one takes thirty seconds longer to write, and whoever reads it knows where to start.

None of this needs a tool. A section name, a timestamp and a version number in a message get you most of the way. The hard part is doing it every time, including at 11pm, when "chorus feels off" is all you've got the energy to type.

Versions are where notes go missing

Notes don't usually get lost inside a version. They get lost between them.

Version 3 gets twelve notes. Version 4 deals with eight of them and picks up two new ones. By version 5 nobody's sure whether the bridge note from version 3 was fixed or quietly dropped, so it either gets raised again or it doesn't, and it's still there in the master.

What helps is sending two lists with every new version:

• What changed. Not "some tweaks". The actual list: "pulled the guitars down 1.5dB in the chorus, new vocal comp on verse 2, cut the intro by four bars." Whoever's listening knows what to check, instead of spending the listen hunting for differences.
• Which notes it answered. Go through last round's notes and mark each one done, not done, or "left it, here's why". Anything not done carries into the next round in its original wording, so it doesn't get reinterpreted on the way.

It's tedious, and it's the part most worth keeping up. It also shows you quickly when the two of you are listening to different versions.

A shared doc or a long chat thread can hold both lists, and that's a lot better than nothing. The trouble is that the notes live somewhere other than the track, and other than whatever was measured on it. Every note still has to be carried back onto the audio by each person, every round. "Second chorus, 2:14" in a doc still means opening the session, finding 2:14, and hoping you're both on the same mix.

Where TuneLens sits

That gap is the one I've been building TuneLens around. It isn't where you send stems or run a live session, and tools for that already exist. It's the report you both have open when you're arguing about the second chorus.

You upload the track and get one report on it, covering the writing, production, mix and master, with the measurements and a ranked list of action items. Share the song and your collaborator sees the same report and the same numbers, and can play the same audio. When the next version goes in, the Version comparison shows what moved, and last round's action items are marked Addressed or Still needs work.

The notes go on the thing you mean. You leave one on an action item, a score, a loudness reading, a section on the bars along the waveform, or a moment in the track: click under the waveform at 2:14 and the note sits at 2:14, and clicking it takes the player back there. Type @ to mention your collaborator, they reply under it, and whoever deals with it resolves it. If an action item is flagged and it's a choice rather than a mistake, mark it "This is on purpose". The next time you run Analyze new version, the analysis is told you left it that way on purpose.

Open notes come with you to the next version, tagged with the date they were written, so the bridge note from version 3 is still there in version 5 until one of you resolves it. Deciding which notes the new mix actually answered is still your call. Resolving them as you go is how you keep that second list without a separate doc. When you sit down to do the next pass, the Notes button has every note on the song in one place, and you can narrow it to what's open, what mentions you, or what's new since you last looked. Click one and you're at the spot it's about.

If your collaborator is the one doing the next mix, they can upload it with Analyze new version themselves, on their own credits, and it lands in your song next to the earlier versions. When they've left notes while you were away, TuneLens shows you which songs have something new the next time you sign in. There's no email for it, so it's worth telling them where to look.

What this doesn't settle

A shared reference doesn't decide taste. Two people can look at the same measurement and want different things from it, and that's still a conversation, on a call or in a room, that no report replaces. The analysis doesn't know what you meant either. It measures and suggests, and it'll flag a deliberate choice the same way it flags an accident until somebody marks it.

What it does remove is the rounds lost to reading each other wrong: the note that meant the second chorus and got applied to the first, or the fix from version 3 that nobody can confirm happened.

What's in each plan: TuneLens pricing →