Mastering workflow

How to get client sign-off on a master

A sign-off names one version, one person and a time, and it is kept with the file. “Sounds good” in a chat names none of them. Here is what to ask for, what to do when the answer is unclear, and how to keep the record. For preparing and sending the master itself, see how to send a master to a client.

Updated ~5 min read

THE CLIENT EXPERIENCE

Approve a specific
version.

Your client checks the track and version before approving. The record stays with that version.

  1. Upload the revised mix
  2. Check the version before approval
  3. Keep a record of the sign-off
Open the client demo

No account needed to explore the demo.

Version approvalIN SONEAM
Mobile browser demo Silent walkthrough
What the approval record includes

The approval records the selected version, the name the reviewer supplied and the time. It is not identity verification. Approval of v1 does not approve a later v2. A checksum identifies file bytes, not who listened or signed.

The recording uses demo audio in a demo project. No customer data or real payment is involved. The public demo lets you explore the review experience; it does not collect payment or approval for your own project.

Before delivery, ask the client to confirm the version they want to release. Keep that confirmation with the file and the revision notes so you can refer back to it later.

What to include in an approval

An approval names a version, a person and a time. A casual email reply can leave the version unclear:

  • A specific version. "It sounds great" doesn't say whether they mean v2 or the v3 you sent an hour later. An approval names the exact master.
  • Reviewer details and a timestamp. Who approved it, and when. This is what a sign-off is for.
  • A link to the actual file. The approval points at the exact audio that will ship, not "the mix" in the abstract.

These details identify the version the client accepted and make it easier to resolve questions later. Keep the approval alongside the agreed scope, revision requests, and delivery files.

Compare versions at matched loudness

A louder version can sound preferable in a quick comparison, even when the processing change is not an improvement. Matching playback loudness helps the client compare the tone and dynamics of two versions.

Use a loudness-matched A/B to check your revisions before sending them. The client can use the same approach when reviewing. The streaming loudness guide explains how playback level differs from the level of the delivered file.

When approval is not clear

If a client replies “sounds good” after several versions, ask which one they mean before releasing files. For example: “Is that approval for v3 of both tracks, or are there still changes to the second track?” Save the reply with the project.

Agree who can approve when several people are reviewing. A singer’s approval may not be the label’s final decision. Soneam records the submitted approval; you still need to establish who is authorized for the job.

Reviewing a revised master

Upload each revision to the same track. The client can return to earlier versions and compare them at matched loudness. In Soneam, open comments carry forward; check their positions if an edit changes the timing of the song.

Keep the accepted file alongside the approval record and the agreed scope. If the client asks for new work after approval, confirm the cost and schedule before starting it.

Record approval of a specific version in Soneam

Soneam is an option for mixing and mastering engineers who need client feedback, a record of approval, and delivery on one review link. The client can listen and approve without creating an account. The demonstration at the top of this page shows approval of v2.

  1. Send the project’s review link. Ask the client to listen to the version you want approved. Keep revision notes with the audio.
  2. The client selects Approve. They check the track and version in the approval dialog and supply their name if it is not already known. On an album, they also check which tracks are selected.
  3. Check the approval record. Open the approval entry on your project. It identifies the approved version, the name and optional email the reviewer supplied, and the time. It records what was submitted. It does not verify who that person is.
  4. Check the delivery separately. Approval does not release files or confirm payment. Select the intended files in Delivery, check the balance if payment is required, then use Release files.

Approval of v1 does not approve v2. A new version needs its own sign-off. Released tracks follow the current version; approval does not freeze delivery to an older file. Use Unrelease before replacing a released version if you need the client to approve the replacement before downloading it.

For the next step, see delivery after a bank transfer.

Frequently asked questions

What counts as client approval of a master?

A statement that the client accepts one specific version. An email can do this if it identifies the file clearly. Soneam records the version, supplied reviewer details and approval time on the project.

How do I get a client to sign off on a master?

Send the review link, identify the version and ask for any remaining changes. Once those are resolved, ask the client to approve that version. Keep the approval with the project and check the selected delivery files before release.

Why do clients keep approving the louder version?

Because louder playback sounds fuller, so the hotter version tends to win a quick comparison. Match the playback loudness before asking the client to choose between versions.

How do I prove which version a client approved?

Keep a record that names the version, the reviewer’s supplied name and optional email, and the time, and keep the file it refers to. An email that clearly identifies the version works too.

Share this guide

Record approval of your next master

In Soneam, approval stays with the version the client selected. You can review that record before releasing the final files.