How to send a master to a client for approval

Sending the master is also the start of the client review. Include a clear version name and explain where to leave comments and how to approve the final file.

What to check when sending a master

File-transfer links can deliver audio, but feedback and approval may need to be recorded elsewhere. Check these points before choosing how to send the master:

• Lossy review. An MP3 can differ from the WAV you intend to deliver. Use a lossless review copy when detailed comparison matters.
• Unclear feedback. Ask the client to identify the version and passage so you can locate the requested change.
• No sign-off. Keep a confirmation that names the approved version.
• Expiring links. Check the expiry date and tell the client how long the files will be available.
• Unprotected masters. A link without access restrictions may be opened by anyone who receives it.

From review to delivery

Four steps, one link, no accounts for the client:

1. Share a lossless review link

Send a link that plays the master without requiring an account or a download. Lossless playback avoids an additional lossy encode during review. The metering guide explains the measurements you may want to check before sharing.

2. Collect feedback on the waveform

Ask for comments at a specific time or over a marked range. A note about the de-essing at 2:14 gives you a passage to inspect and discuss with the client.

3. Get the sign-off on the record

Record which version was approved, the supplied reviewer details and the date. Keep the file and the approval together. See how to get client sign-off on a master for the full process.

4. Deliver the master, protected

Check that the selected delivery files match the approved version. Then configure access before you release them:

• Password-protected. The unreleased master isn't reachable by URL alone.
• Revocable. You can disable or replace the link if it was shared by mistake.
• Download-tracked. You can inspect download requests and follow up with the client. A request alone does not prove the complete file was saved.

For more detail, see delivery formats and private sharing settings.

Keeping track of revisions

Add each revision to the same track and tell the client it is ready. They can compare versions at matched loudness. Check carried-over comments if the edit changes the timing, and request approval of the new version before delivering it.

Frequently asked questions

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

A review link can combine playback, timestamped feedback and version approval. Choose settings the client can use easily, identify the file being reviewed, and check access permissions before releasing the final files.

Should I send clients an MP3 or a lossless file for review?

Use a lossless file for the main review when possible. An MP3 can be useful as a reference, but it adds lossy encoding to the listening chain. Label references clearly so they are not confused with the release file.

How do I prove a client approved a master?

Save a record of the accepted version, reviewer details and approval time, along with the file. An email that clearly identifies the version can also be kept with the project. An approval record does not establish identity or determine liability.

Is WeTransfer good for delivering masters?

A file-transfer service can deliver the master. Check its access and expiry settings, and agree where the client should send feedback and confirm approval. If you want those steps on one page, use a service designed for audio review.

How should I handle revisions?

Upload the new version against the same track so feedback carries across revisions and the client compares v1, v2, v3 at the same timecode. Then they approve the specific version that's final.