How to send a mix to a client for feedback and approval

Reviewing a mix on a phone with Soneam

Soneam gives the client a browser player with comments tied to the audio. They do not need an account or an app. You can send the review link through WhatsApp, LINE or email and keep the revision notes in the project. The demonstration above shows the client opening the player and leaving a comment.

1. Send one review link. The client opens it on their phone, enters the link password if you set one, and plays the mix.
2. Ask for a comment at the relevant moment. For example, pause at 1:42 and leave a note about the vocal. The client supplies a display name when prompted. The comment stays associated with that track and version.
3. Add the revised audio as the next version of the same track. Keep each EP song as its own track in the project. A new project for every bounce would split the revision history.
4. Send a short message that v2 is ready. The review link stays the same. The client can check the new version and, when version history is enabled, return to earlier versions.

Version history and the supplied commenter name help you follow the discussion; they do not verify a person’s identity. If the edit changes the song’s timing, check carried-over comments against the new audio. A timestamp alone cannot establish that the same musical moment still sits at 1:42.

When the revisions are done, record approval of the selected version. If a balance remains, keep the delivery locked until payment. Listening, approval and permission to download are separate steps.

When you send a mix, tell the client which version to review and where to leave comments. Collect feedback from everyone involved before starting the next round.

Keeping feedback with the right version

Email and messaging apps are useful for sharing a link. Keeping the detailed notes with the audio helps you avoid these common problems:

• They judge a lossy file. An MP3 adds lossy encoding, which can affect what the client hears.
• Notes without timestamps. A comment about “the second chorus” can be ambiguous. Ask for a timestamp when the location is unclear.
• Feedback in several places. Collect notes from email, messages and voice recordings into one list before revising.
• Versions at different levels. When a client A/Bs two versions at different levels, the level difference can affect their preference.
• No agreed version. Record which mix the client accepted so both sides can refer back to it.

A mix review workflow

The whole loop runs through a single link, and the client never makes an account:

1. Share a lossless review link

A browser review link lets the client listen without downloading a file or creating an account. Use lossless playback when possible to avoid an extra lossy encode. The metering guide explains the audio measurements used during review.

2. Take feedback on the waveform

Ask the client to mark a point or a range on the waveform for each request. They can identify a vocal phrase at 1:12 or a whole chorus where the guitars need adjusting. You can also send them the guide to giving mix feedback.

3. Compare versions loudness-matched

When reviewing v1 and v2, match their playback loudness before comparing. A level difference can influence which one the client prefers. See why louder sounds better for the comparison method.

4. Get the sign-off, then deliver

Ask the client to approve a named version. Check the delivery files against that version, then set the sharing permissions. See client sign-off and private delivery for those steps.

If you are considering a video review service for audio, the Frame.io comparison covers playback and review features to check.

Managing revision rounds

Agree the number of included rounds and the price of further work before you start. Add revisions to the same track to retain the history and open comments. See revision policies for sample wording and payment before delivery for the next step.

Files to include

Keep the review and the handoff separate:

• For review: one stereo mix. Use the stereo mix unless the client needs to review individual stems.
• For the final handoff: the stereo mix at full resolution (a 24-bit WAV at the session sample rate), plus a labeled reference so everyone knows which file is which.
• If it's in your agreement: stems or an instrumental and a TV mix. The pre-send checks live in the mix delivery checklist.
• Prepare the mix for mastering. Check for clipping and discuss mix-bus processing with the mastering engineer. See the mix delivery checklist.

Frequently asked questions

What's the best way to send a mix to a client?

Use a review link that the client can open easily, identify the version and ask for timestamped comments. Once the changes are agreed, record approval and check the files before final delivery.

Should I send a mix as an MP3 or a lossless file?

Use lossless playback for the main review when possible. An MP3 is useful for casual reference listening but introduces another lossy encode. Make clear which file the client should approve.

How many mix revisions should I include?

You could include two or three rounds in the quote, depending on the scope. Define a round, ask the client to collect their notes together and agree the cost of further work before starting it.

How do I stop endless mix revisions?

Agree the scope and revision allowance before work starts, collect clear feedback and record the accepted version. Discuss additional requests with the client rather than assuming every change is included.

What files should I send the client for a mix?

For review, a single stereo mix is enough. For the final handoff, send the stereo mix at full resolution (24-bit WAV at the session rate), plus a labeled reference and, if it's in your agreement, stems or an instrumental and a TV mix. Keep the mastering engineer in mind: leave headroom and don't bake in a limiter you can't undo.