The project closed six weeks ago. Final files delivered, invoice paid, everyone happy. Then the text arrives on a Sunday night: “hey! quick one. can you just bring the vocal up a touch? shouldn’t take you more than two minutes.” You say yes, because saying no over two minutes feels petty. That instinct is costing you more money than almost anything else in your business, and a mix recall fee is the thing that stops the bleeding.
Here is the uncomfortable math. It genuinely is a two-minute fader move. It is also a ninety-minute afternoon. Those two facts are both true, and only one of them is visible to your client.
What a Recall Actually Costs You (It Is Never Two Minutes)
Walk through what really happens when that message lands.
First, you have to find the session. Which drive? Which version? The one on the backup, or the one you touched last on the laptop? Then you open it, and three plugins have updated since you closed it. One has moved its parameters around. Another is authorized to a machine you no longer own, so you spend eleven minutes inside an iLok account you had forgotten existed.
Then comes the part nobody budgets for. You have not heard this song in six weeks. Your ears have no context for it anymore, which means you cannot responsibly touch a single fader until you have listened to the whole thing at least twice.
Only now do you make the change. That part is, in fairness, two minutes. Then you check what the change did, because the vocal moved and the bus compressor noticed. You bounce. You check the bounce. You rename the file, upload it, and write the email.
Add it up honestly and you land somewhere between forty-five minutes and two hours. Nobody bills for it, so it evaporates. Do that four times a month and you have donated a full working day to clients who already paid you and already left.
This Is Not a New Problem, and Studios Solved It Decades Ago
Engineers have complained about unpaid recalls on Gearspace for twenty years. The complaint is always the same, and it always ends the same way: the engineer does it for free the first time as a goodwill gesture, and the door never closes again.
Meanwhile, actual studios simply publish a number. Women’s Audio Mission, a professional facility in San Francisco, lists session recalls on its public rate card, with a free window for re-sending files that were already bounced and standard revision rates for anything requiring real work. Nobody finds that outrageous. Nobody argues with it. It is simply how the place operates, and the client reads it before they book.
That is the difference between a working business and a working engineer with no policy. Not confidence, not toughness. A published number.
A Recall Is Not a Revision, and Your Client Needs to Know It
This distinction is the entire foundation of a mix recall fee that feels fair rather than punitive.
A revision happens inside an open project. It is in scope, it has a count, and your client already paid for it. Your revision policy governs how many rounds are included and what counts as a round. That system already exists in your business, or it should.
A recall is something else entirely. A recall happens after the project is closed: after final approval, after final delivery, after the invoice cleared. The job was finished. You archived it. Reopening it is not a revision, because there is nothing left to revise. It is a new, small job that happens to concern an old song.
So define “closed” explicitly and say it out loud at delivery. Final files sent, approval given, invoice paid. That is the door shutting, and everyone can hear it shut. Without that moment, every project you have ever finished is technically still open, which is precisely how engineers end up with clients who never actually finish anything.
How to Price a Mix Recall Fee
Three models work. Pick the one that fits how you already charge, because a mix recall fee that contradicts your pricing structure will feel bolted on.
Flat per song. The simplest option, and the easiest to say out loud. A flat recall charge per song, quoted upfront, covering one reopening and one revised bounce. Freelance engineers commonly land somewhere between seventy-five and a hundred and fifty dollars depending on their rate. It is clean, it is predictable, and clients understand it instantly.
Hourly with a one-hour minimum. The most honest model, because it mirrors what actually happens. Your standard hourly rate, one-hour minimum, billed in half-hour increments after that. This one is especially sensible if you work with outboard gear, where a physical recall is genuinely slow and has to be printed in real time.
Free window, then paid. Free for fourteen days after delivery, charged after. This reads as generous, which it is, and it quietly does something useful: it gives your client a reason to actually sit down and listen properly on the first pass instead of approving on a phone in a car park.
What You Never Charge For
This line matters more than the number itself, because it is what keeps the whole policy from feeling greedy.
If you made the mistake, it is free. Always. Wrong file sent, wrong sample rate, a mute left on, a reference bounce delivered instead of the master. That is not a recall. That is a correction, and charging for it would be indefensible.
Similarly, when a client loses the files you already delivered and asks for them again, just send them. Re-uploading a bounce you already made costs you four minutes and buys you enormous goodwill. Save the fee for work that is actually work. Getting the free-versus-paid boundary right is what makes the rest of your pricing feel principled rather than arbitrary.
The Mastering Engineer Edge Case
One situation deserves a softer touch. If the client’s mastering engineer comes back and says the low end is fighting the limiter, or the vocal is not surviving the chain, that is a professional note about your work from someone whose job is to catch exactly that.
Treat it as a fix, not a recall. Charging for it looks defensive, and the mastering engineer talks to other artists. That conversation is worth more than an hour of your time.
The exception is timing. If those notes arrive four months later on a track that already came out, the window has closed and it is a recall like any other. What decides it is when the request lands, not who sent it.
How Long Do You Keep the Session, Anyway?
Almost nobody tells clients this, and it quietly causes half the awkwardness.
Sessions live on drives. Drives fill up, and drives die. An eighty-track mix with a video reference and six months of alternate bounces is not free to keep forever, and pulling a two-year-old session off a cold archive, then getting it to actually open with plugins that have since changed hands or vanished, is a genuine job in itself.
So publish an archive window alongside your mix recall fee. Something like: sessions stay live for ninety days after delivery, then get archived. Recalls inside that window are billed at the standard rate. Recalls after it require retrieving and rebuilding the session, which costs more, because it does.
Two good things happen. You start pricing the work you are genuinely doing rather than the work the client imagines you are doing. And clients with a nagging doubt about the mix tend to raise it inside the window instead of two years later, which is better for everyone.
Be honest about the limits, too. If you cannot promise a session will open cleanly in three years, say so at delivery rather than when someone asks.
Where Your Mix Recall Fee Belongs (Not in an Awkward Text)
Charging feels bad for one reason, and it is not the money. It feels bad because you are inventing the policy at the exact moment you need to apply it, which makes it look personal. It looks like you are annoyed at them specifically.
The fix is to put the number somewhere impersonal, long before you need it. It belongs in your booking email and in your contract, alongside your revision policy and payment terms. If the client agreed to a mix recall fee on the day they hired you, then applying it eight weeks later is not a confrontation. It is just admin.
The clause does not need to be complicated:
“Two rounds of revisions are included. The project is considered complete upon final delivery and approval. Changes requested after that point are billed as a recall at [rate] per song, covering session reopening, revision, and re-delivery.”
Two sentences. That is the entire difference between an awkward negotiation and a rate card.
The Email That Charges Without Sounding Like a Bill Collector
When the request lands, your reply should be warm, short, and completely undramatic. Lead with yes.
“Happy to do that. Recalls after final delivery run at [rate] per song, which covers reopening the session, making the change, and re-checking and re-bouncing the mix. Want me to go ahead?”
Notice what that does. You said yes before you said money, so you do not read as difficult. You explained what the fee actually buys, so it does not sound arbitrary. Then you handed them a decision instead of a lecture.
Some clients will say yes immediately, and you will feel slightly silly for having worried. Some will push back gently, and the answer is simply to hold the line without apologizing: the number is the number, and it was in the agreement. And some will go quiet, which is itself a useful answer. The change was worth doing when it was free. It was not worth doing at your rate. That tells you exactly how important it was.
The Best Mix Recall Fee Is the One You Never Get to Charge
Here is the thing nobody says out loud about recalls. Most of them are symptoms, not events.
The client who comes back three weeks later almost never had a genuine change of heart. They approved the mix while distracted, on laptop speakers, between other things, and then actually heard it properly in the car. The recall is not really about the vocal level. It is about an approval that was never a real approval.
So the highest-value move is upstream. Make the approval moment mean something. Collect feedback in one consolidated round rather than nine scattered texts. Confirm that the person signing off is the person who decides, not the person forwarding it to a manager who has not listened yet. Deliver on a proper listen, not a passing glance.
The same logic applies to how the work reaches you in the first place. Projects that start organized tend to end cleanly, which is why we built session.trackbloom.com: you send your client an upload link, and their tracks arrive grouped by instrument, vocals with vocals, drums with drums. Think WeTransfer built for audio. Fewer surprises going in usually means fewer “wait, actually” messages coming out the other side, and it is worth pairing with a deliberate approach to setting expectations before a project starts.
Get Paid for the Hour You Actually Spend
A recall is never two minutes of fader movement. It is two minutes of fader movement buried inside an hour of session archaeology, plugin updates, re-listening, re-checking, and re-delivery. Your client cannot see that hour, and they are not being malicious about it. They simply have no way of knowing.
Your job is to make it visible, once, in writing, before it ever comes up. Put a mix recall fee in your contract. Say the project is complete when you deliver it. Then when the Sunday night text arrives, you get to say yes with a clear conscience, because the hour you are about to spend is an hour you are getting paid for.
You already did the work. Charging for doing it a second time is not greed. It is arithmetic.