Running Client Feedback Rounds
Turn a vague note into actionable items, change one class of problem per round, and accept against the same standard.
Related
When a client says it feels wrong and you ask what feels wrong, that round is already wasted. A feedback round turns a feeling into a timecode, a category and an acceptance test, then changes things in batches instead of chatting through each tweak.
Collect: anchor the feeling to a timecode
Do not touch the session when the notes arrive. Ask for a timecode, a reference and one sentence of intent: the chorus at 0:48 does not open up, the reference is a particular song's chorus, the vocal should sit further forward. With those three, the problem can be located. If the note is only 'make it more premium', send two versions, one wider and one more dynamic, and let the client choose before you edit. Text, voice notes and screenshots all work, but everything ends on one shared revision sheet with numbers, timecodes, priority and owner.
| What the client says | What it may mean | An actionable change |
|---|---|---|
| Too full | Midrange stacking, unclear layers | Remove a layer or clear the lead's midrange |
| Not premium enough | Flat dynamics, thin tone | Add section contrast, choose a richer sound |
| Vocal unclear | Sibilance, masking, level | Check masking around 2 to 4 kHz first |
| The ending is odd | Tail cut or fade too short | Restore the reverb tail, redo the fade |
| Does not match the reference | Different low end or space | Match loudness, then compare both |
Change: one category per round
Group the sheet by type: structure, arrangement, timbre, level, effects. Handle one group per round and freeze the rest. Only then can the next listen be attributed, and nobody argues that changing the vocal also moved the drums. Save a snapshot before each round with the round number and date, and export a comparison version at the end while keeping the previous one. New requests go to the next round rather than jumping the queue, or the work never closes.
Accept: three conditions at once
Acceptance is not about the client's tone of voice but three conditions: every item on the sheet is closed; an A/B against the previous version at matched loudness shows only the agreed changes; and a final listen against the original brief and delivery spec shows nothing drifted. Sign only when all three hold. Anything raised after sign-off is a new round with new scheduling or a new fee. That is a professional boundary, not unfriendliness.
Stop: unclear scope means endless rounds
Endless rounds usually come from an unclear scope rather than a difficult client: how many rounds, what each covers, what happens beyond them. When approved parts get reopened or the reference changes every round, pause and reconfirm the brief; that saves more time than another edit. Feedback rounds govern process, not taste. When the two sides define good differently, align on references before discussing changes. The other failure is accepting everything: requests that contradict each other leave nobody satisfied, and the right move is to state the trade-off rather than implement every note.
Listen in the library
All tracks from midicn-lib — inline badge is the license tier (C1 commercial / C2 non-commercial / C3 study only).
Along the same line
Sources
- Bobby Owsinski, The Mixing Engineer's Handbook 关于修订、客户沟通与版本管理的章节
- Avid Pro Tools 与 Apple Logic Pro 官方文档中关于工程快照、注释与导出版本的说明
- AES 关于混音修订与母带交付流程的会议文献