Unlimited Revisions Clause: How to Push Back
“Unlimited revisions” sounds like great service. On a fixed fee, it is an open-ended commitment with no defined end — and no extra pay for the extra rounds.
What this clause looks like
An unlimited revisions clause almost never uses that exact phrase. It shows up dressed as generosity — a line meant to sound like great client service, buried in the scope section where nobody expects a payment term to hide. A typical version reads:
Two words do all the damage: "until" and "satisfied." There is no number, no round count, and no definition of what satisfaction means or who decides when it's been reached. The clause has no exit condition. On a fixed fee, that means the project is not actually fixed — it ends whenever the client says it does, and every hour between now and then is unpaid.
Why it costs you money
The damage is easiest to see with real numbers. Say you quote a $3,000 flat fee for a brand identity package, budgeting for two rounds of feedback based on your usual process — roughly 30 hours of work, or $100/hour effectively. The contract says "unlimited revisions until satisfied." Round one goes fine. Round two, the client changes their mind about the direction entirely. Round three brings in a business partner with different opinions. By round seven, three months have passed, you've logged 58 hours, and your effective rate has fallen to $52/hour — before accounting for the opportunity cost of the other clients you turned down to stay available for this one.
The same pattern shows up in web development, copywriting, and video editing, just with different units: not "rounds" but "another look," "one more pass," or "just a few small tweaks" that turn out not to be small. The clause doesn't just cost you the extra hours directly worked — it costs you the hours you can't bill to anyone else because you're perpetually on call for a project that was supposed to have ended weeks ago.
There's a second, quieter cost: scope creep hides inside "revisions." A request to fix a typo is a revision. A request to redesign the entire homepage from scratch, framed as "just a revision to what we discussed," is scope creep wearing a revision's clothes — and an unlimited revisions clause gives the client no reason to ever call it by its real name.
Where it hides
Once you know the pattern, it's easy to spot in the wild. Watch for any of these phrasings, all of which mean the same thing as "unlimited":
- "Revisions until Client is satisfied" — no cap, subjective trigger
- "As many rounds of revisions as needed" — "needed" is defined by the client, not you
- "Reasonable revisions" with no number attached — "reasonable" has no fixed meaning until a dispute forces one
- "Unlimited minor changes" — "minor" is doing a lot of undefined work here too
- Silence — no revision clause at all defaults to the same result, because there's nothing stopping the client from asking for round twelve
That last one matters: a contract that says nothing about revisions is not neutral. It's the same trap with one fewer sentence, which is why FairClause's missing-protection audit flags a contract with no stated revision cap even when it doesn't contain an explicit "unlimited" clause.
The counter-language to send
You don't need to remove the idea of revisions — clients reasonably expect some feedback loop, and refusing one entirely reads as inflexible. What you need is a number and a price for what comes after it. This is the base language FairClause's free check suggests when it flags this clause, adapted to your project:
Fill in $XXX with your real hourly rate — even if the project itself is fixed-fee, having a stated hourly rate for overflow work gives both sides a concrete number to react to instead of an argument about what's fair. Two rounds is a reasonable default for most freelance work; adjust up for genuinely iterative work like brand identity or down for narrowly scoped technical deliverables where the acceptance criteria are objective (does the script run, does the API return the right response).
If a client pushes back on capping revisions at all, the easiest concession is to keep the number generous but keep the price attached — three or four rounds included, with the overflow rate still spelled out. What you're negotiating is rarely the number itself; it's whether there's a number at all.
What actually counts as "one round"
A revision cap is only as good as its definition of a round, so define it in the same clause or the section next to it. The version that holds up in practice: a round is Client's consolidated feedback on a single version of the deliverable, submitted together, with Contractor implementing the changes and returning one updated version. Feedback that trickles in over two weeks in five separate emails is still one round if it's responding to the same delivered version — this stops "just one more small thing" emails from silently multiplying your round count without ever formally starting round three.
When to walk away
Most clients accept a revision cap without friction — it's boilerplate they never specifically chose, not a hill they're prepared to defend. Treat continued resistance as information. If a client insists on literal "unlimited revisions until fully satisfied" and won't move off that wording after you've explained why it's a problem for you, that's usually a preview of how the whole engagement will go: scope that never quite closes, and a client who doesn't see your time as something with a cost. It's reasonable to walk away from that relationship before you've sunk any hours into it, and far cheaper than discovering it on round nine.
A middle path exists too: if you can't get a number, at minimum get a milestone. "Revisions accepted until the Homepage Design milestone is signed off in writing" isn't as strong as a hard round count, but it at least gives the relationship a formal end point instead of an open-ended vibe.
Frequently asked questions
Is any revision cap normal, or does it look cheap to ask for one?
It's standard practice, not a red flag on your side. Agencies, studios, and solo freelancers across every discipline cap revisions — it's how professional service work is priced. Clients who've worked with freelancers before expect to see a number; the ones who push back usually haven't hired a freelancer with a real contract before.
What if the client's own template already has a specific revision count?
Then you're in good shape — read it carefully rather than assuming it's fair. Check that the round count matches your actual process, that overflow work has a stated rate rather than being silently unpaid, and that "round" is defined the way described above. A specific number that's too low (one round) is still worth negotiating up.
Should I cap total hours instead of rounds?
Either works, and for less structured engagements — ongoing consulting, retainer-style work — an hours cap can be clearer than a round count. For discrete deliverables (a logo, a landing page, a video edit) rounds are usually easier for both sides to track without timesheets.
What happens if I hit the cap and the client still isn't happy?
The cap doesn't mean you stop caring about a good outcome — it means further work is billed. In practice, naming the overflow rate is usually what ends the loop: clients who were treating feedback rounds as free suddenly get specific about what actually needs fixing once there's a price attached to being vague.
Does an unlimited revisions clause ever favor the freelancer?
Only if you're deliberately pricing a retainer or subscription-style engagement where ongoing changes are the product itself — think a monthly design-subscription service. Even then, "unlimited" should come with a defined scope per request and a monthly cap on request volume, not literally unlimited effort for a fixed monthly fee.
Check your own contract first. FairClause reads it in your browser, names the clauses that hurt you, and drafts the counter-language for each one. Nothing is uploaded.
Also see: 21 contract red flags freelancers shouldn't sign, freelance non-compete: should you sign it?, pay-when-paid clause: why it's risky, kill fee clauses: what's fair, and how to negotiate a freelance contract.
FairClause is automated pattern analysis and drafting help, not a law firm and not legal advice. For anything binding, talk to a licensed lawyer in your jurisdiction.