I spent three weeks in 2014 chasing a single client through a never-ending loop of “just one more tiny tweak” until I realized I wasn’t producing a podcast anymore; I was performing unpaid labor. Most of the gurus online will tell you that “client satisfaction is paramount” or suggest some complex, expensive project management software to handle your workflow. That’s nonsense. In the real world, if you don’t learn how to set boundaries on revisions before you even touch the faders, you aren’t a producer—you’re a volunteer. You’ll find yourself staring at a waveform at 2:00 AM because a client decided they suddenly hate the way a transition feels, even though it’s technically perfect.
I’m not here to sell you a productivity masterclass or a template that promises to automate your soul away. I want to show you how to build a contract that actually holds weight and how to have the uncomfortable conversation that stops a project from bleeding out. We’re going to talk about specific numbers, hard stops, and the exact language you can use to protect your time without losing the gig.
Defining Project Deliverables in Contracts Before the Work Starts
You can’t fix a problem you haven’t named. When I started out, I thought a “podcast episode” was a single, understood unit of work. It isn’t. To a client, that might mean a raw recording, a mastered file, and a social media clip. To me, it meant a single WAV file. This ambiguity is exactly how you end up preventing scope creep in freelance projects by realizing you didn’t actually define what “done” looks like. You need to be explicit in your paperwork: specify the file format, the sample rate, and exactly how many assets are included in the flat fee.
If it isn’t in the contract, it doesn’t exist. I’ve learned the hard way that defining project deliverables in contracts is your only real shield against the “just one more quick thing” email that arrives at 10 PM on a Tuesday. Don’t just list the final product; list the components. If you are providing a clean edit plus a music bed and a separate intro/outro, write that down. If they want a version with different music later, that’s a new invoice, not a “tweak.”
Managing Client Expectations During the Creative Process
Once the first draft is in their inbox, the dynamic shifts. You aren’t just an editor anymore; you’re a service provider being tested. This is where managing client expectations during the creative process becomes a survival skill rather than a courtesy. I’ve seen too many producers fall into the trap of being “too helpful,” responding to every “just one quick tweak” email at 10:00 PM on a Tuesday. If you don’t establish a rhythm early, you aren’t managing a project—you’re managing a crisis.
The best way to handle this is to be incredibly boring about your process. When you send over the first cut, don’t just say “let me know what you think.” That is an invitation for chaos. Instead, tell them exactly how to give feedback. Tell them you need a single, consolidated document with timestamps, rather than ten separate emails sent over three days. By limiting feedback loops in professional services, you aren’t being difficult; you are actually ensuring the quality of the final audio. You’re telling them that your time is structured, and that structure is what protects their budget.
Five ways to stop the endless edit loop
- Build a “Revision Cap” into your initial quote. Don’t just say “includes revisions”; say “includes two rounds of consolidated feedback.” If they want a third round because they forgot they hated the intro music, that’s a new invoice. Period.
- Demand consolidated feedback. I’ve had clients send me three separate emails over four days, each containing one “tiny” tweak. It kills my workflow. Tell them you will only begin the revision process once you have one single, comprehensive list of notes from all stakeholders.
- Define what a “revision” actually is. A revision is a tweak to existing work—adjusting the EQ on a voice or trimming a pause. If they decide halfway through that they actually want to re-record the entire interview with a different guest, that isn’t a revision; that’s a new project.
- Set a deadline for feedback. If a client takes three weeks to get back to you with “thoughts,” they’ve lost the thread of the edit. Tell them they have seven days to provide notes, or the project is considered approved and closed. It keeps the momentum up and prevents you from having to re-learn their project six months later.
- Use a feedback tool, not an email thread. Stop trying to track “at 04:12, can we lower the bed?” in a long-winded email. Use something like Frame.io or even just a shared Google Doc with timestamps. It forces the client to be specific and prevents the “it just feels a bit off” feedback that leads to nothing but wasted hours.
The Bottom Line
Put a hard number on it in the contract—three rounds of revisions is standard for a reason, and anything beyond that needs a new invoice attached to it.
Stop treating “small tweaks” like favors; if a client asks for a fifth pass because they “just want to see how it feels,” that’s a scope creep that costs you money.
Use a shared feedback document or a specific tool like Frame.io or even a simple Google Doc to centralize notes, so you aren’t chasing contradictory feedback through three different email threads.
## The Infinite Polish
“If you don’t bake a specific number of revision rounds into your initial agreement—say, two rounds of structural notes and one final polish—you aren’t just a producer anymore; you’re a permanent, unpaid intern to a client’s indecision.”
Nadine Okafor
Stop Polishing, Start Producing
At the end of the day, managing revisions isn’t about being difficult; it’s about being professional. You have to nail down your deliverables in the contract, keep the client in the loop while the edit is actually happening, and—most importantly—draw a hard line on how many times you are willing to reopen a project file. If you don’t, you aren’t a producer; you’re just an unpaid intern for a client’s indecision. It’s easy to let a project drift into a sixth or seventh round of “just one more tweak,” but that is how you lose your margin and, eventually, your sanity. You have to protect your time as fiercely as you protect your audio quality.
Look, the first few years of this job are a steep climb, and you’ll likely feel like you’re failing if you ever have to say “no” to a client. You won’t. In fact, clients usually respect a producer who knows exactly where the finish line is. Podcasting is a marathon of technical hurdles, guest cancellations, and quiet months, and you cannot afford to let a single project bleed your energy dry. Build your boundaries early, hold them steady, and then get back to the work that actually matters. The craft is hard enough without you making it harder on yourself.
