Respond to feedback with a new revision

Keep every requested change on the version that received it, then send the next bounce through the same project review.

Before you start

Have these ready:

• a project with a client review and a track whose status is Changes requested
• the next audio bounce in MP3, WAV, AAC, M4A, OGG, or FLAC format
• permission to edit the project and track

Uploading is available on every plan. Client review, feedback, and approval are available on Pro and Studio.

1. Read the feedback on the exact version

1. Open Projects, then open the project.
2. Select Review & Delivery.
3. Select the track marked Changes requested.
4. Select Track details to open the track workspace.
5. In Revision timeline, select the version marked Needs changes and read its feedback section.

Feedback is attached to the version and, when the client used a timestamp, to the exact point or range in that audio. Keep the requested changes in view while you prepare the next bounce.

2. Upload the next bounce as a new version

1. In the track workspace, select New version. If a menu opens, select Audio file.
2. Choose the new audio bounce.
3. In Add track details, check Name. Mixhaus starts with the filename without its extension.
4. Add or correct Tempo (BPM), Key, and Tags as needed.
5. Wait for Upload ready. Confirm to add it., then select Upload.

The dialog may show Preparing upload..., Uploading while you add details..., or Finishing upload... while the private upload is in progress. Keep the dialog open until the upload is ready to confirm.

Mixhaus shows Version uploaded and adds the new revision to the Revision timeline. The new version becomes the track's Active version and starts as Draft. Uploading does not notify the client or change the version already shared in the review.

3. Send the new version through the existing review

1. Return to the project and select Review & Delivery.
2. Select the revised track. Its next action is Send [version] for review.
3. Select that send action and confirm the selected version in the Send for review form.
4. In Client and recipients, keep the active project contacts who should receive the update. Use Add another contact only when another contact should also have access.
5. Add an optional note in Message (optional), then select Send for review.

Mixhaus adds the new version to the existing project review room, keeps the same review link and access settings, and sends a new version notification to the selected contacts. The confirmation shows Sent for review and the track returns to In review.

If the previous review link was expired or disabled, the project shows an access warning. Sending the next version restores the durable project review access while retaining its review history.

Expected result

The new version is the current private draft until you send it. After sending, the client sees it as Latest shared in the same review and can compare it with earlier shared versions when more than one version is available.

The earlier Changes requested decision and its comments remain attached to the earlier version in Review history. Approval does not carry over to the new version. The client must decide on the new version again.

What happens next

• The selected contacts receive the new version request unless they opted out. Their delivery status appears in the send confirmation.
• The client can listen, compare versions, and leave comments on the new version. Older comments remain available on the versions where they were made.
• The designated approver can select Approve version or Request changes. If no approver is set, any active project contact can make the formal decision.
• When the new version is approved, return to Review & Delivery and select Prepare delivery.

Common problems

• I still see Start next version. The new upload may still be processing, or the project has not refreshed. Return to the track workspace, confirm the new row appears in Revision timeline, then reopen Review & Delivery.
• I created another track. Remove the extra project item if you do not need it, then upload the bounce from the original track's New version action. The original track keeps the existing comments and decisions.
• The client still hears the old bounce. Uploading does not share a version. Send the new active version from Review & Delivery and check that the client review shows the new version as Latest shared.
• The upload fails. Select the file again and keep Add track details open until the preparation finishes. Use a supported audio format and check that your account has storage available. The failed upload does not notify the client.
• Some emails fail after the version is shared. The confirmation says Version shared; some emails failed and lists each recipient's status. Select Retry failed emails. The version and review room remain saved while the failed notifications are retried.
• No recipient can be selected. Add or restore an active project contact with an email address. Opted out contacts cannot be selected, and a designated approver must have an active email before you send.
• The review link is unavailable. Check Access settings for expiry or revocation, then send the new version again. Sending the next version restores the project review access; removing a contact's project access still prevents that contact from opening it.

Related articles

• Upload a revision as a new version
• Send a version for review
• See what a project is waiting on
• Review a mix as a client
• Compare two versions of a mix