What to say when a client asks for one more revision

“Just one quick thing.” The email arrives on a Friday afternoon.

You’ve delivered two revision rounds. The contract says two. But it’s a small change, they say — shouldn’t take long.

You fix it. They send another small thing. Then a third. By this point the project has had four rounds of revisions, none of them billed, and the client has learned that your revision limit is a suggestion.

Why revision limits stop working

The limit didn’t fail at the fourth request. It failed at the first one you absorbed without comment.

Clients aren’t trying to exploit you. They’re testing — consciously or not — whether the limit is real. When the first extra request disappears silently, the boundary disappears with it. Each subsequent request becomes progressively easier to make because the pattern is already established.

The other failure mode is vague language in the contract. “Two rounds of revisions” means nothing without a definition of what a round is. If a round is “any number of small requests sent separately over two weeks,” you have unlimited revisions with extra steps.

What counts as a revision round

Define it before the project starts.

The clearest version: one revision round = one consolidated document of feedback, submitted in a single email or shared document, responded to within a defined timeframe.

That definition does three things. It puts the responsibility for consolidating feedback on the client. It makes it obvious when a new round starts. And it closes the “just one quick thing” channel — because a quick thing sent separately still counts against the revision total.

Put this in your scope of work, not buried in general terms. Walk through it on the kick-off call. “We have two revision rounds — I define a round as one consolidated set of feedback. That way you can send everything at once rather than in pieces, and nothing gets missed.”

What to say when it happens anyway

The conversation doesn’t need to be confrontational. It needs to be clear.

When the third request arrives:

“Happy to incorporate this. We’ve used both revision rounds included in the project — this would be an additional round. I can quote that at €[X], or if you’d prefer, we can hold this alongside anything else that comes up and address them all together in one new round.”

Two options, both reasonable. No accusation, no lecture. The key phrase is “we’ve used both revision rounds” — past tense, factual, no blame attached.

If the client agrees to an additional round, confirm it in writing before you start. A change order doesn’t need to be formal — one line stating what’s included and the agreed price is enough.

If the extra request is genuinely tiny — a word change, a colour swap — you can absorb it once. But absorb it silently and the pattern resets. The better move: do it, and mention it. “Done — this one was small so I’ve included it, but further changes would go on a new round.”

That sentence does something the silent fix doesn’t: it names the limit again without making it a confrontation.

How to price additional rounds upfront

The easiest way to avoid an awkward price conversation is to have it before the project starts.

In the proposal or contract, add one line: “Additional revision rounds: €[X] per round.” The price doesn’t need to be high — it needs to exist. When a client has already seen the rate, “this would be an additional round at €[X]” is a reference to something they already agreed to, not a surprise.

For longer projects, some freelancers price revision rounds as a percentage of the total fee — typically 5–10% per round. For shorter projects, a flat rate works better.

Setting the price upfront also changes how clients use revision rounds. When extra rounds are free, clients use them carelessly. When they have a price, feedback arrives more consolidated, more considered, and often more useful.

The framing that makes it normal

The argument for revision limits isn’t “I don’t want to do extra work.” It’s that unlimited revisions make the project worse.

When clients know they have two rounds, they consolidate feedback. They think before they send. They involve the right people before the document goes out. Projects with defined revision limits tend to produce cleaner output because the client’s review process becomes more deliberate.

Unlimited revisions create the opposite. Feedback trickles in over weeks. Each small request generates a new back-and-forth. The project never quite closes. That kind of scope creep isn’t always a new feature — sometimes it’s twelve “just one more” requests that never find an end.

When you frame the limit as a quality mechanism rather than a protection clause, it lands differently. “I use revision rounds so feedback arrives consolidated and the project moves forward cleanly” is a better explanation than “my contract says two rounds.”

The conversation you’re avoiding isn’t the uncomfortable one

Freelancers absorb extra revisions because the alternative feels awkward. But the conversation you avoid when you absorb silently doesn’t disappear — it resurfaces at invoice time, when the gap between the hours worked and the hours billed is hardest to explain.

One clear exchange at the third request: “We’ve used both revision rounds — this would be an additional one at €[X].” That’s the uncomfortable conversation. It takes thirty seconds. The alternative is a project that runs for three extra weeks and gets billed at two.

When extra revision rounds happen without extra billing, the gap shows up clearly in your time records. Timescanner reads your calendar and shows exactly how many hours went into each project — so you can see what extra rounds actually cost, and price them accurately next time. Works with any iCal-compatible calendar.