The message arrives on a Thursday. “Hey, I need this back by Monday morning. We’re releasing next week.” The session has 48 tracks, the files came in late, and you already have two other projects in queue.
You say yes. You work the weekend. You deliver. And then it happens again next month.
Mix turnaround time is one of the most underdiscussed parts of running a mixing business. Most engineers either set no expectation at all, leaving clients to assume their own timeline, or they agree to whatever deadline lands in their inbox and figure it out later. Neither approach works. The first creates friction. The second creates burnout.
This is a guide to doing it properly: what a realistic mix turnaround time actually looks like, how to communicate it before a project starts, what to do when clients push for faster delivery, and when to charge a rush fee for the privilege.
What a Realistic Mix Turnaround Time Looks Like
Before you can set expectations with a client, you need honest numbers for yourself.
A single song from a typical indie session (24 to 40 tracks, no major problem sources) takes most working engineers four to eight hours of focused mixing time. That includes the first pass, time away from monitors, and a second listen before you send. Add an hour or two for session setup, gain staging, and export if files come in raw. For a well-organized, well-recorded session, a full day of work is realistic. For a messy one, more.
That does not mean clients get their mix the same day files arrive. Engineers have other projects, standing commitments, and the simple reality that mixing at 11pm when you are mentally fried produces worse work than mixing at 10am when your ears are fresh. Most professional working engineers quote three to five business days for a first mix delivery, with revision turnaround in the 24 to 48 hour range after notes arrive.
TapeOp put it plainly in their engineer workflow guide: clarity about mix turnaround time is important, and if a client needs something right now, both parties need to understand what that actually means before the work starts.
Albums and EPs Take Longer Than Clients Expect
A common mistake engineers make is quoting turnaround time per song without accounting for the full project load. A client hears “five days per song” and assumes their six-song EP takes five days total. It does not.
Be explicit. If you are mixing an EP, tell the client the expected delivery date for the full project, not just the first single. A six-song project where you are mixing one song per working day is a two-week project minimum, and that is before revision rounds. Set that expectation in your first email, not after they start asking where the mixes are.
The same applies to albums. If a client has twelve songs and you are mixing one at a time in sequence, that is a month of work on your calendar. Some engineers run them in batches (three songs at a time), some mix sequentially. Either way, the client deserves a realistic project end date from the start, not a vague “probably a few weeks.”
How to Communicate Mix Turnaround Time Before a Problem Starts
The time to set your mix turnaround time is not after files arrive. It is in your initial project email, before any work begins.
Keep it simple. Your project kickoff message should include three things: when you plan to start, when the client can expect a first mix, and how long revision rounds typically take. Something like:
“I will start on your session Tuesday and plan to send the first mix by Thursday. After that, plan on 24 to 48 hours for each revision round once I receive your notes.”
That single paragraph eliminates 90 percent of the “when will it be ready?” messages that eat up your week. Clients who know what to expect do not fill the silence with anxiety.
Put Your Turnaround Policy in Your Contract
Verbal timelines are invisible. A client who did not write it down will not remember what you said. When the mix is late in their mind, you have no way to point back to what was agreed.
Your mixing contract should state a delivery window and clarify what happens when the client causes delays. If files arrive two days late, the delivery date moves accordingly. If revision notes take ten days to arrive, the next turnaround restarts from when you receive them. Write it down once and reference it whenever a timeline conversation comes up. If you want a full framework for what else belongs in that contract, the post on mix engineer contracts covers the clauses that actually protect your schedule.
The Rush Fee: What It Is and When to Charge One
A rush fee is not a penalty. It is what you charge when a client needs their mix faster than your standard schedule can accommodate. That means bumping other work, mixing on weekends, or cutting short the mental distance you need between first pass and second listen.
The standard approach is to charge 25 to 50 percent of your project fee as a rush surcharge for turnarounds under 48 hours. Some engineers use a flat rate. Others tier it: 24-hour delivery costs more than 48-hour delivery, which costs more than 72-hour delivery. All of these work. Pick the one you will actually quote without hesitation.
The more important thing is that you have a policy before the request arrives. Engineers who decide case by case end up either undercharging out of guilt or saying yes to things they should have declined. A policy turns the conversation from a negotiation into a statement of fact.
How to Quote a Rush Fee Without Losing the Client
Most engineers dread the rush fee conversation because they assume the client will push back. In practice, clients who genuinely need something fast expect to pay for it. The clients who push back usually did not actually have a hard deadline. They defaulted to “as soon as possible” because no one told them otherwise.
Quote it directly. “My standard mix turnaround time is five business days. To get this back to you by Monday, I would need to prioritize it over my current queue. I can do that for a rush rate of X. Would you like me to move forward on that basis?” That is it. No apology, no hedging. You are offering a service at a price. The client can say yes, ask for the standard timeline instead, or take the work elsewhere.
Most of the time they say yes.
When to Waive the Rush Fee
There are clients who have earned the occasional fast turnaround without a surcharge. Long-term clients who plan ahead, book properly, and give you good notes are worth rewarding sometimes. Just make sure you call it out when you do it. “I had a gap open up this week, so I can get this to you by Friday at no extra charge” lands differently than just delivering early without comment. If you waive it silently, the client will expect that pace every time. Name the exception so it stays an exception.
What Happens When Clients Cause the Delay
Mix turnaround time runs in both directions. Engineers worry about being late, but clients blow timelines constantly. Files arrive wrong, reference tracks take three days to appear, the vocalist shows up to the tracking session a week after the files were supposed to be delivered.
Your contract should address this explicitly. A good working clause: if the client delays file delivery by more than 48 hours past the agreed date, the project delivery window restarts from the date of actual receipt. This protects your schedule when a project is pushed back by things outside your control, and it creates a natural incentive for clients to actually get organized before they book you.
The other thing to state clearly: your mix turnaround time clock does not start until you have everything you need. Partial files mean a delayed start date, not a compressed delivery window.
Incomplete Files Are a Special Case
A related problem is clients who send partial sessions and expect you to start mixing anyway. You open the folder and half the vocal takes are missing, the bass DI is nowhere to be found, and the reference track they mentioned is not in the zip file.
Do not start. Ask for complete files before you commit to any delivery date. The mix turnaround time should not begin until you have everything you need to do the job. This is worth stating in your initial project email: “Once I have all session files, I will confirm a delivery date.”
When clients use a dedicated upload link like session.trackbloom.com, their tracks arrive grouped by instrument (vocals, drums, guitars, bass) so you can see at a glance whether anything is missing before you even open a session. That five-minute check at the start of a project prevents the “where is the kick stem?” message three days into your work.
Setting a Mix Turnaround Time for Revision Rounds
First mix delivery and revision turnaround are different timelines and should be quoted separately.
Revision rounds are faster than first delivery for most engineers because you are working inside a session you already know. 24 to 48 hours is standard once notes arrive. But “once notes arrive” is the key phrase. If a client sits on the first mix for ten days before sending feedback, your 48-hour revision window starts when you get the notes, not when you sent the mix.
Make that clear upfront. “Once I receive your revision notes, I turn around changes within 48 hours.” Some engineers also build in a waiting period after initial delivery. If notes do not arrive within a set number of days, they move the project to their backlog and it queues behind whatever came in during that window.
This is not punitive. It is how professional service businesses work. A printer that does not hear back from a client does not hold the press open indefinitely. Your session is the same.
What Counts as a Revision Round
While you are setting revision turnaround expectations, also clarify what counts as a round. Some clients send a three-paragraph note and call it “one revision.” Others send eight separate emails over four days and treat each one as the same round.
State it cleanly: one revision round equals one set of consolidated notes, delivered in a single message. Notes that arrive in multiple batches after the first email count as a new round. This keeps your turnaround commitment realistic and gives clients a reason to actually consolidate their feedback before they send it.
Building a Mix Turnaround Time That Works for Your Schedule
The last piece to figure out is how your mix turnaround time fits your actual week.
Some engineers batch their work. All first passes happen on Tuesdays and Thursdays. All revision rounds happen on other days. Others mix one project start to finish before opening the next. Neither is wrong. What matters is that you have a rhythm and your clients know when they fit into it.
If you regularly have two or three projects in queue, your turnaround time needs to reflect that. A client who books you on a Monday should hear “I can start on this Wednesday after I close out the project I am finishing” rather than “I will get to it soon.” Clarity about where they are in the queue is not bad news. It is professionalism.
Clients who know they are third in line wait patiently. Clients who have no idea where they stand send check-in messages every two days.
Rush Fees Protect Your Other Clients Too
One final reason to charge properly for rush work: when you say yes to a last-minute request at no premium, you are saying no to someone else. The project you bump to make room for the weekend emergency did not consent to that delay. Your other clients booked you in good order and deserve the turnaround you promised them.
A rush fee makes the tradeoff honest. The client who needs it fast pays the cost of fast. Your other clients keep their agreed timelines. That is a fair system, and most clients understand it when you explain it that way.
Set your standard mix turnaround time. Write it into your contracts and your project emails. Build a rush policy and charge for it without apology. Those three things alone will cut your schedule stress in half.