How to get client sign-off on a master
Record which version the client accepts, keep their feedback with the audio, and confirm what will be delivered. Here is how to make approval clear for both sides.
THE CLIENT EXPERIENCE
Approve a specific
version.
Your client checks the track and version before approving. The record stays with that version.
- Upload the revised mix
- Check the version before approval
- Keep a record of the sign-off
No account needed to explore the demo.
Play the video to see the steps.
What the approval record includes
The approval records the selected version and the reviewer’s supplied name. 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 the Mood Swing jazz demo audio and artwork in a local 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.
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 above shows approval of v2.
- Send the project’s review link. Ask the client to listen to the version you want approved. Keep revision notes with the audio.
- 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.
- Check the approval record. Open the approval entry on your project. It identifies the approved version, supplied reviewer details and time. An email address, when supplied, is contact information, not verified identity.
- 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.
A checksum identifies the file’s bytes. It does not verify who listened or guarantee a legal outcome. For the next step, see delivery after a bank transfer.
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.
A review and approval workflow
The following steps cover review, revisions, approval and delivery. Agree the number of included revision rounds before the work starts.
If you already use a video review service, check whether its audio playback and version controls suit the job. Our Frame.io for audio comparison covers the relevant features.
1. Share a review link for one version
Send the project review link and name the version to review. Lossless playback avoids adding another lossy encode during review. For file preparation and sharing, see how to send a master to a client.
2. Take feedback pinned to the waveform
Ask the client to include a time or a marked range with each comment. A note such as “bring the vocal up at 2:14” identifies the passage you need to check. Use replies to clarify a request before making the change.
3. Capture an explicit sign-off on that version
Ask the client to approve the version by name or number. Save the version, the supplied reviewer details and the time of approval. If you make further changes, request approval of the new version.
4. Set revision scope up front
Specify the included revision rounds and the price of additional work in the quote. For examples of how to define a round and handle changes to the brief, see how many revisions to offer clients.
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.
What a good approval record contains
Keep the following details with the project:
- The version. Not "the master," but the specific version number that was accepted.
- Who and when. Supplied name, email when provided, and timestamp. These record the submission; they do not verify identity.
- The exact file. Ideally the deliverable is the same file that was approved, so what shipped provably matches what was accepted.
The record helps both parties identify what was accepted. Additional requests still need to be handled according to your agreement.
Frequently asked questions
What counts as client approval of a master?
Approval confirms that the client accepts a 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.
How many revisions should a mastering job include?
Agree a number of rounds that fits the scope of the job. One or two rounds is an example of a mastering package; state what each round includes and how further changes will be priced.
Why do clients keep approving the louder version?
A level difference can influence a quick comparison. Match the playback loudness before asking the client to choose between versions, then compare the changes to tone, balance and dynamics.
How do I prove which version a client approved?
Keep the approved version, the supplied reviewer name and optional email, and the timestamp. Retain the corresponding file. These details record the submission; they do not verify the reviewer’s identity.
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.