Your client’s Dropbox is littered with “v12_FINAL_3.wav.” The label wants one more tweak. The artist just texted you at 11 PM: “Can we bump the snare 0.25 dB?” Meanwhile, you quoted this as a two-round project, you’re eight rounds deep, and the mastering engineer is waiting.
If you don’t learn to close the door on revision creep, you’ll burn your margins, blow your schedule, and train clients to treat your revision policy as a suggestion. Here’s a straightforward playbook for knowing when a mix is finished — and how to keep clients happy without hitting version 27.
Why Client Revisions Never End
| Culprit | What’s Really Happening | Fix |
|---|---|---|
| Ear Fatigue | Client listens on repeat for hours—perspective warps, tiny details feel huge. | Require 24-hour gap between listens before sending notes. |
| Decision Fear | Artist/exec worries the “perfect” mix is one tweak away and doesn’t want to commit. | Clear reference targets set upfront + hard deadline. |
| Too Many Cooks | Five people sending notes separately = endless conflicting loops. | Single point-of-approval; all feedback funneled through one person. |
The pattern is always the same: when there’s no structure, clients fill the void with more notes. Your job is to build the structure before it gets to round four.
The “95 Percent Rule”
Once your mix nails clarity, vibe, translation, and technical compliance, you’re in the 95% zone. Everything after that is taste refinement, not technical improvement — and the streaming audience won’t hear the difference.
Your “done” checklist:
- Vocal sits clearly on phones, cars, and monitors
- Kick/bass relationship locks in mono
- LUFS target hit (-8 to -10 for pop/urban; -12 for acoustic)
- Peaks ≤ -1 dBTP, no clipping on meters
- No distracting clicks, pops, or edit seams
If every technical box is checked and the mix matches the approved references, you’re done. Everything beyond this point is opinion, not correction. Learn to recognize when the client is chasing feelings instead of fixing flaws — and know when to call it.
A Hard-Stop Revision Policy (Use This)
The single best way to prevent endless revisions is to set the policy before you start the project. Not buried in a contract nobody reads — stated clearly when you take on the work.
Here’s a framework that works:
1. Three-Pass Maximum
Initial delivery, one creative round, one polish round. Anything beyond that is billed hourly or declined. Make this explicit in your proposal.
2. Time-Stamped Notes Only
If the client’s feedback doesn’t reference a specific timestamp or section, it’s too vague to act on. Require precise notes: “vocal at 1:32 feels buried” instead of “the vocal needs more energy.”
3. 24-Hour Cooling Period
After the second revision round, require the client to sit with the mix for 24 hours before sending final notes. This kills the impulse-driven changes that come from listening on repeat for three hours straight.
4. Single Decision-Maker
The artist designates one person — manager, producer, A&R — to collect and deliver all notes. No side emails. No separate messages from the featured artist’s team. One channel, one voice.
5. Sign-Off Documentation
Final bounce gets delivered with a simple sign-off form. Client confirms approval in writing. Once signed, the project is closed. No take-backs two weeks later when someone’s cousin has thoughts.
Spotting Red-Flag Revision Requests
Not all revision requests are actually revisions. Learn to identify when a client is asking for something outside scope.
“Can we try a completely different drop?” Translation: New production work, not a mix adjustment. This is a re-work, not a revision. Flag it as additional production and quote separately.
“Let’s bump the vocal 0.3 dB at 1:44.” If this is the first time they’ve mentioned it and it’s a legitimate balance issue, fine. If you’re on version 12 and this is hair-splitting, invoke your hard stop. Explain that at this stage, you’re chasing diminishing returns.
“Make it more ‘sparkly’ but also warmer.” Conflicting descriptors = unclear vision. Ask for a reference track that demonstrates what they mean, or politely decline to chase contradictory goals.
Using TrackBloom to Keep Audio Engineer Mix Revisions Under Control
A clean revision process needs a single channel where everything is tracked. When clients send notes via email, text, WhatsApp, and voice memo, you lose the thread — and you can’t prove what was or wasn’t requested.
TrackBloom handles this at the file intake stage:
- Clients upload stems and references to a single organized link before the project starts
- Time-stamped feedback keeps notes specific and actionable
- Version tracking prevents confusion about which file the client is reviewing
- Clear revision rounds documented in one place
When the workflow is structured from day one, clients adapt to it. The revision chaos doesn’t happen because the infrastructure doesn’t allow it.
Mastering Prep: The Final Technical Gate
Before you call the mix done, run this 60-second pre-master checklist. If it passes, you’re finished — anything else is subjective preference, not technical necessity.
| Item | Target |
|---|---|
| Peak headroom | -1 dBTP |
| Integrated LUFS | Match genre standard (-8 to -12) |
| Noise floor | ≤ -60 dB |
| Fade tails | No abrupt cut-offs |
| Stereo field | ≤ 30% sides below 80 Hz |
Pass every metric, print the 24-bit WAV, send it to mastering, and close the session. The mix is done. Anything after this is rework, not revision.
The Psychology of Calling It
The hardest part of calling a mix done isn’t technical — it’s psychological. Clients want perfection. You want to deliver excellent work. But perfection doesn’t exist, and chasing it destroys timelines and margins.
Here’s the truth: the pros aren’t better at mixing. They’re better at stopping.
They know when the mix serves the song. They know when further changes are lateral moves, not improvements. And they know how to communicate that to clients without sounding dismissive.
When a client pushes for version 13, the response isn’t “no.” It’s: “We’ve hit every technical target, the mix matches the references you approved, and we’re well past the point of meaningful improvement. If we keep going, we risk over-working it. I’m confident this is ready.”
That’s not refusing to work. That’s protecting the project — and protecting your time.
Your Revision Process Is Part of Your Service
Clients who work with engineers that have clear processes trust those engineers more. When you set boundaries, communicate them professionally, and stick to them, you’re not being difficult — you’re being a professional.
The engineers who build sustainable practices aren’t the ones who say yes to every client request. They’re the ones who know when to say “this is done” and mean it.
Start with the three-round policy. Add the single-approval-point rule. Require time-stamped notes. Run the technical checklist before delivery. The whole system takes ten minutes to explain and saves you from weeks of scope creep.
And if you want to handle file intake and feedback with structure from the start, TrackBloom gives you a free client intake link where everything arrives organized before you’ve even opened the session. When the project starts clean, it’s easier to finish clean.
Ship the mix. Close the project. Move on to the next one.