How to Get Your Mix Approved (Without Chasing Emails)

The revision loop isn't a talent problem

Most mix engineers assume that if a project goes through seven versions, it's because the mix wasn't good enough. Sometimes that's true. But more often, the real problem is that neither side has a shared understanding of what “approved” actually means.

The client says “sounds great” via text. You send the final file. Two weeks later they come back with “actually I was thinking about the vocals and...” That wasn't a revision — it was a miscommunication. You both thought the project was done, but you were never in the same place at the same time with the same understanding.

The endless revision cycle is a process problem. And process problems have process solutions.

Why “sounds great!” is not an approval

A real approval has three properties:

1. It's explicit.“Sounds great in the mix!” in a WhatsApp message is an opinion. “Approved” is a decision. They feel the same in the moment but mean very different things later.
2. It's tied to a specific version.If you've sent four versions and the client says they're happy, which version are they approving? If you don't both know the answer, you'll find out at the worst possible time.
3. It creates a record.“But I never approved the final version” is a lot harder to say when there's a timestamp proving otherwise.

The two-part approval workflow that works

You don't need complex software or a formal contract for every project. You need two things: a structured feedback channel and a clear approval moment.

Part 1: Structured feedback

All feedback needs to happen in one place, attached to the audio, with timestamps. This means no WhatsApp, no email chains with “around 2 mins”, no voice notes. Your client clicks on the waveform at the exact moment they mean and types their note there. Every comment is in context. Nothing gets lost. You can see exactly what still needs to be addressed before you start working.

Part 2: A formal approval status

Once the feedback is addressed, the project moves to a status your client actively confirms. Not “I think they're happy” — a status that reads Approved, tied to the specific version they've heard, with a timestamp. That's the finish line. Both sides know where it is.

How to handle the “I haven't heard it yet” problem

Here's the scenario: you send the mix. Two days go by. No feedback. You write to follow up. They say “oh sorry, been busy, will listen tonight.” Another day goes by.

The old approach is to wait and follow up again. The better approach is to know before you even write the first follow-up. Listening analytics — who opened the link, how much they heard, and when — tell you the answer immediately.

If they haven't played it at all, your message isn't “what did you think?” — it's “here's a nudge to take a listen.” A different conversation, handled more efficiently.

If they listened to 80% of it an hour ago, you know feedback is probably coming. No need to follow up yet.

Handling scope creep after approval

The most common source of project grief isn't bad clients — it's unclear project endings. When there's a record of when the client approved a specific version, any request after that point is a new request, not a revision.

This isn't about being difficult. It's about having a shared language for what's inside and outside the project scope. An explicit approval status gives both sides that language.

Setting up the workflow step by step

1. Upload each version as a new file version — not a new file, not a renamed export. A version, so the history is preserved.
2. Set the status to “In Review”when you send the link. Your client sees this and understands they're expected to respond.
3. Address the commentsand upload the next version. Move the status to “Needs Changes” if you want to flag that work is still in progress.
4. When the client is happy, mark it Approved.That's the finish line. Both sides see it. The project is done.

The short version

Get all feedback in one place, attached to timestamps on the audio. Use a formal approval status instead of relying on “sounds great” texts. Check whether your client has actually listened before you follow up. Know exactly which version was approved and when.

That's the whole system. It won't eliminate revisions — clients will always want changes. But it will eliminate the ambiguity that turns three revisions into seven.