Browse Docs

Send a version for review

Choose the exact mix version and send it to the right client contacts.

Last reviewed 4 September 2026

Before you start

Have these ready:

  • a project with the track you want to review
  • the version you intend to send set as that track's current version
  • a client and at least one active contact, or the details needed to add them

Client review is available on Pro and Studio. Uploading a file alone does not notify the client or add the file to their review.

1. Select the version to send

  1. Open Projects, then open the project.
  2. Select Review & Delivery.
  3. Select the track. The track panel shows its current version label and date.
  4. Check that the current version is the one you want the client to hear.
  5. Select Send for review. When the track card includes the version name, the action may appear as Send [version] for review.

The send form receives the selected track and version before it opens. It does not have a separate version dropdown. If the current version is not ready, close the form and upload the intended file as a new version of the same track before sending.

2. Choose the client and recipients

The form opens with Client and recipients.

  • If the project already has a client, its active project contacts are selected automatically.
  • If the project has no client, choose one from Choose a client, or enter a Client name when you create the relationship during this send.
  • Clear any contact who should not receive this review. An opted out contact is disabled and cannot be selected.
  • Select Add another contact when another active recipient needs access, then enter the contact name and email.

Each selected contact receives access to the same project review. Their access follows the project's client relationship and review room settings. A designated approver can make the formal decision; other active contacts can still comment.

Check the client and recipients before sending the selected version.

3. Add a message and send

  1. In Message (optional), tell the client what to focus on. For example, mention a vocal level, transition, or lyric change.
  2. Keep the message within the 4,000 character limit.
  3. Select Send for review.

The message is stored with the review request. Feedback and any approval or change request stay attached to the version the client received, not to a later private upload.

Expected result

Mixhaus saves the review request and gives the selected contacts access to the shared version. The confirmation shows Sent for review, names the version, and marks the track In review. If the project already has a review room, Mixhaus keeps its review link and adds this version to the versions shared there.

Only deliberately shared versions appear to the client. The newest file in your project can be newer than the version marked Latest shared in the client review.

Check review activity

Open the project's Review & Delivery view and select the track. Select Insights to see Listeners, Plays, Latest play, and listener rows with the version label and source, such as Review or Public share.

To see broader client activity, select Access settings, then open Client activity. The activity list can show who opened the review, listened, commented, or made an Approved or Changes requested decision. Activity helps you understand engagement; it does not change the track's review status.

If the review room is expired or revoked, the project shows that access state. Sending the next version restores the durable project review access. Revoking access removes future playback and download access while retaining the comments, decisions, and activity record.

What happens next

  • If the client is still reviewing, use Copy review link or Resend from the track card when you need to share the existing review again.
  • If the client requests changes, upload the next bounce as a new version of the same track. Its status stays Draft until you send that version.
  • After you send the new version, the track becomes In review again. Earlier comments and decisions remain attached to their original versions in Review history.
  • After the client approves, select Prepare delivery to package the approved version.

Common problems

  • There is no version to send. Select a track with a current version, or upload a file to the existing track first.
  • The wrong version is selected. Close the send form, return to the selected track, and make the intended file its current version before opening Send for review.
  • No recipient can be selected. Choose a client with an active contact, restore the correct project contact, or add a new contact with a valid email address. Opted out contacts cannot receive a review.
  • The confirmation says "Version shared; some emails failed." The version and review request were saved. Select Retry failed emails to try the unsuccessful notifications again.
  • The client cannot open the review. Check Access settings for expiry, password, and download settings. If access was revoked or expired, send the next version to restore the project review access.
  • No activity appears yet. Listener activity appears after someone opens or plays a shared track. It is separate from the review decision and status.

For the status meaning and next action on each track, see See what a project is waiting on. For the client side of the review, see Review a mix as a client.

Was this useful?