Make the next decision easier
“Can the vocal pop more?” is a useful starting impression. The next step is to explain where that impression occurs and what is hard to hear. The engineer can then evaluate a specific moment without guessing whether the note concerns the whole song.
A revision note does not need specialist vocabulary or a prescribed compressor setting. It needs enough context for another person to hear the problem and understand the desired result.
Give each note four anchors
- Version and location. Name the file revision, then give an elapsed timestamp, bar number or exact range. If using timecode, include its frame rate and timeline origin.
- Observation. Describe what you hear: the final word disappears, the snare becomes sharp, or the bass masks the kick.
- Desired result. Explain what should become clearer. Offer a processing suggestion only when it is useful, and leave room for the engineer to solve the cause differently.
- Priority. Separate approval-blocking issues from optional experiments. Agree on the labels before reviewing a long list.
A format you can reuse
File: Song_Mix_v07.wav
Position format: elapsed minutes:seconds from file start
01:24 | Must fix | Verse 2, last vocal phrase gets masked
Desired result: keep the words clear as the guitar enters.
Suggestion: try a short guitar ride before lifting the whole vocal.
02:47 | Optional | The final "s" sounds sharp on headphones
Desired result: soften that syllable while keeping the phrase bright.The example uses elapsed time, not SMPTE timecode. Saying which convention you use prevents a timestamp from landing on the wrong moment after a pre-roll or export-range change.
Review once for content, once for contradictions
Listen through without stopping and note the larger impression. On the second pass, check each timestamp and consolidate repeated observations. “More bass everywhere” and “less bass in the chorus” may be compatible, but the difference should be explicit.
Avoid making ten nearly identical notes when one section-level instruction explains the issue. Conversely, do not merge unrelated issues into a paragraph that leaves the engineer unsure when each one has been resolved.
Before sending, play the marked moment from the same export the engineer will receive. Include the listening context if it matters, such as speakers versus headphones, and identify any reference track by version.
Keep the note with the audio revision
UTUVO Player Pro supports timecoded review notes and severity tags, with report export in the review workflow. The timecoded notes lesson shows the existing process.
The tool preserves location; the reviewer supplies judgment. Confirm the timestamp, revision and wording in the outgoing report, then record how each must-fix item was addressed. That gives the next review a clear starting point instead of another unstructured list.