Every agency owner and freelancer has had this internal debate:
"I should set revision limits. But what if the client gets upset? What if they think I don't care about quality? What if they go to a competitor who offers 'unlimited revisions'?"
So you avoid the conversation. You don't put limits in the contract. And six revision rounds later, you're working for free and resenting a client who has no idea they've done anything wrong.
Let's fix this once and for all. I'll show you exactly how to set revision limits that protect your margins without making clients feel like you're nickel-and-diming them.
Why you need revision limits (the honest version)
Revision limits aren't about being stingy. They're about two things:
1. Protecting your profitability. When you quote a project, you estimate a certain number of hours. If the client can request unlimited changes, your estimate is meaningless. You're essentially signing a blank check for your own time.
2. Producing better work faster. This one is counterintuitive, but it's true. When clients know they have a limited number of revision rounds, they give more thoughtful, consolidated feedback. They loop in all stakeholders at once instead of sending feedback in drips. They think before they speak.
Unlimited revisions don't lead to better outcomes. They lead to indecisive feedback cycles where the client keeps tweaking without ever committing.
For a deeper look at how feedback cycles erode profit, read how the feedback loop is killing your margins.
How many revisions should you include?
Here's the guideline most successful agencies follow:
| Deliverable type | Recommended revision rounds |
|---|---|
| Logo design | 2–3 rounds |
| Website design | 2 rounds per page/section |
| Brand identity package | 2–3 rounds |
| Social media content | 1–2 rounds |
| Video editing | 2 rounds (rough cut + fine cut) |
| Copywriting | 2 rounds |
| Print design | 2 rounds |
A "round" should be defined as one consolidated batch of feedback from all stakeholders. Not three separate emails from three different people over two weeks. One round = one submission of feedback, incorporating everyone's input.
This distinction matters. Without it, a client will argue that each email is a "minor tweak" rather than a formal revision round, and your limits become unenforceable.
How to word revision limits in your contract
Here's the language that works. Feel free to adapt it:
Template 1: Simple and direct
Revisions. This project includes [2] rounds of revisions. A revision round is defined as one consolidated set of feedback from the Client, submitted within [3] business days of deliverable presentation. Additional revision rounds beyond those included will be billed at [$X] per round or [$Y] per hour.
Template 2: More detailed (for larger projects)
Revisions and Amendments. The project scope includes [2] rounds of design revisions per phase. Each revision round consists of one consolidated set of written feedback from all Client stakeholders, submitted via [the project portal / email] within [5] business days of deliverable review.
Feedback received after the stated review period, or feedback submitted in multiple separate communications rather than one consolidated set, may be treated as an additional revision round at the Agency's discretion.
Additional revision rounds beyond those specified will be invoiced at [$X per round / $Y per hour], payable within [14] days.
Changes to the approved project direction, creative brief, or scope of deliverables are not considered revisions and will be quoted separately as a change order.
Template 3: Friendly freelancer version
I include two rounds of revisions with every project. In my experience, this is more than enough to get the work exactly where you want it.
A revision round means one batch of feedback covering everything you'd like changed. (Tip: get all stakeholders to review before sending — this way you don't use a round on conflicting feedback!)
If you need additional rounds, I'm happy to help at [$X] per round. I'll always let you know before any extra charges apply.
The friendly version works especially well for freelancers who don't want to sound overly corporate but still need clear boundaries.
How to present limits without sounding difficult
The way you present revision limits matters as much as the limits themselves. Here are the framing techniques that work:
Frame it as "included" not "limited"
Don't say: "You are limited to 2 rounds of revisions."
Do say: "Your project includes 2 rounds of revisions — which is more than enough based on our experience with similar projects."
The word "includes" implies generosity. The word "limited" implies restriction. Same policy, completely different perception.
Normalize it with a benchmark
"Most of our projects are finalized within 1–2 revision rounds. We include 2 rounds as standard, and if you need more, we're flexible."
This tells the client that your limits are typical, not unusual, and that you're not rigid about it. Most clients will never push past 2 rounds once they know the norm.
Explain the benefit to them
"We structure our revision process to get you the best result as efficiently as possible. By consolidating feedback into rounds, we ensure nothing gets lost and every change is addressed together."
This reframes limits as a quality measure, not a cost-saving tactic.
Enforcing limits without damaging the relationship
Setting limits in a contract is one thing. Enforcing them when a client pushes past them is another. Here's how to handle the common situations:
"Just one more small change"
The single most common boundary test. And yes, sometimes it genuinely is one small change. The trick is distinguishing between:
- A legitimate minor fix (typo, color tweak) — just do it, don't make a fuss
- A significant change disguised as "small" (reworking a layout, changing the creative direction) — this is a new round
When it's the latter, respond warmly: "Happy to make that change! Since we've used our included revision rounds, this would fall under additional revisions at [$X]. Want me to go ahead?"
No drama. No lecture. Just a clear, professional statement.
Stakeholder feedback arriving in waves
The client sends feedback Monday. Then their partner sends feedback Wednesday. Then the CEO chimes in Friday.
Address this proactively: "To make sure we address everyone's feedback in one round, can you collect all stakeholder input and send it together? That way we can make all the changes at once instead of going back and forth."
This is where a structured review tool helps enormously. With TryApprove, all stakeholders review in the same portal, and you can see who's reviewed and who hasn't before starting a revision round.
The client who says "but I'm not happy yet"
This is the hardest conversation. But here's the thing: if a client has gone through 3 revision rounds and still isn't happy, the issue usually isn't the revisions. It's one of these:
- The brief wasn't clear enough (a discovery/scoping problem)
- The client doesn't know what they want (a decision-making problem)
- There's a stakeholder conflict (an internal politics problem)
None of these are solved by doing more revisions for free. They're solved by having a conversation about what's really going on and potentially rescoping the project.
Making approvals formal
The single best thing you can do to enforce revision limits naturally is to make approval a formal, documented action.
When the client reviews a deliverable and clicks an "Approve" button — not just says "looks good" in an email — two things happen:
- There's an unambiguous record that the work was approved
- The client takes the decision more seriously
This is why we built the one-click approval system into TryApprove. When approval is a button rather than a vague email response, clients review more carefully and approve more confidently.
Start with your next project
You don't need to retroactively renegotiate existing contracts. Just make two changes for your next project:
- Add revision limit language to your proposal or contract (use the templates above)
- Use a review tool that creates formal approval moments — TryApprove's free plan works perfectly for this
Two simple changes. Your margins will improve, your projects will finish faster, and your clients will actually respect you more for having a professional process.
The agencies that set clear boundaries don't lose clients. They attract better ones.