How to Prepare a Vocal Handoff for a Remote Producer

What to Send So the Producer Can Keep Working

To prepare a vocal handoff, agree on who will edit, tune, and mix the vocals. Then send the requested parts, a reference from the same version, and notes on what's done and what's still pending. Clearly label the dry and processed alternatives, and check your exported files before sharing them. wuse can help you keep the project, its versions, and your collaborators' comments together.

The handoff should answer three questions without another call: which files to use, what artistic direction to preserve, and what work still needs doing. The workflow below is a suggested approach you can adapt to your team's agreement; the folder structure and example names aren't a required standard.

Use the recording session checklist to prepare the recording day and record your takes.

Why Misunderstandings Happen and What You End Up Redoing

When you say the vocals are finished, you might mean the takes are cleaned up and tuned, while the producer expects them to be mixed. My advice is to clear that up before exporting: write down what you're delivering and what still needs doing.

As a hypothetical example, imagine you've approved the performance and consider your work done, while the producer is expecting a different selection of takes. You could both be following your own understanding of the brief. Sorting that out later means reopening decisions that seemed settled and coordinating the handoff again.

A reference of the song helps you check that all the parts are there and that you're sending the right version. If an effect is part of the sound you're going for, keep a processed version too so the producer understands your intention.

1. Define the Scope Before Preparing Files

Write a short agreement wherever you coordinate the project. Don't assume that “producer” covers every possible task. Suggest someone to take responsibility for each decision and a date for feedback. If something is still open, mark it as pending instead of presenting it as approved.

You can adapt this message: “I'll prepare the v03 vocal handoff. The take selection is approved; we still need to decide who will check the tuning in the bridge. I'll send the agreed parts and a reference over instrumental v07. Confirm which processing you'd like to keep and which files you need to move forward.” It's a template to adapt to your project.

It's useful to separate artistic approval from confirming receipt of the files. Someone confirming they've received the files doesn't mean they've approved the performance. Suggest two separate responses: first, confirmation that the handoff is complete; then, feedback on the content.

• Assign responsibility for take selection, editing, tuning, and mixing.
• Note which decisions are approved and which are still open.
• Confirm which files and variants the producer expects to receive.
• Agree on who will gather feedback and communicate the next revision.

2. Make an Inventory of the Parts and Their Alternatives

A stem combines several tracks into a submix; a multitrack keeps the individual tracks separate. For this job, clarify whether you'll send the lead, doubles, harmonies, and ad-libs separately or as a vocal submix. Ad-libs are those extra vocal phrases that accompany or respond to the lead.

The inventory can be a simple note: lead approved; chorus double approved; high harmony awaiting review; ad-libs selected. Match each item to its filename. If a part has been dropped, say so explicitly so its absence doesn't look like an oversight.

Use dry for the dry vocal and wet for the processed one, but write down what's included in each file. If you send both, explain that they're alternatives or references: they don't necessarily need to play together.

An example instruction would be: “Use Lead_Dry as the working material. Lead_Wet shows the approved approach for the chorus. Check before changing that direction.” Also describe any cleanup or tuning you've already done: the filename shouldn't have to carry the whole explanation.

3. Check How Your DAW Exports

Export all parts from the same starting point and with the same duration, even if some come in later. Keep the silence at the beginning and include the tempo. In Ableton Live, check Normalize and Render as Loop; leave them off for this workflow. When importing, check Auto-Warp Long Samples so it doesn't change the timing. In another DAW, check the equivalent controls.

In Live, exporting individual tracks captures the signal after the fader and can include returns and main channel effects. So an individual track export doesn't prove that it's dry: check the routing and effects before labeling it that way. Normalize changes the gain; Render as Loop puts the tail at the beginning. To preserve endings with effects, check the export range.

For exchanging working files, agree on WAV or AIFF and the sample rate with whoever will receive them. In Live, 32-bit is a useful option if there's more processing to come, but it isn't a universal requirement. Avoid using MP3 to align tracks: exporting it can add silence at the beginning.

4. Include a Reference and Notes You Can Copy

Prepare a reference labeled with the same version as the handoff, and note which instrumental you used. To keep things organized, set aside one place for working material, another for alternatives, and another for the reference. What matters is that the recipient can tell what each file is for.

For example, you could name the folder Aurora_Voces_v03 and use filenames like Aurora_Lead_Dry_v03.wav and Aurora_Lead_Wet_v03.wav. If you use abbreviations, explain them once. Avoid names like “good,” “new,” or “final final”: replace them with an identifier you can both refer to without confusion.

The following README is an example template. Replace the fields in brackets and remove anything that doesn't apply. Don't claim you've done checks you haven't done yet.

• Project: [song]. Handoff: [version and date]. Person responsible: [name]. Reference instrumental: [identifier]. Status: [for review or approved].
• Agreed specs: tempo [BPM]; time origin [position]; range [start and end]; format [format, sample rate, and bit depth].
• Contents: [file inventory]. Main material: [files]. Alternatives: [files and purpose]. Reference: [name].
• Work completed: [selection, editing, tuning, and processing]. Pending: [task and person responsible]. Artistic direction to preserve: [description].

5. Review the Handoff from the Recipient's Point of View

One suggested check is to open a separate session and import the actual files you're going to share. Listen to the entrances and endings, and compare the contents with the reference and inventory.

Read through everything without listening to the audio, too: could you tell the main material apart from the alternatives using only the notes? Is it clear who's responsible for each pending task? If you need to remember a private conversation to make sense of the handoff, add that information to the document.

After sharing, ask for a specific confirmation: “Confirm that the inventory is complete and that you can identify the working material for v03.” If you replace a file later, explain what changed and which version it belongs to. Avoid silently changing what a handoff represents while it's already being reviewed.

Mistakes to Check for Before Sharing

This final review is about spotting contradictions between what you promise and what you deliver. Pay particular attention to exceptions: a pending harmony, a rejected alternative, or an older reference should be flagged wherever the producer will look for the material.

If you find a mismatch, fix the file or the description before sending. A precise note about a limitation is more useful than calling a handoff complete when it still needs a decision.

• The “dry” label doesn't explain what editing or processing has been kept.
• The reference and files have different version labels without an explanation.
• The inventory leaves out parts, alternatives, or pending decisions.
• The handoff message doesn't say what the producer should review or who will answer their questions.

Where wuse Fits and What to Do Next

wuse fits in as a space to organize music projects, audio versions, stems, and files, share handoffs, and talk with collaborators. You can follow this workflow by keeping the labeled handoff, its reference, and the feedback together within the project.

The technical preparation is still up to the team and their DAW. wuse doesn't automatically convert sessions between programs, and organizing a handoff doesn't replace an agreement on editing, tuning, or mixing. Its role here is to help keep the material and conversation tied to the same version.

To build on this workflow, continue with Stems or Multitracks: What to Send for Mixing a Song and How to Organize Versions and Stems in a Music Project. The first guide helps you pin down what to include in the handoff; the second covers how to organize it.

The next step is simple: complete the agreement and inventory for your next handoff, check the files, and share the project in wuse with a specific request for feedback.

Frequently asked questions

Should I deliver tuned vocals or leave that to the producer?

Agree on who's handling it before exporting. The conversations consulted show different expectations, so there's no basis for presenting one option as universal. Note whether tuning is done, approved, or pending, and who can request changes.

What should I write if they ask for dry vocals but I've already cleaned them up?

Describe their actual state: for example, “vocals edited and cleaned up; see the notes for processing details.” Ask the recipient to confirm whether that material meets their request. Don't rely on the word dry alone.

Do I have to send every take I recorded?

Suggest delivering the agreed selection and labeling any requested alternatives separately. If the selection is still open, say so and assign someone to make the decision. The inventory is there to make clear what each file represents, not to pile up material without instructions.

What if we haven't decided on the chorus effect yet?

Mark the proposal as pending and ask a specific question, such as “Do we approve this direction for the chorus?” Identify which file lets them hear it and who needs to respond. Avoid presenting that alternative as an already approved decision.

How do I send a correction after sharing the vocals?

Give it a new version and include a short note explaining which file is changing, why, and which handoff it replaces. Clarify whether you're sharing a complete package or just a correction. Ask for confirmation that the producer will work with the specified version.