Mixing Prep Checklist Tool: What First-Time Clients Should Confirm
Before you book a mix, confirm four things: the engineer has the right audio files, the rough mix shows your intent, the references explain your target sound, and the revision scope is clear. A clean mixing prep checklist prevents the most common first-time client problems: missing stems, mismatched start times, confusing file names, printed effects that should have been dry, vague references, and late creative changes that are really a new mix direction.
Most first-time mixing orders do not slow down because the song is impossible to mix. They slow down because the handoff is unclear. The engineer opens the folder and has to ask basic questions before touching EQ: Which file is the lead vocal? Is the reverb printed on purpose? Does the beat have stems? Is this rough bounce the source or only a reference? Are the doubles supposed to be that loud?
This checklist gives you a clean buyer-readiness pass before you pay for mixing. It is not about sounding technical. It is about removing ambiguity so the first draft can focus on the song instead of file cleanup.
If your files, rough mix, references, and notes are ready, the next step is a mix that turns the session into a finished record.
Book Mixing ServicesThe Short Version: What to Confirm Before You Order
If you only have five minutes, check these before sending payment or uploading files:
- Files: every track the engineer needs is exported clearly and starts from the same point.
- Rough mix: one bounce shows your current balance, effects intent, and emotional direction.
- References: one or two songs explain the vocal level, low end, brightness, or overall style you want.
- Creative notes: anything intentional is labeled so the engineer does not "fix" it by mistake.
- Revision scope: you understand what counts as a revision and what counts as a new direction.
Those five items solve most first-time client confusion. They tell the engineer what to mix, what to protect, and what result you are trying to reach.
1. Confirm the Engineer Has the Right Files
A mixing engineer cannot build a proper mix from a random folder of bounced audio. The files need to line up, make sense, and include the source material that actually needs mixing. The cleaner the files are, the less time the engineer spends reconstructing your session.
For a normal song, send individual tracks or multitracks when possible:
- Lead vocal
- Doubles
- Ad-libs
- Harmonies
- Beat stems if you have them
- Instrument tracks if you produced the beat yourself
- A rough mix bounce for reference
If you only have a two-track beat and vocal stems, say that upfront. A mixer can still improve the record, but the expectations are different. A full tracked production gives more control over drums, bass, instruments, and vocal space. A two-track beat limits what can be separated later.
Every exported track should start at the same point in the song. If the lead vocal starts at bar one, the doubles start at bar seventeen, and the beat starts at the first downbeat, the engineer has to manually line everything up. That creates risk. Export from the same start point even if some tracks contain silence at the beginning. Silence is better than misalignment.
2. Name Files So the Session Is Obvious
File names are part of the mix prep. Names like `Audio_17.wav`, `FinalVocalNew2.wav`, or `bounceREALFINAL.wav` slow the session down because the engineer has to audition files just to understand what they are. Use plain names that describe the source.
| Weak Name | Better Name | Why It Helps |
|---|---|---|
| Audio 1.wav | Lead_Vocal.wav | The engineer knows it is the main vocal. |
| VoxNew.wav | Lead_Vocal_Tuned.wav | Printed tuning is clear. |
| Track 22.wav | Double_Left.wav | Panning intent is obvious. |
| Beat.wav | Two_Track_Beat.wav | The mixer knows there are no beat stems. |
| Reverb.wav | Lead_Reverb_Print.wav | The effect print has a clear role. |
You do not need a complicated naming system. Short, direct names are better than long names. The goal is that the engineer can import the files and know what each track is before hitting play.
3. Send Dry and Wet Versions When the Effect Matters
First-time clients often ask whether to send vocals with effects or without effects. The answer depends on whether the effect is part of the performance or only part of your rough mix. If the effect is a creative decision the song depends on, include a wet version. If the effect is just your temporary mixing attempt, send the dry version too.
Use this rule:
- Always send dry vocals: the engineer needs a clean source to mix properly.
- Send wet vocals as references: if your delay throw, distortion, or tuning style is part of the idea.
- Label printed effects clearly: write `Lead_Vocal_Dry` and `Lead_Vocal_Wet_Reference` instead of guessing later.
- Do not print master-bus loudness processing into every stem: that limits what the mixer can fix.
- Keep intentional tuning if it is part of the sound: but tell the engineer it is intentional.
If you used a vocal preset while recording and the tone is close to what you want, send a dry vocal and a preset-processed reference. That lets the engineer hear the target while still having control over the final chain.
4. Include a Rough Mix Even If It Is Not Good
A rough mix is not a quality test. It is a map. It tells the engineer what you thought the song should feel like before professional mixing. Even if the balance is messy, the rough mix reveals your intent: which vocal is the lead, how loud the beat should feel, whether the hook doubles are important, and whether the ad-libs are supposed to be tucked or obvious.
Label the rough mix clearly. Use a name like `Rough_Mix_For_Reference.mp3`. Do not name it `Final.wav`, because that creates confusion. The rough mix should not replace the multitracks. It should sit next to them as a guide.
A useful rough mix can answer questions like:
- Should the vocal sit in front of the beat or tucked inside it?
- Are the doubles part of the hook energy or just support?
- Is the beat supposed to stay dark, bright, wide, dry, or aggressive?
- Are any effects part of the song identity?
- Does the artist prefer a clean polish or a rougher texture?
If the rough mix is extremely distorted, clipped, or overly loud, still include it, but say it is only for direction. The engineer will not copy its technical problems. They will use it to understand your taste.
5. Pick References That Actually Communicate Direction
References are most helpful when they answer a specific question. Sending five famous songs and saying "make it like these" can create more confusion than clarity. One song might have a bright vocal, another might have a huge low end, another might have a dry mix, and another might have a different genre arrangement.
Pick one or two references and explain what each one means:
- "Use this for vocal level and clarity."
- "Use this for low-end tightness."
- "Use this for how dry the lead vocal feels."
- "Use this for the hook width, not for the verse."
- "Use this for overall polish, but keep my vocal darker."
The note matters as much as the reference. A mixer cannot know whether you like the drums, vocal, low end, reverb, loudness, or overall mood unless you say it. Short notes beat vague taste statements.
6. Confirm What Is Finished Creatively
Mixing is not the same as arranging, rewriting, tuning from scratch, producing the beat, or re-recording the song. Some engineers offer those services separately, but they are not automatically included in a standard mix. Before ordering, confirm which creative decisions are already final.
Ask yourself:
- Is the lead vocal comp final?
- Are the doubles and ad-libs placed where I want them?
- Is the tuning printed or should the engineer tune it?
- Are all beat stems final?
- Are any production effects part of the sound?
- Do I still plan to change lyrics, vocal takes, or arrangement sections?
If the arrangement is still changing, wait before booking mixing or be clear that the first delivery may change. A mix engineer can handle creative changes, but late replacement vocals and new stems change the scope. It is cleaner and cheaper to finalize the song first.
7. Write a Short Mix Brief
A mix brief does not need to be long. In fact, a short brief is usually better. The engineer needs useful direction, not a full biography of the song. Send enough information to avoid guessing.
Use this simple structure:
- Goal: "I want a clean, modern rap vocal that sits upfront without harshness."
- References: "Reference A for vocal level, Reference B for low-end tightness."
- Must keep: "The distorted ad-lib in the second hook is intentional."
- Problem areas: "The verse vocal feels nasal and the hook doubles feel messy."
- Revision priority: "If anything needs attention first, prioritize vocal clarity over loudness."
This kind of brief gives the engineer a hierarchy. If there is a tradeoff between loudness and clarity, they know which direction to choose. If an effect sounds strange, they know whether it is a mistake or intentional.
8. Understand Revision Scope Before You Pay
Revisions are where first-time projects get tense. A revision is usually a change within the same direction: turn the vocal up, lower the hi-hat, make the hook delay less obvious, clean a harsh word, or bring the bass down. A new direction is different: replacing the lead vocal, changing the beat stems, switching the song reference, asking for a darker mix after approving a bright direction, or adding new production ideas.
Before you order, confirm:
- How many revisions are included?
- How long do you have to request revisions?
- What counts as a revision versus a new mix?
- Can you submit replacement files after the first draft?
- Are instrumental, clean, performance, or TV versions included?
- Is mastering included, separate, or not part of the order?
Clear revision scope protects both sides. You know what you are buying, and the engineer knows how much iteration is included. If you need a mix and master together, confirm whether that is a package or separate service before the project starts. Mixing services work best when the deliverables are defined up front.
9. Know When a Checklist Is Not Enough
A checklist is enough for many singles, demos, and straightforward vocal mixes. It may not be enough for complex projects. If the song has multiple vocalists, unusual effects, film or sync requirements, heavy live instrumentation, or a large stem count, you may need a more detailed written brief or a short call before mixing starts.
| Project Type | Checklist Enough? | Extra Prep Needed |
|---|---|---|
| Single with two-track beat and vocals | Usually yes | Rough mix, dry/wet vocals, references. |
| Full production with 40+ tracks | Sometimes | Track groups, stem map, arrangement notes. |
| Feature with two artists | Maybe | Lead priority, approval process, merged feedback plan. |
| Live band recording | Rarely | Bleed notes, edit status, drum/vocal priorities. |
| Sync or film delivery | No | Technical specs, versions, stems, timing requirements. |
If the project has more moving parts than a normal song, say that before booking. It is better to scope the job correctly than to force a complex project into a standard package.
10. Prepare Your Folder Like a Professional
A clean folder tells the engineer you are serious. It also prevents missing files. Put everything in one main folder named with the artist and song title. Inside, use simple subfolders so nothing gets lost.
A strong folder layout looks like this:
- `01_Source_Files` for stems or multitracks.
- `02_Rough_Mix` for the rough bounce.
- `03_References` for notes or reference links.
- `04_Notes` for lyrics, BPM, key, and mix brief.
- `05_Wet_Refs` for printed effects that show intent.
Use zip compression before uploading the folder. That keeps the folder structure intact and reduces the chance that a cloud service reorders or drops files. If the engineer has a specific upload portal, use it. If not, a clean cloud link is better than scattered attachments.
What Not to Send
Some files create more confusion than value. Do not send every unused take, random phone recordings, old beat versions, unlabeled exports, or a dozen alternate rough mixes unless the engineer asks for them. More files do not automatically create a better mix. They create sorting work.
A first-time client should send the final intended material, plus clear references. If you are unsure whether a file matters, label it as optional or put it in a separate folder. Do not bury important vocals inside a giant folder of maybes.
If the vocal was recorded with a structured setup from the beginning, recording templates can make the export stage cleaner because leads, doubles, harmonies, and ad-libs are already organized before mix prep starts.
Special Case: You Only Have a Two-Track Beat
A lot of independent artists order mixing with a two-track beat and separate vocals. That is normal, but it should be stated clearly. A two-track beat means the engineer cannot separately turn down the hi-hat, change the kick, move the snare, or rebalance every instrument. They can still shape the vocal, control harshness, carve space, manage the stereo balance, and make the vocal sit better against the beat.
If you only have the beat as one stereo file, send:
- The highest-quality beat file you have, preferably WAV or another lossless format.
- The exact beat version used during recording.
- Dry lead vocals, doubles, ad-libs, and harmonies.
- A rough mix showing where you wanted the vocal to sit.
- Notes about any beat problems you already hear, such as harsh hats or muddy low end.
Do not promise yourself that mixing will fully separate a bad two-track. The better expectation is improvement, balance, and vocal integration. If you can buy or request tracked-out beat stems from the producer, do that before mixing. If you cannot, be clear that the project is a two-track mix so the engineer can judge it correctly.
Special Case: You Need Vocal Mixing Only
Some clients do not need a full production mix. They already like the beat, but the vocal sounds raw, harsh, buried, or disconnected. In that case, prep the order as a vocal-mixing project, not a full multitrack mix.
Send the beat, dry vocal tracks, wet vocal references, rough mix, and notes about the vocal problem. Be specific. "Make the vocal better" is less useful than "the lead is too nasal in the verse, the hook doubles are messy, and the ad-libs are too sharp." The more clearly you name the vocal issue, the faster the engineer can solve it.
This is also where the source chain matters. If your vocal was recorded through a rough preset that added too much compression, too much noise, or a harsh high shelf, say so. The engineer may ask for a cleaner dry export. If you only send the overprocessed version, they may have to work around decisions that should have stayed adjustable.
How to Give First-Round Feedback
Prep does not stop after upload. The first revision round is part of the workflow. Good feedback is specific, prioritized, and tied to timestamps. Bad feedback is emotional but unclear: "make it hit harder," "more professional," "cleaner," or "industry quality." Those phrases may be true, but they do not tell the engineer what to change.
Use this feedback format:
- Timestamp: where the issue happens.
- Element: vocal, beat, bass, snare, ad-lib, reverb, or hook.
- Problem: too loud, too low, too harsh, too dry, too wet, too wide, too buried.
- Priority: must fix, nice to improve, or taste preference.
- Reference: if a reference explains the change better than words.
For example: "1:04 hook lead vocal is too sharp on the word 'tonight'; please soften that without making the whole hook darker." That is actionable. "The hook sounds weird" is not. Clear feedback keeps revisions inside scope and helps the engineer protect the parts you already like.
What a Mixer Can and Cannot Fix
A mixer can do a lot, but the source still matters. Mixing can improve balance, tone, dynamics, width, vocal presence, harshness, mud, effects, and translation. It can also reduce some noise, tighten some timing, and make a two-track beat work better with vocals. But mixing cannot fully replace a clipped vocal, an out-of-tune performance, a badly recorded room, missing beat stems, or an arrangement that fights itself.
Use the checklist partly as a reality check. If the files reveal a problem before you order, fix it before the engineer starts. Rerecord a clipped lead. Re-export missing doubles. Find the correct beat version. Remove accidental master-bus clipping. Clean prep is not busywork. It is how you buy more actual mix time and less rescue work.
Before You Submit: Final Mixing Prep Checklist
- All source tracks are exported from the same start point.
- Files are clearly named.
- Dry vocals are included.
- Wet vocal references are included only when helpful.
- The rough mix is labeled as a reference.
- One or two references are explained with notes.
- BPM and key are included if known.
- Intentional effects are marked as must-keep.
- Revision scope is understood.
- Mastering expectations are separate or clearly included.
That last point matters. Mixing and mastering are related, but they are not the same job. Mixing balances the multitrack song. Mastering finishes the stereo mix for release. If you need both, confirm whether the project includes mastering services or whether mastering will happen after mix approval.
FAQ
What should I send before booking mixing services?
Send clearly named source tracks, a rough mix, one or two references with notes, BPM and key if known, dry vocals, any intentional wet vocal references, and a short mix brief. Confirm revision scope before the project starts.
Do I need to send stems or the whole DAW session?
Most remote mixing projects work well with exported audio tracks that all start from the same point. Some engineers may accept full DAW sessions, but audio exports are usually safer because they avoid missing plugin and version problems.
Should I leave vocal effects on before sending files?
Send dry vocals when possible, plus a wet reference if the effect is part of your sound. Label the files clearly so the engineer knows what is source material and what is only direction.
How many reference songs should I send?
One or two strong references are usually better than a long playlist. Write what each reference means, such as vocal level, low-end tightness, brightness, dryness, or overall polish.
What counts as a revision in a mixing project?
A revision is usually an adjustment within the agreed direction, such as vocal level, effect level, bass balance, or harshness control. New vocals, new stems, new references, or a changed creative direction may count as a new mix or paid extra work.
Can a mixer fix a bad recording?
A mixer can improve many problems, but clipping, heavy room noise, bad timing, missing files, and poor performances have limits. If the source is badly damaged, rerecording is often better than expecting the mix to hide everything.





