How to Say No to 'Unlimited Revisions' Without Sounding Difficult

"Unlimited revisions" is one of those phrases that sounds generous on a sales call and turns into a slow-motion disaster three weeks into a project, and if you've been freelance editing for more than a year you almost certainly have a story about the client who took "unlimited" literally and used it to request a fourteenth round of notes on a ninety-second video, notes that kept arriving right up until the deadline you'd already quoted to someone else. We hear this constantly from editors who come to PlayPause after a bad project: they offered unlimited revisions to win the job, felt too awkward to push back once the requests kept coming, and ended up working three or four times the hours they quoted for the exact same fee. The good news is that saying no to unlimited revisions doesn't require confrontation, it just requires the right language and the right moment to use it, and most of that moment is before you ever sign the contract.

Why Editors Say Yes to Unlimited in the First Place

At the end of the day, most editors don't offer unlimited revisions because they think it's good business, they offer it because a competing freelancer mentioned it in a proposal, or because saying "two rounds included" out loud on a discovery call feels like it might cost them the job. That fear is understandable, nobody wants to lose a client over what sounds like a small detail, but the math on unlimited revisions is brutal in practice: a project scoped for fifteen hours of work can easily balloon to thirty or forty once a client realizes there's no ceiling on how many times they can ask for "just one more tweak," and by the time you notice the pattern you're usually already several unpaid rounds deep with no clean way to introduce a boundary that wasn't there from the start.

Think about how this actually plays out on a real project: an editor quotes a flat $600 fee for a ninety second explainer video, mentally budgets around twelve hours of total work including two revision rounds, and offers unlimited revisions anyway because the client sounded a little hesitant on the discovery call. By round six, the editor has logged eighteen or nineteen hours against a project that only paid for twelve, and the notes coming in by that point are often smaller and more granular than the ones in round one, half second timing shifts and tiny color tweaks that keep the file open indefinitely instead of letting it close. That's the real mechanism behind the unlimited trap, it's rarely that any single round is unreasonable on its own, it's that the offer never built in a natural stopping point, so the project just keeps drifting instead of concluding on schedule.

What to Say on the Discovery Call, Before Anything Is Signed

The Reframe: Revisions Aren't Free, They're Priced In

The easiest way to avoid the unlimited trap is to never let it become the framing in the first place. When a prospective client asks about revisions, the answer isn't "how many do you want," it's "my packages include two rounds of revisions, which covers the vast majority of projects, and additional rounds are billed at my hourly rate." That single sentence does two things: it sets a real boundary, and it turns extra requests into a revenue opportunity instead of a favor you're expected to give away.

The Script for When a Client Pushes for "Unlimited" Anyway

Some clients will ask directly, especially if they've worked with editors who offered it before. Here's language that holds up without sounding difficult: "I don't do unlimited revisions, because in practice it ends up costing clients more, not less, since the project drags on and priorities shift. What I do instead is two structured rounds, which is enough for almost every project, plus a clear rate for anything beyond that if we need it." This works because it reframes the boundary as something that protects the client too, not just you, and that reframe genuinely lands with clients who've been burned by a slow, scope-creeping project before.

The Difference Between a Revision and a New Request

Part of what makes "unlimited" so dangerous is that it doesn't distinguish between a genuine revision, a small adjustment to something already agreed on, and a new creative direction disguised as feedback. A client asking you to trim two seconds off the intro is a revision. A client asking you to swap the entire music bed, re-order three scenes, and add a completely new graphics package "while you're in there" is a new request wearing a revision's clothes, and treating it as included work is how scope quietly doubles without anyone officially agreeing to it. We tell editors to draw this line explicitly in their proposal: revisions address existing choices, new requests introduce new ones, and only the first category counts against the included rounds. You know exactly what this looks like if you've ever gotten a "small note" that turned into rebuilding half the timeline.

Naming the Line Without Sounding Petty

You don't need a legal document to enforce this, you just need a sentence ready for the moment it comes up: "That's a great idea, and it's a bit outside what we scoped for the current rounds, so let's either swap it in for one of the existing notes or price it as an add-on, whichever works better for you." This keeps the tone collaborative while still protecting the boundary, and most clients take the swap option without any friction at all, because they usually didn't realize they'd crossed a line in the first place.

What Changes When the Relationship Is a Retainer, Not a Project

Everything above assumes a single scoped project with a defined end point, but a fair number of freelance editors also run retainer clients, the kind paying a flat monthly fee for a set volume of ongoing work, and "unlimited revisions" gets confused a lot more easily in that context because the client is already paying for continuity, not for a single deliverable. The honest answer here is that retainers should still have a revision structure, it just gets defined per deliverable inside the retainer rather than per project. If a retainer covers eight short videos a month, each individual video still gets its own two-round limit, the retainer fee buys you steady volume and a predictable relationship, not an unlimited well of notes on every single asset that goes out the door. Editors who skip this distinction are the ones who end up quietly doing four rounds on video three of eight because the client assumes the whole retainer is "unlimited" simply because the fee is recurring, when really recurring and unlimited were never the same promise in the first place.

Handling the Client Who's Already Mid-Project

If you're reading this because you're already three rounds deep into a project you scoped as unlimited, the fix is less about saying no cold and more about introducing structure retroactively. Something like: "I want to make sure round four actually nails it for you, so let's get very specific about what's changing this time," works well because it doesn't reject the request, it channels it into something bounded. From there, you can introduce a going-forward policy: "For anything past this round, I'll switch to billing extra rounds at my hourly rate, just so we're both clear on where things stand." Clients respond better to this than editors expect, mostly because most of them didn't realize the arrangement was open-ended in the first place, they just kept asking because nobody told them there was a limit. Say you quoted a project at $800 assuming two rounds, and you're already on round five with a sixth request sitting in the client's inbox waiting to be sent, the numbers make the case for you better than any script could, since you've already put in roughly two and a half times the revision work the fee covered and the client likely has no real sense that the count has crept that high.

• Acknowledge the request without immediately saying no
• Get specific about what "one more round" actually needs to fix
• Introduce a going-forward rate for anything beyond the agreed count
• Confirm the new terms in writing, even just a short email

Why This Conversation Gets Easier With a Real Process Behind It

Editors who push back successfully on unlimited revisions almost always have something structural backing them up, whether that's a documented revision count from intake or a clean record of how many rounds have already happened. This is exactly the ground we cover in the client onboarding checklist that prevents scope creep, because "no" is a much easier word to say when you can point to a number both sides agreed to at the start rather than relying purely on your own memory of what felt fair. It also helps to have your revision history tracked cleanly, which is the whole subject of how freelance editors track billable revision hours across multiple clients, because a client is far less likely to argue with "we're on round five against an agreement for two" when you can show them exactly what those five rounds included.

Making the Boundary Visible Inside the Actual Review Process

One reason "unlimited" creeps in so easily is that most email- and file-based feedback loops have no visible round structure at all, so a client genuinely can't tell whether they're on round one or round six, they just keep replying to the same thread. When revisions run through a proper approvals process instead, each round is a distinct, visible stage the client can see, which does a lot of the boundary-setting work for you without you having to say anything confrontational at all. This is part of why solo freelance editors lean on structured video proofing tools rather than email, because the structure itself communicates "this is round two of two" far more clearly than a verbal reminder ever could.

As No Film School has covered repeatedly in pieces on the business side of editing, the freelancers who last in this industry are the ones who treat their time as a finite, priced resource rather than something a client's enthusiasm gets to redefine mid-project. Unlimited revisions sounds like hospitality. In practice it's just unpriced labor, and the sooner an editor makes peace with charging for it, the sooner the resentment that builds up around scope-heavy clients tends to disappear entirely.

Set the Boundary Before You Need It

Saying no to unlimited revisions isn't about being difficult, it's about pricing your time honestly and giving clients a structure that actually serves them too, since a project with a real revision limit tends to wrap faster and cleaner than one that drags on indefinitely. State your included rounds up front, price anything beyond that clearly, and run your feedback somewhere the round count is visible to everyone, not just you. See how PlayPause makes revision rounds and approvals visible on every project so the boundary sets itself instead of you having to defend it every single time.