The last export can undermine an otherwise well-prepared project: a wrong revision, a cut-off reverb tail or an accidental working effect may reach distribution. Mastering preparation therefore starts with a simple question: is this really the approved mix? A clear input and agreed technical settings leave more attention for the music and less for investigating handover mistakes.
Prepare an approved mix and a short brief
Deliver a clearly labelled stereo file in the agreed uncompressed format. Do not use a random messaging-app export when the original high-quality file is available. Confirm sample rate, bit depth and channel format with the recipient. A larger number produced by unnecessary conversion does not add information that was absent from the source.
Include the intention, a useful reference and the required outputs. For an album, provide the sequence and intended transitions. If songs flow continuously into each other, discuss that before splitting files. State whether the mix is final or still awaiting an artist's decision. Mastering an openly provisional mix can create avoidable repeated work. A brief does not need to be long, but it should distinguish decisions already approved from questions that remain open.
Explain master-bus processing
Not every processor on the stereo output is a mistake. Compression, saturation or another effect may be part of the approved sound. Distinguish that creative intention from temporary loudness processing used only to send a preview. Instead of automatically disabling everything, explain what is active and why. By agreement, provide a comparison version without a particular processor when that would help the mastering engineer.
Do not assume that lowering the export level repairs distortion created earlier in the signal path. Investigate the source of that distortion. Similarly, there is no single compulsory headroom number that suits every project and engineer. The priority is a usable input without unintended overload, delivered according to the agreed specification. If uncertain, send a short example for review before exporting an entire collection. This creates an opportunity to resolve a shared technical question once instead of repeating it across every song.
Check the exported file itself
Listen to the export outside the original session. Check the first entrance, transitions and final decay, then play the complete song without interruption. Look for an accidentally muted track, a solo state or a recording note that should not be present. Compare the duration with the approved version. The filename should identify the song and revision clearly rather than simply calling it “new”.
For several deliverables, make a short checklist. An instrumental must not contain an unintended lead vocal; a clean version needs its edited passages reviewed independently. Although versions may come from the same session, an error in one export may not occur in the others. Check the actual delivered files, not just the settings in the export window. If someone else is preparing distribution, give them a list that maps each filename to its intended use.
Close approval and archive the result
Send consolidated mastering feedback with timestamps. Distinguish a technical fault from a change in taste or a new arrangement request. Once approved, retain the final file, related alternatives and a note of what was delivered. Do not rename a later revision so it can be confused with the version already sent. Include the deadline and intended use when discussing the work with the studio. A clear brief and verified delivery help the music move into the next stage without requiring other people to guess which file is authoritative.
Sources & further reading
Sources checked on 29 October 2026. Platform interfaces and requirements may change.