How to Prepare a Mix Delivery Checklist

A dependable mix delivery starts before export: confirm what the recipient needs, organize the session, and make each file easy to identify. Use this checklist to prepare a clean handoff from a home studio or professional room, while adapting the technical details to the recipient’s specifications.

1. Confirm the delivery brief

Do not assume that “send the mix” means one particular file or format. Ask the client, artist, producer, or mastering engineer what they expect, and put the answers in writing. A short brief prevents avoidable re-exports and confusion about which version is final.

Confirm:

• The number and names of songs or versions.
• The intended destination: listening, distribution, mastering, video, or another production stage.
• The requested file format, sample rate, bit depth, and channel layout.
• Whether they need a full-resolution mix, a reference MP3, instrumental, a cappella, clean edit, performance version, or other alternate.
• Whether they want a specific loudness target or peak ceiling. If none is specified, do not guess at a delivery standard; ask or provide an unprocessed mix alongside a clearly labeled reference if appropriate.
• The delivery method, folder structure, deadline, and whether revisions should replace or sit alongside earlier versions.

Keep a distinction between technical requirements and preferences. For instance, a mastering engineer may want a full-resolution stereo file with processing on the mix bus, while another may request a version without limiting. Neither preference should be treated as universal. If a request conflicts with the session’s available settings or the recipient’s stated workflow, clarify before committing.

2. Make the session ready to export

Save a new, clearly named session version before making delivery changes. Use the DAW’s collect, consolidate, or archive function when handing off a project, and read its documentation because behavior differs by software. A copied session may still reference audio from outside its folder.

Before exporting:

1. Set the start and end points deliberately. Include the full musical beginning and the intended reverb, delay, and instrument tails, but avoid long accidental silence.
2. Check that the song plays from start to finish and that the chosen export range includes every section. For a collection, check each song’s range separately.
3. Confirm the intended sample rate and stereo or mono routing. Avoid changing the session rate casually; sample-rate conversion is a real processing step, and the best place to do it depends on the workflow.
4. Look for muted tracks, solo buttons, disabled plugins, bypassed buses, and unintended routing changes. Verify that the master output receives the correct mix bus.
5. Check automation at the beginning and end, including fades, mutes, effects sends, and master processing.
6. Save the session and, if practical, create a separate delivery version so the working mix remains easy to recover.

A session handoff needs more than the stereo export. If stems or a full project are requested, agree on whether stems should include effects, whether they should all begin at the same time, and how shared effects will be represented. For project portability, include the audio and any required assets that the recipient is permitted to receive, then test the copied session on a different location or account when possible. Missing plugins may prevent an exact playback match; document those dependencies instead of implying the project is self-contained.

3. Choose formats that match the use

Use the recipient’s requested specifications when supplied. When no specification is given, ask first if timing allows. The table below offers a practical starting point, not a universal standard.

Delivery purpose	Typical file choice	Check before sending
Mastering handoff	Uncompressed stereo WAV or AIFF at the agreed session or delivery resolution	Confirm bit depth, sample rate, headroom or peak requirements, and whether bus processing stays on
Listening review	WAV or a compressed reference copy	Label the reference clearly; avoid treating a lossy file as the production master
Video or live playback	Format and channel layout requested by the editor or playback system	Confirm frame or session alignment, start time, mono compatibility, and routing
Stems or session transfer	Separate aligned files or a collected DAW project	Agree on names, effects, start points, and required dependencies

WAV and AIFF are common uncompressed formats, but compatibility depends on the recipient’s software and device. Check that the DAW exports the requested encoding and channel count; a stereo interleaved file is different from two separate mono files. A bit-depth change may involve dithering when reducing word length. Follow the DAW’s instructions and the recipient’s specification, and avoid applying dithering repeatedly across intermediate exports.

Do not normalize or add a final limiter simply because a file is being delivered. Those changes can alter the balance and dynamics. If the recipient asks for a loud reference, export it as a separate, plainly labeled listening version and preserve the agreed mix version. Likewise, do not remove mix-bus processing automatically: clarify whether the recipient wants the sound as approved or a version prepared for further processing.

4. Export a deliberate set of versions

Create only the versions that serve a stated purpose, but make requested alternates complete and consistent. Each export should start at the same musical position when it will be compared, aligned, or substituted in another project.

Useful checks for each file:

• Listen through the beginning, a dense section, the quietest section, and the ending. For a short track, listen to the whole export.
• Confirm that the final fade and effect tails are not cut off, and that there is no unintended silence or count-in.
• Check for clipping, unexpected distortion, abrupt edits, clicks, dropouts, or a wrong mix balance. A peak meter can help identify overload, but it cannot replace listening.
• Verify the exported channel count and that the file opens in a player or audio editor compatible with the format.
• Compare the export with the DAW session at a matched playback level. A louder reference may seem better simply because it is louder.

For alternates, use the same start and end points wherever possible. Name the difference precisely: “instrumental” should not be confused with “TV mix,” and “clean” should mean the agreed edit rather than an assumed standard. A vocal-up or vocal-down version should be checked against the main mix so the change is intentional and limited to the requested balance. If an alternate changes timing, arrangement, or effects, state that in a notes file.

5. Name files and build a clear folder

A useful filename identifies the project, song, version, and format without relying on a recipient to infer what “new final” means. Avoid characters that may be awkward across operating systems, and keep names concise.

For example:

Artist_Project_Song_Mix-v03_Instrumental_48kHz-24bit.wav
Artist_Project_Song_Mix-v03_Reference.mp3

Use a stable version scheme such as v01, v02, and v03, and reserve labels like approved or final for versions that really have that status. Include the date only if it helps distinguish deliveries and use an unambiguous format such as 2026-11-11. Do not overwrite an earlier approved file without agreement; retaining a dated or versioned copy makes revision history easier to follow.

A compact folder might look like this:

Project_Song_Delivery/
  01_Mixes/
  02_Alternates/
  03_Stems/       (if requested)
  README.txt

Keep the folder proportionate. Do not send duplicate files in several directories or include abandoned drafts that could be mistaken for the deliverable. A short README can identify the approved mix, list included alternates, state the export specifications, and note any known dependencies or differences. It should not contain private information the recipient does not need.

6. Organize stems and project files carefully

Stems are groups of tracks or buses intended to recreate parts of a mix; the term is used inconsistently. Before printing them, agree on the grouping, such as drums, bass, instruments, and vocals, and whether each print includes its effects. Clarify how shared reverb or delay returns should be handled. A separate “effects” stem can be useful, but it may not reproduce the mix if the recipient’s routing differs.

Render all stems from the same start and end point. Keep them at the agreed sample rate and bit depth, and make sure muted groups and solo logic do not accidentally omit material. Import the rendered stems into a fresh session or audio editor and play them together. Their combined playback should correspond to the intended mix closely; differences can arise from nonlinear bus processing, sidechains, automation, or effects that react differently when separated. Explain those limitations in the notes rather than promising a perfect reconstruction.

For a DAW project, collect the audio and other necessary assets into the project folder using the application’s supported method. Include a text note listing the DAW and version, tempo and meter if relevant, and plugins or instruments that may be unavailable elsewhere. Do not assume that another studio owns the same third-party plugins, sample libraries, or operating system. Where permitted, print essential virtual instruments or effects to audio as a safety reference while preserving editable tracks if requested.

7. Transfer and verify the handoff

Choose a transfer method that supports the folder size and preserves filenames. Cloud folders, managed transfer services, and physical storage can all work; consider recipient access, upload limits, and whether the method can resume an interrupted transfer. If the recipient needs a single archive, create it only after checking the folder contents and confirm that the recipient can extract the format.

After transfer, verify the uploaded files from the destination view, not only from the local folder. Check that uploads completed, filenames are intact, files have plausible sizes, and access is granted to the intended recipient. If the service provides checksums or upload verification, use them for large or important deliveries. For a physical drive, safely eject it and, where practical, test the copied files from the drive before shipping or handing it over.

Send a concise delivery note that states:

• The folder or link and the approved mix filename.
• The versions included and their purposes.
• The format specifications and any unusual processing choice.
• Any known issue, limitation, or dependency that could affect playback.
• Which version the recipient should review if multiple options are present.

Do not describe an upload as complete until the destination copy is available and checked. Keep a local copy of the delivered package until receipt is confirmed, subject to your normal storage practices.

8. Troubleshoot common delivery problems

The recipient reports a missing file. Check the exact filename and destination folder, then compare the local package with the uploaded copy. Re-upload only the missing or damaged item when possible, and clarify whether a revised file supersedes an earlier version.

The file plays at the wrong speed or pitch. Compare the exported sample rate with the session and playback settings. A file interpreted at an unintended rate can sound faster, slower, or shifted in pitch. Re-export with the requested rate or use a documented conversion workflow; do not rename a file to disguise its actual encoding.

The mix sounds different in another application. Check whether the player is applying loudness normalization, spatial audio, system enhancement, or a different channel mapping. Compare through a known playback path and confirm the file itself is the intended version. Consumer playback tools can alter sound, so they are useful for checking access and gross issues, not for proving identical monitoring conditions.

A stem bundle does not recreate the stereo mix. Inspect start alignment, omitted tracks, shared effects, sidechains, and bus processing. If the mix uses processing that cannot be reproduced from separated stems, tell the recipient and provide the approved stereo reference. A stem set is not always mathematically capable of recreating the original mix.

The project opens with missing media or plugins. Recollect or relink the audio using the DAW’s documented procedure, then check that the project opens from the delivered folder. Note unavailable plugins and provide printed references where suitable. Plugin substitutes can change sound, so avoid claiming the session will reproduce exactly on every system.

Final handoff checklist

• The brief and export specifications are confirmed.
• The session is saved, the export range is correct, and the mix has been checked from start to finish.
• Every requested format and alternate is present and accurately labeled.
• Files open, play at the intended rate and channel layout, and have no obvious export faults.
• Stems align and their grouping and effects are documented where relevant.
• The folder contains only intended deliverables, with a useful note for the recipient.
• The destination copy and recipient access have been checked.
• The delivery message identifies the approved version and any practical limitations.