Write Mix Notes

---
name: write-mix-notes
description: Use when documenting mix revision requests, feedback sessions, or communicating changes between mixer and client
source: AES (Audio Engineering Society) professional workflow standards, major label mix revision practices
tags: [music, mixing, revision, feedback, workflow, communication, timestamped-notes]
verified: true
---

# Write Mix Notes

Produce precise, actionable mix revision notes that a mixer can implement without a follow-up call.

## Why This Is Best Practice

**Adopted by:** Major label A&R and professional mixing workflows; AES publishes professional communication standards for studio collaboration
**Impact:** Professional studios report that vague mix notes (e.g., "make it bigger") are the leading cause of unnecessary revision rounds, each costing 2-4 hours of mixer time

**Why best:** Ambiguous mix notes waste everyone's time. "More energy" is not actionable; "raise the snare by 2dB from bar 17 onward" is. Notes that include timestamps, element names, reference tracks, and directional descriptors (more/less, brighter/darker, wider/narrower) eliminate interpretation errors. Structured notes also create a record of creative decisions for future reference.

## Steps

1. **Listen to the full mix twice before taking notes** — First pass: global impression (balance, tone, emotional impact). Second pass: detailed feedback with timestamp tracking. Never write notes on the first listen.
2. **Use timestamps for every note** — Format: `[MM:SS] Element — Issue — Direction`. Example: `[1:32] Lead vocal — too quiet in the chorus — raise 1-2dB relative to the kick.`
3. **Name elements specifically** — "Guitar" is ambiguous; "right-panned electric guitar" is not. Use the same element names the producer/mixer uses.
4. **Use comparative descriptors** — Compare to a reference: "The snare should have more crack — reference: chorus of 'Levitating' by Dua Lipa." Avoids subjective interpretation.
5. **Separate "must fix" from "nice to have"** — Mark each note as Priority 1 (must change before approval) or Priority 2 (optional improvement if time allows).
6. **Include a global note** — One paragraph summarizing the overall mix direction: what's working, what the core issue is, and the emotional target. This contextualizes all specific notes.
7. **Attach a reference track** — Include one or two commercially released tracks that represent the target sound. Specify what specifically to reference (low end, vocal presence, reverb length).
8. **Confirm scope of revision** — State explicitly what NOT to change; prevents a mixer from inadvertently fixing things that were already approved.

## Rules

- Every note must be actionable without a follow-up question — if a note requires interpretation, rewrite it.
- Never send notes without timestamps — "the chorus" is not a location; `[1:15-1:47]` is.
- Limit revision rounds to 3 before escalating to a listening session — accumulated notes across 4+ rounds indicate a communication failure, not a mixing failure.
- Positive notes are not optional — confirming what's working prevents a mixer from inadvertently changing approved elements.

## Examples

Good note: `[2:05] Background vocals — the "oohs" are washing out the lead in the second chorus. Bring them down 3dB from 2:05 to 2:22. They are correct in the first chorus.`

Bad note: `The background vocals are too much in places.`

Global note example: "The mix is sitting well overall. The main issue is low-end clarity — the kick and bass are competing between 80-120Hz, making the bottom feel muddy on headphones. Reference the low end of 'As It Was' (Harry Styles) for the separation we're going for. Do not change the vocal or guitar levels — those are approved."

## Common Mistakes

- No timestamps — mixer spends 30 minutes finding the moment the client means; resentment and missed notes result.
- Prescribing the solution instead of the problem — "add a 3kHz boost" presumes the mixer's solution; "the vocal sounds dull in the bridge" states the problem and lets the mixer solve it.
- Sending notes after one listen — first-listen impressions are often wrong; the second listen reveals which issues are real.
- Approving a mix with outstanding Priority 1 notes to "be polite" — creates a released record with known flaws and no clear revision record.