Name the exact version first.
Begin each feedback message with the song title and precise mix filename. ‘Notes for SongTitle_mix02.wav’ is more useful than ‘the latest mix’ when several versions are circulating. Keep notes for each export together.
Listen once without stopping and describe the overall direction. Then listen again for specific moments. This is a suggested review workflow, not a service policy or a promise about included revisions.
Use timestamps and an observation.
Identify where the issue happens, what you hear and the result you want. Example: ‘0:42–0:50, hook lead: I lose the last words behind the instrumental. I want the lyric to stay clear without changing the energy.’
That gives the engineer room to solve the problem. ‘Boost everything’ does not identify the desired result. A technical guess is optional; a clear listening observation is the important part.
Separate corrections from experiments.
Label essential changes separately from ideas you would like to test. An incorrect vocal take is a different priority from a wider ad-lib effect. State which existing parts should stay unchanged.
Combine collaborator feedback into one agreed message. Where people disagree, identify the unresolved question instead of presenting contradictory instructions.
Keep a revision log.
Use one line per note: version; timestamp; element; observation; desired result; priority. Save the response and next filename beside it. Check each requested change against the new version.
Download the feedback template. Confirm the revision allowance before work begins. For a new project, follow stem preparation and the mixing request process.